Can not open USB when flashing TX2 board

Autonomous Machines Jetson & Embedded Systems Jetson TX2
1

Dear,

Currently, I have problem when flashing my custom TX2 board.
My OS: Ubuntu 14.04. I don’t use any virtual machine.
After forcing TX2 board to recovery mode, this is result:

vu@vu-desktop:~$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 001 Device 005: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 001 Device 035: ID 0955:7c18 NVidia Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Then I try to run these commands to flash

sudo ./apply_binaries.sh
sudo ./flash.sh jetson-tx2 mmcblk0p1

But it stuck forever at this line

[ 360.5754 ] tegradevflash_v2 --oem platformdetails eeprom cvm /home/vu/Desktop/Projects/JetsonTX2/64_TX2/Linux_for_Tegra_tx2/bootloader/cvm.bin

With the same PCB, if I put TX1 module into and flash TX1 file system, everything work well.
Do you think my custom design has any problem?

Thanks

2

Please forgive if I am wrong. Seems you have designed a PCB to use TX2 module.
Would you mind sharing your design schematic?

3

Hi WayneeWWW,

Sorry but I cannot share to you because I have no permission.
However almost things are same with reference design. You can refer here

4

Update:

I tried to mount TX2 module from NVIDIA developer kit to our PCB then firmware flashing work well.
I still can not figure out where is problem.

And about the firmware package, I used L4T 28.1 Driver package to flash my board. After finish I can boot to OS properly however my HDMI screen display nothing. On the debug terminal, it shows like above:

[   50.262065] tegradc 15210000.nvdisplay: sanitize_flip_args: WIN 3 invalid size:w=0,h=0,out_w=0,out_h=0
[   50.296240] tegradc 15210000.nvdisplay: sanitize_flip_args: WIN 3 invalid size:w=0,h=0,out_w=0,out_h=0
[   50.330464] tegradc 15210000.nvdisplay: sanitize_flip_args: WIN 3 invalid size:w=0,h=0,out_w=0,out_h=0
[   50.364655] tegradc 15210000.nvdisplay: sanitize_flip_args: WIN 3 invalid size:w=0,h=0,out_w=0,out_h=0

Anybody face this problem ?

5

Hi forever3000,

This seems a unknown HDMI issue. May I ask the detail of your HDMI monitor? (brand, edid…)

Please paste

sudo cat /sys/kernel/debug/tegradc.0/edid  #please check tegradc.0 and tegradc.1

Do you have any other setting ?

6

Thank for your reply,

This is the result of cat edid command:

00 ff ff ff ff ff ff 00 4c 2d 1c 0c 45 54 4c 30
 32 19 01 03 80 3c 22 78 2a 97 91 a5 56 54 9d 25
 0e 50 54 bf ef 80 71 4f 81 c0 81 00 81 80 95 00
 a9 c0 b3 00 01 01 02 3a 80 18 71 38 2d 40 58 2c
 45 00 56 50 21 00 00 1e 01 1d 00 72 51 d0 1e 20
 6e 28 55 00 56 50 21 00 00 1e 00 00 00 fd 00 32
 4b 1e 51 11 00 0a 20 20 20 20 20 20 00 00 00 fc
 00 53 32 37 45 33 39 30 0a 20 20 20 20 20 01 d3
 02 03 1a f1 46 90 04 1f 13 03 12 23 09 07 07 83
 01 00 00 66 03 0c 00 10 00 80 01 1d 00 bc 52 d0
 1e 20 b8 28 55 40 56 50 21 00 00 1e 8c 0a d0 90
 20 40 31 20 0c 40 55 00 56 50 21 00 00 18 8c 0a
 d0 8a 20 e0 2d 10 10 3e 96 00 56 50 21 00 00 18
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 61

My screen specs:

Model Number 	LS27E390HS
Screen Size
	27" (16:9)
Display Type
	PLS
Resolution
	1920 x 1080
Brightness 	300cd/m2
Static Contrast Ratio
	1,000:1
Dynamic Contrast Ratio
	Mega ∞ DCR
Viewing Angle (Horizontal/Vertical)
	178°/178°
Response Time
	4ms (GTG)
Color Support
	16.7M
7

Thanks a lot. I will try to reproduce the issue by using your EDID.

May I ask if other HDMI monitors also hit the error?

8

I also tried with HD projector (PicoPro) that support HDMI as input, everything is same.
This is edid:

