I am having trouble flashing my drive pegasus system using SDK manager. Please see the attached screen shots for more information. I have been using the same method to flash my drive xavier platform and never had the same problem. Please advice what to do.
Thank you
Ian.
13:21:16 INFO : Flash Xavier A+B in parallel : -------------------------------------
13:21:16 INFO : Flash Xavier A+B in parallel :
13:21:16 INFO : Flash Xavier A+B in parallel : Tool OutPut:
13:21:16 INFO : Flash Xavier A+B in parallel : USB communication failed.Check if device is in recovery
13:21:16 INFO : Flash Xavier A+B in parallel : Tool OutPut to stderr:
13:21:16 INFO : Flash Xavier A+B in parallel : USB communication failed.Check if device is in recovery
13:21:16 INFO : Flash Xavier A+B in parallel : error-tool-tegrarcm
13:21:16 INFO : Flash Xavier A+B in parallel : bootburn flashing failed! error code = 50
13:21:16 INFO : Flash Xavier A+B in parallel : exit status 50
13:21:16 INFO : Flash Xavier A+B in parallel : [ Component Install Finished with Error ]
13:21:16 ERROR : Flash Xavier A+B in parallel : NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP command ./pdk_flash.sh -b e3550b03-t194-es finished with error
13:21:16 INFO : Flash Xavier A+B in parallel :
13:21:16 INFO : Flash Xavier A+B in parallel : [ 604.00 KB used. Disk Avail: 303.35 GB ]
13:21:16 INFO : Flash Xavier A+B in parallel : [ NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP Install took 33s ]
13:21:16 INFO : Flash Xavier A+B in parallel : command ./pdk_flash.sh -b e3550b03-t194-es finished with error
13:21:16 ERROR : Flash Xavier A+B in parallel : command terminated with error
13:21:16 ERROR : Flash Xavier A+B in parallel : install 'Flash Xavier A+B in parallel' failure, command <
Did you connect Host PC and Drive Xavier(USB Debug port) with USB 2.0 Type A cable?
If yes, could you please help to check the platform status via minicom tool?
Please refer to DRIVE OS → Utilitis → Minicom Terminal Emulation in DRIVE™ Software Documentation (ZIP).
Did you connect the USB cable when flashing with SDK manager?
If not, please connect the USB cable and try flashing with SDK manager.
13:21:16 INFO : Flash Xavier A+B in parallel : USB communication failed.Check if device is in recovery
According to the log you uploaded, USB cable seemed to be disconnected.
I am 100% sure that I have the USB cable connected. I was able to get the console print out in my host computer thru minicom. As I mentioned, I used the same method to flash Drive Xaiver board and I did not encounter the flashing problem.
There was a new finding today. I can flash the Drive Pegasus Board successfully if I log into the partner account (NVONLINE) in SDK manager, but I can’t flash the board (same problem as mentioned above) if I log into the developer account instead. Please let me know your suggestions and comments.
Could you please let me know what is the DRIVE build the you are trying to flash with both accounts?
When flashing failed, could you export and attach the full sdkm log?
We reviewed the log, it looks like there is a process that has a hold on the tty for the target:
+++++++++++++++++++++++++++++++++++++++++++++++++
38575 2019-04-02 11:29:56.512 - info: Aurix Port = /dev/ttyUSB3
38576 2019-04-02 11:29:56.512 - info: Target rootfs will be flashed into emmc
38577 2019-04-02 11:29:56.512 - info: ./bootburn.sh -b e3550b03-t194 -B qspi -x /dev/ttyUSB3
38578 2019-04-02 11:29:56.513 - info: Execute Xavier Script
38579 2019-04-02 11:29:56.544 - info: Successfully acquired lock over /var/lock/LCK…bootburn
38580 2019-04-02 11:29:56.545 - info: Successfully acquired lock over /var/lock/LCK…ttyUSB3
38581 2019-04-02 11:29:56.563 - info: Read skuinfo from InfoRom…
38582 2019-04-02 11:30:00.624 - info: Disabling SIGINT <Ctrl+C> temporarily
38583 2019-04-02 11:30:04.514 - info: Setting Tegra-A on hold… Done
38584 2019-04-02 11:30:07.493 - info: Setting Tegra-B on hold… Done
38585 2019-04-02 11:30:10.087 - info: Setting Tegra-A in recovery… Process CMD (16547) still running. Trying to kill after 5 seconds
38586 2019-04-02 11:30:18.435 - info: Done
38587 2019-04-02 11:30:24.095 - info: Setting Tegra-B in recovery… Process CMD (16907) still running. Trying to kill after 5 seconds
38588 2019-04-02 11:30:29.583 - info: Done
38589 2019-04-02 11:30:29.818 - info: Enabling SIGINT <Ctrl+C>
+++++++++++++++++++++++++++++++++++++++++++++++++
We are a little unclear on the exact process going on here, but could you check if the port is has a user on it?
I think I am in the same situation as ian.liu has reported before:
I cannot flash “Drive software 8.0” on Pegasus via Developer account. Got the same error message on minicom:
[0007.587] C> RATCHET: MB1 binary ratchet level 1 is less than ratchet level 2 from HW fuses.
[0007.595] E> task 4 failed (err: 0x5b5b0108)
[0007.599] E> top caller module: RATCHET, error module: RATCHET, reason: 0x08, aux_info: 0x01
[0007.607] I> MB1(00.24.180726-t194-41334769-23fb1f28) BIT boot status dump :
1111100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[0007.637] I> Reset to recovery mode
[000
I can flash “Drive OS 5.1.0.0” via Partner account successfully, but DriveWorks is not installed by default.
By talking with the Nvidia representative, I understand the discrete GPU is not supported by “Drive Software 8.0” yet, will have to wait for next release.
In this situation, If assume I don’t use the discrete GPU features on Pegasus for now, is it possible to emulate the “Drive-Xavier” configurations with “Drive-Pegasus” hardware? Or is there any other way to run some of the “Drive Networks” apps on Pegasus?
@SteveNV,
Could you please kindly help me to clarify if SDKManager v0.9.9.2.3.5.1 (or any newer version) is ready to flash Pegasus SKU2200? I cannot flash my two units of Pegasus so far…:( Thanks!
@SteveNV,
It seems my issue is not belonging to Chip ID Error while flashing a DRIVE AGX Pegasus, no “Failed to get UID of chip” from error-tool-tegrarcm and being similar to problem of ian.liu.
@ian.liu
Do you fix it and any suggestion for me? Thanks!
@SteveNV,
I have been investing on flashing Pegasus but saw comment from leowang,
"…I can flash “Drive OS 5.1.0.0” via Partner account successfully, but DriveWorks is not installed by default.
By talking with the Nvidia representative, I understand the discrete GPU is not supported by “Drive Software 8.0” yet, will have to wait for next release…"
@SteveNV,
I flash Pegasus by NVONLINE account (garywang@itri.org.tw) again but suffer this account is not have authorized to flash Pegasus. Any idea to help me?
I can create issue in nvidia online (e.g. #2485258 Gary Wang 1/13/2019 ITRI automotive [ITRI TW] Clock skew detected when booting finished).
Because I only used built-in DRIVE OS (5.1.0.0-13431798) for testing and development so far.
For risk management in project schedule, I am afraid some situations of my Pegasus fail rebooting due to our testing or Ubuntu setting in DRIVE OS then needs flash mechanism to reset our DRIVE OS in Pegasus.
Could you please help to teach me how to flash or factory reset for DRIVE OS (5.1.0.0-13431798) on Pegasus.
Did you connect USB cable between Pegasus and HostPC?
Because according to the log files you attached, USB cable seems to be disconnected.
“Make sure only one target is connected to USB”
.
.
.
Tool OutPut:
USB communication failed.Check if device is in recovery
Tool OutPut to stderr:
USB communication failed.Check if device is in recovery
error-tool-tegrarcm