ARM Launches Cortex M55 and Ethos-U55
fuse.wikichip.org
fuse.wikichip.org
I am not sure but I think this one might be different. In case of M33 it was fast because you just adopt the chip for the existing solution, but you need to come up with a new business idea, or a technical stack (that uses machine learning on the edge devices) to fully benefit from the new chip.
I've been comfortable designing with M3/M4 and for most applications M33 is not such a big step as to suddenly drop whatever you are doing and redesign your app around new features.
Even with new products I don't necessarily want to spend time learning new functionality since the cores I already know do everything I need.
Given possibility to learn new M33 functionality for a bunch of time I preferred to learn to make my designs more energy efficient with existing cores, for example.
Only just recently I have decided to start using M33 and mainly for security.
I can imagine most people designing go through similar process. The advantage of M33/M55 is/will be when you actually have a need for the new features and when you design your application around those new features, otherwise the cores provide only incremental improvement.
It is a hardware-specific library that relies Cortex-M DSP instruction.
> not even a state of the art one at that
What do you expect? Here we are talking about microcontrollers which is always far behind of the cutting-edge computing.
The tooling for proprietary DSP ISAs sucks, and with the dominance of ARM and available toolchains for cross compiling various languages over LLVM on basically any OS, it's just so much nicer than dealing with whatever garbage, dated, and poorly documented toolchain/IDE that they charge you to use for their ancient designs.