# OrinNX 8GB flash support for CustomBoard in 35.3.1 **URL:** \ **Category:** Jetson Orin NX\ **Tags:** board-design, boot\ **Created:** [April 25, 2023, 6:04am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187 "2023-04-25T06:04:05Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![shinichiro.adachi](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@shinichiro.adachi](https://forums.developer.nvidia.com/u/shinichiro.adachi)\ **Post date:** [April 25, 2023, 6:04am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187/1 "2023-04-25T06:04:05Z")
We are using custom conf based on p3509-a02+p3767-0000.conf The modification for custom config is only PINMUX\_CONFIG, PMC\_CONFIG, DTB\_FILE, ODMDATA. We have already confirmed that it is possible to write to OrinNX 16GB + Custom Board with the following command. ```auto $ 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" \ --network usb0 \ --showlogs \ dx-u2200+p3767-0000 \ internal ``` However, when we use same command to write to OrinNX 8GB + Custom Board, the following error occurs at startup. ```auto E> I2C_DEV: Could not read 256 registers of size 1 from slave 0xae at 0x00000000 via instance 0. E> eeprom: Failed to read I2C slave device C> Task 0x0 failed (err: 0x1f1e050d) E> Top caller module: I2C_DEV, error module: I2C, reason: 0x0d, aux_info: 0x05 I> Busy Spin ``` Custom Board is exactly the same. Do we need to make any modifications to the OrinNX 8GB write? Is it possible to share the same massflash blob for OrinNX 8GB/16GB? ---
**Author:** ![KevinFFF](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/kevinfff/32/15508_2.png) [@KevinFFF](https://forums.developer.nvidia.com/u/KevinFFF)\ **Post date:** [April 25, 2023, 6:59am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187/3 "2023-04-25T06:59:52Z")
Hi shinichiro.adachi, Please refer to the BOARDSKU difference between Orin NX 16GB and 8GB. - Jetson Orin NX 16GB (P3767-0000) - Jetson Orin NX 8GB (P3767-0001) Do you distinguish them in your board config (_dx-u2200+3767-0000.conf_)? You could refer to the following line in _p3768-0000+p3767-0000.conf_. ```auto if ["${board_sku}" = "0000"] || ["${board_sku}" = "0002"]; then # use default DTB and CFG files except for TS1 & EB1 revisions if ["${board_FAB}" = "TS1"] || ["${board_FAB}" = "EB1"]; then PINMUX_CONFIG="tegra234-mb1-bct-pinmux-p3767-dp-a01.dtsi"; PMC_CONFIG="tegra234-mb1-bct-padvoltage-p3767-dp-a01.dtsi"; BPFDTB_FILE="tegra234-bpmp-3767-0000-a00-3509-a02.dtb"; fi elif ["${board_sku}" = "0001"]; then BPFDTB_FILE="tegra234-bpmp-3767-0001-3509-a02.dtb"; DTB_FILE="tegra234-p3767-0001-p3768-0000-a0.dtb"; elif ["${board_sku}" = "0003"] || ["${board_sku}" = "0005"]; then BPFDTB_FILE="tegra234-bpmp-3767-0003-3509-a02.dtb"; DTB_FILE="tegra234-p3767-0003-p3768-0000-a0.dtb"; elif ["${board_sku}" = "0004"]; then BPFDTB_FILE="tegra234-bpmp-3767-0004-3509-a02.dtb"; DTB_FILE="tegra234-p3767-0004-p3768-0000-a0.dtb"; fi ``` ---
**Author:** ![shinichiro.adachi](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@shinichiro.adachi](https://forums.developer.nvidia.com/u/shinichiro.adachi)\ **Post date:** [April 25, 2023, 9:14am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187/4 "2023-04-25T09:14:29Z")
Hi,@KevinFFF, We refer to the following URL and modify update\_flash\_args\_common() as follows. > [@How to flash Orin NX 8GB on Xavier NX devkit？](https://forums.developer.nvidia.com/t/how-to-flash-orin-nx-8gb-on-xavier-nx-devkit/248253/14): > > Please apply the following patch for Orin NX + p3509 carrier board. --- a/scripts/board\_config/p3509-a02+p3767-0000.conf +++ b/scripts/board\_config/p3509-a02+p3767-0000.conf @@ -55,7 +55,7 @@ update\_flash\_args\_common() BPFDTB\_FILE="tegra234-bpmp-3767-0000-a00-3509-a02.dtb"; fi elif ["${board\_sku}" = "0001"]; then - DTB\_FILE="tegra234-p3767-0000-p3509-a02.dtb"; + DTB\_FILE="tegra234-p3767-0001-p3509-a02.dtb"; … ```auto update_flash_args_common() { ... elif ["${board_sku}" = "0001"]; then #DTB_FILE="tegra234-p3767-0000-p3509-a02.dtb"; DTB_FILE="tegra234-p3767-0001-p3509-a02.dtb"; BPFDTB_FILE="tegra234-bpmp-3767-0001-3509-a02.dtb"; elif ["${board_sku}" = "0003"] || ["${board_sku}" = "0005"]; then ``` And, we flashed with the following command as same as above. ```auto $ 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" \ --network usb0 \ --showlogs \ dx-u2200+p3767-0000 \ internal ``` SKU is confirmed to be set at 0001 during flash log. ```auto Board ID(3767) version(300) sku(0001) revision(M.3) Chip SKU(00:00:00:D4) ramcode(00:00:00:02) fuselevel(fuselevel_production) board_FAB(300) emc_opt_disable_fuse:(0) ``` As a result, log output stopped after UEFI booting and nothing was displayed on HDMI as shown below. ```auto I/TC: This is only for TZ-SE testing and should NOT be used for a shipping product! I/TC: Primary CPU switching to normal world boot  疂etson UEFI firmware (version 3.1-32827747 built on 2023-03-19T14:56:32+00:00) ``` Do we need to change all BPFDTB\_FILE/DTB\_FILE in the conf file to p3767-0001’s file,not just update\_flash\_args\_common()? [dx-u2200+p3767-0000.conf](https://forums.developer.nvidia.com/uploads/short-url/cVlwE1ldypnf9qfzgwFV3nfsjOW.conf) (3.6 KB) ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [April 25, 2023, 9:26am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187/5 "2023-04-25T09:26:20Z")
please follow the document and disable the **cvb** eeprom read. [https://docs.nvidia.com/jetson/archives/r35.3.1/DeveloperGuide/text/HR/JetsonModuleAdaptationAndBringUp/JetsonOrinNxNanoSeries.html?highlight=cvb#eeprom-modifications](https://docs.nvidia.com/jetson/archives/r35.3.1/DeveloperGuide/text/HR/JetsonModuleAdaptationAndBringUp/JetsonOrinNxNanoSeries.html?highlight=cvb#eeprom-modifications) ---
**Author:** ![shinichiro.adachi](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@shinichiro.adachi](https://forums.developer.nvidia.com/u/shinichiro.adachi)\ **Post date:** [April 25, 2023, 9:33am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187/6 "2023-04-25T09:33:30Z")
Hi, @WayneWWW, > please follow the document and disable the **cvb** eeprom read. We already did it. ```auto Linux_for_Tegra$ cat bootloader/t186ref/BCT/tegra234-mb2-bct-misc-p3767-0000.dts /dts-v1/; #include "tegra234-mb2-bct-common.dtsi" / { mb2-misc { eeprom { cvm_eeprom_i2c_instance = <0>; cvm_eeprom_i2c_slave_address = <0xa0>; cvm_eeprom_read_size = <0x0>; cvb_eeprom_i2c_instance = <0x0>; cvb_eeprom_i2c_slave_address = <0xae>; cvb_eeprom_read_size = <0x0>; }; }; }; ``` ```auto Linux_for_Tegra/bootloader$ sudo find ./ -name "*.dts" -print |xargs grep -n "cvb_eeprom_read_size" ./tegra234-mb2-bct-misc-p3767-0000.dts:13: cvb_eeprom_read_size = <0x0>; ./t186ref/BCT/tegra234-mb2-bct-misc-p3767-0000.dts:13: cvb_eeprom_read_size = <0x0>; ./t186ref/BCT/tegra234-mb2-bct-misc-p3701-0002-p3711-0000.dts:12: cvb_eeprom_read_size = <0x0>; ./t186ref/BCT/tegra234-mb2-bct-misc-p3701-0002-p3740-0002.dts:41: cvb_eeprom_read_size = <0x0>; Linux_for_Tegra/bootloader$ sudo find ./ -name "*.dtsi" -print |xargs grep -n "cvb_eeprom_read_size" ./tegra234-mb2-bct-common.dtsi:40: cvb_eeprom_read_size = <0x0>; ``` ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [April 25, 2023, 9:36am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187/7 "2023-04-25T09:36:13Z")
Please enable UEFI debug log and share full log agin. For every log you shared on this forum in future, please always share full log. Start from the moment you power on the board. ---
**Author:** ![shinichiro.adachi](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@shinichiro.adachi](https://forums.developer.nvidia.com/u/shinichiro.adachi)\ **Post date:** [April 26, 2023, 1:09am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187/8 "2023-04-26T01:09:37Z")
> Please enable UEFI debug log and share full log agin. After updating UEFI build environment to R35.3.1, we are encounting following error at UEFI build. ```auto $ edk2_docker edk2-nvidia/Platform/NVIDIA/Jetson/build.sh ... nvidia: found command: python3. nvidia: found command: virtualenv. nvidia: found command: mono. nvidia: found command: aarch64-linux-gnu-gcc. nvidia: Activating Python virtual environment. nvidia: Building from tarball nvidia: Updating build environment (edk2-nvidia/Platform/NVIDIA/Jetson/PlatformBuild.py). edk2-nvidia/Silicon/NVIDIA/scripts/prepare_stuart.sh: line 49: stuart_update: command not found ``` Could you tell me how to resolve the error? or could you give me R35.3.1 UEFI debug binary? ---
**Author:** ![shinichiro.adachi](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@shinichiro.adachi](https://forums.developer.nvidia.com/u/shinichiro.adachi)\ **Post date:** [April 26, 2023, 2:57am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187/9 "2023-04-26T02:57:49Z")
Redone "edk2\_docker edkrepo clone ~ " and finally UEFI for R35.3.1 build succeeded. Replace bootloader/uefi\_jetson.bin to uefi\_Jetson\_DEBUG.bin. And, we flashed with the command as same as previous. ```auto [hostpc_log] *************************************** * * * 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... ``` ```auto [console_log] TegraI2cStartRequest: No ACK received Failed to read eeprom (No Response) ValidateEepromData: CRC mismatch, expected 35 got FF Eeprom data validation failed(Device Error) TegraI2cStartRequest: No ACK received Failed to read eeprom (No Response) ValidateEepromData: CRC mismatch, expected 35 got FF Eeprom data validation failed(Device Error) PROGRESS CODE: V02010000 I0 PROGRESS CODE: V02010004 I0 PROGRESS CODE: V02010004 I0 PROGRESS CODE: V02010004 I0 PROGRESS CODE: V02010000 I0 PROGRESS CODE: V02010004 I0 PROGRESS CODE: V02010004 I0 PROGRESS CODE: V02010004 I0 MnpSyncSendPacket: No network cable detected. MnpSyncSendPacket: No network cable detected. ``` It seems that EEPROM CRC errors are occurring in UEFI during flashing from the host. [20230426\_1150\_OrinNX8GB\_CustomBoard\_flash\_host\_log.txt](https://forums.developer.nvidia.com/uploads/short-url/xlW0oMj2HgIMnmlCmPZeG96kO1g.txt) (261.7 KB) [20230426\_1150\_OrinNX8GB\_CustomBoard\_flash\_console\_log.txt](https://forums.developer.nvidia.com/uploads/short-url/qb7n7LTMMScLt8nNYJMwODkXvsy.txt) (105.0 KB) ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [April 26, 2023, 3:02am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187/11 "2023-04-26T03:02:17Z")
Hi, Is this a fresh module? Sounds like eeprom value is already corrupted. Do you have nv devkit to validate? ---
**Author:** ![shinichiro.adachi](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@shinichiro.adachi](https://forums.developer.nvidia.com/u/shinichiro.adachi)\ **Post date:** [April 26, 2023, 5:41am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187/12 "2023-04-26T05:41:51Z")
> Do you have nv devkit to validate? I haven’t nv devkit, so confirmed by XavierNX Devkit instead. When I use OrinNX 8GB + XavierNX EVK, flash succeeded with no EEPROM error. [20230426\_1436\_OrinNX8GB\_XavierNXEVK\_flash\_console\_log.txt](https://forums.developer.nvidia.com/uploads/short-url/dlDTsw6g6JtAoY6qwn1Z4twtAuX.txt) (164.6 KB) [20230426\_1436\_OrinNX8GB\_XavierNXEVK\_flash\_host\_log.txt](https://forums.developer.nvidia.com/uploads/short-url/bnxbDZ89zOMqYaXcnIcZpMwosq3.txt) (2.5 KB) ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [April 26, 2023, 5:45am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187/13 "2023-04-26T05:45:17Z")
Sounds weird. It feels like there are some i2c hardware issue on your custom board which leads you not even able to read cvm eeprom? Could you enable UEFI log on devkit cases too and see if it still prints eeprom error? ---
**Author:** ![shinichiro.adachi](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@shinichiro.adachi](https://forums.developer.nvidia.com/u/shinichiro.adachi)\ **Post date:** [April 26, 2023, 6:48am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187/14 "2023-04-26T06:48:54Z")
> Could you enable UEFI log on devkit cases too and see if it still prints eeprom error? Enable UEFI debug log and flash again for XavierNX EVK. ```auto PROGRESS CODE: V02010004 I0 DeviceDiscoveryBindingStart, failed to enable clocks Device Error TegraI2cStartRequest: No ACK received TegraI2cStartRequest: No ACK received TegraI2cStartRequest: No ACK received TegraI2cStartRequest: No ACK received TegraI2cStartRequest: No ACK received TegraI2cStartRequest: No ACK received Failed to read eeprom (No Response) TegraI2cStartRequest: No ACK received Failed to read eeprom (No Response) ``` It seems No ACK received in XavierNX EVK case. Our Custom Board has one I2C-EEPROM on c240000 bus, i2c addr is 0x50. Would this cause a problem? The content is blank. This is command log in R35.2.1. ```auto root@test-desktop:~# i2cdetect -y -a -r 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --" root@test-desktop:~# i2cdump -f -y 0 0x50 No size specified (using byte-data access) 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef 00: 02 00 fe 00 00 00 00 00 00 00 00 ff 00 00 00 00 ?.?............. 10: 00 01 00 01 36 39 39 2d 31 33 37 36 37 2d 30 30 .?.?699-13767-00 20: 30 30 2d 33 30 30 20 47 2e 33 00 00 00 00 00 00 00-300 G.3...... ... root@test-desktop:~# i2cdetect -y -a -r 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- 2c -- -- -- 30: -- -- UU -- -- -- -- -- -- -- -- -- -- -- -- -- 40: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- root@test-desktop:~# hexdump -C /sys/devices/platform/c240000.i2c/i2c-1/1-0050/eeprom 00000000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| * 00001000 ``` [20230426\_1529\_OrinNX8GB\_XavierNXEVK\_flash\_console\_log\_with\_UEFI\_debug.txt](https://forums.developer.nvidia.com/uploads/short-url/geF84UFKMxBGHDqXcewTer311GL.txt) (322.2 KB) [20230426\_1529\_OrinNX8GB\_XavierNXEVK\_flash\_host\_log\_with\_UEFI\_debug.txt](https://forums.developer.nvidia.com/uploads/short-url/vapqO341AL8p81j2ETR8NaHmTgH.txt) (296.1 KB) ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [April 26, 2023, 7:35am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187/15 "2023-04-26T07:35:03Z")
The devkit does not have the CRC mismatch error, so the error is different. If you think your extra i2c eeprom is causing error, please disable it in the device tree first and see if you can bypass it. ---
**Author:** ![shinichiro.adachi](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@shinichiro.adachi](https://forums.developer.nvidia.com/u/shinichiro.adachi)\ **Post date:** [April 28, 2023, 3:50am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187/16 "2023-04-28T03:50:34Z")
Finally, I just made the following changes in dx-u2200+p3767-0000.conf ```auto --- dx-u2200+p3767-0000.conf +++ dx-u2200+p3767-0000.conf @@ -55,7 +55,7 @@ update_flash_args_common() BPFDTB_FILE="tegra234-bpmp-3767-0000-a00-3509-a02.dtb"; fi elif ["${board_sku}" = "0001"]; then - DTB_FILE="tegra234-p3767-0000-p3509-a02.dtb"; + DTB_FILE="tegra234-p3767-0000-dx-u2200.dtb"; BPFDTB_FILE="tegra234-bpmp-3767-0001-3509-a02.dtb"; elif ["${board_sku}" = "0003"] || ["${board_sku}" = "0005"]; then ``` We confirmed that execute ./tools/kernel\_flash/l4t\_initrd\_flash.sh directly can be written successfully. [20230427\_1553\_OrinNX8GB\_CustomBoard\_flash\_console\_log\_succeed\_with\_nodebug.txt](https://forums.developer.nvidia.com/uploads/short-url/7gOQpHjiabB8PNB3HKzVWCbbTbO.txt) (184.1 KB) [20230427\_1553\_OrinNX8GB\_CustomBoard\_flash\_host\_log\_succeed\_with\_nodebug.txt](https://forums.developer.nvidia.com/uploads/short-url/mJNBPQFo1PO0eWLbHxMJXaxdZjR.txt) (295.6 KB) ---
**Author:** ![shinichiro.adachi](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@shinichiro.adachi](https://forums.developer.nvidia.com/u/shinichiro.adachi)\ **Post date:** [April 28, 2023, 3:51am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187/17 "2023-04-28T03:51:27Z")
After that, creating massflash blob, and following error occur when writing from the massflash blob. ```auto [0144.977] E> BL_CARVEOUT: Failed to allocate memory of size 0x8000000 for CO:31. [0144.984] C> Task 0x0 failed (err: 0x49490003) [0144.988] E> Top caller module: BL_CARVEOUT, error module: BL_CARVEOUT, reason: 0x03, aux_info: 0x00 [0144.997] C> Boot Info Table status dump : 1 [0145.001] I> Busy Spin ``` Is there any workaround for this? [20230428\_1148\_OrinNX8GB\_CustomBoard\_massflash\_console\_log\_failed.txt](https://forums.developer.nvidia.com/uploads/short-url/n7gkoKufVwixCoHNgMJhipYjqN1.txt) (4.2 KB) [20230428\_1148\_OrinNX8GB\_CustomBoard\_massflash\_host\_log\_failed.txt.txt](https://forums.developer.nvidia.com/uploads/short-url/vTAm9nIxWg4bVxGMsefE5oFW7y2.txt) (1.1 KB) ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [April 28, 2023, 4:21am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187/18 "2023-04-28T04:21:59Z")
Are you talking about this error only happens with massflash but not initrd flash with single module? ---
**Author:** ![shinichiro.adachi](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@shinichiro.adachi](https://forums.developer.nvidia.com/u/shinichiro.adachi)\ **Post date:** [April 28, 2023, 4:56am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187/19 "2023-04-28T04:56:19Z")
Yes, direct flash command is below. This command suceeded with no error. ```auto 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" \ --network usb0 \ --showlogs \ dx-u2200+p3767-0000 \ internal ``` And, massflash blob create command is below. ```auto TARGET_CONF=dx-u2200+p3767-0000 ROOTFS_SIZE=$((18*1024*1024*1024)) echo "run l4t_initrd_flash.sh" sudo ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash \ --external-device nvme0n1p1 \ -S ${ROOTFS_SIZE} \ -c tools/kernel_flash/flash_l4t_external.xml \ -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" \ --network usb0 \ --massflash 5 \ --showlogs \ ${TARGET_CONF} \ internal ``` And, massflash command is below. It causes Busy Spin error. ```auto sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --massflash 5 ``` ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [April 28, 2023, 4:58am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187/20 "2023-04-28T04:58:13Z")
Just to clarify 1.does this massflash issue happen to multiple modules or only one module? 1. Is your issue able to reproduce on NV devkit? I mean same module with same flash command on devkit. Will it reproduce issue? ---
**Author:** ![shinichiro.adachi](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@shinichiro.adachi](https://forums.developer.nvidia.com/u/shinichiro.adachi)\ **Post date:** [April 28, 2023, 5:48am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187/21 "2023-04-28T05:48:13Z")
> 1. does this massflash issue happen to multiple modules or only one module? Multiple modules. > 1. Is your issue able to reproduce on NV devkit? I mean same module with same flash command on devkit. Will it reproduce issue? Yes. I swapped OrinNX 8GB CPU Module from CustomBoard to XavierNX EVK, and flash with same command, reproduced Busy Spin in EVK. [20230428\_1429\_OrinNX8GB\_XavierNXEVK\_flash\_BusySpin\_console\_log.txt](https://forums.developer.nvidia.com/uploads/short-url/20GdQB3u0VSKlMS2h4X9OJHJXcK.txt) (4.2 KB) [20230428\_1429\_OrinNX8GB\_XavierNXEVK\_flash\_BusySpin\_host\_log.txt](https://forums.developer.nvidia.com/uploads/short-url/ewbeYWIfEYRCuZnc16ToyCF2tfH.txt) (876 Bytes) ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [April 28, 2023, 5:51am UTC](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187/22 "2023-04-28T05:51:39Z")
Hi, There is a bug in the flash config. It seems you are using the problematic dtb to flash orin nx 8GB. Could you try to use the correct dtb first? > [@\[35.3.1\] help to check what the dtb file using by board\_sku 0001](https://forums.developer.nvidia.com/t/35-3-1-help-to-check-what-the-dtb-file-using-by-board-sku-0001/249902/3): > > no, it is not normal. It is a bug. Please apply this patch. --- a/scripts/board\_config/p3509-a02+p3767-0000.conf +++ b/scripts/board\_config/p3509-a02+p3767-0000.conf @@ -55,7 +55,7 @@ update\_flash\_args\_common() BPFDTB\_FILE="tegra234-bpmp-3767-0000-a00-3509-a02.dtb"; fi elif ["${board\_sku}" = "0001"]; then - DTB\_FILE="tegra234-p3767-0000-p3509-a02.dtb"; + DTB\_FILE="tegra234-p3767-0001-p3509-a02.dtb"; B… [Next page](https://forums.developer.nvidia.com/t/orinnx-8gb-flash-support-for-customboard-in-35-3-1/251187.md?page=2)