3 ms·

Does anyone have an idea about when we should expect this chips to be incorporated in devices on the generally available market after an announcement like this?

deleted 7y ago
[deleted]
kbumsik 7y ago
Referring the previous M33 architecture, it took around 2 years to get the actual chips as a public developer if you don't have a priority from the vender. And it took less than 3 years to see consumer products using it. 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.
- lmilcin 7y ago
  I think I can explain the delay. 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.
raryanpur 7y ago
Anecdotally - probably in about 2 years, based on the time between announcement of the core and general silicon availability for past Cortex-M cores (M33, M23, M7, and M4).
_-___________-_ 7y ago
Bear in mind that ARM doesn't make chips, so this is effectively the launch of a design. The chips still have to be created based on this design.
- lmilcin 7y ago
  I can't imagine STMicroelectronics isn't already in the process of designing new chips.

deleted 7y ago

[deleted]

kbumsik 7y ago

Referring the previous M33 architecture, it took around 2 years to get the actual chips as a public developer if you don't have a priority from the vender. And it took less than 3 years to see consumer products using it. 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.

lmilcin 7y ago
I think I can explain the delay. 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.

raryanpur 7y ago

Anecdotally - probably in about 2 years, based on the time between announcement of the core and general silicon availability for past Cortex-M cores (M33, M23, M7, and M4).

_-___________-_ 7y ago

Bear in mind that ARM doesn't make chips, so this is effectively the launch of a design. The chips still have to be created based on this design.

lmilcin 7y ago
I can't imagine STMicroelectronics isn't already in the process of designing new chips.