Hi,
I was trying to use Jetpack-3.0 to flash OS images on TX-2. However, and host is ubuntu 14.04 LTS.
When I flash the OS, I got the following error message:
./tegraflash.py --chip 0x18 --applet "/home/jungle/workspace/jetpack3.0/64_TX2/Linux_for_Tegra_tx2/bootloader/mb1_recovery_dev.bin" --cmd "dump eeprom boardinfo cvm.bin" --skipuid
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
[ 0.0016 ] Generating RCM messages
[ 0.0026 ] tegrarcm_v2 --listrcm rcm_list.xml --chip 0x18 --download rcm /home/jungle/workspace/jetpack3.0/64_TX2/Linux_for_Tegra_tx2/bootloader/mb1_recovery_dev.bin 0 0
[ 0.0035 ] File /home/jungle/workspace/jetpack3.0/64_TX2/Linux_for_Tegra_tx2/bootloader/mb1_recovery_dev.bin open failed
[ 0.0035 ] Cannot create RCM messages
[ 0.0035 ]
Error: Return value 19
Command tegrarcm_v2 --listrcm rcm_list.xml --chip 0x18 --download rcm /home/jungle/workspace/jetpack3.0/64_TX2/Linux_for_Tegra_tx2/bootloader/mb1_recovery_dev.bin 0 0
Reading board information failed.
I also tried to use jetpack 3.0 and 3.1 with ubuntu 16.04 LTS, but I got the same message.
Does someone have same problem?
And can anyone help me in fixing this problem?
Hi linuxdev,
I don’t use the USB HUB, and the USB is the pure micro USB line…
By the way, I can not boot my Tx2 normally(no internet, and the screen shows “Not support input”). I used the HDMI to VGA converter, but I can boot the tx1 with same way.
When the Jetson is in recovery mode does it show up with “lsusb”? FYI, “lsusb -d 0955:” shows all NVIDIA USB devices, “lsusb -d 0955:7721” shows all TX1s in recovery mode, and “lsusb -d 0955:7c18” shows all NVIDIA TX2s in recovery mode. If you see recovery mode devices then you know the USB pipe is functioning to at least some minimal extent…if you can’t see it via lsusb, then you know there is a USB issue needing a fix before you can continue.
Using a VGA adapter guarantees video cannot auto configure. This would of course have nothing to do with the flash problem, but if flash does succeed the monitor will only work if you get lucky and the default mode is something the monitor works with (VGA adapters literally cut the cable wire used for monitor query). So far as boot success goes, don’t count video not working as a way to determine if the system is failing.
Unless the hardware is non-standard it shouldn’t be possible for this value to differ. I would suspect a corrupt ROM if this is an ordinary TX2 and the ID does not match 0955:7c18. Or perhaps this is the ID of something else from NVIDIA and not the Jetson. Are you absolutely positive that the 0955:7018 shows up only when the TX2 is connected and in recovery mode? If this really is the TX2, what do you see from:
Is there anything at all custom about this hardware? I don’t know if NVIDIA has a product ID 0x7018…if not, then this is a hardware failure…if there is such a product, and if this really is a Jetson TX2, then you got the wrong chip (I see it listed as “APX”…perhaps this is a real product which is different from a JTX1/JTX2). On the assumption that this really is a JTX2 and is not customized, then you probably should RMA. RMA info is near the top of this:
[url]https://devtalk.nvidia.com/default/topic/793798/embedded-systems/some-jetson-web-links/[/url]