Running issue with dvxplorer and jetson nano

[jmenness]

Hello,

First of all, thank you very much for this library! I have a problem when I run dvxplorer_test.py on my jetson nano. I have the following errors:

Device ID: 1
Device Serial Number: DXM00013
Device USB bus Number: 2
Device USB device address: 3
Device String: DVXplorer ID-1 SN-DXM00013 [2:3]
Device Firmware Version: 8
Logic Version: 18
Device Chip ID: 20
Device is master.
MUX has statistics: False
Device size X: 640
Device size Y: 480
DVS has statistics: False
IMU Type: 3
EXT input has generator: False
2022-02-26 14:05:40 (TZ-0800): ERROR: DVXplorer ID-1 SN-DXM00013 [2:3]: Error message: 'VR_CPLD_CONFIG READ: failed SPI config read' (code 64 at time 137065).
2022-02-26 14:05:40 (TZ-0800): ERROR: DVXplorer ID-1 SN-DXM00013 [2:3]: Error message: 'VR_CPLD_CONFIG READ: failed SPI config read' (code 64 at time 137070).
2022-02-26 14:05:40 (TZ-0800): ERROR: DVXplorer ID-1 SN-DXM00013 [2:3]: Error message: 'VR_CPLD_CONFIG READ: failed SPI config read' (code 64 at time 137075).
2022-02-26 14:05:40 (TZ-0800): ERROR: DVXplorer ID-1 SN-DXM00013 [2:3]: Error message: 'VR_CPLD_CONFIG WRITE: failed SPI config write' (code 64 at time 137081).
2022-02-26 14:05:40 (TZ-0800): ERROR: DVXplorer ID-1 SN-DXM00013 [2:3]: Error message: 'VR_CPLD_CONFIG WRITE: failed SPI config write' (code 64 at time 137100).
2022-02-26 14:05:41 (TZ-0800): ERROR: DVXplorer ID-1 SN-DXM00013 [2:3]: Error message: 'VR_CPLD_CONFIG READ: failed SPI config read' (code 64 at time 137869).
2022-02-26 14:05:41 (TZ-0800): ERROR: DVXplorer ID-1 SN-DXM00013 [2:3]: Error message: 'VR_CPLD_CONFIG READ: failed SPI config read' (code 64 at time 137874).
2022-02-26 14:05:41 (TZ-0800): ERROR: DVXplorer ID-1 SN-DXM00013 [2:3]: Error message: 'VR_CPLD_CONFIG READ: failed SPI config read' (code 64 at time 137880).
2022-02-26 14:05:41 (TZ-0800): ERROR: DVXplorer ID-1 SN-DXM00013 [2:3]: Error message: 'VR_CPLD_CONFIG READ: failed SPI config read' (code 64 at time 137885).
2022-02-26 14:05:41 (TZ-0800): ERROR: DVXplorer ID-1 SN-DXM00013 [2:3]: Error message: 'VR_CPLD_CONFIG READ: failed SPI config read' (code 64 at time 137890).
{'mux_timestamp_reset': 0, 'drop_extinput_on_transfer_stall': 0, 'mux_drop_dvs_on_transfer_stall': 0, 'imu_accel_data_rate': 6, 'imu_accel_filter': 2, 'imu_accel_range': 1, 'imu_gyro_data_rate': 5, 'imu_gyro_filter': 2, 'imu_gyro_range': 2, 'extinput_detect_rising_edges': 0, 'extinput_detect_falling_edges': 0, 'extinput_detect_pulses': 0, 'extinput_detect_pulse_polarity': 0, 'extinput_detect_pulse_length': 0, 'usb_early_packet_delay': 0, 'current_range_log': 0, 'current_range_sf': 1, 'current_range_on': 1, 'current_range_nrst': 0, 'current_range_loga': 1, 'current_range_logd': 1, 'current_level_sf': 1, 'current_level_noff': 0, 'current_amp': 4, 'current_on': 0, 'current_off': 8}
Traceback (most recent call last):
File "dvxplorer_test.py", line 48, in
device.get_event("events_hist")
TypeError: 'NoneType' object is not iterable

On my laptop, there's no problem, everything works fine.

Can you help me please ?

Thank you !

Best regards !

[duguyue100]

Hi, @jmenness , may I ask how did you install pyaer on Jetson Nano? I recall Jetson Nano has an ARM processor, therefore you will need to build the library yourself. Although I had supplied some ARM wheel files in the past, they were built on a Raspberry Pi.

You said it works fine on your computer, which means there might be a difference between the X86 and ARM architecture.

The device info was correctly parsed, so that means the libcaer indeed compiled successfully.
I tried to search the error message in the libcaer source but there is no luck.
I've experienced a similar error before. At that time, the USB port was busy. Perhaps you can try to reboot the Jetson Nano, connect the device, and run the script again?

In the meantime, let me check with the iniVation user group, and see if they have any solutions.

Yuhuangl

[jmenness]

Hi @duguyue100,

Thank you very much for your very quick answer !
Indeed, I build the library by myself using the makefile. I tried to reboot my jetson nano but I still have the same error.

Thank you very much again for your answer! I'll let you know if I find the solution.
best regards

José

[duguyue100]

@jmenness

This is the quick response by the awesome Luca Longinotti

This is a DVXplorer Mini. That's basically an error that it cannot
properly setup the chip configuration in the firmware.
If the same code works on one pc and fails on the other, and you can
reproduce this going back and forth, the camera itself is fine.
My best guesses would be faulty USB cable or insufficient USB power.

This is where I posted the thread at iniVation user group: https://groups.google.com/g/dv-users/c/v8ZBUr7I0H8/m/sXo-TVadAgAJ

Yuhuang.

[jmenness]

@duguyue100,

Thank you so much ! I will try to find a solution to increase USB power output !

Best regards,

José

[tobidelbruck]

It might be that the jetson nano and camera together take too much power from the USB bus... do you have one of the little USB voltage/current meters? Like these? https://www.aliexpress.com/wholesale?spm=a2g0o.productlist.0.0.21402c6cGn6NP1&catId=15370310&SearchText=usb%20power%20meter Those will show you that VBUS is dropping way down from 5V. Or else the Jetson itself is limiting the VBUS power it supplies on its USB port

[jmenness]

Hi @tobidelbruck,

Thank you so much for your response !
Unfortunately, I don't personally have this kind of USB current meter but I will try to get one to test. I will let you know as soon as I have taken the measurements.

Best regards,

José

[jmenness]

Hi @duguyue100 and @tobidelbruck,

I found a solution ! The problem was due to libcaer version. First, I tried to install it with the script provided in pyaer.
Now, I just compile libcaer directly from the libcaer git repository and everything works very well !
Maybe, the script to install libcaer should be updated in pyaer repository.

Thank you again for your support !

Best regards !

José

[duguyue100]

I see, very interesting, the last time I updated the libcaer version was about 3 months ago. I will bump the version later.

thanks for the tips!