Sorry @WayneWWW , We are not having.
Then do you have xavier nx devkit?
above logs are with Orin Nano
How many module do you have there? Could you try other modules and see if they all hit same issue?
1 Like
Hi @WayneWWW
I tried with diffrent Orin_Nano8Gb module.
while flashing in host got error like below and attached target and host logs . Please can you check and guide me
<<<<<<<<<<<<<<<<<<<<<<<<<<<
Sha1 checksum matched for /qspi/internal/gpt_secondary_3_0.bin
Writing /qspi/internal/gpt_secondary_3_0.bin (16896 bytes) into /dev/mtd0:67091968
Copied 16896 bytes from /qspi/internal/gpt_secondary_3_0.bin to address 0x03ffbe00 in flash
[ 214]: l4t_flash_from_kernel: Successfully flash the qspi
[ 214]: l4t_flash_from_kernel: Flashing success
Error flashing non-qspi storage
Cleaning up…
hmecd001409@DSC:~/BSP/flashdir/Linux_for_Tegra$
<<<<<<<<<<<<<logs end
host3_Orin_nano8GB.txt (290.2 KB)
Target3_Nano8GB (102.6 KB)
Hi,
Could you use the default kernel image instead of the one built by yourself?
Okay .
Before that , few more info i wanted update
1)
in target i got bash window
<<<<<<<<target logs <<<<<<
bash-5.0# cat /etc/board_spec.txt
3767-300-0003-M.2-1-1-jetson-orin-nano-devkit-
bash-5.0# ls
bin etc initrd_flash.cfg mnt qspi run sys usr
dev init lib proc root sbin tmp var
bash-5.0# cat initrd_flash.cfg
external_device=/dev/nvme0n1
instance=0
bash-5.0#
<<<<<<logs end
-
after power cycle
<<<<<<<< target logs as
I> Task: Program CBB PCIE AMAP regions (0x50019b64)
I> Task: Boot device init (0x50001d74)
I> Boot_device: QSPI_FLASH instance: 0
I> Qspi clock source : pllc_out0
I> QSPI-0l initialized successfully
E> Error in command_complete 18000 int_status
E> Sending CMD_SD_SEND_IF_COND failed
E> Error opening sdcard-0
E> Failed to initialize device 6-0
C> Storage init failed
C> Task 0x0 failed (err: 0x39390706)
E> Top caller module: SDMMC, error module: SDMMC, reason: 0x06, aux_info: 0x07
I> Busy Spin
<<<<<<<<<<<<<<logs end. -
Please can you cross check command is correct ?
"sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --showlogs --network usb0 jetson-orin-nano-devkit internal
" -
still it is pointing to SDMMC only.
afterFlashBoot1 (41.7 KB)
I don’t know what you want to try here. Your previous flash to nvme does not finish because of other error. So what you are doing now is meaningless.
1 Like
okay , then I will try this one first .
Also, please try not to make too much customizations on your side without notifying me about it…
So far I shall only see the kernel dtb and mb2 config file are changed by you… other software should be same as default BSP.
1 Like
@WayneWWW I will setup L4T again. Please can you share any specific flash command without building for Orin Nano with NVMe?
What does that mean without building for Orin Nano with NVMe… then what do you want here…? USB drive?
I am using below command. Is this okay ? or any modification required ?
…>>>>>>>>>>>>
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --showlogs --network usb0 jetson-orin-nano-devkit internal
…>>>>>>>>>>>>>>>>>>>>>>>>
That command is okay.
I would suggest just get a Orin Nano devkit for yourself to play around first…
It is not only for flashing, every issue you hit in future may get help with the orin nano devkit…
1 Like
Hi @WayneWWW ,
I have tried with default L4T(only cvb eeprom read size modified). But seen block dev error at target.
<<<<<<<target log
[0958.122] I> Task: Load MB2/Applet/FSKP (0x5000ca55)
[0958.127] I> Loading MB2 Applet
[0958.130] I> Slot: 1
[0958.133] E> BLOCK_DEV: Failed to open blockdev.
[0958.138] E> LOADER: Failed to open blockdev 0(0).
[0958.143] E> LOADER: Failed to get storage info for binary 21 from loader.
[0958.150] C> LOADER: Could not read binary 21.
[0958.154] E> Failed to load MB2
<<<<<<<target log error
Any thing else you suspect ?
Is this from orin nano devkit or you are still pasting same log in same test setup?
@WayneWWW.
Not old logs.
This is from not dev kit but equivalents devkit (customized) which is not having EEPROM.
modified “cvb_eeprom_read_size = <0x0>;” and followed
“https://docs.nvidia.com/jetson/archives/r35.3.1/DeveloperGuide/text/IN/QuickStart.html#jetson-modules-and-configurations”
with tried to flash observed error as mentioned.
Apart from this do i need to do format or partition for NVMe device ?
<<<<<<<<<< PCI Config: I/O=0x36100000, Memory=0x36200000
I> MEM64 bar_num=0 bar=0x36200000
I> Number of PCIe devices detected: 2
I> NVME page size: 4096
I> NVMe serial number: 50026B728253DCF0
I> NVMe model number: KINGSTON SA2000M8250G
I> NVMe firmware revision: S5Z42105
I> block_count: 488397168
I> supported_lba: 0
I> block_size_log2: 0x9
I> tegrabl_create_io_queue_cmd: queue size: 2
I> tegrabl_create_io_queue_cmd: queue size: 2
I> nvme device id 000c0004
I> Task: Partition Manager Init (0x50001d70)
I> Found 57 partitions in QSPI_FLASH (instance 0)
I> Found 14 partitions in NVME (instance 4)
I> Task: Load and authenticate registered FWs (0x5001ce48)
I> Task: Load AUXP FWs (0x5002680c)
I> Successfully register SPE FW load task with MB2 loader
I> Skipping SCE FW load
Please just try to get a orin nano devkit or xnx devkit.
I really don’t care about those terms " equivalents devkit (customized)". Those do no matter. They are just custom baord which we cannot guarantee.
1 Like
can i use XNX dev kit with Orin nano 8GB module ?