00 ff ff ff ff ff ff 00 17 10 01 09 01 00 00 00
 1e 18 01 03 80 73 41 78 2a 7c 11 9e 59 47 9b 27
 10 50 54 21 01 00 01 01 01 01 01 01 01 01 01 01
 01 01 01 01 01 01 01 1d 00 72 51 d0 1e 20 6e 28
 55 00 10 09 00 00 00 1e 8c 0a d0 8a 20 e0 2d 10
 10 3e 96 00 04 03 00 00 00 18 00 00 00 fc 00 45
 50 2d 48 44 4d 49 2d 52 58 0a 20 20 00 00 00 fd
 00 3b 3d 0f 2e 08 00 0a 20 20 20 20 20 20 01 8a
 02 03 18 71 45 84 03 02 10 01 23 09 07 07 83 01
 00 00 65 03 0c 00 00 00 01 1d 00 72 51 d0 1e 20
 6e 28 55 00 10 09 00 00 00 1e 8c 0a d0 8a 20 e0
 2d 10 10 3e 96 00 10 09 00 00 00 18 01 1d 00 bc
 52 d0 1e 20 b8 28 55 40 10 09 00 00 00 1e 02 3a
 80 18 71 38 2d 40 58 2c 45 00 ba 88 21 00 00 1e
 8c 0a d0 8a 20 e0 2d 10 10 3e 96 00 04 03 00 00
 00 18 00 00 00 00 00 00 00 00 00 00 00 00 00 c4

May I have more question?
Now I try many packages but still not successful. Those errors are:

  1. Jetpack 3.0: Can not download repository
  2. Jetpack 3.1: can not display HDMI
  3. L4T 27.1 Driver package: Our system stuck in reboot loop
  4. L4T 28.1 Driver package: can not display HDMI
  5. JetPack_3.0/64_TX2/Linux_for_Tegra_tx2: work well

Could you recommend most stable package that I should use?

Thanks

9

More information

nvidia@tegra-ubuntu:~$ sudo get-edid | parse-edid
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 3
No EDID on bus 4
No EDID on bus 5
No EDID on bus 6
No EDID on bus 8
1 potential busses found: 7
Bus 7 doesn't really have an EDID...
Couldn't find an accessible EDID on this computer.
I'm sorry nothing was successful. Maybe try some other arguments
if you played with them, or send an email to Matthew Kern <pyrophobicman@gmail.com>.
Partial Read... Try again

Hope it will be helpful

10 
Jetpack 3.1: Our system stuck in reboot loop  # What is the exact log for this??
L4T 28.1 Driver package: can not display HDMI # Two different errors?
11

Sorry my mistake, Jetpack 3.1 and L4T 28.1 Driver package have same error. Only can not display HDMI. I will edit.

12

Do you have tegra devkit that can test? If this only happens on the PCB, then I might not be able to reproduce it on my board.

13

I tried L4T 28.1 Driver package with tegra devkit then everything look working well.

But when I try download firmware with my previous Linux_for_Tegra_tx2 in Jetpack 3.0 for my custom board, HDMI work well.
It only happen on L4T 28.1 Driver package.

14

According to your previous comment, I make a brief summary. Please make confirmation.

1. Use TX2 + devkit
#HDMI work good on both BSP from Jetpack3.0 and Jetpack3.1.
2. Use TX1 + custom board
#HDMI work good only on BSP from Jetpack3.0 (rel-27.1) but not Jetpacke3.1 (rel-28.1)
3. Use TX1 + devkeit/custom board 
#Both work good
15

Correct summary

1. Use TX2 + dev kit : work well in every case
2. Use TX2 + custom: 
   + Jetpack3.0 (rel-27.1): HDMI work well even though I have to plug in/out a few time, network can not start
   +  Jetpacke3.1 (rel-28.1): HDMI only show mouse arrow, network work well

I will work around with Jetpacke3.1 (rel-28.1) by ssh to target board. But I hope HDMI will work soon.
And I need to rebuild kernel to support OV10635 image sensor so I hope kernel source rel-28.1 will be update soon.

Thanks

16

Hi forever3000,

Could you share following logs after boot up?

  1. /var/log/Xorg.0.log

  2. dmesg

It would be long, please don’t directly paste it on forum.

17

Yes, here it is

https://drive.google.com/open?id=0B1mvR8dWqu5xRWRBRThDbFdRTmM
18

It is long, please don’t directly paste it on forum. Could you put it into a file and use some share space?

19

Yes sorry, because I think [code] tag is big enough. I modified.

Thanks

20

Could you describe how is the test running?

Do you hotplug or just plugged and boot up?