Due to the instructions I set a jumper between pins 9 and 10 (FC REC - GND) and re-powered the kit. But the USB does not appear in on the host PC (lsusb command), thus, the SDK manager does not recognize the board.
Even with the jumper on those pins the jetson boots into the “normal” working mode.
Hello @joerg.hoenig,
Can you try rebooting in recovery mode from the command line?
sudo reboot --force forced-recovery
In the past, I have had issues with certain jumpers, sometimes they are not great quality.
I ended up getting some of the little square shaped ones.
Please let me know how it goes.
regards,
Andrew
Embedded Software Engineer
1 Like
Thank you for your hint. This is unfortunately also not working, I tried this command also already. I also checked the jumper with an ohmmeter.
Hello @joerg.hoenig,
That is very strange.
Do you have another board available you can test?
regards,
Andrew
Embedded Software Engineer
Hi joerg.hoenig,
Have you confirmed that you are using the devkit?
Do you have another devkit to verify to check if the issue is specific to current board?
Do you connect TypeC port with your host PC?
Are you using standalone Ubuntu for SDK Manager or you are using VM?
Unfortunately, I do not have another board. I am using a a Yahboom Jetson Orin Nano Development Kit with 8GB RAM and 256GB M.2 drive.
The “normal” boot process takes about 16sec till the first “NVIDIA” screen appears and about 44 sec till one can login to the Ubuntu login screen.
When I shortcut pins 9 an 10 then it takes about 60 sec till the NIVIDIA screen appears and overall 90sec till the Ubuntu login screen is available.
I am connecting the USB-C connector from the Jetson - I tried also already different cables beside the provided one.
I am using the SDK manager on a Ubuntu laptop and checked also - especially during the 1st minute - with the “lsusb” command in a terminal, but no USB connection to the NVIDIA hardware shows up.
Hello @joerg.hoenig,
That is very strange.
Have you tried contacting the manufacturer to see if they could provide support in the case that it could be a HW issue ?
regards,
Andrew
Embedded Software Engineer at ProventusNova
Hello proventusnova,
I did not yet contact the manufacturer, but will do so now as the only reason I see currently is a kind of hardware issue.
Best Regards
Joerg
Hello @joerg.hoenig,
Sounds good.
Please keep us posted.
And don’t hesitate to reach out if you have more questions moving past this issue.
regards,
Andrew
Embedded Software Engineer at ProventusNova
Yes, force recovery state should be determined by hardware and you should get into this state by simply shorting REC/GND pin before power up the board.
It is a custom carrier board from Yahboom.
I would suggest you contacting them for this issue.
Thank you for your remarks Kevin. I contacted Yahboom. I will update here after getting their reaction.
Here is the answer from the Yahboom technical support, what is not very helpfull. I will not comment things I stated already to the support.
Of course, I will not format the provided SSD. What do you think of placing an empty M.2 SSD and try to get this way into the recovery mode ?
Hello friend
You need to know the following information
-
When you use the SSD with image provided by Yahboom, it can boot normally
This means that all hardware is normal.
2.If you need to use a different Jetpack version
First you need to format the SSD yourself
Then install the SSD on the orin board
Finally, use the type-c cable to connect to the SDK Manager software -
If SDK Manager cannot detect the NVIDIA device
First, please check whether the type-c cable you are using has the function of transmitting data.
Then check if the orin board is connected to the Windows computer
You can check it in the Windows device manager.
Have a good weekend
Best Wish.
Yahboom Support.
Before using the NVMe SSD, please format it as ext4.
It seems you vendor suggesting you using SDK Manager for their board. I suppose that there’s no much difference from the official devkit so that they suggest you for SDK Manager.
I’m curious about this.
Why they suggest a Windows PC?
As my understanding, we would suggest using standalone Ubuntu host PC for SDK Manager.
Hello @KevinFFF,
My main concern is that @joerg.hoenig reported that the board is unable to boot in recovery mode. Therefore, it does not even show up on lsusb.
This is an issue that will not allow @joerg.hoenig to use SDK manager to flash the board.
I don’t think formatting the SSD will change the fact that the board does not boot into recovery, or could it ?
I believe the Yahboom support team did not understand the issue.
regards,
Andrew
Embedded Software Engineer at ProventusNova
Hello Andrew and @KevinFFF Kevin,
attached you will see the last answer from Yahboom. I will not comment it.
Hello friend
Due to the holidays, I’m sorry for not replying to you in time.
- When using the Yahboom factory SSD solid state, the system starts normally, which indicates that the hardware and system are normal.
2.About installing other languages and input methods in the Jetson system
This has nothing to do with the hardware
You need to go to NVIDIA’s official website to check whether the relevant instructions support the installation of such languages.
I haven’t tested this environment.
- The system provided by Yahboom is based on the official system of NVIDIA and some environment has been built.
If you need other environments yourself, I recommend using NVIDIA’s system without any environment.
4.If your computer cannot detect the jetson board, then I suggest you change the computer and type-c cable for testing.
Best Wish.
Yahboom Support.
My last attempt was - due the previous support email - to place an empty, ext4-formatted SSD into the box, shorten the pins 9 and 10 and power the device. The result was, that the Jetson was booting into an UEFI Shell and there was still no NVIDIA - USB visible at the host computer connected via USB-C-cable.
Thus, it seems, that the given kit cannot be booted in recovery mode and I cannot update the software to the current version.
Or is there a way of external preparing the SSD with the actual software ? But, if I am correct, for Jetpack 6.x one has to update the BIOS too, or I am wrong ?
Best Regards
Joerg
The next reply from Yahboom is not understandable for me:
Hello friend
You need to know the following information
1. If you connect pins 9 and 10 with a jumper cap, the system will not boot. This is normal.
-
-
- If Yahboom provides a SSD with a system to boot normally*
- This means that the hardware of the jetson core board is normal*
-
3. Please shut down the virtual machine software on your Windows computer while using the Yahboom factory system to boot normally. （No need to short any pins）
- Then use a data line that can transmit data*
- Open the Device Manager on your Windows computer*
- Connect the type-c port of the orin board to the usb port of the windows computer （Please do not connect the USB interface to the USB expansion module on the computer）*
- （You can also try different computers or other USB ports on your computer.）*
- And record all the wiring videos of the orin board for me to check*
- In addition, please record a video of the changes in the Windows system device manager interface for me to review.*
-
4. The attached video shows me connecting the normally powered on orin board to the USB port of the Windows system.
- You can connect your type-c cable to other devices. If the disk manager interface is refreshed and a device disappears*
- This indicates that the data line can transmit data normally.*
- If you connect the orin board, the device manager will automatically refresh and the device will appear*
- This shows that the type-c port of the orin carrier board can transmit data normally *
-
Looking forward to your reply
Best Wish.
Yahboom Support.
Attached was a video in Chineese. I do not want to answer and tell another time what I already told. I only want to send back the hardwareand try another manufacturer.
Do you have a hint how to react ?
Hello @joerg.hoenig,
We are very sorry to hear how problematic this experience has been so far.
If you want to return the HW, I guess it depends on how you acquired it in first place.
If you bought it through Amazon for example, it should be fairly simple, Amazon is great at customer service.
However, if you bought it somewhere else, you might need to contact the specific marketplace to request a refund.
regards,
Andrew
Embedded Software Engineer at ProventusNova
Hi joerg.hoenig,
Do you still fail to enter into recovery mode on Yahboom’s board?
Maybe you can also get our official devkit for a try.
Hello Kevin,
this would be a great idea, what do we have to do to do so ? What would be the cost, how long we could “rent” your official dev kit ?
Best Regards
Joerg
Sorry that I have no idea about “renting the devkit”.
Enter force recovery state should be easily to achieve since it is controlled by HW.
I’ll still suggest you connect the vendor for this.