U-Boot has a command line interface, the U-Boot console, in which you work with U-Boot commands and environment variables to create a customized boot process. The U-Boot projects attempts to maintain a fixed, predictable Release Cycle as follows: We will have U-Boot releases at a fixed release interval of (approximately) every 3 months. Refer to U-Boot Documentation and U-Boot Command Line Interface.
I tried what feels like a million configurations and I'm out of ideas what could be the reason for this behavior. Note: Documentation on how to use and develop U-Boot can be found at U-Boot Release Cycle. In case not use TI SDK and building U-Boot out of mainline, then k3-image-gen (For generating tiboot3.bin and b) project is located here Linux Firmware (for device specific ti-dm and ti-sysfw binaries) project is located here. For a comprehensive list of all possible directives you can use in nf. Neither can I stop autoboot nor can I use the shell to complete the boot script. conf is located, as exemplified in the U-Boot documentation. So it is potential not a problem with U-Boot but with the Model B configuration. The other way around though it does not work. It seemingly works as both are close enough. I moved the working u-boot.bin from the cm 3 to the model B to see what happens. This configuration works just fine on the compute module, but doen't register input on the model 3B. I left out support for mini-uart as this would break the output too. At the time of writing, there is a correction/. I applied the miniuart-bt overlay to restore /dev/ttyAMA0 respectively UART0 on gpio pins 14/15. git clone git:///u-boot.git u-boot -b master -depth 1. U-Boot documentation is very rich in addition to the official U-Boot website, several others are dealing with U-Boot getting started or configuration.
I'm connected to the serial console with a serial-USB adapter and picocom.
I used the term serial very loosely here. Mender provides special integration points for your existing boot code to hook into so that Mender can be a part of the normal.
The following output is produced by U-Boot on serial console. U-Boot v2020.10 is used.Īfter some small changes regarding the device tree and dtoverlays I managed to get U-Boot to print on the serial console(as expected), but it ignores all keyboard input. As I need the same setup on a raspberry Pi Model 3 B I tried bringing the config over.Įverything is compiled in a buildroot environment. I already have a working config for a compute module 3+.