unable to build NBOOT beside UBOOT with current repo (state 07/24). (Standalone build)

BrenkeM · Jul 25th 2024

Hello Ladies and Gentleman,

I am able to build and adjust the bootloader UBOOT from [GITHUB]. Because I we use BUILDROOT for the picocore MX8MP platform. Which means we want to build NBOOT and UBOOT directly from the repo.

But building NBOOT is failing, see [1]. So how are we able to build NBOOT standalone without using the yocto project?

[GITHUB]:

https://github.com/FSEmbedded/…58b1bd2602ea70764313ba110

[1]:

Code

$ make nboot
…
UPD include/generated/timestamp_autogenerated.h
HOSTCC tools/mkenvimage.o
HOSTLD tools/mkenvimage
HOSTCC tools/fit_image.o
HOSTCC tools/image-host.o
HOSTCC tools/dumpimage.o
HOSTLD tools/dumpimage
HOSTCC tools/mkimage.o
HOSTLD tools/mkimage
CC board/F+S/common/fs_fdt_common.o
LD board/F+S/common/built-in.o
CC cmd/version.o
LD cmd/built-in.o
CC common/main.o
LD common/built-in.o
CC drivers/fastboot/fb_fsl/fb_fsl_getvar.o
LD drivers/fastboot/fb_fsl/built-in.o
LD drivers/fastboot/built-in.o
LD drivers/built-in.o
CC lib/smbios.o
CC lib/display_options.o
LD lib/built-in.o
LD u-boot
DISASM u-boot.dis
CC spl/common/spl/spl.o
LD spl/common/spl/built-in.o
CC spl/lib/display_options.o
LD spl/lib/built-in.o
LD spl/u-boot-spl
OBJCOPY spl/u-boot-spl-nodtb.bin
COPY spl/u-boot-spl.bin
SYM spl/u-boot-spl.sym
DISASM spl/u-boot-spl.dis
./tools/imx8m_image.sh spl/u-boot-spl.cfgout 1
25782+0 Datensätze ein
25782+0 Datensätze aus
103128 Bytes (103 kB, 101 KiB) kopiert, 0.156601 s, 659 kB/s
MKIMAGE SPL
FSIMG board/F+S/fsimx8mp/nboot/fsimx8mp_spl.fs
make[1]: *** Keine Regel vorhanden, um das Ziel „board/F+S/fsimx8mp/nboot/fsimx8mp_firmware.fs“,
benötigt von „nboot-fsimx8mp-2024.06.fs“, zu erstellen. Schluss.
Makefile:1468: recipe for target 'nboot' failed
make: *** [nboot] Error 2

Display More

fs-support_HK · Jul 26th 2024

NBoot ist not meant to be built by customers. Which is why there is no mannula how to do this. Nboot releases are done by F&S and all the NBoot version can always beo found in the F&S download sections. Each board is already shipped with a matching NBoot.

The reason is this: NBoot contains information about the board variants and parts that are mounted. If for example a DRAM chip goes end of life, then we can prepare a new variant with a replacement DRAM chip. So when you get the next shipment, there will be an NBoot installed on the board that can handle the new DRAM chip and you will notice no difference. But if you install your own NBoot version, then this is most probably not aware of the new DRAM chip yet. So the boot process may fail or the board will be instable due to wrong DRAM timings.

Of course the next regular Linux release will again hold all NBoot code to support the new DRAM chip. But this release may come out significantly later. NBoot releases are basically independent from Linux releases and may also happen between regular releases.

And here is another important rule: never downgrade NBoot to a version before the one that was shipped with the board. This may cause the same problem as above, tand the board may fail to boot are may behave strangely.

Your F&S Support Team

BrenkeM · Aug 5th 2024

Unserstand.

Thanks for the info. I was able to download and update the current version (nboot-fsimx8mp-2024.06.fs) of NBOOT from [1].

[1]:

https://fs-net.de/en/support/my-f-and-s

unable to build NBOOT beside UBOOT with current repo (state 07/24). (Standalone build)

Share

Tags