Open Metatron2k2 opened 3 years ago
Guys, I do not know if this is the same issue I was facing, but u-boot did not work for me on kirkstone and I did the following to solve it:
Modify config.txt as follows:
dtoverlay=disable-bt
to be able to use the UART properly for anything following after the second stage bootloader finishedVery interesting. Did you encounter this while using network booting? As far as the issue you are referencing is describing, it only applies to network booting.
Description U-Boot of Hardknott Branch does not boot on CM3+ at all. U-Boot 2020.1 from Dunfell works as expected (after updating with @emilm 's Patch.
Setting uart_2ndstage=1 in config.txt reveals that the system stops after loading U-Boot
Steps to reproduce the issue:
Describe the results you received: Stuck on boot.
Describe the results you expected: Booting system.
Additional information you deem important (e.g. issue happens only occasionally): 2nd stage logs:
Additional details (revisions used, host distro, etc.): Poky Hardknott with meta-raspberry