Flashing p2379 Aurix from Windows - Documentation is unclear

I am trying to flashing the Aurix version of my p2379 from windows.
According to the doc:
To flash the firmware

  1. On the Windows system, navigate to the location of the AURIX flashing script:

<aurix_version>/bin/EB-DrivePX-BSL

  1. With a text editor, open Triload.bat and modify it as follows:

Specify the COM port connected to the AURIX console as determined in the steps in Configuring the Windows COM Port. For example:

set uart_comport=COM39

  1. Place the AURIX switch into programming (PRG) mode.

The AURIX UART flashing switch on the vehicle harness enables AURIX firmware programming.

The PRG mode is also referred to as ASC bootloader mode.

Note: The flashing switch is only evaluated by AURIX at power-up.

What does that mean? Do I have to switch the button to PRG and then restart the p2379 in order to make aurix be aware of the state change from Run to Prg?
If so, then I’m afraid all windows terminal settings are reset to 9600 baud and hence the update is doomed to fail??

Another documentation part that needs clarification is:
What is the necessary state that the system has to be in, in order to enable flashing the AURIX firmware?
I am asking, because in order to flash Tegra A and B boards it was necessary to issue commands via ubuntu terminal (i.e.: tegra recovery a on and tegra reset a (same for b)
Do I have to manually switch the Tegra recovery mode off before AURIX flashing?

Thank you for your support.

Dear @hermann.fuerntratt,
keep the aurix switch in prog mode and reboot the target and check flashing. Once the aurix flashing is completed, change the aurix switch to RUN mode and reboot the target and check if the aurix verison is updated.
Let us know if you have issues?

Yeah, there are issues indeed: /

Ok, I have successfully flashed the AURIX firmware with the Windows tool.
I have successfully flashed the firmware update with the Windows tool.
I have shut down p2379
I have reconnected the 8 cams - that have been working before
I switched to RUN mode
I have rebooted p2379
I have started nvidia@tegra-ubuntu:/usr/local/driveworks/bin$ ./sample_camera_gmsl
I see the same error as before

nvidia@tegra-ubuntu:/usr/local/driveworks/bin$ ./sample_camera_gmsl
[3-12-2020 11:22:49] Initialize DriveWorks SDK v1.2.400
[3-12-2020 11:22:49] Release build with GNU 4.9.4 from v1.2.0-rc11-0-ga7f5475 against Vibrante PDK v5.0.10.3
[3-12-2020 11:22:49] Platform: Detected Drive PX2 - Tegra A
[3-12-2020 11:22:49] TimeSource: monotonic epoch time offset is 1606994456075403
[3-12-2020 11:22:49] TimeSource: PTP ioctl returned error. Synchronized time will not be available.
[3-12-2020 11:22:49] TimeSource: Could not detect valid PTP time source at ‘eth0’. Fallback to CLOCK_MONOTONIC.
[3-12-2020 11:22:49] Platform: number of GPU devices detected 2
[3-12-2020 11:22:49] Platform: currently selected GPU device discrete ID 0
[3-12-2020 11:22:49] SDK: Resources mounted from …/./data/resources
[3-12-2020 11:22:49] SDK: Create NvMediaDevice
[3-12-2020 11:22:49] SDK: Create NvMediaIPPManager
[3-12-2020 11:22:49] SDK: use EGL display as provided
[3-12-2020 11:22:50] SensorFactory::createSensor() -> camera.gmsl, output-format=yuv,fifo-size=3,camera-type=ar0231-rccb-bae-sf3324,csi-port=a,slave=0
[3-12-2020 11:22:50] CameraGMSL: required FPS = 30, resolution = 1920x1208
receive_from: Timeout Error.
Please check Ethernet ip configuration or
Update Aurix firmware version by the following command

sudo /bin/bash /etc/systemd/scripts/nv_aurix_check_fw.sh -auto_update

nvmedia isc: TacpCamPowerControl: 237: TACP command failed with ret -5
iscRootDevOpen: Failed to power on camera(s)
NvMediaISCRootDeviceCreate: Unable to open root device
nvmedia: ERROR: Init: Failed to create NvMedia ISC root device
[3-12-2020 11:22:55] Driveworks exception thrown: DW_SAL_CANNOT_CREATE_SENSOR: CameraGMSL: cannot connect to camera

terminate called after throwing an instance of ‘std::runtime_error’
what(): [2020-12-03 11:22:55] DW Error DW_SAL_CANNOT_CREATE_SENSOR executing DW function:
dwSAL_createSensor(&m_camera, params, m_sal)
at /builds/driveav/dw/sdk/samples/sensors/camera_gmsl/main.cpp:153
Aborted (core dumped)
nvidia@tegra-ubuntu:/usr/local/driveworks/bin$ sudo /bin/bash /etc/systemd/scripts/nv_aurix_check_fw.sh -auto_update
[sudo] password for nvidia:
starting Aurix FW checking…
Checking arguments…
Rootfs FW version is 4.02.04.0
No_Response_From_Aurix
Ping to 10.42.0.146
Try with virtual ethernet iface
Remove ethernet cable from port if board is connected to external network
Press any key to continue
Cannot find device “eth0.200”

!!! IMPORTANT INFORMATION BELOW REGARDING Aurix FW (PLEASE READ) !!!

Aurix is booted with old FW which doesn’t support Aurix OTA
Please Flash new 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

Restore_default_network
nvidia@tegra-ubuntu:/usr/local/driveworks/bin$

what can I do to be able to record again?
Thank you

Dear @hermann.fuerntratt,
Could you please follow the discussion on Sf3325 can not work on px2 to see if helps and provide feedback.

It does not help really.
For a test, I have connected the cams to p3407 running DriveWorks 1.2.400, aurix version
shell> version
Info: Executing cmd: version, argc: 0, args:
SW Version: DRIVE-V5.0.10-P3407-EB-Aurix-With3LSS-4.02.04
Compilation date: Aug 13 2018, 21:50:50
Command Executed
shell>

shell> status shows
Hardware information:
PMU-chip: B-Step
SCU_CHIPID: 0x4B459051
SystemUpInit-Time[ms]: 49

IP-address (Tegra): 10.42.0.28
IP-address (AURIX): 10.42.0.146

MAC-address (Tegra): 0x0000000000000000
MAC-address (AURIX): 0x0000000000000000

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
nvidia@tegra-ubuntu:/usr/local/driveworks/bin$ ./sample_camera_gmsl --camera-type=ar0231-rccb-bae-sf3324 runs without problems

nvidia@tegra-ubuntu:/usr/local/driveworks/bin$ ./sample_camera_gmsl --camera-type=ar0231-rccb-bae-sf3324
[30-11-2020 17:3:59] Initialize DriveWorks SDK v1.2.400
[30-11-2020 17:3:59] Release build with GNU 4.9.4 from v1.2.0-rc11-0-ga7f5475 against Vibrante PDK v5.0.10.3
[30-11-2020 17:3:59] Platform: Detected Drive PX2 - Tegra A
[30-11-2020 17:3:59] TimeSource: monotonic epoch time offset is 1606752056144372
[30-11-2020 17:3:59] TimeSource: PTP ioctl returned error. Synchronized time will not be available.
[30-11-2020 17:3:59] TimeSource: Could not detect valid PTP time source at ‘eth0’. Fallback to CLOCK_MONOTONIC.
[30-11-2020 17:3:59] Platform: number of GPU devices detected 1
[30-11-2020 17:3:59] Platform: currently selected GPU device integrated ID 0
[30-11-2020 17:3:59] SDK: Resources mounted from …/./data/resources
[30-11-2020 17:3:59] SDK: Create NvMediaDevice
[30-11-2020 17:3:59] SDK: Create NvMediaIPPManager
[30-11-2020 17:3:59] SDK: use EGL display as provided
[30-11-2020 17:3:59] SensorFactory::createSensor() -> camera.gmsl, output-format=yuv,fifo-size=3,camera-type=ar0231-rccb-bae-sf3324,csi-port=a,slave=0
[30-11-2020 17:3:59] CameraGMSL: required FPS = 30, resolution = 1920x1208
***** aurix state *****
CAM_PWR_ON: 0x0
TEGRA_GMSL: TEGRA B
TEGRA_FPDL: TEGRA B
TEGRA_A_HDMI: MXM
TEGRA_B_HDMI: MXM
TEGRA_PCI: TEGRA B
FAN_STATE: UNKNOWN


***** aurix state *****
CAM_PWR_ON: 0x1
TEGRA_GMSL: UNKNOWN
TEGRA_FPDL: UNKNOWN
TEGRA_A_HDMI: UNKNOWN
TEGRA_B_HDMI: UNKNOWN
TEGRA_PCI: UNKNOWN
FAN_STATE: UNKNOWN


[30-11-2020 17:3:59] CameraGMSL: default IPP event callback function set
Successfully initialized camera with resolution of 1920x1208 at framerate of 30.000000 FPS
Timing results:
Thread main:
-onProcess CPU: 26us, std= 36 | GPU: 10us, std= 82 | samples=259
-onRender CPU: 31289us, std=3068 | GPU: 32846us, std=2822 | samples=259

[30-11-2020 17:4:8] Sensor statistics for: camera.gmsl, output-format=yuv,fifo-size=3,camera-type=ar0231-rccb-bae-sf3324,csi-port=a,slave=0
[30-11-2020 17:4:8] Events: 261
Errors: 0
Drops: 0
minDelta: 33307.0000000
maxDelta: 33368.0000000
meanDelta: 33332.394531
Standard deviation: 10.866838
***** aurix state *****
CAM_PWR_ON: 0x0
TEGRA_GMSL: UNKNOWN
TEGRA_FPDL: UNKNOWN
TEGRA_A_HDMI: UNKNOWN
TEGRA_B_HDMI: UNKNOWN
TEGRA_PCI: UNKNOWN
FAN_STATE: UNKNOWN


[30-11-2020 17:4:8] SDK: Release NvMediaDevice
[30-11-2020 17:4:8] Driveworks SDK released
[30-11-2020 17:4:8] SDK: Release NvMedia2D

//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
So the same cams just run without problems on p3407
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Compare output with p2379

nvidia@tegra-ubuntu:/usr/local/driveworks/bin$ ./sample_camera_gmsl --camera-type=ar0231-rccb-bae-sf3324
[3-12-2020 11:31:16] Initialize DriveWorks SDK v1.2.400
[3-12-2020 11:31:16] Release build with GNU 4.9.4 from v1.2.0-rc11-0-ga7f5475 against Vibrante PDK v5.0.10.3
[3-12-2020 11:31:16] Platform: Detected Drive PX2 - Tegra A
[3-12-2020 11:31:16] TimeSource: monotonic epoch time offset is 1606994456035886
[3-12-2020 11:31:16] TimeSource: PTP ioctl returned error. Synchronized time will not be available.
[3-12-2020 11:31:16] TimeSource: Could not detect valid PTP time source at ‘eth0’. Fallback to CLOCK_MONOTONIC.
[3-12-2020 11:31:16] Platform: number of GPU devices detected 2
[3-12-2020 11:31:16] Platform: currently selected GPU device discrete ID 0
[3-12-2020 11:31:16] SDK: Resources mounted from …/./data/resources
[3-12-2020 11:31:16] SDK: Create NvMediaDevice
[3-12-2020 11:31:16] SDK: Create NvMediaIPPManager
[3-12-2020 11:31:16] SDK: use EGL display as provided
[3-12-2020 11:31:16] SensorFactory::createSensor() -> camera.gmsl, output-format=yuv,fifo-size=3,camera-type=ar0231-rccb-bae-sf3324,csi-port=a,slave=0
[3-12-2020 11:31:16] CameraGMSL: required FPS = 30, resolution = 1920x1208
receive_from: Timeout Error.
Please check Ethernet ip configuration or
Update Aurix firmware version by the following command

sudo /bin/bash /etc/systemd/scripts/nv_aurix_check_fw.sh -auto_update

nvmedia isc: TacpCamPowerControl: 237: TACP command failed with ret -5
iscRootDevOpen: Failed to power on camera(s)
NvMediaISCRootDeviceCreate: Unable to open root device
nvmedia: ERROR: Init: Failed to create NvMedia ISC root device
[3-12-2020 11:31:21] Driveworks exception thrown: DW_SAL_CANNOT_CREATE_SENSOR: CameraGMSL: cannot connect to camera

terminate called after throwing an instance of ‘std::runtime_error’
what(): [2020-12-03 11:31:21] DW Error DW_SAL_CANNOT_CREATE_SENSOR executing DW function:
dwSAL_createSensor(&m_camera, params, m_sal)
at /builds/driveav/dw/sdk/samples/sensors/camera_gmsl/main.cpp:153
Aborted (core dumped)

What can I do next?

Dear @hermann.fuerntratt,
Are you able to ping Aurix from Tegra A?
Please share the output of cat /etc/tacp/tacp.cfg

I cannot ping Aurix 10.42.0.146 neither on p3407 nor on p2379.

The minicom - version command shows a difference in the compilation date
shell> version
Info: Executing cmd: version, argc: 0, args:
SW Version: DRIVE-V5.0.10-P2379-EB-Aurix-With3LSS-4.02.04
Compilation date: Aug 13 2018, 21:48:18
Command Executed
shell>
21:48:18 on p2379 vs 21:50:50 on p3479

catalog of tacp.cfg shows

nvidia@tegra-ubuntu:~ sudo cat /etc/tacp/tacp.cfg [sudo] password for nvidia: AURIX_IP_ADDRESS=10.42.0.146 TEGRA_A_IP_ADDRESS=10.42.0.28 TEGRA_B_IP_ADDRESS=10.42.0.29 TEGRA_CVM_IP_ADDRESS=10.42.0.30 TEGRA_IP_ADDRESS=10.42.0.28 AURIX_SERVER_PORT=5000 AURIX_EASYCAN_PORT=50000 TEGRA_EASYCAN_PORT=60395 drive-px2-a=eth0.200 drive-px2-b=eth0.200 drive-px2-autocruise=lo drive-ax=eth0.200 ddpx-a=eth0.200 ddpx-b=eth0.200 ddpx-c=eth0.200 e3550_t194a=eth0.200 e3550_t194b=eth0.200 p2888-t194=eth0.200 RECEIVE_TIMEOUT_S=5 RECEIVE_TIMEOUT_US=0 SPI_RECEIVE_TIMEOUT_US=1000000 nvidia@tegra-ubuntu:~

nvidia@tegra-ubuntu:~$ sudo cat /etc/tacp/tacp.cfg
[sudo] password for nvidia: 
AURIX_IP_ADDRESS=10.42.0.146
TEGRA_A_IP_ADDRESS=10.42.0.28
TEGRA_B_IP_ADDRESS=10.42.0.29
TEGRA_CVM_IP_ADDRESS=10.42.0.30
TEGRA_IP_ADDRESS=10.42.0.28    
AURIX_SERVER_PORT=5000
AURIX_EASYCAN_PORT=50000
TEGRA_EASYCAN_PORT=60395
drive-px2-a=eth0.200
drive-px2-b=eth0.200
drive-px2-autocruise=lo
drive-ax=eth0.200
ddpx-a=eth0.200
ddpx-b=eth0.200
ddpx-c=eth0.200
e3550_t194a=eth0.200
e3550_t194b=eth0.200
p2888-t194=eth0.200
RECEIVE_TIMEOUT_S=5
RECEIVE_TIMEOUT_US=0
SPI_RECEIVE_TIMEOUT_US=1000000
nvidia@tegra-ubuntu:~$

ifconfig on p2379 shows

nvidia@tegra-ubuntu:~$ sudo ifconfig

 docker0   Link encap:Ethernet  HWaddr 02:42:fe:a8:e9:6a  
      inet addr:172.17.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
      UP BROADCAST MULTICAST  MTU:1500  Metric:1
      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0 
      RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

enp3s0    Link encap:Ethernet  HWaddr 00:04:4b:5f:fb:41  
      UP BROADCAST MULTICAST  MTU:1500  Metric:1
      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000 
      RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth0      Link encap:Ethernet  HWaddr 00:04:4b:70:71:87  
      inet addr:10.42.0.2  Bcast:10.42.0.255  Mask:255.255.255.0
      inet6 addr: fe80::204:4bff:fe70:7187/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:276 errors:0 dropped:0 overruns:0 frame:0
      TX packets:282 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000 
      RX bytes:36420 (36.4 KB)  TX bytes:38258 (38.2 KB)
      Interrupt:46 

eth0.200  Link encap:Ethernet  HWaddr 00:04:4b:70:71:87  
      inet addr:10.42.0.28  Bcast:10.42.0.255  Mask:255.255.255.0
      inet6 addr: fe80::204:4bff:fe70:7187/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:25 errors:0 dropped:0 overruns:0 frame:0
      TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000 
      RX bytes:2195 (2.1 KB)  TX bytes:8522 (8.5 KB)

lo        Link encap:Local Loopback  
      inet addr:127.0.0.1  Mask:255.0.0.0
      inet6 addr: ::1/128 Scope:Host
      UP LOOPBACK RUNNING  MTU:65536  Metric:1
      RX packets:26 errors:0 dropped:0 overruns:0 frame:0
      TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1 
      RX bytes:2012 (2.0 KB)  TX bytes:2012 (2.0 KB)

Dear @hermann.fuerntratt,
The aurix version on both seems to be the latest one. So p3407 works with out any issue where as p2379 has issues in running sample_camera_gmsl.
Did you change ethernet ip configuration? Not sure why eth0 is showing 10.42.x.x. Is it your subnet?
Do you notice the same error on both TegraA/B of p2379?
Which camera module are you using?

Dear @SivaRamaKrishnaNV,
since the settings described in


have not worked -

auto eth1
iface eth1 inet static
    address 10.0.0.1
    netmask 255.255.255.0

(no response)
and the network configuration file on the target side is undocumented, or I have not digged deep enough to find them
Which network configuration do I need on the target side to make the settings above work?

Thank you

Dear @hermann.fuerntratt,
You do not need to make any extra network setting on target. DHCP server assign IP as per your subnet. Could you just keep the default settings(after flashing the target with sdkmanager) and connect LAN cable to your target and see ifconfig. The sample_camera_gmsl is expected to work out of the box without any extra settings.

Ok, I have the following network setup on the host:
nic1 is configured as eth0 is the local connection to target
nic2 is configured as eth1 and connects to the internet.

ifconfig on the host shows

eth0      Link encap:Ethernet  HWaddr 00:50:fc:6a:00:df  
      inet addr:10.0.0.1  Bcast:10.0.0.255  Mask:255.255.255.0
      inet6 addr: fe80::250:fcff:fe6a:df/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:8 errors:0 dropped:0 overruns:0 frame:0
      TX packets:80 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000 
      RX bytes:2696 (2.6 KB)  TX bytes:9850 (9.8 KB)

eth1      Link encap:Ethernet  HWaddr 00:19:99:e0:de:f0  
      inet addr:<whatever>  Bcast:<whatever>  Mask:255.255.255.0
      inet6 addr: <whatever>/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:3978 errors:0 dropped:0 overruns:0 frame:0
      TX packets:1973 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000 
      RX bytes:1681138 (1.6 MB)  TX bytes:341719 (341.7 KB)
      Interrupt:20 Memory:fb600000-fb620000 

lo        Link encap:Local Loopback  
      inet addr:127.0.0.1  Mask:255.0.0.0
      inet6 addr: ::1/128 Scope:Host
      UP LOOPBACK RUNNING  MTU:65536  Metric:1
      RX packets:182 errors:0 dropped:0 overruns:0 frame:0
      TX packets:182 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000 
      RX bytes:13614 (13.6 KB)  TX bytes:13614 (13.6 KB)

dhcp settings are

cuda@drivepx2host:~$ sudo cat /etc/default/isc-dhcp-server 
# Defaults for isc-dhcp-server initscript
# sourced by /etc/init.d/isc-dhcp-server
# installed at /etc/default/isc-dhcp-server by the maintainer scripts

#
# This is a POSIX shell fragment
#

# Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf).
#DHCPD_CONF=/etc/dhcp/dhcpd.conf

# Path to dhcpd's PID file (default: /var/run/dhcpd.pid).
#DHCPD_PID=/var/run/dhcpd.pid

# Additional options to start dhcpd with.
#	Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead
#OPTIONS=""

# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
#	Separate multiple interfaces with spaces, e.g. "eth0 eth1".
# changed this from INTERFACES="" to "eth0"
INTERFACES="eth0"

/etc/dhcp/dhcpd.conf shows

cuda@drivepx2host:~$ sudo cat /etc/dhcp/dhcpd.conf

#
# Sample configuration file for ISC dhcpd for Debian
#
# Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as
# configuration file instead of this file.
#
#

# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style none;

#Added to allow dhcp for the local eth0 connection on AutoChauffeur p2379
allow bootp;
subnet 10.0.0.0 netmask 255.255.255.0 {
   option routers 10.0.0.1
   option domain-name joanneum.at
   option domain-name-servers <whatever>, <whatever>
   default-lease-time 345600;  
   max-lease-time 31557600;   
   range 10.0.0.2 10.0.0.254;
   option root-path "10.0.0.1:/home/cuda/nvidia/nvidia_sdk/DRIVE_OS_5.0.10.3_SDK_with_DriveWorks_Linux_OS_PX2_AUTOCHAUFFEUR/DriveSDK/drive-t186ref-linux/targetfs,wsize=8192,rsize=8192,v3";
}



# option definitions common to all supported networks...
option domain-name "example.org";
option domain-name-servers ns1.example.org, ns2.example.org;

default-lease-time 600;
max-lease-time 7200;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;

# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;

# No service will be given on this subnet, but declaring it helps the 
# DHCP server to understand the network topology.

#subnet 10.152.187.0 netmask 255.255.255.0 {
#}

# This is a very basic subnet declaration.

#subnet 10.254.239.0 netmask 255.255.255.224 {
#  range 10.254.239.10 10.254.239.20;
#  option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
#}

# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.

#subnet 10.254.239.32 netmask 255.255.255.224 {
#  range dynamic-bootp 10.254.239.40 10.254.239.60;
#  option broadcast-address 10.254.239.31;
#  option routers rtr-239-32-1.example.org;
#}

# A slightly different configuration for an internal subnet.
#subnet 10.5.5.0 netmask 255.255.255.224 {
#  range 10.5.5.26 10.5.5.30;
#  option domain-name-servers ns1.internal.example.org;
#  option domain-name "internal.example.org";
#  option subnet-mask 255.255.255.224;
#  option routers 10.5.5.1;
#  option broadcast-address 10.5.5.31;
#  default-lease-time 600;
#  max-lease-time 7200;
#}

# Hosts which require special configuration options can be listed in
# host statements.   If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.

#host passacaglia {
#  hardware ethernet 0:0:c0:5d:bd:95;
#  filename "vmunix.passacaglia";
#  server-name "toccata.fugue.com";
#}

# Fixed IP addresses can also be specified for hosts.   These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP.   Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
#host fantasia {
#  hardware ethernet 08:00:07:26:c0:a5;
#  fixed-address fantasia.fugue.com;
#}

# You can declare a class of clients and then do address allocation
# based on that.   The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.

#class "foo" {
#  match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
#}

#shared-network 224-29 {
#  subnet 10.17.224.0 netmask 255.255.255.0 {
#    option routers rtr-224.example.org;
#  }
#  subnet 10.0.29.0 netmask 255.255.255.0 {
#    option routers rtr-29.example.org;
#  }
#  pool {
#    allow members of "foo";
#    range 10.17.224.10 10.17.224.250;
#  }
#  pool {
#    deny members of "foo";
#    range 10.0.29.10 10.0.29.230;
#  }
#}

Restarting dhcp server

sudo /etc/init.d/isc-dhcp-server restart

ping 10.42.0.28
cuda@drivepx2host:~$ ping 10.42.0.28
PING 10.42.0.28 (10.42.0.28) 56(84) bytes of data.
From 10.42.0.28 icmp_seq=1 Packet filtered
From 10.42.0.28 icmp_seq=2 Packet filtered
From 10.42.0.28 icmp_seq=3 Packet filtered
From 10.42.0.28 icmp_seq=4 Packet filtered
From 10.42.0.28 icmp_seq=5 Packet filtered
From 10.42.0.28 icmp_seq=6 Packet filtered
From 10.42.0.28 icmp_seq=7 Packet filtered
^C
— 10.42.0.28 ping statistics —
7 packets transmitted, 0 received, +7 errors, 100% packet loss, time 6147ms

cuda@drivepx2host:~$ ping 10.42.0.29
PING 10.42.0.29 (10.42.0.29) 56(84) bytes of data.
From 10.42.0.29 icmp_seq=1 Packet filtered
From 10.42.0.29 icmp_seq=2 Packet filtered
From 10.42.0.29 icmp_seq=3 Packet filtered
From 10.42.0.29 icmp_seq=4 Packet filtered
^C
— 10.42.0.29 ping statistics —
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3075ms

cuda@drivepx2host:~$ ping 10.42.0.146
PING 10.42.0.146 (10.42.0.146) 56(84) bytes of data.
From 10.42.0.146 icmp_seq=1 Packet filtered
From 10.42.0.146 icmp_seq=2 Packet filtered
^C
— 10.42.0.146 ping statistics —
2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1010ms

cuda@drivepx2host:~$

So configuring according to the doc does not work as expected.

nfs is configured as follows:

cuda@drivepx2host:~$ sudo cat /etc/exports
# /etc/exports: the access control list for filesystems which may be exported
#		to NFS clients.  See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes       hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4        gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes  gss/krb5i(rw,sync,no_subtree_check)
#

# ADDed to mount target filesystem 
# Add the corresponding path to the target file system:
10.0.0.1:/home/cuda/nvidia/nvidia_sdk/DRIVE_OS_5.0.10.3_SDK_with_DriveWorks_Linux_OS_PX2_AUTOCHAUFFEUR10.0.0.1/DriveSDK/drive-t186ref-linux/targetfs *(async,rw,no_root_squash,no_all_squash,no_subtree_check)

sudo ifconfig on p2379 shows

docker0   Link encap:Ethernet  HWaddr 02:42:55:d1:b4:4c  
      inet addr:172.17.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
      UP BROADCAST MULTICAST  MTU:1500  Metric:1
      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0 
      RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

enp3s0    Link encap:Ethernet  HWaddr 00:04:4b:5f:fb:41  
      UP BROADCAST MULTICAST  MTU:1500  Metric:1
      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000 
      RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth0      Link encap:Ethernet  HWaddr 00:04:4b:70:71:87  
      inet6 addr: fe80::204:4bff:fe70:7187/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:26 errors:0 dropped:0 overruns:0 frame:0
      TX packets:118 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000 
      RX bytes:3926 (3.9 KB)  TX bytes:15558 (15.5 KB)
      Interrupt:46 

eth0.200  Link encap:Ethernet  HWaddr 00:04:4b:70:71:87  
      inet addr:10.42.0.28  Bcast:10.42.0.255  Mask:255.255.255.0
      inet6 addr: fe80::204:4bff:fe70:7187/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:12 errors:0 dropped:0 overruns:0 frame:0
      TX packets:72 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000 
      RX bytes:1008 (1.0 KB)  TX bytes:7961 (7.9 KB)

lo        Link encap:Local Loopback  
      inet addr:127.0.0.1  Mask:255.0.0.0
      inet6 addr: ::1/128 Scope:Host
      UP LOOPBACK RUNNING  MTU:65536  Metric:1
      RX packets:20 errors:0 dropped:0 overruns:0 frame:0
      TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1 
      RX bytes:1533 (1.5 KB)  TX bytes:1533 (1.5 KB)

Dear @SivaRamaKrishnaNV,
as the current state - not beeing able to record any camera stream with the upgraded p2379 - is very unpleasant, what can I do to fix this issue?
Thank you

Dear @hermann.fuerntratt,
What is the camera module you are using? As aurix is upgraded, If possible, could you reflash the target again and try check using camera. Don’t make any networking changes on target after flash. Once you connect lan cable to target, I would expect to see IP gets assigned. Please share ifconfig outputs on both tegras. Please revert back with update

Dear @kuyteam001,
the cams are working now, just after installing the new NVSDKManager and reflashing aurix.

Dear @hermann.fuerntratt,
Thank you for update. please file a new topic, if you notice any issue