Jetson nano dev Kit B01 Not booting after setup

After setting up the jetson nano, after the api memory allocation and user creation the jetson rebooted and stopped working. It does not provides signal to the keyboard, or screen or mouse. Removing the memory card changes nothing. Not sure what to do. When connecting it via USB to a pc it cannot be detected. But the green light in all of the cases is still on. I have also tried to clean the SD card and intall the image again. No difference

Dump the serial console log:

Or re-flash with SDK Manager.
You need a jumper to put the device into force recovery mode, or it’s expected it doesn’t get detected by the host PC.

Thanks for the response. I have tried the recovery mod and sdk manager, but when using a linux 22.04 no sdk version are avaliable, i tried on a 20.04 linux, when i switch to the jetson nano target hardware, all the sdk version option disappear .
Can i dump the serial consol log with the micro usb port? and if yes how?

You need a TTL-USB cable for dumping log.
If SDK Manager does not work, manually flash with:
https://docs.nvidia.com/jetson/archives/l4t-archived/l4t-3274/index.html

i do not have a TTL_USB cable. is there another way.
I have managed to use linux 18.04 for the sdk manager and the process stopped at 33.33% when the flashing menu pops up. The error message informs that “the jetson target is in a bad state and cannot be flashed. Please manually out the target in recovery mode and then retry flashing”. I am using a Virtual machine but the device had no connection issues so far.

Please avoid using virtual machines.
Also, if you don’t get the cable and cannot dump the log, there’s very little I can help.

Update: I have also tried via: sudo ./flash.sh jetson-nano-qspi-sd mmcblk0p1 and the flashing failed.
I will try to get my hands on the ttl_usb cable

since the jetson was working fine until he decided to reboot, is it possible to factory reboot the device without the need of serial consol or sdk?

There’s no such thing called “factory reboot”.
The only thing you can do is re-flash, and since the process failed, we need serial console log to check why.

i have round an AZDelivery FT232RL Adapter and connected the pins GND to GND on the J44 header, the RX to TX and TX to RX. Set a voltage to 3.3 V and i was ran it with putty. When starting the jetson only a strange square appears (3 characters long) and nothing else. And in any other configuration nothing appears. I was expecting at least the information that is booting, but no, nothing.


I used this updated guide to perform the connection:https://jetsonhacks.com/2019/04/19/jetson-nano-serial-console/

And the it looks like it gets stuck in “Starting CPU & Halting co-processor”, it just repeats this log:

[0001.433] Starting CPU & Halting co-processor

64NOTICE: BL31: v1.3(release):b5eeb33
NOTICE: BL31: Built : 08:56:32, Feb 19 2022
ERROR: Error initializing runtime service trusty_fast
[0001.555] RamCode = 0
[0001.560] LPDDR4 Training: Read DT: Number of tables = 2
[0001.565] EMC Training (SRC-freq: 204000; DST-freq: 1600000)
[0001.578] EMC Training Successful
[0001.581] 408000 not found in DVFS table
[0001.587] RamCode = 0
[0001.591] DT Write: emc-table@204000 succeeded
[0001.596] DT Write: emc-table@1600000 succeeded
[0001.600] LPDDR4 Training: Write DT: Number of tables = 2
[0001.648]
[0001.649] Debug Init done
[0001.651] Marked DTB cacheable
[0001.654] Bootloader DTB loaded at 0x83000000
[0001.659] Marked DTB cacheable
[0001.662] Kernel DTB loaded at 0x83100000
[0001.666] DeviceTree Init done
[0001.679] Pinmux applied successfully
[0001.683] gicd_base: 0x50041000
[0001.687] gicc_base: 0x50042000
[0001.690] Interrupts Init done
[0001.694] Using base:0x60005090 & irq:208 for tick-timer
[0001.699] Using base:0x60005098 for delay-timer
[0001.704] platform_init_timer: DONE
[0001.707] Timer(tick) Init done
[0001.711] osc freq = 38400 khz
[0001.715]
[0001.716] Welcome to L4T Cboot
[0001.719]
[0001.720] Cboot Version: 00.00.2018.01-t210-a2f2e4b8
[0001.725] calling constructors
[0001.728] initializing heap
[0001.730] initializing threads
[0001.733] initializing timers
[0001.736] creating bootstrap completion thread
[0001.741] top of bootstrap2()
[0001.743] CPU: ARM Cortex A57
[0001.746] CPU: MIDR: 0x411FD071, MPIDR: 0x80000000
[0001.751] initializing platform
[0001.758] Manufacturer: MF = 0xc2, ID MSB = 0x25
[0001.763] ID LSB = 0x36, ID-CFI len = 194 bytes
[0001.767] Macronix QSPI chip present
[0001.771] SPI device register
[0001.774] init boot device
[0001.776] allocating memory for boot device(SPI)
[0001.781] registering boot device
[0001.799] QSPI bdev is already initialized
[0001.803] Enable APE clock
[0001.806] Un-powergate APE partition
[0001.809] of_register: registering tegra_udc to of_hal
[0001.814] of_register: registering inv20628-driver to of_hal
[0001.820] of_register: registering ads1015-driver to of_hal
[0001.826] of_register: registering lp8557-bl-driver to of_hal
[0001.831] of_register: registering bq2419x_charger to of_hal
[0001.837] of_register: registering bq27441_fuel_gauge to of_hal
[0001.848] gpio framework initialized
[0001.852] of_register: registering tca9539_gpio to of_hal
[0001.857] of_register: registering tca9539_gpio to of_hal
[0001.863] of_register: registering i2c_bus_driver to of_hal
[0001.868] of_register: registering i2c_bus_driver to of_hal
[0001.874] of_register: registering i2c_bus_driver to of_hal
[0001.879] pmic framework initialized
[0001.883] of_register: registering max77620_pmic to of_hal
[0001.888] regulator framework initialized
[0001.892] of_register: registering tps65132_bl_driver to of_hal
[0001.898] initializing target
[0001.904] gpio_driver_register: register ‘tegra_gpio_driver’ driver
[0001.912] board ID = D78, board SKU = 0
[0001.916] Skipping Z3!
[0001.921] fixed regulator driver initialized
[0001.938] initializing OF layer
[0001.941] NCK carveout not present
[0001.945] Skipping dts_overrides
[0001.949] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0001.965] I2C Bus Init done
[0001.968] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0001.978] I2C Bus Init done
[0001.981] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0001.991] I2C Bus Init done
[0001.994] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0002.004] I2C Bus Init done
[0002.007] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0002.017] I2C Bus Init done
[0002.020] of_children_init: Ops found for compatible string maxim,max77620
[0002.030] max77620_init using irq 118
[0002.035] register ‘maxim,max77620’ pmic
[0002.039] gpio_driver_register: register ‘max77620-gpio’ driver
[0002.046] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0002.056] I2C Bus Init done
[0002.060] NCK carveout not present
[0002.069] Find /i2c@7000c000’s alias i2c0
[0002.073] get eeprom at 1-a0, size 256, type 0
[0002.082] Find /i2c@7000c500’s alias i2c2
[0002.086] get eeprom at 3-a0, size 256, type 0
[0002.090] get eeprom at 3-ae, size 256, type 0
[0002.094] pm_ids_update: Updating 1,a0, size 256, type 0
[0002.100] I2C slave not started
[0002.103] I2C write failed
[0002.105] Writing offset failed
[0002.108] eeprom_init: EEPROM read failed
[0002.112] pm_ids_update: eeprom init failed
[0002.116] pm_ids_update: Updating 3,a0, size 256, type 0
[0002.146] pm_ids_update: The pm board id is 3448-0000-402
[0002.153] Adding plugin-manager/ids/3448-0000-402=/i2c@7000c500:module@0x50
[0002.162] pm_ids_update: pm id update successful
[0002.166] pm_ids_update: Updating 3,ae, size 256, type 0
[0002.196] pm_ids_update: The pm board id is 3449-0000-400
[0002.203] Adding plugin-manager/ids/3449-0000-400=/i2c@7000c500:module@0x57
[0002.210] pm_ids_update: pm id update successful
[0002.241] eeprom_get_mac: EEPROM invalid MAC address (all 0xff)
[0002.247] shim_eeprom_update_mac:267: Failed to update 0 MAC address in DTB
[0002.255] eeprom_get_mac: EEPROM invalid MAC address (all 0xff)
[0002.260] shim_eeprom_update_mac:267: Failed to update 1 MAC address in DTB
[0002.269] updating /chosen/nvidia,ethernet-mac node 48:b0:2d:d3:ea:c3
[0002.275] Plugin Manager: Parse ODM data 0x000a4000
[0002.287] shim_cmdline_install: /chosen/bootargs:
earlycon=uart8250,mmio32,0x70006000
[0002.302] Find /i2c@7000c000’s alias i2c0
[0002.306] get eeprom at 1-a0, size 256, type 0
[0002.315] Find /i2c@7000c500’s alias i2c2
[0002.318] get eeprom at 3-a0, size 256, type 0
[0002.323] get eeprom at 3-ae, size 256, type 0
[0002.327] pm_ids_update: Updating 1,a0, size 256, type 0
[0002.332] I2C slave not started
[0002.335] I2C write failed
[0002.338] Writing offset failed
[0002.341] eeprom_init: EEPROM read failed
[0002.345] pm_ids_update: eeprom init failed
[0002.349] pm_ids_update: Updating 3,a0, size 256, type 0
[0002.379] pm_ids_update: The pm board id is 3448-0000-402
[0002.386] Adding plugin-manager/ids/3448-0000-402=/i2c@7000c500:module@0x50
[0002.392] pm_ids_update: pm id update successful
[0002.397] pm_ids_update: Updating 3,ae, size 256, type 0
[0002.427] pm_ids_update: The pm board id is 3449-0000-400
[0002.433] Adding plugin-manager/ids/3449-0000-400=/i2c@7000c500:module@0x57
[0002.440] pm_ids_update: pm id update successful
[0002.471] Add serial number:1420623025684 as DT property
[0002.478] Applying platform configs
[0002.485] platform-init is not present. Skipping
[0002.489] calling apps_init()
[0002.495] Couldn’t find GPT header
[0002.500] Proceeding to Cold Boot
[0002.503] starting app android_boot_app
[0002.507] Device state: unlocked
[0002.510] display console init
[0002.518] could not find regulator
[0002.542] hdmi cable not connected
[0002.545] is_hdmi_needed: HDMI not connected, returning false
[0002.550] hdmi is not connected
[0002.554] sor0 is not supporDT entry for leds-pwm not found
t[0002.562] ed
[0002.564] display_console_init: no valid display out_type
[0002.572] subnode volume_up is not found !
[0002.576] subnode back is not found !
[0002.579] subnode volume_down is not found !
[0002.583] subnode menu is not found !
[0002.587] Gpio keyboard init success
[0002.667] found decompressor handler: lz4-legacy
[0002.682] decompressing blob (type 1)…
[0002.748] display_resolution: No display init
[0002.752] Failed to retrieve display resolution
[0002.757] Could not load/initialize BMP blob…ignoring
[0002.762] -------> se_aes_verify_sbk_clear: 747
[0002.767] se_aes_verify_sbk_clear: Error
[0002.770] SE operation failed
[0002.773] bl_battery_charging: connected to external power supply
[0002.782] display_console_ioctl: No display init
[0002.787] switch_backlight failed
[0002.793] device_query_partition_size: failed to open partition spiflash0:MSC !
[0002.800] MSC Partition not found
[0002.807] device_query_partition_size: failed to open partition spiflash0:USP !
[0002.814] USP partition read failed!
[0002.817] blob_init: blob-partition USP header read failed
[0002.823] android_boot Unable to update recovery partition
[0002.828] kfs_getpartname: name = LNX
[0002.832] Loading kernel from LNX
[0002.841] Found 19 BFS partitions in “spiflash0”
[0003.162] Failed to validate boot-image
[0003.166] Set to failover in the next boot
[0003.170] fail control word = 0xb08364bb
[0003.173] Rebooting …
[0000.157] [L4T TegraBoot] (version 00.00.2018.01-l4t-e82258de)
[0000.162] Processing in cold boot mode Bootloader 2
[0000.167] A02 Bootrom Patch rev = 1023
[0000.171] Power-up reason: software reset
[0000.174] No Battery Present
[0000.177] pmic max77620 reset reason
[0000.180] pmic max77620 NVERC : 0x0
[0000.184] RamCode = 0
[0000.186] Platform has DDR4 type RAM
[0000.189] max77620 disabling SD1 Remote Sense
[0000.193] Setting DDR voltage to 1125mv
[0000.197] Serial Number of Pmic Max77663: 0xe3d61
[0000.205] Entering ramdump check
[0000.208] Get RamDumpCarveOut = 0x0
[0000.211] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8
[0000.216] Last reboot was clean, booting normally!
[0000.221] Sdram initialization is successful
[0000.225] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0000.231] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0000.237] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0000.243] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0000.249] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0000.255] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0000.260] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0000.266] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0000.282] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0000.288] Platform-DebugCarveout: 0
[0000.292] Nck Carveout Base=0x00000000ff080000 Size=0x00200000
[0000.297] Non secure mode, and RB not enabled.
[0000.302] BoardID = 3448, SKU = 0x0
[0000.305] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.309] Nano-SD: checking PT table on QSPI …
[0000.313] Read PT from (2:0)
[0000.329] Using BFS PT to query partitions
[0000.334] Loading Tboot-CPU binary
[0000.363] Verifying TBC in OdmNonSecureSBK mode
[0000.373] Bootloader load address is 0xa0000000, entry address is 0xa0000258
[0000.380] Bootloader downloaded successfully.
[0000.384] Downloaded Tboot-CPU binary to 0xa0000258
[0000.389] MAX77620_GPIO5 configured
[0000.392] CPU power rail is up
[0000.395] CPU clock enabled
[0000.399] Performing RAM repair
[0000.402] Updating A64 Warmreset Address to 0xa00002e9
[0000.407] BoardID = 3448, SKU = 0x0
[0000.410] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.414] Nano-SD: checking PT table on QSPI …
[0000.418] Loading NvTbootBootloaderDTB
[0000.484] Verifying NvTbootBootloaderDTB in OdmNonSecureSBK mode
[0000.556] Bootloader DTB Load Address: 0x83000000
[0000.561] BoardID = 3448, SKU = 0x0
[0000.564] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.568] Nano-SD: checking PT table on QSPI …
[0000.572] Loading NvTbootKernelDTB
[0000.638] Verifying NvTbootKernelDTB in OdmNonSecureSBK mode
[0000.710] Kernel DTB Load Address: 0x83100000
[0000.714] BoardID = 3448, SKU = 0x0
[0000.717] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.721] Nano-SD: checking PT table on QSPI …
[0000.727] Loading cboot binary
[0000.843] Verifying EBT in OdmNonSecureSBK mode
[0000.885] Bootloader load address is 0x92c00000, entry address is 0x92c00258
[0000.892] Bootloader downloaded successfully.
[0000.896] BoardID = 3448, SKU = 0x0
[0000.899] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.903] Nano-SD: checking PT table on QSPI …
[0000.907] PT: Partition NCT NOT found !
[0000.911] Warning: Find Partition via PT Failed
[0000.915] Next binary entry address: 0x92c00258
[0000.920] BoardId: 3448
[0000.924] Overriding pmu board id with proc board id
[0000.929] Display board id is not available
[0000.933] BoardID = 3448, SKU = 0x0
[0000.937] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.941] Nano-SD: checking PT table on QSPI …
[0001.046] Verifying SC7EntryFw in OdmNonSecureSBK mode
[0001.102] /bpmp deleted
[0001.104] SC7EntryFw header found loaded at 0xff700000
[0001.292] OVR2 PMIC
[0001.294] Bpmp FW successfully loaded
[0001.297] BoardID = 3448, SKU = 0x0
[0001.301] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0001.304] Nano-SD: checking PT table on QSPI …
[0001.310] WB0 init successfully at 0xff780000
[0001.314] Set NvDecSticky Bits
[0001.318] GSC2 address ff53fffc value c0edbbcc
[0001.324] GSC MC Settings done
[0001.327] BoardID = 3448, SKU = 0x0
[0001.330] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0001.334] Nano-SD: checking PT table on QSPI …
[0001.339] TOS Image length 53680
[0001.342] Monitor size 53680
[0001.345] OS size 0
[0001.360] Secure Os AES-CMAC Verification Success!
[0001.365] TOS image cipher info: plaintext
[0001.369] Loading and Validation of Secure OS Successful
[0001.385] SC7 Entry Firmware - 0xff700000, 0x4000
[0001.389] NvTbootPackSdramParams: start.
[0001.394] NvTbootPackSdramParams: done.
[0001.398] Tegraboot started after 84879 us
[0001.402] Basic modules init took 883408 us
[0001.406] Sec Bootdevice Read Time = 12 ms, Read Size = 61 KB
[0001.411] Sec Bootdevice Write Time = 0 ms, Write Size = 0 KB
[0001.417] Next stage binary read took 102860 us
[0001.421] Carveout took -126356 us
[0001.425] CPU initialization took 487208 us
[0001.429] Total time taken by TegraBoot 1347120 us

[0001.433] Starting CPU & Halting co-processor

I just remembered that i can also provide the export logs form the SDKM when it failed

YES.
Please dump both log from SDK Manager and serial console during flashing.

Here is the terminal information during the SDKM process, it failed:

Terminal: 09:50:06 INFO: TensorRT on Target - target: Found file
/home/nurise/Downloads/nvidia/sdkm_downloads/libnvparsers-dev_8.2.1-1+cuda10.2_arm64.deb
with correct checksum, skip downloading.
09:50:06 INFO: TensorRT on Target - target: verifying checksum of
/home/nurise/Downloads/nvidia/sdkm_downloads/libnvinfer-doc_8.2.1-1+cuda10.2_all.deb
09:50:06 INFO: TensorRT on Target - target: Found file
/home/nurise/Downloads/nvidia/sdkm_downloads/libnvinfer-bin_8.2.1-1+cuda10.2_arm64.deb
with correct checksum, skip downloading.
09:50:06 INFO: TensorRT on Target - target: verifying checksum of
/home/nurise/Downloads/nvidia/sdkm_downloads/libnvinfer-samples_8.2.1-1+cuda10.2_all.deb
09:50:06 INFO: TensorRT on Target - target: Found file
/home/nurise/Downloads/nvidia/sdkm_downloads/libnvinfer-doc_8.2.1-1+cuda10.2_all.deb
with correct checksum, skip downloading.
09:50:06 INFO: TensorRT on Target - target: verifying checksum of
/home/nurise/Downloads/nvidia/sdkm_downloads/tensorrt_8.2.1.9-1+cuda10.2_arm64.deb
09:50:06 INFO: TensorRT on Target - target: Found file
/home/nurise/Downloads/nvidia/sdkm_downloads/tensorrt_8.2.1.9-1+cuda10.2_arm64.deb
with correct checksum, skip downloading.
09:50:06 INFO: TensorRT on Target - target: verifying checksum of
/home/nurise/Downloads/nvidia/sdkm_downloads/python3-libnvinfer_8.2.1-1+cuda10.2_arm64.deb
09:50:06 INFO: TensorRT on Target - target: Found file
/home/nurise/Downloads/nvidia/sdkm_downloads/python3-libnvinfer_8.2.1-1+cuda10.2_arm64.deb
with correct checksum, skip downloading.
09:50:06 INFO: TensorRT on Target - target: verifying checksum of
/home/nurise/Downloads/nvidia/sdkm_downloads/python3-libnvinfer-dev_8.2.1-1+cuda10.2_arm64.deb
09:50:06 INFO: TensorRT on Target - target: Found file
/home/nurise/Downloads/nvidia/sdkm_downloads/python3-libnvinfer-dev_8.2.1-1+cuda10.2_arm64.deb
with correct checksum, skip downloading.
09:50:06 INFO: TensorRT on Target - target: verifying checksum of
/home/nurise/Downloads/nvidia/sdkm_downloads/graphsurgeon-tf_8.2.1-1+cuda10.2_arm64.deb
09:50:06 INFO: TensorRT on Target - target: Found file
/home/nurise/Downloads/nvidia/sdkm_downloads/graphsurgeon-tf_8.2.1-1+cuda10.2_arm64.deb
with correct checksum, skip downloading.
09:50:06 INFO: TensorRT on Target - target: verifying checksum of
/home/nurise/Downloads/nvidia/sdkm_downloads/uff-converter-tf_8.2.1-1+cuda10.2_arm64.deb
09:50:06 INFO: TensorRT on Target - target: Found file
/home/nurise/Downloads/nvidia/sdkm_downloads/uff-converter-tf_8.2.1-1+cuda10.2_arm64.deb
with correct checksum, skip downloading.
09:50:06 INFO: VisionWorks on Target - target: verifying checksum of
/home/nurise/Downloads/nvidia/sdkm_downloads/libvisionworks-repo_1.6.0.501_arm64.deb
09:50:07 INFO: VisionWorks on Target - target: Found file
/home/nurise/Downloads/nvidia/sdkm_downloads/libvisionworks-repo_1.6.0.501_arm64.deb
with correct checksum, skip downloading.
09:50:07 INFO: VisionWorks on Target - target: verifying checksum of
/home/nurise/Downloads/nvidia/sdkm_downloads/libvisionworks-sfm-repo_0.90.4.501_arm64.deb
09:50:08 INFO: VisionWorks on Target - target: Found file
/home/nurise/Downloads/nvidia/sdkm_downloads/libvisionworks-sfm-repo_0.90.4.501_arm64.deb
with correct checksum, skip downloading.
09:50:08 INFO: VisionWorks on Target - target: verifying checksum of
/home/nurise/Downloads/nvidia/sdkm_downloads/libvisionworks-tracking-repo_0.88.2.501_arm64.deb
09:50:08 INFO: VisionWorks on Target - target: Found file
/home/nurise/Downloads/nvidia/sdkm_downloads/libvisionworks-tracking-repo_0.88.2.501_arm64.deb
with correct checksum, skip downloading.
09:50:08 INFO: NVIDIA Container Runtime with Docker integration (Beta)

  • target: verifying checksum of
    /home/nurise/Downloads/nvidia/sdkm_downloads/nvidia-container-csv-cuda_10.2.460-1_arm64.deb
    09:50:08 INFO: NVIDIA Container Runtime with Docker integration (Beta)
  • target: Found file
    /home/nurise/Downloads/nvidia/sdkm_downloads/nvidia-container-csv-cuda_10.2.460-1_arm64.deb
    with correct checksum, skip downloading.
    09:50:08 INFO: NVIDIA Container Runtime with Docker integration (Beta)
  • target: verifying checksum of
    /home/nurise/Downloads/nvidia/sdkm_downloads/nvidia-container-csv-cudnn_8.2.1.32-1+cuda10.2_arm64.deb
    09:50:08 INFO: NVIDIA Container Runtime with Docker integration (Beta)
  • target: Found file
    /home/nurise/Downloads/nvidia/sdkm_downloads/nvidia-container-csv-cudnn_8.2.1.32-1+cuda10.2_arm64.deb
    with correct checksum, skip downloading.
    09:50:08 INFO: NVIDIA Container Runtime with Docker integration (Beta)
  • target: verifying checksum of
    /home/nurise/Downloads/nvidia/sdkm_downloads/nvidia-container-csv-tensorrt_8.2_arm64.deb
    09:50:08 INFO: NVIDIA Container Runtime with Docker integration (Beta)
  • target: Found file
    /home/nurise/Downloads/nvidia/sdkm_downloads/nvidia-container-csv-tensorrt_8.2_arm64.deb
    with correct checksum, skip downloading.
    09:50:08 INFO: NVIDIA Container Runtime with Docker integration (Beta)
  • target: verifying checksum of
    /home/nurise/Downloads/nvidia/sdkm_downloads/nvidia-container-csv-visionworks_1.6.0.501_arm64.deb
    09:50:08 INFO: NVIDIA Container Runtime with Docker integration (Beta)
  • target: Found file
    /home/nurise/Downloads/nvidia/sdkm_downloads/nvidia-container-csv-visionworks_1.6.0.501_arm64.deb
    with correct checksum, skip downloading.
    09:50:08 INFO: NVIDIA Container Runtime with Docker integration (Beta)
  • target: verifying checksum of
    /home/nurise/Downloads/nvidia/sdkm_downloads/libnvidia-container0_0.10.0+jetpack_arm64.deb
    09:50:08 INFO: NVIDIA Container Runtime with Docker integration (Beta)
  • target: Found file
    /home/nurise/Downloads/nvidia/sdkm_downloads/libnvidia-container0_0.10.0+jetpack_arm64.deb
    with correct checksum, skip downloading.
    09:50:08 INFO: NVIDIA Container Runtime with Docker integration (Beta)
  • target: verifying checksum of
    /home/nurise/Downloads/nvidia/sdkm_downloads/libnvidia-container1_1.7.0-1_arm64.deb
    09:50:08 INFO: NVIDIA Container Runtime with Docker integration (Beta)
  • target: Found file
    /home/nurise/Downloads/nvidia/sdkm_downloads/libnvidia-container1_1.7.0-1_arm64.deb
    with correct checksum, skip downloading.
    09:50:08 INFO: NVIDIA Container Runtime with Docker integration (Beta)
  • target: verifying checksum of
    /home/nurise/Downloads/nvidia/sdkm_downloads/libnvidia-container-tools_1.7.0-1_arm64.deb
    09:50:08 INFO: NVIDIA Container Runtime with Docker integration (Beta)
  • target: Found file
    /home/nurise/Downloads/nvidia/sdkm_downloads/libnvidia-container-tools_1.7.0-1_arm64.deb
    with correct checksum, skip downloading.
    09:50:08 INFO: NVIDIA Container Runtime with Docker integration (Beta)
  • target: verifying checksum of
    /home/nurise/Downloads/nvidia/sdkm_downloads/nvidia-container-toolkit_1.7.0-1_arm64.deb
    09:50:08 INFO: NVIDIA Container Runtime with Docker integration (Beta)
  • target: Found file
    /home/nurise/Downloads/nvidia/sdkm_downloads/nvidia-container-toolkit_1.7.0-1_arm64.deb
    with correct checksum, skip downloading.
    09:50:08 INFO: NVIDIA Container Runtime with Docker integration (Beta)
  • target: verifying checksum of
    /home/nurise/Downloads/nvidia/sdkm_downloads/nvidia-container-runtime_3.7.0-1_all.deb
    09:50:08 INFO: NVIDIA Container Runtime with Docker integration (Beta)
  • target: Found file
    /home/nurise/Downloads/nvidia/sdkm_downloads/nvidia-container-runtime_3.7.0-1_all.deb
    with correct checksum, skip downloading.
    09:50:08 INFO: NVIDIA Container Runtime with Docker integration (Beta)
  • target: verifying checksum of
    /home/nurise/Downloads/nvidia/sdkm_downloads/nvidia-docker2_2.8.0-1_all.deb
    09:50:08 INFO: NVIDIA Container Runtime with Docker integration (Beta)
  • target: Found file
    /home/nurise/Downloads/nvidia/sdkm_downloads/nvidia-docker2_2.8.0-1_all.deb
    with correct checksum, skip downloading.
    09:50:09 INFO: Multimedia API - target: verifying checksum of
    /home/nurise/Downloads/nvidia/sdkm_downloads/nvidia-l4t-jetson-multimedia-api_32.7.4-20230608212426_arm64.deb
    09:50:09 INFO: CUDA Toolkit for L4T - target: Found file
    /home/nurise/Downloads/nvidia/sdkm_downloads/cuda-repo-l4t-10-2-local_10.2.460-1_arm64.deb
    with correct checksum, skip downloading.
    09:50:09 INFO: Nsight Systems CLI - target: verifying checksum of
    /home/nurise/Downloads/nvidia/sdkm_downloads/nsight-systems-linux-tegra-public-2021.5.4.19-e642d4b_2021.5.4.19-1_arm64.deb
    09:50:10 INFO: Multimedia API - target: Found file
    /home/nurise/Downloads/nvidia/sdkm_downloads/nvidia-l4t-jetson-multimedia-api_32.7.4-20230608212426_arm64.deb
    with correct checksum, skip downloading.
    09:50:11 INFO: Nsight Systems CLI - target: Found file
    /home/nurise/Downloads/nvidia/sdkm_downloads/nsight-systems-linux-tegra-public-2021.5.4.19-e642d4b_2021.5.4.19-1_arm64.deb
    with correct checksum, skip downloading.
    09:50:13 INFO: TensorRT on Target - target: Found file
    /home/nurise/Downloads/nvidia/sdkm_downloads/libnvinfer-samples_8.2.1-1+cuda10.2_all.deb
    with correct checksum, skip downloading.
    09:50:15 INFO: CUDA Cross Compile Package on Host - host: Found file
    /home/nurise/Downloads/nvidia/sdkm_downloads/cuda-repo-cross-aarch64-ubuntu1804-10-2-local_10.2.460-1_all.deb
    with correct checksum, skip downloading.
    09:50:34 INFO: File System and OS - target_image: Found file
    /home/nurise/Downloads/nvidia/sdkm_downloads/Tegra_Linux_Sample-Root-Filesystem_R32.7.4_aarch64.tbz2
    with correct checksum, skip downloading.
    09:50:40 INFO: CUDA on Host - host: Found file
    /home/nurise/Downloads/nvidia/sdkm_downloads/cuda-repo-ubuntu1804-10-2-local_10.2.460-450.115-1_amd64.deb
    with correct checksum, skip downloading.

Then i pressed the retry button and:

09:53:42 SUMMARY: Nsight Systems - host: Install completed successfully.
09:54:36 SUMMARY: Drivers for Jetson - target_image: Install completed
successfully.
09:59:21 SUMMARY: Flash Jetson Nano - flash: First Error: Depends on
failed component

The FTDI logs:
[0175.679] Enabled early print
[0175.682] [L4T TegraBoot] (version ¾Ð‡0¹4¢úú 9@‚²Ûó/ñEŒ›ÞÞþaÅ)
[0175.688] Processing in recovery mode
[0175.691] A02 Bootrom Patch rev = 1023
[0175.695] Power-up reason: pmc por
[0175.698] Established communication link with host
[0176.904] NvTbootI2cWrite(): error code 0x00045100 Error while
starting write transaction
[0176.912] NvTbootI2cDeviceRead(): error code 0x00045001 Error while
sending the offset to slave
[0176.921] NvTbootI2c: Read failed for slave 0xac, offset 0x00 with
error code 0x00045001

Please just use the export button of SDK Manager and put the archive here.
Also put the serial console log as a text file here.

SDKM_logs_JetPack_4.6.4_Linux_for_Jetson_Nano_modules_2023-11-23_10-26-37.zip (117.4 KB)
serial_log.pdf (59.6 KB)

The serial log is strange, i checked and the baud rate is correct (115200). If i copy and past it here, it gives the information i mentioned:

[0175.679] Enabled early print
[0175.682] [L4T TegraBoot] (version ¾Ð‡0¹4¢úú 9@‚²Ûó/ñEŒ›ÞÞþaÅ)
[0175.688] Processing in recovery mode
[0175.691] A02 Bootrom Patch rev = 1023
[0175.695] Power-up reason: pmc por
[0175.698] Established communication link with host
[0176.904] NvTbootI2cWrite(): error code 0x00045100 Error while
starting write transaction
[0176.912] NvTbootI2cDeviceRead(): error code 0x00045001 Error while
sending the offset to slave
[0176.921] NvTbootI2c: Read failed for slave 0xac, offset 0x00 with
error code 0x00045001

Hi,

Looks like contents of EEPROM on your module is somehow corrupted.
You may try methods in the link shown below to bypass reading EEPROM info during flashing:

It worked, thank you.

I used everything new, (probably made no difference), reformated an old pc with linux 18.04, new sd card, and new sdk manager, Recovery mode connected and also tried before the steps you suggested. And it worked, thanks.

Is the default 18.04, or just installed that version because of the host pc OS?

Thank you one again

default ubuntu 18.04 if using jetpack4.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.