Problem with TACP after DriveInstall 4.1.8.0

Hello,

After I flashed the DrivePX 2 P2379 with DriveInstall 4.1.8.0 I cannot power on the cameras anymore. The IP Address of Aurix is consistent with the one configured in the /etc/tacp/tacp.cfg. The version of the EB FW is 2.02.04.

This is the output of ‘status’:

shell> status
Info: Executing cmd: status, argc: 0, args: 
Alive       : 00:04:38
CPU load    : 40%
CPU load max: 42%

Hardware information: 
PMU-chip: B-Step
SCU_CHIPID: 0x4B459051
SystemUpInit-Time[ms]: 27
FPD-switch = 1 (Tegra-B)

IP-address (Tegra-A): 10.42.0.28
IP-address (Tegra-B): 10.42.0.29
IP-address   (AURIX): 10.42.0.146

MAC-address (Tegra-A): 0x000000044B7072E0
MAC-address (Tegra-B): 0x000000044B7072E1
MAC-address   (AURIX): 0x000000044B7072E2
MAC-address    (FPGA): 0x0000000000000000

Command Executed
shell>

This is the cat of tacp.cfg files:

Tegra A:

nvidia@nvidia:~$ cat /etc/tacp/tacp.cfg 
AURIX_IP_ADDRESS=10.42.0.146
TEGRA_A_IP_ADDRESS=10.42.0.28
TEGRA_B_IP_ADDRESS=10.42.0.29
TEGRA_IP_ADDRESS=10.42.0.28
AURIX_SERVER_PORT=5000
drive-px2-a=eth0.200
drive-px2-b=eth0.200
drive-px2-autocruise=lo
RECEIVE_TIMEOUT_S=5
RECEIVE_TIMEOUT_US=0
SPI_RECEIVE_TIMEOUT_US=1000000
nvidia@nvidia:~$

Tegra B:

nvidia@nvidia:~$ cat /etc/tacp/tacp.cfg 
AURIX_IP_ADDRESS=10.42.0.146
TEGRA_A_IP_ADDRESS=10.42.0.28
TEGRA_B_IP_ADDRESS=10.42.0.29
TEGRA_IP_ADDRESS=10.42.0.28
AURIX_SERVER_PORT=5000
drive-px2-a=eth0.200
drive-px2-b=eth0.200
drive-px2-autocruise=lo
RECEIVE_TIMEOUT_S=5
RECEIVE_TIMEOUT_US=0
SPI_RECEIVE_TIMEOUT_US=1000000
nvidia@nvidia:~$

When I run the TACP samples, they fail and tell me to check the IP Address of Aurix or the version of FW. The firmware delivered with PDK 4.1.8 is the 2.02.04, which is the same one I have installed. So in my mind it makes no sense to flash it manually again. However, I get this info when trying to auto update it with the script:

nvidia@nvidia:~$ sudo /etc/systemd/scripts/nv_aurix_check_fw.sh -auto_update
[sudo] password for nvidia: 
starting Aurix FW checking...
Checking arguments...
Rootfs EB FW version is 2.02.04.0
Remove ethernet cable from port if board is connected to external network
Press any key to continue
--------------------------------------------------------------------
!!! IMPORTANT INFORMATION BELOW REGARDING Aurix FW (PLEASE READ) !!!
 
Aurix is booted with old EB FW which doesn't support Aurix OTA
Please Flash new EB FW from Windows based Flasher as provided by PDK
 
THIS MESSAGE WILL CONTINUE TO BE SHOWN UNTIL ACTION MENTIONED IS TAKEN
With action taken, this script will be muted and not shown again
----------------------------------------------------------------------
 
nvidia@nvidia:~$

Where should I investigate the problem in this case?

Thank you,
Fabio

Dear Reway,

Could you check Aurix FW version with below command?
shell> version

I think you don’t need camera power on step manually when you run some camera applications.
Could you let me know your issued application or camera power on step in detail? Thanks.

Thank you for the prompt reply, SteveNV.

shell> version
Info: Executing cmd: version, argc: 0, args: 
SW Version: DPX2-EB-Aurix-1.02.1
Compilation date: Oct 21 2016, 13:57:23
Command Executed

I was just trying to run the sample camera applications

Problem solved

I had to update aurix fw with windows (run triload.bat and triload_update.bat);
Changed the IP address of aurix with setip a and changed it also in tacp.cfg files;
Run aurixreset.

Thanks!