MCUs are all well under 10MB of onboard RAM (often single-digit kbytes, but bigger MCUs exist). And if they support external RAM, its MCU-protocols like SPI-RAM (which rarely goes much further than 1MB)
STM32 MCU family goes 64-bit with the STM32MP2x (Cortex-A35)
21–30 of 54 posts
Re: STM32 MCU family goes 64-bit with the STM32MP2x (Cortex-A35)
#22Editorialized title; its not part of the MCU family, its part of the MPU family
And the line between the two is blurred now with MCU running at hundreds of MHz. The STM32H7 is has more IPC than the original Raspberry Pi.
There's a blurry line sometimes, but Application-class (Cortex A* cores, like A5, A35, etc. etc.) are solidly MPU. Not even close.
Re: STM32 MCU family goes 64-bit with the STM32MP2x (Cortex-A35)
#23Editorialized title; its not part of the MCU family, its part of the MPU family
What’s the diff between an SoC and MPU? Lack of a wireless connectivity subsystem?
For ARM, its rather simple. Cortex-M cores are MCUs, while Cortex-A cores are Microprocessors.
Cortex A72?? That's a Microprocessor.
Cortex M7? This is a Microcontroller.
Re: STM32 MCU family goes 64-bit with the STM32MP2x (Cortex-A35)
#24Re: STM32 MCU family goes 64-bit with the STM32MP2x (Cortex-A35)
#25Editorialized title; its not part of the MCU family, its part of the MPU family
And the line between the two is blurred now with MCU running at hundreds of MHz. The STM32H7 is has more IPC than the original Raspberry Pi.
Re: STM32 MCU family goes 64-bit with the STM32MP2x (Cortex-A35)
#26Editorialized title; its not part of the MCU family, its part of the MPU family
What’s the diff between an SoC and MPU? Lack of a wireless connectivity subsystem?
MCU -> Microcontroller. Low power, less RAM, limited MMU/memory protection features, typically run baremetal firmware or an RTOS. Usually so simple it only needs a single voltage rail. More or less self-contained. Has RAM and ROM on-die.
SoC -> System-on-a-chip. Actually a very vague term. But in broad strokes, an SoC is what it says: An entire system on a single chip. Could incorporate an MCU or an MPU, plus other peripherals, etc. You can almost think of it as a "single chip computer" as opposed to a "single board computer". It's almost more of a marketing term than an EE term. For example, the Apple Silicon stuff is a "SoC" because it has the MPU + GPU + RAM on a single die.
Re: STM32 MCU family goes 64-bit with the STM32MP2x (Cortex-A35)
#27Still calling your new 64-bit chips STM32, just like your 32-bit chips, instead of STM64, feels like your branding/marketing team is asleep at the wheel or just non-existent. Even Nintendo figured that out ~30 years ago.
Re: STM32 MCU family goes 64-bit with the STM32MP2x (Cortex-A35)
#28Still calling your new 64-bit chips STM32, just like your 32-bit chips, instead of STM64, feels like your branding/marketing team is asleep at the wheel or just non-existent. Even Nintendo figured that out ~30 years ago.
STM32 is a very strong brand in the MCU space...
Re: STM32 MCU family goes 64-bit with the STM32MP2x (Cortex-A35)
#29Still calling your new 64-bit chips STM32, just like your 32-bit chips, instead of STM64, feels like your branding/marketing team is asleep at the wheel or just non-existent. Even Nintendo figured that out ~30 years ago.
STM32 is a very strong brand in the MCU space...
Still seems very strange to label 64-bit processors STM32...
Re: STM32 MCU family goes 64-bit with the STM32MP2x (Cortex-A35)
#30Does anyone know why some of the balls in the (render pics) are missing around the edges? Unrelated: Would this be suitable for a CV system eg in robotics? Eg do the realtime stuff on the Cortex-M, and run a linux + OpenCV/OpenVINO etc on the Cortex-A?
The balls are missing to enable making connections to inner balls in a board with fewer layers. The outer balls take up space and so block the traces from inner balls. By strategically removing some of the outer balls, you create channels that can be used for routing taxes from the inner balls.