Dear @ashwin.nanda ,
Yes please try on other boot chain.
Hi @SivaRamaKrishnaNV thank you for the confirmation, but we tried to set the bootchain to B and reproduced the same steps again, however, we have encountered into a issue now:
pomo@tegra-ubuntu:/usr/local/driveworks$ common_if_testapp -set_next_bootchain x1 B
DU_MCC_InitResources: Failed to open NvSciIpc endpoint. err is: 0x1100
Failed to initialize IPC resource
Failed to initialize DU MCC
pomo@tegra-ubuntu:/usr/local/driveworks$ common_if_testapp -tegrareset x1
DU_MCC_InitResources: Failed to open NvSciIpc endpoint. err is: 0x1100
Failed to initialize IPC resource
Failed to initialize DU MCC
pomo@tegra-ubuntu:/usr/local/driveworks$
This was minicom port ACM0, as we cant access the target through monitor now
Plus when tried to clean flash again after poweron/off (through ACM1) :
2024-11-26 16:53:36 INFO : Flashing already set for dual bootchain
2024-11-26 16:53:36 INFO : Setting flash clean to initialize persistent partitions
2024-11-26 16:53:36 INFO : Initiating pre-flash check
2024-11-26 16:53:36 INFO : Checking Serial Port Connection
2024-11-26 16:53:36 INFO : Serial Port found /dev/ttyACM1
2024-11-26 16:53:36 INFO : Running basic open/close tests on Serial Port Connection
2024-11-26 16:53:36 INFO : Serial Port is open
2024-11-26 16:53:36 INFO : Flushing input and output buffer, discard all content
2024-11-26 16:53:36 INFO : Serial Port is closed
2024-11-26 16:53:36 INFO : Checking available targets
2024-11-26 16:53:36 INFO : Checking Orin board connection
2024-11-26 16:53:36 INFO : Orin board with Device ID -- 0955:7045 found.
2024-11-26 16:53:36 INFO : Orin board device path is /dev/bus/usb/003/040
2024-11-26 16:53:36 INFO : Pre-flash check complete
2024-11-26 16:53:36 INFO : Flashing DRIVE OS Docker
2024-11-26 16:53:56 INFO : driveinstaller v2.0
2024-11-26 16:53:56 INFO :
2024-11-26 16:53:56 INFO : SDK/PDK Installer and Flasher
2024-11-26 16:53:56 INFO : Run `./driveinstaller --help` for usage information.
2024-11-26 16:53:56 INFO :
2024-11-26 16:53:56 INFO : Initializing board and OS configuration to Autonomous vehicle p3710 Linux Tegra A
2024-11-26 16:53:56 INFO : Manifest version 2.0
2024-11-26 16:53:56 INFO :
2024-11-26 16:53:56 INFO : BOARD SKU : 940-63710-0010-300
2024-11-26 16:53:56 INFO : Found matching board id p3710-10-s05 in 940-63710-0010-300 sku
2024-11-26 16:53:56 INFO : Applying additional Bind opts []
2024-11-26 16:53:56 INFO : Binding of partitions failed ! Check log for more details.
2024-11-26 16:53:56 INFO : Failed to bind partitions!
2024-11-26 16:53:56 INFO : driveinstaller cannot continue! Check the log file for details: /drive/driveinstaller/driveinstaller.log
2024-11-26 16:53:56 ERROR : Flashing failed, please contact provider with logs /drive_flashing/log_3chr046pu8jm1d7kyxw9ebvqa5fz2sli.txt and /drive/driveinstaller/driveinstaller.log.
attached the flash logs as well:
driveinstaller.log (175.5 KB)
dear @SivaRamaKrishnaNV please note that I tried resetting the SoC through ACM1 as well, however no effects.
dear @SivaRamaKrishnaNV Im creating a new thread regarding this, this has lead to divergent problems with the SoC.
Dear @ashwin.nanda ,
It is not clear why flashing is tried again. Do you any issue with booting into another bootchain? Please file a new topic
@SivaRamaKrishnaNV CGF custom node integration fails with display, we have decided to run the applications in offscreen mode for now.
Dear @SivaRamaKrishnaNV ,
We are making the new thread for the Custom CGF Issue
CGF custom node integration queries will be handled by @prit.shah from now on.