VickNV
December 13, 2022, 5:54pm
22
Did you mean JetPack? It shouldn’t support DRIVE AGX Orin DevKit? How could you install/flash successfully? We are trying to figure out why only your system encountered this issue.
Please also provide the serial number of your system for us to check which version was pre-flashed prior to shipping it to you.
There are two systems, they have different SW problems, and neither shipped with an OS installed. The serial number does not appear anywhere on the computer, and I don’t know which came in which box. The cardboard shipping boxes say S/N 1412422000100 and 1412422000069
I used the SDKmanager to flash this system, and the only option it gave me was “Jetson”. After sorting out my developer account permissions my choices are “DRIVE” and “Jetson”. Nvidia product naming is incomprehensible.
VickNV
December 15, 2022, 3:35am
24
@jace.mogill1
Per below from your post in another topic (No network in DRIVE OS 6.0.5 on AGX Orin - #11 by jace.mogill1 ), the system still has the original aurix firmware instead of the one compatible with DRIVE OS 6.0.5. So DRIVE OS 6.0.5 installation with SDK Manager (tracked with this topic) is incomplete.
adi@tegra-ubuntu:~$ cat /etc/nvidia/version-ubuntu-rootfs.txt
6.0.5.0-31732390
adi@tegra-ubuntu:~$ sudo bash /etc/systemd/scripts/nv_aurix_check_fw.sh
[sudo] password for adi:
starting Aurix FW checking…
Checking arguments…
Checking Ping to AURIX
Ping to AURIX failed. Exit Aurix Updater.
adi@tegra-ubuntu:~$
Let’s focus on this installation topic first. I’ll check with our team and get back to you.
VickNV
December 28, 2022, 8:07pm
25
@jace.mogill1
Please follow Installation Methods to flash the devkit again with the docker container way.
After flashing and rebooting, please check if Aurix FW is automatically updated to DRIVE-V6.0.5-P3710-AFW-Aurix-StepB-5.06.05.
I’m not able to download/install the container because the PRIVATE REGISTRY
tab is missing from my NGC session. In the attached screenshot you can see I’m logged in and have selected drive/driveos-sdk, but the necessary tab is missing:
VickNV
January 5, 2023, 5:49pm
27
@jace.mogill1
Happy New Year. Good to see you going back to try the issue.
Please help create another topic for your NGC issue. Thanks.
VickNV
January 5, 2023, 5:57pm
28
In the meantime, please help check if installing with SDK Manager again still hit the original issue. If not, is aurix firmware upgraded successfully?
I will create another ticket for NGC.
I noticed yesterday the SDKManager was updated and tried it again, but it’s back to the UTF-8 decoding error:
[2023-01-05 09:30:03,198 root DEBUG console_logger.py 17 12899] b"[bootburn]: [ParseInfoRom_OAT(693)] : <class 'bootburn_t23x_py.bootburn_aurix.Object_Location_Table_Object'>\r\n"
[2023-01-05 09:30:03,198 root DEBUG console_logger.py 17 12899] b'[bootburn]: [ParseInfoRom_OAT(697)] : sysIndex :: 64\r\n'
[2023-01-05 09:30:03,199 root DEBUG console_logger.py 17 12899] b'[bootburn]: [ParseInfoRom_OAT(698)] : sm1Index :: 128\r\n'
[2023-01-05 09:30:03,199 root DEBUG console_logger.py 17 12899] b'[bootburn]: [ParseInfoRom_OAT(704)] : OAT\r\n'
[2023-01-05 09:30:03,200 root DEBUG console_logger.py 17 12899] b'[bootburn]: [ParseInfoRom_OAT(705)] : 6\r\n'
[2023-01-05 09:30:03,200 root DEBUG console_logger.py 17 12899] b'[bootburn]: [setTargetConfigt23xInfoRomInfo(716)] : 940-63710-0010-D00\r\n'
[2023-01-05 09:30:03,201 root DEBUG console_logger.py 17 12899] b'[bootburn]: [setTargetConfigt23xInfoRomInfo(717)] : None\r\n'
[2023-01-05 09:30:03,201 root DEBUG console_logger.py 17 12899] b'[bootburn]: [setTargetConfigt23xInfoRomInfo(724)] : ****** s_InforomSkuVersion D00\r\n'
[2023-01-05 09:30:03,202 root DEBUG console_logger.py 17 12899] b'[bootburn]: [setTargetConfigt23xInfoRomInfo(725)] : ****** s_InforomProdInfo 940-63710-0010\r\n'
[2023-01-05 09:30:03,202 root DEBUG console_logger.py 17 12899] b'[bootburn]: GetTegrasAssocWithAurix entered\r\n[bootburn]: Remove previous instances of files\r\n'
[2023-01-05 09:30:03,203 root DEBUG console_logger.py 17 12899] b'[bootburn]: [GetTegrasAssocWithAurix(507)] : Setting Tegra-A on hold... \r\n[bootburn]: ExecuteAurixCommand entered\r\n'
[2023-01-05 09:30:03,473 root DEBUG console_logger.py 17 12899] b"[bootburn]: [ExecuteAurixCommand(449)] : Send command on Aurix serial port: 'tegrareset x1 h\\n'\r\n"
[2023-01-05 09:30:03,475 root INFO runner.py 37 12899] 'utf-8' codec can't decode byte 0x81 in position 51: invalid start byte
[2023-01-05 09:30:03,475 root DEBUG runner.py 39 12899] Error on line 920
[2023-01-05 09:30:03,475 root DEBUG runner.py 40 12899] Exception info: Exception Type <class 'UnicodeDecodeError'>, Traceback <traceback object at 0x7ff19a90c948>
[2023-01-05 09:30:03,475 root INFO runner.py 45 12899] driveinstaller cannot continue! Check the log file for details: /home/mogill/.nvsdkm/driveinstaller.log
[2023-01-05 09:30:03,576 root DEBUG runner.py 62 12899] Cleaning up...
[2023-01-05 09:30:03,576 root DEBUG utilities.py 137 12899] Deleting temporary directories...
[2023-01-05 09:30:03,576 root DEBUG utilities.py 139 12899] Deleting /tmp/pdkinstall-tmp-vkm2b2nc-bind
[2023-01-05 09:30:03,577 root DEBUG runner.py 64 12899] Closing the log file.
I was able to re-flash the Orin from the container, however, the network interface still is not coming up.
adi@tegra-ubuntu:~$ ifconfig
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:6b:97:a8:75 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enP7p1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::4ab0:2dff:fe69:bbfb prefixlen 64 scopeid 0x20<link>
ether 48:b0:2d:69:bb:fb txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 22 bytes 2969 (2.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 32 bytes 2112 (2.1 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 32 bytes 2112 (2.1 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
VickNV
January 9, 2023, 6:45pm
31
Please help check the current aurix firmware version via the aurix console.
Let’s follow the network issue with your No network in DRIVE OS 6.0.5 on AGX Orin .
It did not update to DRIVE-V6.0.5-P3710-AFW-Aurix-StepB-5.06.05, still on DRIVE-v6.x.x-P3710-NV-Aurix-IFW-StepB-1.46.12:
Shell>version
DDPX Aurix Serial Console
P3710-A05
with TLF35584 B/C-Step
SW Version 1.46.12
DRIVE-v6.x.x-P3710-NV-Aurix-IFW-StepB-1.46.12
Patch 0
* P3710-TS5 bringup firmware
* this binary does not support P3710 TS1 ~ TS3
TC397 Step BD
Shell>
VickNV
January 10, 2023, 1:43am
33
Please share the journalclt log of the devkit for our investigation. Thanks.
Where do I find “the journalclt log”?
VickNV
January 10, 2023, 5:17pm
35
You can get the log by run “journalclt” command on the target.
I was looking in the container because this install was in a container.
These are the logs from the target:
journalctl.out (967.7 KB)
VickNV
January 11, 2023, 2:42pm
37
@jace.mogill1
It looks nv_aurix_check_fw.sh failed to upgrade due to the network issue. Let’s work on it from No network in DRIVE OS 6.0.5 on AGX Orin - #17 by VickNV
Oct 21 05:17:26 tegra-ubuntu bash[1591]: starting Aurix FW checking…
Oct 21 05:17:26 tegra-ubuntu bash[1591]: Checking arguments…
Oct 21 05:17:26 tegra-ubuntu bash[1591]: Checking Ping to AURIX
…
Oct 21 05:17:29 tegra-ubuntu bash[1591]: ***************************
Oct 21 05:17:29 tegra-ubuntu bash[1591]: Ping to AURIX failed. Exit Aurix Updater.
system
Closed
March 17, 2023, 7:04am
38
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.