Beg your pardon Kevin, I missunderstood your last post (… Maybe you can also get our official devkit for a try …) What did you have in mind ?
I will return this kit to the vendor. Do you recommend me to get / buy this devkit directly from NVIDIA ?
We don’t rent anything here. What Kevin told is maybe you could buy a official NV devkit to check as we cannot guarantee the quality of a custom carrier board.
Thank you Wayne, I got it.
From Yahboom it was a quit good starter pack, “everything” included: board, SSD with working software (unfortunately an old one), power supply, all cables, housing for better handling …
The original NVIDIA dev kit is quite “naked”, everything else has to be purchased additionally and one has to hope that it fits. Maybe, you could give a kind of recommendation list, what you would recommend to get a running system ?
The devkit is used for the reference. I think installing Jetpack and related SDK components through SDK manager should be fine for your use case.
But you can still ask your vendor for the steps to enter into force recovery state.
As our understanding, it should enter in to this state by simply shorting REC/GND and then power up the board.
This means, for testing beside the devkit I need only a M.2 SSD, a USB-C cable, an ethernet cable and a power supply ?
I asked the vendor again, how to get into recovery mode.
And a host PC to run lsusb to confirm if the board is in force recovery state.
I guess, we can finish the thread now. The hardware I sent back via Amazon and ordered an original NVIDIA development kit. I will post my experience later.
Now, the last post from the Yahboom support - without comments.
Hello friend
I understand your feelings about the product based on usage
You must understand the following points
-
The problem that needs to be solved at present is just to verify whether the type-c interface of the orin carrier board can communicate normally.
The problem comes from the type-c data cable you use to transmit data and the hardware problem of the orin carrier board. -
Whether the jumper cap is connected or not connected to pins 9 and 10
It does not affect the normal detection of the orin board device by the Windows system
Allowing you to connect to a Windows computer is to eliminate interference when you access the virtual machine system -
Whether you connect orin to a Windows system, a virtual machine system or a dual system.
Under normal circumstances, using a type-c cable that can transmit data, it can detect the orin device
If you have verified that the type-c cable you are using can transmit data normally.
However, using this data cable to connect orin to the USB port of the same computer, the orin motherboard device cannot be detected
This is an obvious hardware problem with the carrier board type c interface
You don’t need to do any additional testing -
Yahboom has a strict after-sales process.
If you cannot provide a test video.
I will not be able to give feedback to after-sales staff for verification
In addition, if you cannot provide the relevant product order number
I suggest you contact the online purchasing platform for after-sales processing
I can only assist you with hardware testing.
Best Wish.
Yahboom Support.
Okay, please let us know if the official devkit working to enter into force recovery state.