QSPI only counts on eMMC models. Is this an eMMC model? If so, then it also implies you need the firmware/flash software from the carrier board provider. QSPI does matter in picking boot device for eMMC models, but does not exist in SD card models. As to the specific boot device being looked for you would use serial console to log the boot and see how far it gets, but typically flashing for a non-default device requires command line flash and altering the arguments to the flash.sh command. You’d want to mention any command line used if you flashed that way.
Hi John,
I would say just forget about the USB SSD at this moment. It really does not help your case. Remove the usb-ssd and focus on the sdcard case only. You can restart your USB-SSD flow once the system can boot up fine with sdcard.
According to your files inside ~/.nvsdkm/logs/JetPack_4.5.1_Linux, I can tell that you didn’t flash anything to your board.
Actually, the flash work didn’t start at all. If it started, there shall be a log like below.
NV_L4T_FLASH_NANO_2GB_DEVKIT_WITH_OS_IMAGE_COMP.log (Nano 2GB as example)
Could you just share a screenshot of what did you see on your sdkmanager GUI step by step so that we can find out why it does not start the flash?
Wayne, it will be late in the day before I get to respond as it is my marketing day here in Costa Rica. We are still under significant restrictions of movements. I must make the best use of ’ My’ day of movement.
John
1 Like
Wayne, yesterday went well. Nano is now working well from the micro SD. There is a movie attached showing the screens. I have ordered the USB/TTL adapter you write about in other threads when moving to USB boot. Thank you again for all your help. I learned much. John Sorry, the file is too big.
Solution June 1