Error dw_out_of_bounds

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General
1

Please provide the following info (check/uncheck the boxes after creating this topic):
Software Version
DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.6 and DriveWorks 4.0
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other

Target Operating System
Linux
QNX
other

Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other

SDK Manager Version
1.9.1.10844
other

Host Machine Version
native Ubuntu 18.04
other

Hello,

We are trying to run the program /usr/local/driveworks-4.0/bin/sample_gps_logger with the following parameters:

./sample_gps_logger --driver=gps.uart --params=device=/dev/ttyUSB0,baud=115200

However, we often get this error message in addition to the coordinates:

ERROR DW_OUT_OF_BOUNDS
Driveworks exception thrown: span::at: access out of bounds

The same program/sensor runs on the Xavier platform under DriveWorks 2.2 without any problems.

Many thanks in advance

3

Could you please specify which device is listed on the page you are using? Additionally, would you be able to share the complete output of the provided command?

4

Hello,

here is the output of the command:

nvidia@tegra-ubuntu:/usr/local/driveworks-4.0/bin$ ./sample_gps_logger  --driver=gps.uart --params=device=/dev/ttyUSB0,baud=115200
[28-11-2023 10:51:39] Platform: Detected DDPX - Tegra A
[28-11-2023 10:51:39] TimeSource: monotonic epoch time offset is 1701164811971061
[28-11-2023 10:51:39] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to eth0
[28-11-2023 10:51:39] TimeSource Eth: Lost PTP time synchronizaton. Synchronized time will not be available from this timesource.
[28-11-2023 10:51:39] TimeSource: Could not detect valid PTP time source at 'eth0'. Fallback to CLOCK_MONOTONIC.
[28-11-2023 10:51:40] Platform: number of GPU devices detected 2
[28-11-2023 10:51:40] Platform: currently selected GPU device discrete ID 0
[28-11-2023 10:51:40] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-4.0/bin/data/': VirtualFileSystem: Failed to mount '/usr/local/driveworks-4.0/bin/data/[.pak]'
[28-11-2023 10:51:40] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-4.0/bin/../data
[28-11-2023 10:51:40] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-4.0/bin/../data/': VirtualFileSystem: Failed to mount '/usr/local/driveworks-4.0/bin/../data/[.pak]'
[28-11-2023 10:51:40] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-4.0/data
[28-11-2023 10:51:40] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-4.0/data/': VirtualFileSystem: Failed to mount '/usr/local/driveworks-4.0/data/[.pak]'
[28-11-2023 10:51:40] SDK: No resources(.pak) mounted, some modules will not function properly
[28-11-2023 10:51:40] SDK: Create NvMediaDevice
[28-11-2023 10:51:40] SDK: Create NvMedia2D
[28-11-2023 10:51:40] egl::Display: found 2 EGL devices
[28-11-2023 10:51:40] egl::Display: use drm device: /dev/dri/card0
[28-11-2023 10:51:40] TimeSource: monotonic epoch time offset is 1701164811971062
[28-11-2023 10:51:40] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to eth0
[28-11-2023 10:51:40] TimeSource Eth: Lost PTP time synchronizaton. Synchronized time will not be available from this timesource.
[28-11-2023 10:51:40] TimeSource: Could not detect valid PTP time source at 'eth0'. Fallback to CLOCK_MONOTONIC.
[28-11-2023 10:51:40] Initialize DriveWorks SDK v4.0.0
[28-11-2023 10:51:40] Release build with GNU 7.3.1 from no-gitversion-build against Drive PDK v5.2.6.0
[28-11-2023 10:51:40] SensorFactory::createSensor() -> gps.uart, device=/dev/ttyUSB0,baud=115200
[28-11-2023 10:51:40] SensorFactory::createSensor() -> gps.uart, device=/dev/ttyUSB0,baud=115200
[28-11-2023 10:51:40] EndpointTTY: started on /dev/ttyUSB0
[28-11-2023 10:51:40] Driveworks exception thrown: span::at: access out of bounds

GPS[1] - 367256927968 ERROR DW_OUT_OF_BOUNDS
[28-11-2023 10:51:40] Driveworks exception thrown: span::at: access out of bounds

GPS[0] - 367256927968 ERROR DW_OUT_OF_BOUNDS
[28-11-2023 10:51:40] Driveworks exception thrown: span::at: access out of bounds

GPS[1] - 367256927968 ERROR DW_OUT_OF_BOUNDS
[28-11-2023 10:51:40] Driveworks exception thrown: span::at: access out of bounds

GPS[0] - 367256927968 ERROR DW_OUT_OF_BOUNDS
GPS[1] - 1701165100461949 lat: 52.555625 lon: 13.298768 alt: 34
GPS[0] - 1701165100461949 lat: 52.555625 lon: 13.298768 alt: 34
[28-11-2023 10:51:40] Driveworks exception thrown: span::at: access out of bounds

GPS[0] - 1701165100461949 ERROR DW_OUT_OF_BOUNDS
[28-11-2023 10:51:40] Driveworks exception thrown: span::at: access out of bounds

GPS[1] - 1701165100461949 ERROR DW_OUT_OF_BOUNDS
[28-11-2023 10:51:40] Driveworks exception thrown: span::at: access out of bounds

GPS[0] - 1701165100461949 ERROR DW_OUT_OF_BOUNDS
[28-11-2023 10:51:40] Driveworks exception thrown: span::at: access out of bounds

GPS[1] - 1701165100461949 ERROR DW_OUT_OF_BOUNDS
GPS[0] - 1701165100662178 lat: 52.555625 lon: 13.298768 alt: 34 course: 0 speed: 0.0
GPS[1] - 1701165100662178 lat: 52.555625 lon: 13.298768 alt: 34 course: 0 speed: 0.0
[28-11-2023 10:51:40] Driveworks exception thrown: span::at: access out of bounds

GPS[1] - 1701165100662178 ERROR DW_OUT_OF_BOUNDS
[28-11-2023 10:51:40] Driveworks exception thrown: span::at: access out of bounds

GPS[0] - 1701165100662178 ERROR DW_OUT_OF_BOUNDS
[28-11-2023 10:51:40] Driveworks exception thrown: span::at: access out of bounds

GPS[1] - 1701165100662178 ERROR DW_OUT_OF_BOUNDS
[28-11-2023 10:51:40] Driveworks exception thrown: span::at: access out of bounds

GPS[0] - 1701165100662178 ERROR DW_OUT_OF_BOUNDS
GPS[1] - 1701165100863303 lat: 52.555625 lon: 13.298768 alt: 34 course: 0 speed: 0.0
GPS[0] - 1701165100863303 lat: 52.555625 lon: 13.2987681 alt: 34 course: 0 speed: 0.0
[28-11-2023 10:51:41] Driveworks exception thrown: span::at: access out of bounds

We use the u-blox ZED-F9P module with NMEA protocol.

Best regards

6

Thank you for the information. It appears that the u-blox ZED-F9P module with NMEA protocol might not be fully compatible with DriveWorks 4.0, and the ‘Ublox: ZED-F9K in C103-F9K’ sensor listed on the page is recommended for use.

The F9P was an interim sensor for F9K, and only the UBX protocol was tested and functional on DriveWorks 3.5 at that time.

8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.