Hi,
When trying to flash the device, below error is observed.
Failed to bind partitions!
You can see the related log part below, how can I fix the problem and flash the chips, thanks!
[2019-11-02 19:03:32,475 root DEBUG inforom_data_handler.py 110 18176] Aurix port /dev/ttyUSB3 is open
[2019-11-02 19:03:35,579 root CRITICAL runner.py 37 18176] Failed to bind partitions!
[2019-11-02 19:03:35,580 root DEBUG runner.py 38 18176] Exception info:
Traceback (most recent call last):
File “/home/otonom/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_E3550/DriveSDK/pdkinstaller/module/pdk_bind.py”, line 87, in pdk_bind
board_rev = inforom_obj.get_Target_PCB()
File “/home/otonom/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_E3550/DriveSDK/pdkinstaller/module/inforom_data_handler.py”, line 86, in get_Target_PCB
self.__get_Inforom_dump()
File “/home/otonom/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_E3550/DriveSDK/pdkinstaller/module/inforom_data_handler.py”, line 124, in __get_Inforom_dump
trim_start = Info_data.index(self.Inforom_start_byte)
ValueError: ‘4D’ is not in list
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File “./pdkinstaller”, line 769, in
root_pwd = arguments.sudo_pwd
File “/home/otonom/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_E3550/DriveSDK/pdkinstaller/module/pdk_bind.py”, line 101, in pdk_bind
raise errors.FailedToBindPartitionsError()
module.errors.FailedToBindPartitionsError: Failed to bind partitions!
[2019-11-02 19:03:35,582 root CRITICAL runner.py 43 18176] pdkinstaller cannot continue! Check the log file for details: /home/otonom/nvidia/nvidia_sdk/DRIVE_Software_9.0_Linux_hyperion_E3550/DriveSDK/pdkinstaller/pdkinstaller.log
[2019-11-02 19:03:35,582 root DEBUG runner.py 60 18176] Cleaning up…
[2019-11-02 19:03:35,582 root DEBUG utilities.py 124 18176] Deleting temporary directories…
[2019-11-02 19:03:35,583 root DEBUG runner.py 62 18176] Closing the log file.
Dear sozekmok,
Could you please attached ~/.nvsdkm/logs folder and ~/.nvsdkm/sdkm.log files to get more insights.
I assume you have checked the prerequisites at [url]https://developer.nvidia.com/drive/downloads[/url] and has no issues with internet.
Yes, I can confirm that we meet prerequisites and have no issues regarding the internet.
I was using the AGX without any problems even on vehicle. But suddenly, first we observed the issue on the ticket that I have opened up this morning. I see that you also replied to that. https://devtalk.nvidia.com/default/topic/1065953/general/agx-tegra-a-amp-tegra-b-command-line-not-showing-up/
In order to solve this I tried flashing the Drive OS only to see this flashing problem.
You can see the logs that you have requested at the attachment. logs.zip (692 KB)
Dear sozekmek, The log shows to look at DRIVE_Software_9.0_Linux_hyperion_E3550/DriveSDK/pdkinstaller/pdkinstaller.log for more details. Could you attach that file
I have tried flashing from a different host and now I am experiencing another problem. You can see its log at the attachment. Flashing aborts with an error around %95.
I do appreciate your swift support, thanks for that. Hopefully we can find a way around this. pdkinstaller.log (994 KB)
Dear sozemek,
I could see “error-adb-timeout" in pdkinstaller.log . We provided a work around for it in Section 2.6 in our flashing technical bulletin shared in earlier message. Please check that. If that does not help, please share ~/.nvsdkm/logs and ~/.nvsdkm/sdkm.log on while flashing using new host. Also, please share host machine linux kernel version
My host machine linux kernel version is 4.15.0-66-generic.
Also, I have checked the link that you have provided. I understand you are refering to “Power Sequencing Required for Certain HDMI Monitors”, but right now I don’t have any HDMI monitors connected.
You can find the logs attached. logs.zip (454 KB)
Dear sozemek,
Could you please run sudo udevadm monitor on host machine terminal and check flashing. Please provide both flashing logs and terminal output check events?
Dear sozemek,
As I understand, the adb devices are not reachable while attempting flashing and hence you see adb timeout in logs. Could you please file a bug with all the logs and share it here. We will look into it.
Dear sozekmek,
Did you file bug, If so , please share bug ID here for follow up.
Please login to https://developer.nvidia.com/drive with your credentials. Please check MyAccount->MyBugs->Submit a new bug to file bug.
I have submitted a bug on the day that you have requested, 7th of November. Since 4th of November I am waiting for a solution and since 7th of November I am waiting for my bug to be resolved. Bug ID is 2752647. I think if you reach me via email we can find a solution for this as fast as possible, maybe through remote connection to the device.
Dear sozemek,
Is it possible to check from another Host PC(which never used for flashing) as I think some settings have messed up your system. Also, did you ever flash the board with anything other than DRIVE SW 9.0?
You have requested flashing from a different host PC on 5th of November and I did provide my feedback then. Yes, I have used another host PC that I have never used for flashing before. With that, I am receiving “error-adb-timeout” error. I have also tried flashing Xavier A and B separately with this host PC but kept on releasing the same error.
For the second question, no we haven’t flashed the board with anything other than Drive SW 9.0.
