[TriEmbed] M0 vs 32u4

Pete Soper pete at soper.us
Wed Oct 11 17:32:38 CDT 2017


This reminded me to dig up your repo and add it to the meeting archive 
<http://triembed.org/blog/meetings/triembed-presentation-archive/> and 
meeting recap post.
-Pete


On 10/11/2017 01:09 PM, Alex Davis via TriEmbed wrote:
>> If the goal is to share this with the typical population of enthusiasts
>> out there the 32u4 seems like the better choice, and it's too simple to
>> be hard to wake up. :-) I've been working on a very tiny clock/calendar
>> that you could slap alongside the MCU (the clock package has a crystal
>> inside and it and a schottky diode for battery or capacitor backup
>> together are smaller than the 32u4 chip).
>>
>> -Pete
> I agree - I'm pretty familiar with 32u4. Maybe I'll buy one of each
> (this is how the parts bin fills back up).
>
> I want to keep it as light as possible as a wearable. I also want to use
> the OLED featherwing, as it provides buttons along with a display. It
> would be nice to view events on the screen with a timestamp for the
> doctor's office.
>
> I'm also going to try a LIS3DH, as it has "tap detection" in the
> hardware and library support, which might work better. I suspect, in any
> event, getting my particular event wakeup correct is going to be a
> struggle.
>
> Oh BTW, I found the source of the glitch/sec stuff in my EDF data: a
> misunderstanding of for loop statements in python, ie: not 0 to 99 but 0
> to 100. The source has been updated on my git repo if you want to pull
> it.
>
> Alex
>
> _______________________________________________
> Triangle, NC Embedded Computing mailing list
> TriEmbed at triembed.org
> http://mail.triembed.org/mailman/listinfo/triembed_triembed.org
> TriEmbed web site: http://TriEmbed.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.triembed.org/pipermail/triembed_triembed.org/attachments/20171011/42982f5d/attachment.htm>


More information about the TriEmbed mailing list