5 ms·

Here are ~200 examples from Digikey (sort by price->increasing at a reasonable quantity): https://www.digikey.com/short/jjhtf0h8 https://www.digikey.com/short/

Here are ~200 examples from Digikey (sort by price->increasing at a reasonable quantity): https://www.digikey.com/short/jjhtf0h8 https://www.digikey.com/short/jjhtf0h8 These are Cortex-M0 and Cortex-M23 parts in manufacturer lines like Atmel SAMD10, Freescale KE04, Nuvoton Mini55, NXP LPC82x, Infineon PSOC4, STmicro STM32G0 and STM32F0, and others. And they often blow the 8-bit parts out of the water in features and performance, usually losing only in battery leakage current/active current consumption. Technically they're often 16/32-bit ARM Thumb cores, not sure I'd call them 32-bit cores when 90% of the instructions you'll execute are 16 bits, even though the memory space and registers are 32 bits wide. I suppose they feel close enough to developers and users like 32 bit cores as opposed to something that's painfully, obviously, only 8 or 16 bits wide that you can just ignore that technicality...

jamesmunns 4y ago
fwiw: cortex-m parts would be pretty conclusively referred to as 32-bit parts (due to the 32-bit address space/pointers as well as 32-bits being the native word size of the platform). Other 32 and 64 bit platforms support some kind of "compressed instruction" support, for example 32-bit ARMv7 microprocessors (think early android phones, original raspberry pi, etc.) also support the 16-bit Thumbv2 instruction mode, though thumbv2 support was removed in AArch64/ARMv8. This is contrasted with a "true" 16-bit platform like msp430, which has 16-bit pointers and native 16-bit words. RISC-V also has an optional compressed instruction set for both 32- and 64-bit platforms as well.
- girvo 4y ago
  And the Xtensa LX6/LX7 use a compressed 24-bit instruction set, but are referred to as 32-bit chips, just to add to your overall point.
- unwind 4y ago
  I agree, I think it's strange to make the instruction encoding influence whether or not a part is to be considered 32-bit. Instead I think the programmer's model is what determines that (which would make these ARM cores firmly 32-bit like you say).

jamesmunns 4y ago

fwiw: cortex-m parts would be pretty conclusively referred to as 32-bit parts (due to the 32-bit address space/pointers as well as 32-bits being the native word size of the platform). Other 32 and 64 bit platforms support some kind of "compressed instruction" support, for example 32-bit ARMv7 microprocessors (think early android phones, original raspberry pi, etc.) also support the 16-bit Thumbv2 instruction mode, though thumbv2 support was removed in AArch64/ARMv8. This is contrasted with a "true" 16-bit platform like msp430, which has 16-bit pointers and native 16-bit words. RISC-V also has an optional compressed instruction set for both 32- and 64-bit platforms as well.

girvo 4y ago
And the Xtensa LX6/LX7 use a compressed 24-bit instruction set, but are referred to as 32-bit chips, just to add to your overall point.
unwind 4y ago
I agree, I think it's strange to make the instruction encoding influence whether or not a part is to be considered 32-bit. Instead I think the programmer's model is what determines that (which would make these ARM cores firmly 32-bit like you say).