Hi, We are using jetson nano p3450 model. Currently we are trying to boot this board using SSD which is connected on USB port. We are following below link for configuration: link: Jetson Nano - Run From USB Drive - JetsonHacks We had done all the steps succsfully but after that system restart continuosly. please check logs in attach file and below. [0000.125] [L4T TegraBoot] (version 00.00.2018.01-l4t-e82258de) [0000.130] Processing in cold boot mode Bootloader 2 [0000.135] A02 Bootrom Patch rev = 1023 [0000.138] Power-up reason: pmc por [0000.141] No Battery Present [0000.144] pmic max77620 reset reason [0000.147] pmic max77620 NVERC : 0x40 [0000.151] RamCode = 0 [0000.153] Platform has DDR4 type RAM [0000.156] max77620 disabling SD1 Remote Sense [0000.161] Setting DDR voltage to 1125mv [0000.165] Serial Number of Pmic Max77663: 0x1240e3 [0000.172] Entering ramdump check [0000.175] Get RamDumpCarveOut = 0x0 [0000.179] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8 [0000.184] Last reboot was clean, booting normally! [0000.188] Sdram initialization is successful [0000.192] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000 [0000.199] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000 [0000.204] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000 [0000.210] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000 [0000.216] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000 [0000.222] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000 [0000.228] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000 [0000.234] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000 [0000.250] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000 [0000.256] Platform-DebugCarveout: 0 [0000.259] Nck Carveout Base=0x00000000ff080000 Size=0x00200000 [0000.265] Non secure mode, and RB not enabled. [0000.269] BoardID = 3448, SKU = 0x0 [0000.272] QSPI-ONLY: SkipQspiOnlyFlag = 0 [0000.276] Nano-SD: checking PT table on QSPI … [0000.281] Read PT from (2:0) [0000.296] Using BFS PT to query partitions [0000.302] Loading Tboot-CPU binary [0000.330] Verifying TBC in OdmNonSecureSBK mode [0000.340] Bootloader load address is 0xa0000000, entry address is 0xa0000258 [0000.347] Bootloader downloaded successfully. [0000.351] Downloaded Tboot-CPU binary to 0xa0000258 [0000.356] MAX77620_GPIO5 configured [0000.359] CPU power rail is up [0000.362] CPU clock enabled [0000.366] Performing RAM repair [0000.369] Updating A64 Warmreset Address to 0xa00002e9 [0000.374] BoardID = 3448, SKU = 0x0 [0000.377] QSPI-ONLY: SkipQspiOnlyFlag = 0 [0000.381] Nano-SD: checking PT table on QSPI … [0000.385] Loading NvTbootBootloaderDTB [0000.452] Verifying NvTbootBootloaderDTB in OdmNonSecureSBK mode [0000.525] Bootloader DTB Load Address: 0x83000000 [0000.530] BoardID = 3448, SKU = 0x0 [0000.533] QSPI-ONLY: SkipQspiOnlyFlag = 0 [0000.537] Nano-SD: checking PT table on QSPI … [0000.541] Loading NvTbootKernelDTB [0000.607] Verifying NvTbootKernelDTB in OdmNonSecureSBK mode [0000.680] Kernel DTB Load Address: 0x83100000 [0000.684] BoardID = 3448, SKU = 0x0 [0000.688] QSPI-ONLY: SkipQspiOnlyFlag = 0 [0000.692] Nano-SD: checking PT table on QSPI … [0000.698] Loading cboot binary [0000.814] Verifying EBT in OdmNonSecureSBK mode [0000.855] Bootloader load address is 0x92c00000, entry address is 0x92c00258 [0000.862] Bootloader downloaded successfully. [0000.866] BoardID = 3448, SKU = 0x0 [0000.870] QSPI-ONLY: SkipQspiOnlyFlag = 0 [0000.873] Nano-SD: checking PT table on QSPI … [0000.878] PT: Partition NCT NOT found ! [0000.882] Warning: Find Partition via PT Failed [0000.886] Next binary entry address: 0x92c00258 [0000.891] BoardId: 3448 [0000.895] Overriding pmu board id with proc board id [0000.900] Display board id is not available [0000.904] BoardID = 3448, SKU = 0x0 [0000.907] QSPI-ONLY: SkipQspiOnlyFlag = 0 [0000.911] Nano-SD: checking PT table on QSPI … [0001.016] Verifying SC7EntryFw in OdmNonSecureSBK mode [0001.073] /bpmp deleted [0001.075] SC7EntryFw header found loaded at 0xff700000 [0001.271] OVR2 PMIC [0001.272] Bpmp FW successfully loaded [0001.276] BoardID = 3448, SKU = 0x0 [0001.279] QSPI-ONLY: SkipQspiOnlyFlag = 0 [0001.283] Nano-SD: checking PT table on QSPI … [0001.288] WB0 init successfully at 0xff780000 [0001.293] Set NvDecSticky Bits [0001.296] GSC2 address ff53fffc value c0edbbcc [0001.302] GSC MC Settings done [0001.305] BoardID = 3448, SKU = 0x0 [0001.309] QSPI-ONLY: SkipQspiOnlyFlag = 0 [0001.312] Nano-SD: checking PT table on QSPI … [0001.318] TOS Image length 53680 [0001.321] Monitor size 53680 [0001.324] OS size 0 [0001.339] Secure Os AES-CMAC Verification Success! [0001.343] TOS image cipher info: plaintext [0001.347] Loading and Validation of Secure OS Successful [0001.363] SC7 Entry Firmware - 0xff700000, 0x4000 [0001.368] NvTbootPackSdramParams: start. [0001.373] NvTbootPackSdramParams: done. [0001.377] Tegraboot started after 51843 us [0001.381] Basic modules init took 886467 us [0001.385] Sec Bootdevice Read Time = 12 ms, Read Size = 61 KB [0001.390] Sec Bootdevice Write Time = 0 ms, Write Size = 0 KB [0001.396] Next stage binary read took 102859 us [0001.400] Carveout took -126357 us [0001.403] CPU initialization took 495389 us [0001.407] Total time taken by TegraBoot 1358358 us [0001.412] Starting CPU & Halting co-processor 64NOTICE: BL31: v1.3(release):5b49e7f80 NOTICE: BL31: Built : 14:33:23, Jan 15 2021 ERROR: Error initializing runtime service trusty_fast [0001.534] RamCode = 0 [0001.539] LPDDR4 Training: Read DT: Number of tables = 2 [0001.544] EMC Training (SRC-freq: 204000; DST-freq: 1600000) [0001.557] EMC Training Successful [0001.560] 408000 not found in DVFS table [0001.566] RamCode = 0 [0001.570] DT Write: emc-table@204000 succeeded [0001.575] DT Write: emc-table@1600000 succeeded [0001.579] LPDDR4 Training: Write DT: Number of tables = 2 [0001.626] [0001.627] Debug Init done [0001.630] Marked DTB cacheable [0001.633] Bootloader DTB loaded at 0x83000000 [0001.638] Marked DTB cacheable [0001.640] Kernel DTB loaded at 0x83100000 [0001.644] DeviceTree Init done [0001.657] Pinmux applied successfully [0001.662] gicd_base: 0x50041000 [0001.665] gicc_base: 0x50042000 [0001.668] Interrupts Init done [0001.672] Using base:0x60005090 & irq:208 for tick-timer [0001.678] Using base:0x60005098 for delay-timer [0001.682] platform_init_timer: DONE [0001.685] Timer(tick) Init done [0001.689] osc freq = 38400 khz [0001.693] [0001.694] Welcome to L4T Cboot [0001.697] [0001.698] Cboot Version: 00.00.2018.01-t210-39562017 [0001.703] calling constructors [0001.706] initializing heap [0001.709] initializing threads [0001.712] initializing timers [0001.715] creating bootstrap completion thread [0001.719] top of bootstrap2() [0001.722] CPU: ARM Cortex A57 [0001.725] CPU: MIDR: 0x411FD071, MPIDR: 0x80000000 [0001.730] initializing platform [0001.737] Manufacturer: MF = 0xc2, ID MSB = 0x25 [0001.742] ID LSB = 0x36, ID-CFI len = 194 bytes [0001.746] Macronix QSPI chip present [0001.750] SPI device register [0001.752] init boot device [0001.755] allocating memory for boot device(SPI) [0001.760] registering boot device [0001.768] QSPI bdev is already initialized [0001.772] Enable APE clock [0001.775] Un-powergate APE partition [0001.778] of_register: registering tegra_udc to of_hal [0001.783] of_register: registering inv20628-driver to of_hal [0001.789] of_register: registering ads1015-driver to of_hal [0001.794] of_register: registering lp8557-bl-driver to of_hal [0001.800] of_register: registering bq2419x_charger to of_hal [0001.806] of_register: registering bq27441_fuel_gauge to of_hal [0001.817] gpio framework initialized [0001.821] of_register: registering tca9539_gpio to of_hal [0001.826] of_register: registering tca9539_gpio to of_hal [0001.831] of_register: registering i2c_bus_driver to of_hal [0001.837] of_register: registering i2c_bus_driver to of_hal [0001.843] of_register: registering i2c_bus_driver to of_hal [0001.848] pmic framework initialized [0001.852] of_register: registering max77620_pmic to of_hal [0001.857] regulator framework initialized [0001.861] of_register: registering tps65132_bl_driver to of_hal [0001.867] initializing target [0001.873] gpio_driver_register: register ‘tegra_gpio_driver’ driver [0001.881] board ID = D78, board SKU = 0 [0001.885] Skipping Z3! [0001.889] fixed regulator driver initialized [0001.907] initializing OF layer [0001.910] NCK carveout not present [0001.914] Skipping dts_overrides [0001.918] of_children_init: Ops found for compatible string nvidia,tegra210-i2c [0001.935] I2C Bus Init done [0001.937] of_children_init: Ops found for compatible string nvidia,tegra210-i2c [0001.948] I2C Bus Init done [0001.950] of_children_init: Ops found for compatible string nvidia,tegra210-i2c [0001.961] I2C Bus Init done [0001.963] of_children_init: Ops found for compatible string nvidia,tegra210-i2c [0001.974] I2C Bus Init done [0001.976] of_children_init: Ops found for compatible string nvidia,tegra210-i2c [0001.987] I2C Bus Init done [0001.989] of_children_init: Ops found for compatible string maxim,max77620 [0002.000] max77620_init using irq 118 [0002.005] register ‘maxim,max77620’ pmic [0002.009] gpio_driver_register: register ‘max77620-gpio’ driver [0002.015] of_children_init: Ops found for compatible string nvidia,tegra210-i2c [0002.026] I2C Bus Init done [0002.029] NCK carveout not present [0002.039] Find /i2c@7000c000’s alias i2c0 [0002.043] get eeprom at 1-a0, size 256, type 0 [0002.052] Find /i2c@7000c500’s alias i2c2 [0002.056] get eeprom at 3-a0, size 256, type 0 [0002.060] get eeprom at 3-ae, size 256, type 0 [0002.065] pm_ids_update: Updating 1,a0, size 256, type 0 [0002.070] I2C slave not started [0002.073] I2C write failed [0002.075] Writing offset failed [0002.079] eeprom_init: EEPROM read failed [0002.082] pm_ids_update: eeprom init failed [0002.087] pm_ids_update: Updating 3,a0, size 256, type 0 [0002.117] pm_ids_update: The pm board id is 3448-0000-400 [0002.124] Adding plugin-manager/ids/3448-0000-400=/i2c@7000c500:module@0x50 [0002.132] pm_ids_update: pm id update successful [0002.136] pm_ids_update: Updating 3,ae, size 256, type 0 [0002.16pe 0 [0003.583] get eeprom at 3-ae, size 256, type 0 [0003.588] pm_ids_update: Updating 1,a0, size 256, type 0 [0003.593] I2C slave not started [0003.596] I2C write failed [0003.599] Writing offset failed [0003.602] eeprom_init: EEPROM read failed [0003.606] pm_ids_update: eeprom init failed [0003.610] pm_ids_update: Updating 3,a0, size 256, type 0 [0003.640] pm_ids_update: The pm board id is 3448-0000-400 [0003.647] Adding plugin-manager/ids/3448-0000-400=/i2c@7000c500:module@0x50 [0003.655] pm_ids_update: pm id update successful [0003.660] pm_ids_update: Updating 3,ae, size 256, type 0 [0003.690] pm_ids_update: The pm board id is 3449-0000-400 [0003.696] Adding plugin-manager/ids/3449-0000-400=/i2c@7000c500:module@0x57 [0003.704] pm_ids_update: pm id update successful [0003.734] eeprom_get_mac: EEPROM invalid MAC address (all 0xff) [0003.740] shim_eeprom_update_mac:267: Failed to update 0 MAC address in DTB [0003.748] eeprom_get_mac: EEPROM invalid MAC address (all 0xff) [0003.754] shim_eeprom_update_mac:267: Failed to update 1 MAC address in DTB [0003.762] updating /chosen/nvidia,ethernet-mac node 00:04:4b:eb:eb:24 [0003.769] Plugin Manager: Parse ODM data 0x000a4000 [0003.781] shim_cmdline_install: /chosen/bootargs: earlycon=uart8250,mmio32,0x70006000 [0003.789] Add serial number:1423119019959 as DT property [0003.798] “bpmp” doesn’t exist, creating [0003.804] Updated bpmp info to DTB [0003.809] Updated initrd info to DTB [0003.812] “proc-board” doesn’t exist, creating [0003.818] Updated board info to DTB [0003.822] “pmu-board” doesn’t exist, creating [0003.828] Updated board info to DTB [0003.831] “display-board” doesn’t exist, creating [0003.837] Updated board info to DTB [0003.840] “reset” doesn’t exist, creating [0003.845] Updated reset info to DTB [0003.848] display_console_ioctl: No display init [0003.853] display_console_ioctl: No display init [0003.857] display_console_ioctl: No display init [0003.862] Cmdline: tegraid=21.1.2.0.0 ddr_die=4096M@2048M section=512M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 touch_id=0@63 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,4 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff780000 core_edp_mv=1075 core_edp_ma=4000 gpt [0003.897] DTB cmdline: earlycon=uart8250,mmio32,0x70006000 [0003.902] boot image cmdline: root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 [0003.915] Updated bootarg info to DTB [0003.919] Adding uuid 000000016445c8441400000009050200 to DT [0003.925] Adding eks info 0 to DT [0003.931] WARNING: Failed to pass NS DRAM ranges to TOS, err: -7 [0003.937] Updated memory info to DTB [0003.945] set vdd_core voltage to 1075 mv [0003.948] setting ‘vdd-core’ regulator to 1075000 micro volts [0003.954] Found secure-pmc; disable BPMP U-Boot 2020.04-g6b630d64fd (Jan 15 2021 - 14:33:20 -0800) SoC: tegra210 Model: NVIDIA Jetson Nano Developer Kit Board: NVIDIA P3450-0000 DRAM: 4 GiB MMC: sdhci@700b0000: 1, sdhci@700b0600: 0 Loading Environment from SPI Flash… SF: Detected mx25u3235f with page size 256 Bytes, erase size 4 KiB, total 4 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1… Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 1146 bytes read in 27 ms (41 KiB/s) L4T boot options 1: primary kernel 2: primary kernel 3: backup kernel Enter choice: 1: primary kernel Retrieving file: /boot/initrd-xusb.img 15344508 bytes read in 687 ms (21.3 MiB/s) Retrieving file: /boot/Image 34332680 bytes read in 1502 ms (21.8 MiB/s) append: tegraid=21.1.2.0.0 ddr_die=4096M@2048M section=512M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 touch_id=0@63 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,4 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff780000 core_edp_mv=1075 core_edp_ma=4000 gpt earlycon=uart8250,mmio32,0x70006000 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 root=UUID=64268c5c-36f2-4087-a460-67c0ff401227 rootwait rootfstype=ext4 Flattened Device Tree blob at 83100000 Booting using the fdt blob at 0x83100000 ERROR: reserving fdt memory region failed (addr=0 size=0) ERROR: reserving fdt memory region failed (addr=0 size=0) Using Device Tree in place at 0000000083100000, end 000000008317e68d copying carveout for /host1x@50000000/dc@54200000… copying carveout for /host1x@50000000/dc@54240000… Starting kernel … [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.9.140-tegra (buildbrain@mobile-u64-4263) (gcc version 7.3.1 20180425 [linaro-7.3-2018.05 revision d29120a424ecfbc167ef90065c0eeb7f91977701] (Linaro GCC 7.3-2018.05) ) #1 SMP PREEMPT Fri Oct 16 12:32:46 PDT 2020 [ 0.000000] Boot CPU: AArch64 Processor [411fd071] [ 0.000000] OF: fdt:memory scan node memory@80000000, reg size 32, [ 0.000000] OF: fdt: - 80000000 , 7ee00000 [ 0.000000] OF: fdt: - 100000000 , 7f200000 [ 0.000000] earlycon: uart8250 at MMIO32 0x0000000070006000 (options ‘’) [ 0.000000] bootconsole [uart8250] enabled [ 0.000000] OF: fdt:Reserved memory: failed to reserve memory for node ‘fb0_carveout’: base 0x0000000000000000, size 0 MiB [ 0.000000] OF: fdt:Reserved memory: failed to reserve memory for node ‘fb0_carveout’: base 0x0000000000000000, size 0 MiB [ 0.000000] OF: fdt:Reserved memory: failed to reserve memory for node ‘fb1_carveout’: base 0x0000000000000000, size 0 MiB [ 0.000000] OF: fdt:Reserved memory: failed to reserve memory for node ‘fb1_carveout’: base 0x0000000000000000, size 0 MiB [ 0.000000] OF: reserved mem: initialized node vpr-carveout, compatible id nvidia,vpr-carveout [ 0.000000] OF: reserved mem: initialized node iram-carveout, compatible id nvidia,iram-carveout [ 0.000000] OF: reserved mem: initialized node ramoops_carveout, compatible id nvidia,ramoops [ 0.000000] cma: Reserved 64 MiB at 0x00000000fac00000 [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.0 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: MIGRATE_INFO_TYPE not supported. [ 0.000000] psci: SMC Calling Convention v1.1 [ 0.000000] percpu: Embedded 25 pages/cpu @ffffffc0fefa3000 s61656 r8192 d32552 u102400 [ 0.000000] CPU features: enabling workaround for ARM erratum 832075 [ 0.000000] Speculative Store Bypass Disable mitigation not required [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1023544 [ 0.000000] Kernel command line: tegraid=21.1.2.0.0 ddr_die=4096M@2048M section=512M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 touch_id=0@63 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,4 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff780000 core_edp_mv=1075 core_edp_ma=4000 gpt earlycon=uart8250,mmio32,0x70006000 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 root=UUID=64268c5c-36f2-4087-a460-67c0ff401227 rootwait rootfstype=ext4 [ 0.000000] log_buf_len individual max cpu contribution: 32768 bytes [ 0.000000] log_buf_len total cpu_extra contributions: 98304 bytes [ 0.000000] log_buf_len min size: 32768 bytes [ 0.000000] log_buf_len: 131072 bytes [ 0.000000] early log buf free: 29380(89%) [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) [ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) [ 0.000000] Memory: 3560704K/4159488K available (15294K kernel code, 2936K rwdata, 6644K rodata, 8576K init, 611K bss, 123648K reserved, 475136K cma-reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] modules : 0xffffff800000000015344508 bytes read in 687 ms (21.3 MiB/s) Retrieving file: /boot/Image 34332680 bytes read in 1501 ms (21.8 MiB/s) append: tegraid=21.1.2.0.0 ddr_die=4096M@2048M section=512M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 touch_id=0@63 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,4 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff780000 core_edp_mv=1075 core_edp_ma=4000 gpt earlycon=uart8250,mmio32,0x70006000 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 root=UUID=64268c5c-36f2-4087-a460-67c0ff401227 rootwait rootfstype=ext4 Flattened Device Tree blob at 83100000 Booting using the fdt blob at 0x83100000 ERROR: reserving fdt memory region failed (addr=0 size=0) ERROR: reserving fdt memory region failed (addr=0 size=0) Using Device Tree in place at 0000000083100000, end 000000008317e68d copying carveout for /host1x@50000000/dc@54200000… copying carveout for /host1x@50000000/dc@54240000… error_log.txt (19.1 KB) . Please help me to do this.

Search the keyword recovery mode in below document. [image] Jetson Download Center Your board definitely can enter recovery mode or your previous work on sdkmanager is not completed. The flash process can only starts when the board is in recovery mode.

Please use the official method. We don’t guarantee the method on jetsonhacks. https://docs.nvidia.com/jetson/l4t/index.html#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/flashing.html#wwpID0E0HM0HA or https://elinux.org/Jetson/L4T/Boot_From_External_Device

Hi Wayne, Thank you for your prompt reply. We checked above links but we are not getting any reference for folder /Linux_for_Tegra. Please suggest me path or location to that folder or how can i get to that folder.

Let me post what I just shared to other users here. [image] Jetson Nano Flash on USB Drive Jetson Nano Hi, Actually, the real tool that can fully support jetson platform is sdkmanager. Which will download the driver package “Linux_for_Tegra” on your x86 host. Those contents are in this driver package. NVIDIA SDK Manager | NVIDIA Developer Why I say “fully support” is because we only launch sdcard image on Nano and NX sdcard module. Other platforms need sdkmanager to flash. Even nano/nx “production module” require sdkmanager. We don’t provide sdcard image for that module. The step 6 requi… IMO, please do not always rely on sdcard image. This will make you don’t know how real jetson development tools look like…

Hi WayneWWW, Again thanking you for reply. We are trying to install sdkmanager in our system but getting error message. atcs-03@atcs03-desktop:~$ sudo apt install ./sdkmanager_0.9.11-3405_amd64.deb Reading package lists… Done Building dependency tree Reading state information… Done Note, selecting ‘sdkmanager:amd64’ instead of ‘./sdkmanager_0.9.11-3405_amd64.deb’ Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sdkmanager:amd64 : Depends: libgconf-2-4:amd64 but it is not installable Depends: libcanberra-gtk-module:amd64 but it is not installable E: Unable to correct problems, you have held broken packages. We are directly install jetpack4.5 in SD card using rufus 3.13. Is there any way to boot directly from SSD without using SD card?

Hi, What is this atcs03-desktop device?

atcs-03 is the username which we configured after uploading image file in sd card

Hi, Sdkmanager is for x86 host machine but not for arm device.

Hi WayneWWW, Ok. Currently we setup ubuntu18.04 using vmvare in our system. Can you guide us to further setups using sdkmanager for booting jetson nano using SSD directly? Thank you for your kind support.

Unfortunately, vm is not supporting either…

Ok so we need proper ubuntu18.04 system. Please share if any additional setup required and setups for booting jetson nano using ssd drive?

Jetson nano booting from SSD problem

Robotics & Edge Computing Jetson Systems Jetson Nano

WayneWWW March 1, 2021, 9:58am 5

Let me post what I just shared to other users here.

IMO, please do not always rely on sdcard image. This will make you don’t know how real jetson development tools look like…

Topic		Replies	Views
Jetson nano Kit B01 Bricked Jetson Nano boot	44	4039	June 7, 2021
Another boot from ssd + spi thread Jetson Nano spi , boot	23	2983	December 30, 2021
Jetson nano dev Kit B01 Not booting after setup Jetson Nano boot	18	1016	November 24, 2023
Corrupted NvTbootKernelDTB and flashing with an x86 host Jetson Projects boot	11	801	March 7, 2024
Jetson Nano does not boot up Jetson Nano	16	3207	November 4, 2019
Jeston Nano developer kit doesn't boot up Jetson Nano boot , board-design	11	2585	July 23, 2021
Move OS to USB SSD Jetson Nano boot	44	4343	July 2, 2021
[BOOT] Nothing happend after following the Quick Start Guide Jetson Nano	6	907	October 31, 2019
How to setup a JETSON-NANO-DEV-KIT-A (alternative to B01) Jetson Nano reflash	30	4200	April 28, 2022
Jetson 4GB Nano 4GB SDK does not boot Jetson Nano boot	27	2515	April 4, 2021

Jetson nano booting from SSD problem

Related topics