eMMC boot issues after booting USB image
I've had a Debian image installed for months in eMMC using the distro transfer command. I've recently been trying other images from a usb drive without touching the eMMC. USB images were booted using the BOOT USB option in the firmware menu, and the eMMC stays connected the whole time.
After shutting of the usb images, when I try to boot the eMMC, the board goes to network boot, as it says there's no image to be found.
I always manage to boot from eMMC again, but I have to power cycle the board over 10 times until it is able to detect the image.
Any reason why this could be happening?
After shutting of the usb images, when I try to boot the eMMC, the board goes to network boot, as it says there's no image to be found.
I always manage to boot from eMMC again, but I have to power cycle the board over 10 times until it is able to detect the image.
Any reason why this could be happening?
Tagged:
Comments
I'll take a picture next time I try booting
It might have been anecdotal, but I believe it is still looking for a usb drive. As soon as I tried to boot with a different device connected to the USB farthest from the GPIO (a keyboard to be exact), the board was able to boot.
I couldn't get the picture but when it booted it showed up an error: (-2)couldn't get size , or something simillar, but it managed to boot anyway.
Boot: spi
Net: eth0 chip_id MAC address: xx:xx:xx:xx:xx:xx
Error: could not access storage
Net: eth0: ethernet@9410000
starting USB...
USB0: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
USB 1: scanning bus 0 for devices... 2 USB Devices(s) found
scanning bus 1 for devices... 1 USB Device(s) found
Press ESC for menu. 0
Device 0: unknown device
Speed: 100, full duplex
BOOTP broadcast 1
...
and then it goes on with network boot