Regarding MCU programming for the Jetson Orin NANO Development Kit

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
1

When I programmed the firmware (EFM8SB10F2G.hex) downloaded from the Jetson Download Center onto the development kit’s MCU (EFM8SB10F2G), the program stopped at 75%.
Is the firmware programmed correctly?
Does the same issue occur in your lab environment?
The tool used is SimplicityStudio v4.
Please check.

C:\SiliconLabs\SimplicityStudio\v4\developer\adapter_packs\c8051\flash8051.exe C:\SiliconLabs\SimplicityStudio\v4\developer\adapter_packs\c8051\flash8051.exe -sn EC3005A2301 -tif c2 -erase
C:\SiliconLabs\SimplicityStudio\v4\developer\adapter_packs\c8051\flash8051.exe C:\SiliconLabs\SimplicityStudio\v4\developer\adapter_packs\c8051\flash8051.exe -sn EC3005A2301 -tif c2 -upload C:\Users\takeshi.fushihara\Downloads\efm8_sb1_application.hex -erasemode page
Flashing C:\Users\takeshi.fushihara\Downloads\efm8_sb1_application.hex [> ] 0 out of 100, 0%
Flashing C:\Users\takeshi.fushihara\Downloads\efm8_sb1_application.hex [> ] 0 out of 100, 0%
Flashing C:\Users\takeshi.fushihara\Downloads\efm8_sb1_application.hex [> ] 0 out of 100, 0%
Flashing C:\Users\takeshi.fushihara\Downloads\efm8_sb1_application.hex [====================> ] 25 out of 100, 25%
Flashing C:\Users\takeshi.fushihara\Downloads\efm8_sb1_application.hex [========================================> ] 50 out of 100, 50%
Flashing C:\Users\takeshi.fushihara\Downloads\efm8_sb1_application.hex [============================================================> ] 75 out of 100, 75%
Flashing C:\Users\takeshi.fushihara\Downloads\efm8_sb1_application.hex [============================================================> ] 75 out of 100, 75%

5

Hi,
There is no power button on Orin Nano developer kit. Probably you are using custom carrier board?

We do have button MCU on Orin Nano developer kit, although there is no physical button(only button header pins). Yes the firmware is same as the one in download center. Would suggest check with the tool vendor for further suggestion.

6

Excuse me, I’m using a carrier board.
I’m also currently in contact with the vendor (SiliconLabs).
I’m contacting you because I don’t know if the carrier board is the cause or if it’s the programming environment.
Does the programming process complete successfully in your environment?

Thank you

7

Just a thought on the topic: If this device is not plug-n-play (and most such devices are not), then it is likely that the device tree (firmware) needs to be edited for any device which is not an exact match to the developer kit carrier board. Even if everything else is the same programming a device when the location of the device is wrong would fail. Does this vendor have a customized or edited device tree? Or does the vendor state that this uses the NVIDIA default flash software? If this is not the issue, then you have an actual possible hardware issue.

8

Hi,
Have checked and confirmed that on the production line, We pre-flashed the button MCU before SMT. So we don’t flash this by SimplicityStudio v4 tool.

9

Hello.
Thank you for your confirmation. I understand.
I have contacted SiliconLabs and resolved this issue. (I was able to write using a different tool.)
Please close this matter.