I use a third party carrier board. The following error occurs

Robotics & Edge Computing Jetson & Embedded Systems Jetson Nano
1

Jetson-GPIO library

6756761796180
67567617961801920Ă—162 33 KB

2

Most manufacturers have a different electrical layout on their carrier boards. Many pins on the Jetson module can be programmed for different functions, and in general, that function is set up via the “device tree”. The flash software itself for a Jetson dev kit mostly differs from third party manufacturers by minor changes to the device tree related to that. GPIO pins might be the same, but they also might differ. Thus a GPIO library designed for a dev kit might need edits for a third party carrier board.

It is possible a third party carrier board uses the same device tree as the dev kit, but this only occurs in the case of exact replicas of the dev kit layout. Some part of the library probably depends on that layout, and it should be possible to adjust if you know the device tree differences between dev kit and your carrier board, but I have no way of answering (and the software itself probably cannot try to adjust without human input).

3

thank you for your reply. From which direction do I need to study this device tree?

4

I searched for information on the Internet. Some data indicate that it is because of the SN code problem. Is there such a possibility?

5

You wouldn’t need to study device trees unless you are designing a custom carrier board. The manufacturer of that carrier board should provide the software. Flashing it with their software would install that device tree, and thus the errors should go away. It is quite possible that the only difference between the software they provide, and that of the dev kits, is the device tree.

Other software which uses GPIO might have to be adjusted to use the right GPIO pins. A custom device tree might imply different pins are used (or more pins, or fewer pins for GPIO access). Numbering of given pins might be altered. So the first goal is to set up the board correctly to expose its GPIO via the third party manufacturer’s installation software. The second goal (once GPIO is functioning) would be to determine if any errors are simply from naming the wrong GPIO device (which on a dev kit might be the right GPIO device).

1 Like
6

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