Playing with the STM32MP2
serd.es
serd.es
I'm worried they dug too deep a trench with the 32. Like how do much from Espressif is an ESP32 now despite them ranging from slower single core to faster dual core, now even with mmu, some with Wi-Fi some not...
What is in a name?
STM8 is still a thing and they were popular cheap embedded boards before ESP32 took over. They were ok as a cheap alternative to Arduino-compatible AVR boards. I have a few of the boards around. They were around $1 each on Aliexpress and have 8K of flash and 1K of ram, which is enough to run interactive Forth, and there's an SDCC compiler target for them.
only one person
If you don't know English very well I suggest not correcting other people.
Most would start with the significantly cheaper Discovery Kit version.
With ST, the developer kit is usually only needed if you need every pin and function exposed because you’re developing your own board.
> The Pocketbeagle 2 looks interesting to me.
If only it had 2GB+ RAM. Since it has 4 cores, even more RAM would be better.
And 1Gbit Ethernet is what I'm missing.
STM32MP257 application processors (STM32 MPUs) are based on a dual Arm® Cortex®-A35 cores running at up to 1.5 GHz and Cortex®-M33 cores running at 400 MHz.
When it came out we used STM32MP257 to demo a quadrature encoder debugger/logger (for internal use, not a product) since the IO supports easy interfacing of encoders. The micro's peripherals (SPI, I2C, GPIO etc.) are easy to program at the register level and you can run a simple mainloop+interrupts thing on the micro, then run Linux for your UI, networking, etc.
The fact that there's not much activity around these kinds of platforms (CPU+micro or CPU+FPGA) suggests it's too hard to combine the two in a way that makes sense for enough people, easier to just use standard components and have them side-by-side on the PCB.
It is nice to have them on the same die, though, for people like myself who like to work on both ends but don't know how to make their own PCBs.
And if by "very easy to work" you mean "just allocate a shared memory block and put a mailbox in there for the Linux userspace and the RT MCU to talk to each other", you may have inflated expectations of what an average developer using an SBC can easily do. It's "very easy" in the same way rolling your own PCBs or writing your own drivers is very easy. Seasoned developers do it without thinking twice, and then stand dumbstruck when they see entry level developers avoid that like the plague.
Not like we're lacking for the offerings. Plenty of modern SoCs have MCU-like real time cores in them - intended for low power operation, real time control, or both. Even the mainstream RPi 5 boards ship spare PIO and MCU cores - in the RP1 chip. The vendor just couldn't be bothered to document that.
There’s whole sectors of industrial and automotive using these AMP SoMs. And relative to these RPi only recently began providing options that you could design into an embedded product at all. Their FAE and supply presence is way behind.
The boards that people reach for when they roll their first projects, the hardware that ends up in early prototypes and one-off devices, the hardware that gets targeted by open source projects. The chips that return more than a "databrief" 8 pages long and a single page on a vendor site inviting you to visit the snake pit with "contact sales for more information". The boards you can actually buy with a fixed price tag and a delivery to door, and can find writeups on how to use them for specific things.
If you know what "FAE" is, let alone can get into a meeting with one, you're deep in the trenches, and are pretty much expected to wrangle an extremely poorly documented MCU core that happens to be shipped in a SoC as an afterthought into submission.
Engineers actually use these in real products and embedded systems.
The combination of Linux and microcontrollers isn’t new. It’s a very valuable and common structure.
The comments here trying to dismiss it or call it uncommon are bizarre.
The fusion of the two is very valuable if you have applications that require real time work.
> I presume they're trying to milk value out of the name recognition but they're just diluting the name.
No, absolutely not. This is a very valuable structure for embedded work and it’s very common. I don’t know why you’d jump to such a cynical conclusion.
Must be an embedded thing.
I have to wonder if locking up the docs is some kind of export control or government contract requirement.
But also: Cortex A35 is from 2015! And it's still just a trickle of these small application processor cores. Having a MMU enables so much more. Look at what Baochip and Xous are doing, with small cores but with MMU, for radically better interesting OS / systems architectures.
It just feels so cursed, is so beyond my surprise here well past half way through 202X that so many cores from early 201X are still not just alive but utterly dominant. Something has gone super super super wrong in the House of ARM!