Hi,
I am trying to boot custom board with agx-xavier som from ssd.
I am following https://docs.nvidia.com/jetson/archives/l4t-archived/l4t-3261/index.html#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/flashing.html#wwpID0E0PI0HA for the same. I am not able to flash the ssd. Is there any additional changes to be done for custom board?
Regards
Ann Rose Antony
Hi
sdkmanager now provides the options for NVMe SSD directly. How about trying that first?
Hai,
Thanks for the response.
I was able to flash the agx devkit with the ssd image.
I used the below command :
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --external-device nvme0n1p1 -c ./tools/kernel_flash/flash_l4t_nvme.xml -S 8GiB --showlogs <conf file name> nvme0n1p1
Able to create the ssd image.
After that I used the following command :
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --external-device nvme0n1p1 -c ./tools/kernel_flash/flash_l4t_nvme.xml -S 8GiB --showlogs nvme0n1p1
Flashing is not happening and the below logs are coming below:-
> ***************************************
> * *
> * Step 3: Start the flashing process *
> * *
> ***************************************
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Waiting for target to boot-up...
> Timeout
> Cleaning up...
Could you please help me to figure out issue?
Is any specific dts entries are required?
I didn’t notice this is custom board. Please try with initrd flash on emmc case first.
Hi,
I have tried initrd flash on emmc and got the below log:
Log will be saved to Linux_for_Tegra/initrdlog/flash_1-3_0_20220117-171718.log
Ongoing processes: 10255
Ongoing processes: 10255
Ongoing processes: 10255
Ongoing processes: 10255
Ongoing processes: 10255
Ongoing processes: 10255
Ongoing processes: 10255
Ongoing processes: 10255
Ongoing processes: 10255
Ongoing processes: 10255
Ongoing processes: 10255
Ongoing processes: 10255
Ongoing processes: 10255
Ongoing processes: 10255
Ongoing processes: 10255
Ongoing processes:
Flash complete (WITH FAILURES)
Gave the command
cat initrdlog/flash_1-3_0_20220117-171718.log
Then the log ends like
***************************************
* *
* Step 3: Start the flashing process *
* *
***************************************
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Timeout
Cleaning up...
Could you please help me to figure out the issue
Does your custom board have usb0 as usb device mode?
Yes in custom board we are using the usb0 as device mode.
Hi,
@WayneWWW COuld you please help me out on this issue.
I am not even able to flash the devkit SSD image to the custom board.
Thanks and Regards
Ann Rose Antony
Are you able to see ttyACM0 on your host after you boot into system?
ttyACM is not working after bootup.
Please find a AGX Xavier devkit and test it with your host first.
Make sure your host is able to see this interface. The hardware connection is the flash usb port and the host.
Hi @WayneWWW ,
In the AGX Xavier devkit we are able to detect the ACM port.
But in the custom board we are not able to get the ACM port after boot-up.
Regards,
Ann Rose Antony
When I was trying to flash the devkit image to custom board, the flashing gets timed out by giving the below log:
Waiting for target to boot-up…
As a part of debugging I figured out that inside the script “l4t_initrd_flash_internal.sh” , one if condition is always getting failed.
if ls /dev/sd* 1> /dev/null 2>&1;
I guess since the custom board is not being detected in the PC we are not able to flash the SSD to the custom boards.
Regards
Ann Rose Antony
Hi @WayneWWW ,
Is there anyway other than checking for device and flash. I meant prior for the bootup can we flash the SSD and boot from the SSD.
It would be very much helpful if you could give me some pointers to move forward.
Thanks and Regards
Ann Rose Antony
I think it is obvious that you can firstly validate whether your custom board can support usb device mode or not…
Kernel needs to support it first.
Thanks for your responses.
Board is not supporting the device mode currently. We are working on the same.
I hope after the device mode support we will be able to do the SSD flashing.
Thanks and Regards
Ann Rose Antony.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.