I flashed the NVME according to the contents below.
The actual command that was executed is as follows
However, an error occurred as shown below and it did not complete normally.
bash: cannot set terminal process group (-1): Inappropriate ioctl for device bash: no job control in this shell bash-5.1#
The differences between AGX Orin EVK and Custom Board are as follows:
Change UPHY settings
USB Port
I was using flash on the internal eMMC without any problems via flash.sh
Please directly get the serial console log from UART during flash.
This log will tell what is wrong during flash.
I’m sharing the console log so please review it.
insmod /lib/modules/5.15.136-tegra/kernel/drivers/nvme/host/nvme-core.ko
Please attach your “full log” since the start of the flash attempt. Not such partial log.
Also, I mean attach a file. Not copy & paste.
Full log is attached as TEXT FILE since the start of the flash attempt.
AGX ORIN’s CONSOLEssd_flash_custom_board_log.txt (85.5 KB)
PC’s TERMINAL LOGssd_flash_PC_log.txt (289.4 KB)
Please review..
Initrd flash requires the usb device mode to work fine. And that thing is not working according to your log.
What is the design of your custom board of USB2-0 there? Does that one support USB device mode?
It is not same as flash.sh case which flashes eMMC on the board. Also, what I am talking about is not recovery mode either.
Below is part of the USB configuration of the custom board.
Only USB0 is used for flash purposes.
Could you please advise on how to support USB Device mode?
please read document to modify device tree. Default one is for NV devkit and usb2-0 is type C on devkit.
wj.noh
April 8, 2025, 10:10am
10
Hi
To set device mode, I add the following to the device tree.
connector {
compatible = "gpio-usb-b-connector";
label = "micro-USB";
type = "micro";
vbus-gpio = <&gpio TEGRA234_MAIN_GPIO(H, 0) GPIO_ACTIVE_LOW>;
id-gpio = <&gpio TEGRA234_MAIN_GPIO(R, 1) GPIO_ACTIVE_HIGH>;
};
GPIO H0 and GPIO R1 are set as gpio inputs in the pinmux table, and GPIO H0 is set to Low and GPIO R1 is set to High.
But SSD flashing is still not working.
I attach device tree that I used.tegra234-p3737-0000+p3701-0000.zip (3.3 KB)
Could you check it please?
Thanks
wj.noh
April 9, 2025, 2:55am
12
Hi
I attach PC/Console log and dts file that convert back from dtb.eip.zip (51.5 KB)eip_ssd_dl_agx_log.txt (86.8 KB)eip_ssd_dl_PC_log.txt (289.4 KB)
Thanks.
If you have any additional review on this issue, please let me know
I’m planning to make a revision of the custom board soon, and if any H/W modifications are needed, I’d like to reflect them..
Please help me..
When your UART console stuck in above situaton.
If you hotplug your micro usb cable, will there be any new log printed out?
And what is the role from below node?
/sys/class/usb_role/usb2-0-role-switch/role
wj.noh
April 15, 2025, 5:55am
15
Hi,
There is no new log when hotplug my micro usb cable.
bash-5.1# cat /sys/class/usb_role/usb2-0-role-switch/role
Thanks.
some thoughts:
Make sure this is also not causing issue for flashing NVMe. As this UPHY setting “may” make your NVME unavailable for flashing.
we had similar issue when our design team wrongly designed UPHY and we tried flashing for enabing Jetson as End Point device. But flashing was failing, as NVMe was not available for flashing for this UPHY. They had designed it for RP mode only in the hardware connection design.
VBUS_DET is assigned to GPIO_R1, and ID is assigned to GPIO_M0.
When monitoring the two pins from the time of power-on, the values were measured to be the same as the expected value without any change.
Is there a problem with the GPIO assignment?
0x3520360
what is the value of this register when issue happened?
wj.noh
April 15, 2025, 10:16am
20
Hi,
When issue happened, I can’t read register because I can’t use devmem command on board.
Thanks.
