may I know what’s your actual use-case for using JetPack-3.3.1?
the latest production release of JetPack SDK is JetPack-4.4.1, which supporting all Jetson modules.
it seems JetPack release image has already download to your local machine.
could you please duplicate the image flashing process with the flash script file.
you may found the image as following, for example, ~/nvidia/nvidia_sdk/JetPack_3.3.1_Linux_P2888/Linux_for_Tegra/
please refer to developer guide, Basic Flash Script Usage to enable flash script to flash the board.
thanks
I need to use L4T 28 for compatibility with my application, this is why I can’t use 4.4.1. As for why I can’t use 3.3.3, I need L4T 28.3 in order to get a device to flash with balenaOS.
since I’m not working with rel-28 for a long time. I should mentioned it’s my assumption of the path name.
yes, please goes with Linux_for_Tegra directory for the JetPack release image.
there’s param for target board naming, please exclude conf from the command line for a try.
you should execute flash script as following, $ sudo ./flash.sh jetson-tx2 mmcblk0p1
FYI, we had also test this locally. we’re able to flash JP-3.3.1 on TX2 via SDKManager without failures.
thanks
Jerry, please see my most recent post where I said:
I have posted the complete logs of multiple different flashing attempts. Both the specific logs for ./flash.sh and general logs for the SDKmanager flash.
The information that
does not help me if I don’t know why my flashes are failing.
Have you seen this error before?
Am I perhaps missing a step in the flashing process?
Is there anything I need to do to prepare a Tx2 for being flashed again after it has been flashed improperly before?
Is Ubuntu 16.04 + SDKManager1.4.0.7363 the right version combinations to use?
Should I be using the Tx2 devboard or something different?
If I’m reading correctly, you are trying to flash your TX2 for use with the Orbitty Carrier Board, correct? If that’s the case, our Tech Support Team would be happy to point you in the direction of the correct BSP for JetPack 3.3.2, and help you flash your module. If you fill out our support form, the tech team will get you up and running; you can find the form here: Customer Support Form - Connect Tech Inc..
I have tried flashing the TX2 DevKit with SDK Manager 1.4.0 and JetPack 3.3.1. This is something I have attempted about 3 - 4 times. With this approach I get the error:
tegradevflash_vn --iscpubl
Cannot Open USB
I also tried flashing directly onto the CTI Orbitty, which is the series of steps followed in this post:
I am trying to flash my TX2 for use with balenaOS. The particular version of balenaOS I require is compatible only with L4T 28.3 (found in Jetpack 3.3.1 and 3.3.2).
I don’t think I need your help, the flashing step with balenaOS media should take care of the CTI Orbitty carrier board requirements. Does that sound right?
I’m not sure what is going wrong, but here is another attempt to flash a tx2 on theDevKit with SDK Manager, this time on Ubuntu 18.04 (just in case that was the issue) SDKM_logs_2021-01-08_09-13-23.zip (112.9 KB) .
Same Cannot Open USB error. Are you not seeing this issue on your devices? Have you seen this issue before? I’ve seen some mention in the forums, but never really a diagnosis of it.
Use only TX2 devkit and ubutnu 16.04./18.04 Please note that VMs are not permitted. And we don’t know of CTI board would work or not, so do not use that board at this moment.
Try different usb cable/ tx2 modules, if you have multiple of them. This is to prevent hardware defect.
Try different host machines if possible.
Dump the serial console log from both host and device. As this page indicates
Please note that I need both host and device flash log. All the log you have pasted are host side log.
The device log requires the ttl usb cable to dump from uart.
I have done many tests with ubuntu 16.04 and 18.04 on a physical host machine connected to the DevKit.
I have tested 5 usb cables and I have tested different tx2 modules. More on that below
I have tried multiple host machines. 3 different ones.
I haven’t yet dumped the serial console logs from the device. I may do that, however I have an update.
These TX2s I’m trying to flash are brand new, and almost all of them give me problems. Only 3 of the 8 devices I’ve tested have flashed successfully. However, when I try to flash older TX2s from previous orders they work just fine.
I believe there may be a problem with the hardware I have received. It could either be that something changed on the hardware and wasn’t tested with Jetpack 3.3.1/3.3.2, or perhaps this is just a bad batch.
That would explain why, with the exact same setup, some devices work and others don’t. It would also explain why JetPack 3.3.1 is working for you but not for me.
How could I test the hardware to get a more definitive answer as to whether I have received a bad batch?
However, when I try to flash older TX2s from previous orders they work just fine.
I don’t quite understand this comment. Could you elaborate what are “older TX2” and “previous orders”?
Did you mean some tx2 that was bought before that can be flashed without error?
If these new modules failed to get flashed on jetpack3.x release, then please use jetpack4.4.1 and see if you can see the problem on jetpack4.4.1. This is just for debug and not asking you to use jetpack4.4.1 forever. We should at least find a version that can flash your modules to confirm modules are not broken.
If jetpack4.4.1 can flash your boards, I would guess this maybe some issue related to the TX2 PCN. Since you said “new TX2” would be affected. The latest PCN of TX2 indicates that only rel-28.4 and jetpack4.4 support specific modules.
You could just use sdkmanager to download Linux_for_Tegra. After that, directly use flash.sh to do the flash work to save your time.