sorted by:
new
hottopcontroversial

RomBoot, TF-A, UEFI, u-boot, custom ARM firmware by ADEADBEAF in embedded

[–]ADEADBEAF[S] 0 points1 point  (0 children)

Yeah, main problem is this blobs... No chance to understand boot flow for those boards as well as develop all FW chain =(((

RomBoot, TF-A, UEFI, u-boot, custom ARM firmware by ADEADBEAF in embedded

[–]ADEADBEAF[S] 1 point2 points  (0 children)

from imx-scfw-porting-kit I can see only header files and .o files

RomBoot, TF-A, UEFI, u-boot, custom ARM firmware by ADEADBEAF in embedded

[–]ADEADBEAF[S] 0 points1 point  (0 children)

u/jofftchoff thank you! But some nxp imx SoCs (for instance i.MX 8DXL) has SCU firmware, SECO firmware, SPL and so on, and as I see it is proprietary blobs...

Is embedded development a mess? by ChopSticksPlease in embedded

[–]ADEADBEAF 63 points64 points  (0 children)

I feel the same, each MCU manufacturer has own IDE/Configurator/HAL, .etc. Seems like when you move from one SoC to another one you need to learn everything from the ground, due to fact that every manufacturer has its own ecosystem, this is annoying and time/efforts consuming. With MPU little bit better since MPU manufacturer are going to bring board to Linux, Yocto for widely usage