- I am using latest u-boot build which is 2018-rc2 revision, I enabled for more debug information by mentioning “#define DEBUG” in include/common.h file, built it and ran the u-boot, while initializing, I guess on autoboot running time, after USB device verification, mmc check started and the application got hanged after displaying the following information.
mmc0(part 0) is current device
Scanning mmc 0:1…
after this no further update, and not came to CLI, waited more than half-hour, is there anything I missed here. I want to see more debug log, When I cross check it is getting stuck at some where while running environment variables at autoboot time.
- In normal booting, without having debug definition, I successfully able to get into command line interface, I connected the LAN cable and try to check for any ethernet devices connected to the board. FYI, I was not loaded the kernel and rootfs, I am planing to load them through tftp, but it says an error as no device detected. guide me if I missed something.