Guidance to tell if you are using a NV developer kit

Hi,

This post is to guide how to identify whether your carrier board is a NVIDIA developer kit or a custom carrier board.

The reason to explain this is because there are too many users using a custom board and claming they are NV devkits. Most of them turn out not true and they are not able to be used directly.

Background story

A Jetson platform is formed by two parts. The module and the carrier board.

NVIDIA provides two methods to access the Jetson platform.

  1. The module alone.
  2. The module + a reference carrier board → NV developer kit

Generally, a vendor would buy a module alone and make their own carrier board.

Now back to Jetson nano case. There are two kinds of Jetson Nano 4GB modules officially released by NVIDIA.

  1. p3448-0000. This module has a sdcard slot.
  2. p3448-0002. This module has a internal 16GB eMMC storage.

Generally, p3448-0000 module only comes along with NV developer kit and p3448-0002 will be sold alone for vendor to use.


How to identify?

To identify whether a board is custom board or NV devkit, please take a look in the back of your carrier board. A NV devkit shall have a NVIDIA logo and with model name as “p3450” as below picture.


Q&A:

  1. Why does it matter using a NV devkit or not?

All the tools and Image released by NVIDIA (e.g. Sdkmanager/Sdcard image) are all based on NV devkit. We don’t guarantee it would work fine on a custom board.

  1. What is the exact definition of “custom board”?

Any carrier board that is not NV devkit is a custom board.

  1. But my board has a sdcard slot and eMMC at same time, what is this thing?

That board is a custom board. The sdcard slot is definitely “on the carrier board” but not on the module itself. That means the sdcard slot is added by the vendor. NV devkit does not have a sdcard slot on the carrier board.

  1. How should I use a custom board for Jetson?

Generally, you should check with the board vendor or the website of the vendor. They shall provide you customized software for their custom board.

I have a p3448-0000 which I have put in a Seeed Recomputer J101 so this means I have a custom carrier board? How did the SDK manager upload the OS and CUDA files onto the emmc? Is that because that custom carrier board has emmc on it? Can I utilise the SD card slot in my module board?

I have a p3448-0000 which I have put in a Seeed Recomputer J101 so this means I have a custom carrier board?

Yes, it is a custom board.

How did the SDK manager upload the OS and CUDA files onto the emmc

It is flashing by using micro usb connection between Jetson and another x86 host PC. x86 host PC with sdkmanager running.

Can I utilise the SD card slot in my module board?

The sdkmanager does not support extra inteface added by the vendor on a custom board. To enable such extra interface, please go to check with board vendor if they provide a method to enable it.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.