In the documentation for how to build the IMX bootloader container:
Once you correct the “git clone” to refer to the bianca branch, trying to build the bootloader builder container fails due to its inability to find a number of essential packages:
0.192 Reading package lists…
1.271 Building dependency tree…
1.522 Reading state information…
1.566 E: Unable to locate package arm-trusted-firmware-imx
1.566 E: Unable to locate package u-boot-imx
1.566 E: Unable to locate package imx-mkimage
1.566 E: Unable to locate package optee-os-imx
1.566 E: Unable to locate package nxp-cst-signer
The Dockerfile starts with a base image of “elxrlinux/elxr:bianca” – is this image supposed to be able to install those packages?
More critically, is that page supposed to work on a regular Debian 13 development system? It should make that clear.
All our procedures are designed to work on eLxr systems, as I noted in the MR you withdrew concerning the AppArmor tutorial. Please try the procedure with an eLxr distribution and let us know if you continue to have any issues.
I’m going to push back on this slightly since that page on the IMX bootloader uses the phrase “You must have Docker Engine installed on your Linux development host”, and the documentation likes to bounce around between talking about a Linux dev host and an eLxr image, sometimes even saying, “You must have the required development packages on your Linux development host or eLxr 26.04 image”:
thus clearly drawing a distinction between the two, so that page on the bootloader can certainly be misinterpreted given that it uses “Linux development host”.
Also, the AppArmor section very carefully opened with:
"Before You Begin
You must have an eLxr Server 26.04 development host setup with sudo privileges."
so that section is properly careful about making sure the reader understands.