I suffered from this issue today as well, and tested various Ubuntu 16.04 Distro.
From 16.04.1 to 16.04.5.
Testing of every Distro as follows:
Install ubuntu newly
install NVIDIA driver (410.93 on GFX 1060)
install sdkmanager (0.9.9-2351)
Run sdkmanager
As I tested, all Distro. returned faults to install Drive SW.
However, only one, 16.04.3 (4.13.0-36 kernel) could succeed PARTIALLY.
It means ‘Flash Xavier-A’ and ‘Flash Xavier-B’ each other.
‘Flash Xavier A+B’ never done.
And next, even OS installation, none like DriveWorks, DriveAV/AR/IX etc were installed.
Should I install them manually with dependency checks?
Some Error might be there in installation scripts?
Thanks,
updated
I have to add sth.
My desktop has the 8th gen Intel CPU, therefore, some old Distro. can not detect/install proper drivers like Ethernet.
Without Ethernet, sdkmanager is not able to run at first.
Without this condition, IMO, with older than 16.04.3 Distro. Installation job would operate well.
Thanks
updated
I tried to install DriveAV/AR/IX manually.
Manual commands as follow at deb packages /root/apt-repos;
$ sudo dpkg -i *.deb
However lots of dependency error occurred and failed.
Even GMSL sample application of DriveWorks does not work. sample_drivenet works!
Dear astutaka,
Can you try flashing Xavier A again as davyhuang is able to succeed in second attempt after flashing Tegra B. Let us know if you still have issue
I tried to run sdkmanager again to the target with ‘Flash Xavier-A+B’ and made it!
Target looks clear and made sure Xavier A and B boot properly, Aurix FW(V5.0.13-E3550-EB-xxx) as well.
DriveAV/AR/IX are installed as expected, even not tested yet.
However, this time, GMSL camera example does not work, same with #22.
To test I use SF3325 included in the accessory box.
I attach error log here.
Thanks, err_cam1.log (1.79 KB)
Dear ddpx2,
Just to confirm, are you able to flash Xavier A+B in parallel via SDKmanager? or you flashed each xavier at a time?
Could you double check if camera connected to A0 port? The error looks like you have not connected camera to A0 port.
Firstly, flashed each other through sdkmanager.
But, here, I’ve got some problems that some packages were not installed and did something by manual. Therefore, file system might have been changed.
Then I tried to install again via sdkmanager, at this step, only flashing directly.
That’s all. some DriveAV example is running.
I have another one.
I have flashed it by using sdkManager, and everything is OK.
There is a difference of HW only.(Host PC, USB cable, harness cable, power supply are the same.)
I would be grateful if you could tell about any information we should check.
Any information would greatly help.
Thanks.
updated
I have changed to the aurix version below and am testing, but occur the same issue at the moment…
Thank you for your prompt update.
Sorry for the inconvenience, I would like to ask you one more thing.
We need some more data for this issue.
I would appreciate it if you get the log in the following way and share it.
-. Identifying USB device for TegraA and TegraB.
Remove all USB cables connected to the host system
List all ttyUSB and confirm nothing available "ls -la /dev/ttyUSB*”
Connect Target to host, make sure you connect only Tegra board
Confirm 16 ttyUSB devices are listed.“ls -la /dev/ttyUSB*”
The following are the Target ports for
Aurix - /dev/ttyUSB3
TegraA - /dev/ttyUSB2
TegraB - /dev/ttyUSB6
Please get Target kernel logs using minicom/screen.
Like Atsutaka we also have problems with flashing the drive. We made a separate forum post, but there we have not received any repsonse yet. My team and I would like to know if there is a solution or more information about the problem. In the post we will add a bootcapture of Tegra-A and Tegra-B when booting both devices with the AURIX.
The logs “minicom_tegraA_on_ddpx.log” show the kernel boot has stopped.
This is Tegra boot with recovery off, not flashing kernel boot logs (i.e., during flashing with recovery on).
So is it fair to summarize as follows.
User flashed successfully TegraA
switched off TegraA recovery (tegrarecovery x1 off) and reset TegraA
3.captured the TegraA logs.
Could you please update the current status on this target and about the TegraA logs attached?