Breaking News
Design How-To

Freescale preps IoT attack with tiny MCU

2/26/2013 08:21 PM EST
16 comments
NO RATINGS
More Related Links
View Comments: Newest First | Oldest First | Threaded View
Page 1 / 2   >   >>
powell270
User Rank
Author
re: Freescale preps IoT attack with tiny MCU
powell270   3/7/2013 8:21:16 PM
NO RATINGS
Why 32 over 16 or 8 bit? Many reasons... First of all, ARM 32 bit cores scale well from small M-class up to high performance A-class - one can re-use applications written for M on higher performance cores when more performance is needed (i.e. moving from sensors more into the cloud for IOT). Another reason is that memory is costly and it "usually" requires fewer 32 bit instructions to accomplish a given task than if one used 8 or 16 bit instructions (ARM's M0/M0+, by the way uses the thumb (16 bit) instruction set)) thus requiring less memory for code storage. Performance is also typically improved using 32 bit devices (larger registers, greater addressing range). More power may be consumed switching 32 bit registers and supporting a 32bit pipe-line but, again, as fewer instructions may be executed compared to 8/16 bit, one is using more energy but over shorter time.

y_sasaki
User Rank
Author
re: Freescale preps IoT attack with tiny MCU
y_sasaki   2/28/2013 8:00:37 PM
NO RATINGS
There's ongoing discussion what wireless architecture will be "the one" for (hopefully) uprising IoT market. Low-power WiFi, Bluetooth LE, 802.15.4 Zigbee are leading the market, but there's also more than a dozen of so-called "optimized for IoT" architectures (ANT+, Z-Wave, EnOcean, MyraNet, DASH7, WirelessHART... you name it). Many uses 2.4GHz but some uses sub-GHz band. Freescale offers two types of "Kinetis W" series radio-integrated MCUs, KW01 with proprietary sub-GHz radio and KW20 with 2.4GHz 802.15.4. As long as I know, there's no Freescale Bluetooth (LE) chip has been released yet. It is interesting to see how they can do well with "multi-mode radio" chip, and how do they marketing discrete radio chip versus KW series radio-integrated SoCs.

JohnM555
User Rank
Author
re: Freescale preps IoT attack with tiny MCU
JohnM555   2/28/2013 5:02:19 PM
NO RATINGS
@daleste, your question might have a very simple response that is not about complex architectural analysis on 8/16/32 bits. Per ARM's own claim, the M0 core is 32-bit and is the smallest ARM core available. ARM jumped a bit over developing 16-bit cores.

yazhouren
User Rank
Author
re: Freescale preps IoT attack with tiny MCU
yazhouren   2/28/2013 8:59:17 AM
NO RATINGS
so, some things need more power MCU.

yazhouren
User Rank
Author
re: Freescale preps IoT attack with tiny MCU
yazhouren   2/28/2013 8:58:34 AM
NO RATINGS
A good chip! I like it. but for IOT, things would be connected to each other.

docdivakar
User Rank
Author
re: Freescale preps IoT attack with tiny MCU
docdivakar   2/28/2013 7:45:25 AM
NO RATINGS
Rick, you are hitting on one of the hurdles M2M faces in the existing (brown field) and new (green field) markets. Industrial automation (SCADA, CAN) have many applications but penetration there has been a tough sell for wireless M2M nodes. Legacy implementations from the likes of GE, Rockwell, are not going to be displaced any time soon. Naturally some of the attention has been turned toward medical monitoring where many new startups have sprung lately in the Silicon Valley (I think I introduced one of them to you at DesignCon 2013). I hope 2013 is the year a better picture emerges for IoT. There is a lot that is needed in software solutions like analytics and prognostics. MP Divakar

docdivakar
User Rank
Author
re: Freescale preps IoT attack with tiny MCU
docdivakar   2/28/2013 7:34:02 AM
NO RATINGS
The issue of power consumption is a tricky one and it depends on what one employs as a system, whether using the one above or others like i.MX283 also from Freescale. If the IoT is deployed / configured using ZigBee, the battery life is in years; in days for Bluetooth and in hours for WiFi! Typical WiFi 802.11/a/b/g/n versions will restrict to nodes in IoT within a 30m reach node-to-node; one can always have router nodes in the mesh and extend its reach but it is impractical for outdoor & low data applications (like weather / infrastructure health monitoring). For ZigBee, Freescale has MC1322x SoC which I believe consumes sub mW power in sleep mode /quiescent state. MP Divakar

adithya1107
User Rank
Author
re: Freescale preps IoT attack with tiny MCU
adithya1107   2/28/2013 3:08:03 AM
NO RATINGS
In India IoT market is currently growing well and most of the chipsets we use here are either from TI or from chinese vendors .... Freescale does not have potential network in India and their support quality is also very low .... It's very doubtful if this chpset will get considerable amount of Indian market .....

rick merritt
User Rank
Author
re: Freescale preps IoT attack with tiny MCU
rick merritt   2/27/2013 11:21:21 PM
NO RATINGS
The hard thing about IoT, one Berkeley researcher told me recently, is that many of the systems address Luddite markets where they are replacing mechanical or no systems at all--a hard sell, and a more fragmented market than even the so-called catch-all embedded sector. This will take time and hard work.

Roger3
User Rank
Author
re: Freescale preps IoT attack with tiny MCU
Roger3   2/27/2013 10:03:52 PM
NO RATINGS
Peter, 32K ??? Cortex M0+ ???? IOT ???? Does these pieces fit together ???? Apparently this chip will be a stillbirth case ...

Page 1 / 2   >   >>
Most Recent Comments
michigan0
 
SteveHarris0
 
realjjj
 
SteveHarris0
 
SteveHarris0
 
VicVat
 
Les_Slater
 
SSDWEM
 
witeken
Most Recent Messages
9/25/2016
4:48:30 PM
michigan0 Sang Kim First, 28nm bulk is in volume manufacturing for several years by the major semiconductor companies but not 28nm FDSOI today yet. Why not? Simply because unlike 28nm bulk the LDD(Lightly Doped Drain) to minimize hot carrier generation can't be implemented in 28nm FDSOI. Furthermore, hot carrier reliability becomes worse with scaling, That is the major reason why 28nm FDSOI is not manufacturable today and will not be. Second, how can you suppress the leakage currents from such ultra short 7nm due to the short channel effects? How thin SOI thickness is required to prevent punch-through of un-dopped 7nm FDSOI? Possibly less than 4nm. Depositing such an ultra thin film less then 4nm filum uniformly and reliably over 12" wafers at the manufacturing line is extremely difficult or not even manufacturable. If not manufacturable, the 7nm FDSOI debate is over!Third, what happens when hot carriers are generated near the drain at normal operation of 7nm FDSOI? Electrons go to the positively biased drain with no harm but where the holes to go? The holes can't go to the substrate because of the thin BOX layer. Some holes may become trapped at the BOX layer causing Vt shift. However, the vast majority of holes drift through the the un-dopped SOI channel toward the N+Source,...

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)
Like Us on Facebook
EE Times on Twitter
EE Times Twitter Feed