Changes between Version 3 and Version 4 of venice/bootloader

Timestamp:

04/19/2024 10:34:41 PM (19 months ago)

Author:

Ryan Erbstoesser

Comment:

add troubleshooting section for nvme

venice/bootloader

@@ -60 +60 @@
 
 If you wish to select a different boot device priority you can adjust boot_targets. For example:
- * boot from NVMe (nvme dev 0)
+ * Boot from NVMe (nvme dev 0)
 {{{#!bash
 # flash your disk image to the NVMe device
@@ -75 +75 @@
 setenv boot_targets nvme0
 saveenv
+#now reset the board and let it boot to NVMe
+reset
+}}}
+
+  * Troubleshooting: 
+   * There must be a bootable partition and a boot script. In the example here you see we have an NVME device, it has a partition that is flagged as bootable (Type=83 Boot), and has a boot.scr in its /boot directory
+{{{
+u-boot=> nvme devices # show NVMe devices; should show your device
+
+IDE device 0: Vendor: 0x10ec Rev: 0426-D00 Prod: 60272-0005          
+            Type: Hard Disk
+            Capacity: 57241.8 MB = 55.9 GB (117231408 x 512)
+
+u-boot=> part list nvme 0 # show the partition table on nvme device 0
+
+Partition Map for NVMe device 0  --   Partition Type: DOS
+
+Part    Start Sector    Num Sectors     UUID            Type
+  1     32768           117198640       a7d49245-01     83 Boot
+
+u-boot=> ls nvme 0:1 /boot # list files on nvme device 0 partition 1
+<DIR>       4096 .
+<DIR>       4096 ..
+           51836 imx8mm-venice-gw73xx-0x.dtb
+        31556096 Image
+        11414268 kernel.itb
+            2244 boot.scr
+
 }}}
  * boot from microSD (mmc dev 1)