Micro-controllers are at the core of most embedded systems, but working with them isn’t always smooth. From confusing datasheets to fragmented tool-chains, even experienced engineers can hit roadblocks. This month, we want to know:
What micro-controllers are you currently using? (and why that one?)
It's been interesting to look at the replies so far.
I do design work with small embedded processors both commercially and for entertainment.
Most of my designs are based on ARM Cortex micros from ST.
I sometimes buy dev boards but often don't use them at all because I design my own boards. The dev board is insurance in case my own design won't work and I need a functional board in a hurry as a reference.
While its true that for some purposes I could get away with and 8 bit micro the money saved is trivial compared with the design time and prototype parts costs. If the design will be made in large numbers a non ARM micro might be a good choice but I haven't had a commercial project where that has been the case for a long time.
I have used ARM micros from Giga Devices and NXP but I much prefer the ST range.
One of the nicest modern ARM micros is the STM32U575 - floating point, 160MHz clock, 784kRAM, 1 or 2Mbyte FLASH, Cordic Processor, Filter accelerator, 14 bit ADC and loads of other stuff. 48 pin LQFP if you like (bigger packages are available), very low power. About £5 for one.
Having mentioned the STM32U574 family, my current non commercial project is based on an ST32G0B1, slower and cheaper. It has enough 5V tolerant IO to be able to interface with a 5V LCD display while the rest of the logic and the processor use 3.3V.
The board plugs onto the back of the display. This is one I used to check the 5V LCD interface so it didn't get a fancy audio chip to blow up - although as things turned out it would have been OK. It can work with either a 4 x 40 or a 4 x 20 character LCD.
My toolchain gripe is that although ST's documentation and support is about as good as it gets (and way, way ahead of Giga Devices, Espressif or RPie Pico (IMHO of course)) they no longer supply a nice simple set of header files in standard C - so you have to use the Cube thing to generate a project which you can then edit into something decent.
The tool thing lock in works for suppliers because it increases the cost of changing to another brand quite significantly - so they won't stop doing it.
So I voted
Proprietary toolchains and IDE
as my pet gripe.
MK
It's been interesting to look at the replies so far.
I do design work with small embedded processors both commercially and for entertainment.
Most of my designs are based on ARM Cortex micros from ST.
I sometimes buy dev boards but often don't use them at all because I design my own boards. The dev board is insurance in case my own design won't work and I need a functional board in a hurry as a reference.
While its true that for some purposes I could get away with and 8 bit micro the money saved is trivial compared with the design time and prototype parts costs. If the design will be made in large numbers a non ARM micro might be a good choice but I haven't had a commercial project where that has been the case for a long time.
I have used ARM micros from Giga Devices and NXP but I much prefer the ST range.
One of the nicest modern ARM micros is the STM32U575 - floating point, 160MHz clock, 784kRAM, 1 or 2Mbyte FLASH, Cordic Processor, Filter accelerator, 14 bit ADC and loads of other stuff. 48 pin LQFP if you like (bigger packages are available), very low power. About £5 for one.
Having mentioned the STM32U574 family, my current non commercial project is based on an ST32G0B1, slower and cheaper. It has enough 5V tolerant IO to be able to interface with a 5V LCD display while the rest of the logic and the processor use 3.3V.
The board plugs onto the back of the display. This is one I used to check the 5V LCD interface so it didn't get a fancy audio chip to blow up - although as things turned out it would have been OK. It can work with either a 4 x 40 or a 4 x 20 character LCD.
My toolchain gripe is that although ST's documentation and support is about as good as it gets (and way, way ahead of Giga Devices, Espressif or RPie Pico (IMHO of course)) they no longer supply a nice simple set of header files in standard C - so you have to use the Cube thing to generate a project which you can then edit into something decent.
The tool thing lock in works for suppliers because it increases the cost of changing to another brand quite significantly - so they won't stop doing it.
So I voted
Proprietary toolchains and IDE
as my pet gripe.
MK
