Breaking News
Comments
Newest First | Oldest First | Threaded View
<<   <   Page 2 / 2
Ramifr
User Rank
Rookie
re: Freescale preps IoT attack with tiny MCU
Ramifr   2/27/2013 4:58:23 PM
NO RATINGS
What would be typical power consumption per minute assuming transmission of one byte of information once every minute.

ZackS
User Rank
Rookie
re: Freescale preps IoT attack with tiny MCU
ZackS   2/27/2013 4:12:13 PM
NO RATINGS
Power consumption is a very important factor in IoT's wireless devices...is this information available?

Jack.L
User Rank
CEO
re: Freescale preps IoT attack with tiny MCU
Jack.L   2/27/2013 2:14:16 PM
NO RATINGS
If you were designing a single product for today, then 8 or 16 bit may be fine. If you are starting out in the architectural decision stage of a project targeting Internet connectivity of some sort, then would you really want to have the potential to be hobbled by an 8 or 16 bit architecture? Comparatively, a 16 bit architecture is going to offer limited code advantage over 32 bit ARM and with expected die shrinks over time, that pretty much goes away. With 8 bits you will be quickly running into performance issues not to mention limited off the shelf support in terms of software IP (stacks, etc.) Add in potential time to market advantages from common tool chains and you have what is likely the best architecture for the targeted market.

pica0
User Rank
Rookie
re: Freescale preps IoT attack with tiny MCU
pica0   2/27/2013 10:33:49 AM
NO RATINGS
In my opinion " Why does it need ... ?" is the wrong question. I prefer the "Is it more economical to ... ?" pattern. One big cost driver here in Europe and I think also in the USA and Japan are human resources. The big human resource specific advantage of the ARM eco system is, ARM M*, R* and A* all share the same ISA concepts and the same tool chain. As a result teaching/learning efforts are minimized.

chanj0
User Rank
CEO
re: Freescale preps IoT attack with tiny MCU
chanj0   2/27/2013 6:48:40 AM
NO RATINGS
I'm very interested in knowing the power consumption and more importantly, the operating condition. 32kB flash and 4kB SRAM do not sound a lot. I've the same thought as Daleste. For the application areas mentioned in the article, I feel like 16bits might very much be enough.

daleste
User Rank
CEO
re: Freescale preps IoT attack with tiny MCU
daleste   2/27/2013 3:47:05 AM
NO RATINGS
Interesting. Why does it need to be a 32 bit MCU for IoT? Wouldn't 16 bit do, or even 8 bit?

<<   <   Page 2 / 2


EE Life
Frankenstein's Fix, Teardowns, Sideshows, Design Contests, Reader Content & More
Max Maxfield

Feast Your Orbs on My Jiggly Exercise Machine
Max Maxfield
46 comments
Last weekend, I was chatting with my mother on the phone. She's all excited that I'm coming over to visit for a week in November. "I'll be seeing you in only seven weeks," she trilled ...

Glen Chenier

Missing Datasheet Details Can Cause Problems
Glen Chenier
3 comments
It is often said that "the devil is in the details." All too often those details are hidden deep within a datasheet, where you can easily overlook them. When a datasheet reference circuit ...

David Blaza

RadioShack: The End Is Nigh!
David Blaza
120 comments
I'm feeling a little nostalgic today as I read about what looks like the imminent demise of RadioShack, at least as we currently know it. An old ubiquitous cartoon image popped into my ...

Larry Desjardin

Engineers Should Study Finance: 5 Reasons Why
Larry Desjardin
46 comments
I'm a big proponent of engineers learning financial basics. Why? Because engineers are making decisions all the time, in multiple ways. Having a good financial understanding guides these ...

Flash Poll
Top Comments of the Week
Like Us on Facebook
EE Times on Twitter
EE Times Twitter Feed

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)