you need yet to look at the uboot environment. connect to UART, power the board and keep hitting esc key, or "s" key or any key (yeah, on uboot there is variance with this). then when it shows its command line, examine its variables. printenv without arguments spits them all IIRC, especially take a look at these two ${devtype} and ${devnum}. I am not a specialist in uboot/linux guts as well, but definitely your problem sits in the uboot environment.
what those variables do contain? you need to examine the command execution sequence in the uboot environment. save its printenv output, show here and analyze by yourself what that weirdo does. maybe it would be possible to force it to always try the usb3 port first. again, - there is no uboot documentation, so it's all done through this kind of guesses and tries. >_>
what those variables do contain? you need to examine the command execution sequence in the uboot environment. save its printenv output, show here and analyze by yourself what that weirdo does. maybe it would be possible to force it to always try the usb3 port first. again, - there is no uboot documentation, so it's all done through this kind of guesses and tries. >_>
ANT - my hobby OS for x86 and ARM.
