Installing SDK Componets by sdkmanager after flashing with initrd

[Note]

Hi,
After I flash Jetson xavier NX following these commands:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash jetson-xavier-nx-devkit-qspi internal

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --external-device nvme0n1p1 -S 200GiB -c ./tools/kernel_flash/flash_l4t_nvme_viansight.xml --external-only --append flash jetson-xavier-nx-devkit-emmc external

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only

I continue installing SDK components using SDKmanager. However, I get the error below:

I think I’ve not configure Username and Password yet, so I also add User definition by using “l4t_create_default_user.sh” in the next try, but the issue still remains.

[WayneWWW]

You should check the status on your jetson. A IP will not just come out without reason.

If the device actually not boot up, then it won’t be able to run ssh.

If the usb device mode does not work, then ssh on this IP will fail either.

[Note]

I think I’m in the 1st situation, because:

• I can not interact with Jetson by minicom.
• When I normally flash Jetson on skdmanager and install SDK components via USB connection, the installation process runs smoothly.

Would you give me some advices why the device doesn’t boot up when flashing that way ?

[WayneWWW]

You can dump what you see on the minicom first right after device power on.

If you see nothing, then it must be your setup of serial console has problem. I remember already told about this few days ago.

[WayneWWW]

BTW, I don’t actually know how those commands which you are using coming from.

Sdkmanager can flash your NX + nvme too. Why ran a custom command? Which workflow is your command based on?

[Note]

According to this Flashing Support — Jetson Linux<br/>Developer Guide 34.1 documentation

Use l4t_initrd_flash.sh to flash internal or external media connected to a Jetson device

I want the Jetson to detect external camera devices so I flash Jetson by that way.

[WayneWWW]

Please read the README file in your initrd flash directory… there are fixed usecase for this tool.

[Note]

I actually use the above flashing workflow according to the Example 2 in the 10th Workflow in README_initrd_flash.txt.
In the end of the flasing log, it also says “SSH ready”:

[ 232]: l4t_flash_from_kernel: Successfully flash the external device
[ 232]: l4t_flash_from_kernel: Flashing success
Reboot target
Run command: sync; nohup reboot &>/dev/null & exit on root@fe80::1%usb0
SSH ready
Success
Cleaning up…

[WayneWWW]

So what is the minicom result? It cannot be nothing.

I already told the reason in your another post before.

[Note]

The minicom don’t show anything. If the Jetson board is flashed successfuly and boot up, it should request to enter username, password :(

In the post before, I get the issue that I can’t ssh Jetson via ethernet port because IP addr is not generated , then it is solved by using USB-microUSB for connection. But even in that case, flashing by SDKmanager, SDKmanager can still install Components via USB connection.

In this case, flashing with initrd, the flashing process logging looks fine but Jetson board seems not boot up.

[WayneWWW]

Hi,

Is this xavier nx or xavier AGX issue?

[WayneWWW]

If this is xavier nx, then you are not dumping the serial console log.

ttyACM0 is the kernel log from micro usb port. The real serial console log needs to be dumped by using usb-ttl cable. And the node name will be ttyUSB0.

I have no surprise about ttyACM0 does not show anything. I need you to dump correct log from correct pin.

[Note]

Hi, it is xavier NX.
The Jetson I have here is configured, so I can not find any expansion pin :(
But if using USB-TTL cable is the only way to know Jetson boots up or not, I try to contact the one configuring it.
Thank you.

[WayneWWW]

I don’t know what does that mean “Jetson I have here is configured, so I can not find any expansion pin”. Are you talking about this is a custom board?

If so, please contact the board vendor to see if they leave any pinout for UART serial console.