2 ms·
We spin our own build of Linux...We are using an ARM-based SoC from NXP. Okay, so that narrows it down to the i.MX family. We chose this to ensure that the de
by joezydeco 8y ago
We spin our own build of Linux...We are using an ARM-based SoC from NXP.
Okay, so that narrows it down to the i.MX family.
We chose this to ensure that the device can only run signed, trusted code by implementing secure boot and signature verification of software updates.
Maybe read this?
https://blog.quarkslab.com/vulnerabilities-in-high-assurance-boot-of-nxp-imx-microprocessors.html https://blog.quarkslab.com/vulnerabilities-in-high-assurance...
- iancarroll 8y agoFrom the technical specs, it's almost certainly the i.MX 8, which as far as I know is not affected or listed on any of the errata for that vulnerability.
- joezydeco 8y agoI missed the part on the tech page that listed the A72, so yeah it's an iMX8. Hopefully the HAB fix is the reason for the 8. Otherwise this seems like overkill for the work involved.
- gsreenivas 8y agoGood guess and we looked at the i.MX but did not select that line of SoCs. We are using the Layerscape line of SoCs from NXP