Bravo
If ARM was an arm, BRN would be its biceps💪!
Hi @OutbackJohn, Agreed, it's very intersting isn't it?I love this part @Tothemoon24!
According to Arm, more than 90% of in-vehicle infotainment (IVI) systems use the company’s chip designs. The architectures are also found in various under-the-hood applications, including meter clusters, e-mirrors, and heating, ventilation, and air conditioning (HVAC) control.
If I was Arm, I would be incorporating AKIDA, into not just in the Cortex M based MCU's but into the A and R based MCU's as well, just to cover all bases.
View attachment 35570
View attachment 35572
View attachment 35573
View attachment 35575 View attachment 35574
View attachment 35576
https://armkeil.blob.core.windows.n...ide-to-arm-processing-power-in-automotive.pdf
I've suggested previously (as above) that if I were Arm I would be incorporating AKIDA into the A and R based MCU's as well the M based MCU's.
Arms new smartphone tech uses the latest Armv9.2 architecture. The previous Armv9 architecture covers all three profiles (A, R & M), so there's no reason to doubt the new Armv9.2 architecture won't do the same.
So lets say AKIDA E, S & P are are matched up to their corresponding Arm A,R & M profile MCU's then from what a previous article described, it sounds like the chipmakers, device makers and developers will decide on what level of functionality they want included, which is where our IP might come in as an option.
I've also questions previously the third party IP as shown on the ArmV9 architecture diagram that seems to leave room for our inclusion.
All just pure speculation at the moment on my behalf.



B x
Last edited: