Problem flashing L4T 36.2 on new jetson orin nano module

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin Nano
1

I have had a lot of issues flashing a new jetson orin nano module with our custom carrier board. The older jetson modules with the exact same design of carrier board and same type of nvme ssd flashes without issues. That’s why after failing to flash so many times on this new one I used the exact same script to flash an older one and got it to work right away. I have attached four log files:
flash_fail/success.log - the log from the flash script on the host pc
flash_fail/success_uart.log - the debug serial output log taken from using minicom.

Where the success ones are from the older module which worked and the failed ones are from the new module that I have not yet gotten to work.

Thanks in advance,
Fredrik

2

Looks like the log attachments are missing.

3

I had some issues with uploading them, here they are:
flash_success.log (49.3 KB)

flash_fail_uart.log (76.5 KB)

flash_success_uart.log (150.2 KB)

flash_fail.log (9.4 KB)

4

When running with the working case, usb drivers are up to enable USB device mode.

insmod /lib/modules/5.15.122-tegra/kernel/drivers/thermal/tegra/tegra-bpmp-thermal.ko
insmod /lib/modules/5.15.122-tegra/kernel/drivers/hwmon/pwm-fan.ko
insmod /lib/modules/5.15.122-tegra/kernel/drivers/usb/gadget/libcomposite.ko
insmod /lib/modules/5.15.122-tegra/kernel/drivers/usb/typec/typec.ko
insmod /lib/modules/5.15.122-tegra/kernel/drivers/usb/typec/ucsi/typec_ucsi.ko
insmod /lib/modules/5.15.122-tegra/kernel/drivers/usb/typec/ucsi/ucsi_ccg.ko
insmod /lib/modules/5.15.122-tegra/kernel/drivers/usb/gadget/udc/tegra-xudc.ko
insmod /lib/modules/5.15.122-tegra/kernel/net/ipv6/ipv6.ko

However, in your NG log, this does not happen.

Are you using the same BSP package to flash these modules?

5

Yes the same exact BSP package. I actually think the failing one times out before it even comes to that part, the row 1235, meaning this one “Jetson System firmware version 36.2.0-gcid-34956989 date 2023-11-30T18:35:35+00:” shows up after it has already timed out on the host side.

6

Hi,

The “Waiting for target to boot-up…” on host side is purely waiting for USB device mode to come up.

So currently the cause of your issue is somehow the whole USB related drivers are not up.

Are you able to flash into USB drive instead of NVMe as a debug method first? I would like to see the result based on it.

7

Hi,

Oh okay. Sadly the carrier board does not have any USB ports that I can use for a USB drive. We have two USB-C ports, one of which is used for flashing and one is the debug port.

8

Let’s clarify what things do you have there first.

  1. Do you have other NVMe SSD?

  2. Do you have the NV devkit carrier board there?

9
  1. Yes I have other NVMe SSD:s.
  2. Yes I have the NV devkit carrier board as well.

I just swapped out the SSD for the one that was on the working jetson and currently trying to flash it with that one on it instead, if this works I could try a completely new SSD as well?

10

Yes, doing some cross validation would help.

I would say trying these

  1. On your custom board
    → Try different SSD first.

  2. On NV dekvit
    → Put the “NG SSD” from (1) and test if they also failed on NV devkit.

11

Hi again,

I tried a new SSD and it worked right away so must be something wrong with the other one..? They are from two different brands but the same size etc.. Trying to figure out if the NG SSD is useless or if it can be salvaged somehow.