I have no idea how anyone keeps up
-
I've been bare metalling an ARM Cortex A, which while not quite voiding the warranty, is operating it off book, to say the least. It's not easy, but I thought I needed it for a project. Not so. Turns out NXP released a 1GHz M class monster last year, buried in their extensive product line with the cryptic title of mimxrt1176 The eval board is expensive at $200 USD but it's a lifeline. I can code the M class without constantly having to leave the beaten path. What I don't know, and what I've always had a hard time with is picking products. How does anyone in embedded keep up with all of these ARM implementations, even among a particular vendor? Between availability, specs, and just sheer amount of chip variants it seems an almost impossible task.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
Hyper proliferation might be IOT's Achilles heal if it's not clear which rabbit to chase.
-
Hyper proliferation might be IOT's Achilles heal if it's not clear which rabbit to chase.
Seems it's a problem with embedded in general. :~
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
Seems it's a problem with embedded in general. :~
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
And that might be the final frontier too.
-
I've been bare metalling an ARM Cortex A, which while not quite voiding the warranty, is operating it off book, to say the least. It's not easy, but I thought I needed it for a project. Not so. Turns out NXP released a 1GHz M class monster last year, buried in their extensive product line with the cryptic title of mimxrt1176 The eval board is expensive at $200 USD but it's a lifeline. I can code the M class without constantly having to leave the beaten path. What I don't know, and what I've always had a hard time with is picking products. How does anyone in embedded keep up with all of these ARM implementations, even among a particular vendor? Between availability, specs, and just sheer amount of chip variants it seems an almost impossible task.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
"The great thing about standards is there are so many to choose from"
cheers Chris Maunder
-
"The great thing about standards is there are so many to choose from"
cheers Chris Maunder
Obligatory [xkcd: Standards](https://xkcd.com/927/)
-
Obligatory [xkcd: Standards](https://xkcd.com/927/)
Wow - I was gonna give the same type of answer but you and XKCD beat me to it.
-
I've been bare metalling an ARM Cortex A, which while not quite voiding the warranty, is operating it off book, to say the least. It's not easy, but I thought I needed it for a project. Not so. Turns out NXP released a 1GHz M class monster last year, buried in their extensive product line with the cryptic title of mimxrt1176 The eval board is expensive at $200 USD but it's a lifeline. I can code the M class without constantly having to leave the beaten path. What I don't know, and what I've always had a hard time with is picking products. How does anyone in embedded keep up with all of these ARM implementations, even among a particular vendor? Between availability, specs, and just sheer amount of chip variants it seems an almost impossible task.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
Being an old guy, I reminisce about the days when the choice was between the Intel 8051 or the Motorola 6805 ;P Then the MSP430 and the PIC, then ARM came. Now the choices are just too much. Soon time to retire.
-
I've been bare metalling an ARM Cortex A, which while not quite voiding the warranty, is operating it off book, to say the least. It's not easy, but I thought I needed it for a project. Not so. Turns out NXP released a 1GHz M class monster last year, buried in their extensive product line with the cryptic title of mimxrt1176 The eval board is expensive at $200 USD but it's a lifeline. I can code the M class without constantly having to leave the beaten path. What I don't know, and what I've always had a hard time with is picking products. How does anyone in embedded keep up with all of these ARM implementations, even among a particular vendor? Between availability, specs, and just sheer amount of chip variants it seems an almost impossible task.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
You can't keep up!! I did embedded for my whole career and when I had input on the processor selection, I always opted for the older chips that would meet the requirements. This always gave me lots of options in regards to sample code and third party libraries (infrequently needed). I'd would read about the newer chips but rarely used them until they were a year or two old. In regards to ARM, I only did 1 ARM project (mostly did TI DSPs) and I ended up using an ARM7TDMI. There were many more powerful options available but why use a more expensive processor when a cheaper well known processor would handle the job. Turned out I was easily able to run the processor at half speed and still get the job done.
-
You can't keep up!! I did embedded for my whole career and when I had input on the processor selection, I always opted for the older chips that would meet the requirements. This always gave me lots of options in regards to sample code and third party libraries (infrequently needed). I'd would read about the newer chips but rarely used them until they were a year or two old. In regards to ARM, I only did 1 ARM project (mostly did TI DSPs) and I ended up using an ARM7TDMI. There were many more powerful options available but why use a more expensive processor when a cheaper well known processor would handle the job. Turned out I was easily able to run the processor at half speed and still get the job done.
I often find I have trouble sourcing older chips.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
I often find I have trouble sourcing older chips.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
Yep, that can be a problem too. Wasn't really a problem when I went with ARM7TDMI, there were a ton of manufactures at the time. All the TI DSPs we used were obviously single sourced and the age of the product line could cause a problem. We had a contact at one of the distributors that seemed to have good info on how popular the TI DSPs were. We'd always try to get a processor that was going to have a long life (just an educated guess).
-
Wow - I was gonna give the same type of answer but you and XKCD beat me to it.