Jetson TX2 NX BSP

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
1

Hi,
We have received a TX2 NX module and wanted to build an eMMC BSP for it can you please guide on that?

Can we use TX2 stock BSP on it and make changes if needed while building from source? or need to use is it compatible with TX2 circuit?

We already have a TX2 working BSP for our TX2 carrier board and also have a NX working BSP for our NX carrier Board.

Please let us know what is the best approach I can follow? also do you have a plan to support TX2 NX fully in coming months?

2

Please check latest jetpack4.5.1.

1 Like
3

Is this module compatible with NX carrier board? we have a working carrier board for NX, can I try putting module and flash the BSP?

4

In Jetson TX2 NX Product Design Guide, yes you can.

Screenshot from 2021-04-08 09-46-47
Screenshot from 2021-04-08 09-46-47875Ă—670 53.7 KB

1 Like
5

Hi,
What will be the flash script for TX2 NX? for emmc flashing what is the board name?

$ sudo ./flash.sh <board> mmcblk0p1

6

Check those *.conf file under Linux_for_Tegra and you would find it.

This “board” name are just conf file name there.

7

yes thats correct, But I am not getting any specific conf file for TX2 NX? which conf file should I use for TX2 NX?
if I use below then I get error:
/Linux_for_Tegra$ sudo ./flash.sh jetson-xavier-nx-devkit-tx2-nx mmcblk0p1
###############################################################################

L4T BSP Information:

R32 , REVISION: 5.1

###############################################################################
Error: probing the target board failed.
Make sure the target board is connected through
USB port and is in recovery mode.

8

What does the log tell you?

9

module is getting detected as USB

Linux_for_Tegra$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 017: ID 0955:7c18 NVidia Corp.
Bus 001 Device 003: ID 04ca:0061 Lite-On Technology Corp.
Bus 001 Device 002: ID 413c:2107 Dell Computer Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Linux_for_Tegra$

10

Is your board connected with UART or HDMI there?

11

No, only USB cable and power cables are connected. Why are you asking for these connections? you suspect on force recovery mode due to these connections I mean any power related?

12

I suspect your board is not in recovery mode at all.

“lsusb” is not the precise way to tell whether a board is in recovery mode because we enable kernel side usb device mode since rel-32.3. It means you will see “lsusb” give you “nvidia corp” even when board is not in rcm. Thus, I need other peripherals there to tell if you board is really in rcm.

Do you see “/dev/ttyACM0” on your host side?

13

No I dont see “/dev/ttyACM0” on my host.

What is the correct method to ensure the device is in recovery mode?

14

I believe you know how to put the board into recovery mode.

When you posted the last comment and said you got some error logs when used the wrong board config, those error logs will only be printed when board is in rcm.

Actual SoC ID(0x18) mismatches intended jetson-xavier-nx-devkit-emmcSoC ID(0x19)

Thus, just try to set it to rcm with jumper again.

15

Yes, looks like that was the issue. I have put the board in recovery mode again and tried flashing it now its is getting flashed. I will come back if flash is not successful.
this time under lsusb my device is detected correctly:
Jetson TX2 series
P3310-1000
7c18
Jetson TX2

1 Like