Cannot retrieve device list: No such device

[ChrGui]

Hello !
I have a RevPi Connect S on wich I installed 241205-revpi-bookworm-arm64-default.img. Once connected, I installed all updates. In PiCtory 2.11.1, I configured a RevPi Connect/+/S with default configuration. After reboot, when I type piTest -d in the terminal, I get the message Cannot retrieve device list: No such device. What is the problem ?

[nicolaiB]

Hi,

What is the output of the following command?

- dmesg -l warn,err
- dpkg -l | grep -E 'picontrol|linux-image'
- lsmod
- cat /boot/firmware/config.txt

Nicolai

[ChrGui]

Hi, here is the results of the commands :

dmesg -l warn,err
[ 1.241881] dwc2 fe980000.usb: supply vusb_d not found, using dummy regulator
[ 1.242179] dwc2 fe980000.usb: supply vusb_a not found, using dummy regulator
[ 2.595031] piControl: loading out-of-tree module taints kernel.
[ 2.791107] systemd-journald[156]: File /var/log/journal/54035faecfe94b26ac4bee306d0cf519/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 6.815646] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[ 6.865889] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
[ 6.893837] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[ 6.906601] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
[ 6.916606] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[ 6.924294] rpivid_hevc: module is from the staging directory, the quality is unknown, you have been warned.
[ 6.949103] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[ 13.402030] piControl: problem at driver initialization
[ 13.402042] piControl: no piControl reset possible, a firmware update is running
[ 13.534074] piControl: problem at driver initialization
[ 13.534086] piControl: no piControl reset possible, a firmware update is running
[ 16.798024] piControl: problem at driver initialization
[ 16.798035] piControl: no piControl reset possible, a firmware update is running
[ 20.182018] piControl: problem at driver initialization
[ 20.182028] piControl: no piControl reset possible, a firmware update is running
[ 27.714019] piControl: problem at driver initialization
[ 27.714029] piControl: no piControl reset possible, a firmware update is running
[ 41.734012] piControl: problem at driver initialization
[ 41.734022] piControl: no piControl reset possible, a firmware update is running
[ 49.168314] cockpit-tls[2535]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
[ 55.722005] piControl: problem at driver initialization
[ 55.722016] piControl: no piControl reset possible, a firmware update is running
[ 69.754014] piControl: problem at driver initialization
[ 69.754025] piControl: no piControl reset possible, a firmware update is running
[ 83.733997] piControl: problem at driver initialization
[ 83.734008] piControl: no piControl reset possible, a firmware update is running
[ 97.806014] piControl: problem at driver initialization
[ 97.806024] piControl: no piControl reset possible, a firmware update is running
[ 111.737999] piControl: problem at driver initialization
[ 111.738010] piControl: no piControl reset possible, a firmware update is running
[ 125.742003] piControl: problem at driver initialization
[ 125.742013] piControl: no piControl reset possible, a firmware update is running
[ 139.733999] piControl: problem at driver initialization
[ 139.734009] piControl: no piControl reset possible, a firmware update is running
[ 153.738001] piControl: problem at driver initialization
[ 153.738011] piControl: no piControl reset possible, a firmware update is running
[ 167.746002] piControl: problem at driver initialization
[ 167.746012] piControl: no piControl reset possible, a firmware update is running
[ 181.722011] piControl: problem at driver initialization
[ 181.722021] piControl: no piControl reset possible, a firmware update is running
[ 195.734012] piControl: problem at driver initialization
[ 195.734022] piControl: no piControl reset possible, a firmware update is running
[ 209.742018] piControl: problem at driver initialization
[ 209.742027] piControl: no piControl reset possible, a firmware update is running
[ 223.741998] piControl: problem at driver initialization
[ 223.742008] piControl: no piControl reset possible, a firmware update is running
[ 237.734007] piControl: problem at driver initialization
[ 237.734018] piControl: no piControl reset possible, a firmware update is running
[ 251.750002] piControl: problem at driver initialization
[ 251.750012] piControl: no piControl reset possible, a firmware update is running
[ 265.734000] piControl: problem at driver initialization
[ 265.734011] piControl: no piControl reset possible, a firmware update is running
[ 279.734005] piControl: problem at driver initialization
[ 279.734016] piControl: no piControl reset possible, a firmware update is running
[ 293.738000] piControl: problem at driver initialization
[ 293.738011] piControl: no piControl reset possible, a firmware update is running
[ 307.742002] piControl: problem at driver initialization
[ 307.742012] piControl: no piControl reset possible, a firmware update is running
[ 321.730000] piControl: problem at driver initialization
[ 321.730010] piControl: no piControl reset possible, a firmware update is running
[ 335.734021] piControl: problem at driver initialization
[ 335.734031] piControl: no piControl reset possible, a firmware update is running
[ 349.730000] piControl: problem at driver initialization
[ 349.730010] piControl: no piControl reset possible, a firmware update is running
[ 363.818002] piControl: problem at driver initialization
[ 363.818012] piControl: no piControl reset possible, a firmware update is running
[ 377.737999] piControl: problem at driver initialization
[ 377.738008] piControl: no piControl reset possible, a firmware update is running
[ 391.734017] piControl: problem at driver initialization
[ 391.734027] piControl: no piControl reset possible, a firmware update is running
[ 405.742017] piControl: problem at driver initialization
[ 405.742027] piControl: no piControl reset possible, a firmware update is running
[ 419.734018] piControl: problem at driver initialization
[ 419.734028] piControl: no piControl reset possible, a firmware update is running
[ 433.726001] piControl: problem at driver initialization
[ 433.726011] piControl: no piControl reset possible, a firmware update is running
[ 447.722036] piControl: problem at driver initialization
[ 447.722048] piControl: no piControl reset possible, a firmware update is running
[ 461.730018] piControl: problem at driver initialization
[ 461.730029] piControl: no piControl reset possible, a firmware update is running
[ 475.729999] piControl: problem at driver initialization
[ 475.730009] piControl: no piControl reset possible, a firmware update is running
[ 489.738000] piControl: problem at driver initialization
[ 489.738010] piControl: no piControl reset possible, a firmware update is running
[ 503.734016] piControl: problem at driver initialization
[ 503.734027] piControl: no piControl reset possible, a firmware update is running
[ 517.798016] piControl: problem at driver initialization
[ 517.798026] piControl: no piControl reset possible, a firmware update is running
[ 531.730000] piControl: problem at driver initialization
[ 531.730022] piControl: no piControl reset possible, a firmware update is running
[ 545.742013] piControl: problem at driver initialization
[ 545.742024] piControl: no piControl reset possible, a firmware update is running
[ 559.730000] piControl: problem at driver initialization
[ 559.730010] piControl: no piControl reset possible, a firmware update is running
[ 573.730018] piControl: problem at driver initialization
[ 573.730029] piControl: no piControl reset possible, a firmware update is running
[ 587.730000] piControl: problem at driver initialization
[ 587.730010] piControl: no piControl reset possible, a firmware update is running
[ 601.746016] piControl: problem at driver initialization
[ 601.746026] piControl: no piControl reset possible, a firmware update is running
[ 615.729999] piControl: problem at driver initialization
[ 615.730010] piControl: no piControl reset possible, a firmware update is running
[ 629.794019] piControl: problem at driver initialization
[ 629.794029] piControl: no piControl reset possible, a firmware update is running
[ 643.801999] piControl: problem at driver initialization
[ 643.802010] piControl: no piControl reset possible, a firmware update is running
[ 657.726001] piControl: problem at driver initialization
[ 657.726026] piControl: no piControl reset possible, a firmware update is running
[ 671.737999] piControl: problem at driver initialization
[ 671.738009] piControl: no piControl reset possible, a firmware update is running
[ 685.738019] piControl: problem at driver initialization
[ 685.738029] piControl: no piControl reset possible, a firmware update is running
[ 699.733999] piControl: problem at driver initialization
[ 699.734009] piControl: no piControl reset possible, a firmware update is running
[ 713.729999] piControl: problem at driver initialization
[ 713.730009] piControl: no piControl reset possible, a firmware update is running
[ 727.726000] piControl: problem at driver initialization
[ 727.726011] piControl: no piControl reset possible, a firmware update is running
[ 741.737999] piControl: problem at driver initialization
[ 741.738009] piControl: no piControl reset possible, a firmware update is running

dpkg -l | grep -E 'picontrol|linux-image'
ii linux-image-6.6.0-revpi6-rpi-v8 6.6.46-rt39-revpi6-1+deb12+1 arm64 Linux kernel, version 6.6.0-revpi6-rpi-v8
ii linux-image-6.6.0-revpi7-rpi-v8 6.6.46-rt39-revpi7-1+deb12+1 arm64 Linux kernel, version 6.6.0-revpi7-rpi-v8
ii linux-image-revpi-v8 6.6.46-rt39-revpi7-1+deb12+1 arm64 Linux kernel for Revolution Pi devices (meta-package)
ii picontrol 2.3.2-1+deb12+1 arm64 RevPi piControl kernel module package (metapackage)
ii picontrol-6.6.0-revpi6-rpi-v8 2.3.1-1+deb12+3 arm64 RevPi piControl kernel module package
ii picontrol-6.6.0-revpi7-rpi-v8 2.3.2-1+deb12+1 arm64 RevPi piControl kernel module package
ii picontrol-common 2.3.2-1+deb12+1 all RevPi piControl kernel module package (common files)

lsmod
Module Size Used by
ftdi_sio 65536 0
usbserial 61440 1 ftdi_sio
v3d 90112 0
gpu_sched 49152 1 v3d
drm_shmem_helper 24576 1 v3d
raspberrypi_hwmon 12288 0
bcm2835_v4l2 40960 0
vc4 372736 2
videobuf2_vmalloc 16384 1 bcm2835_v4l2
rpivid_hevc 45056 0
bcm2835_codec 45056 0
raspberrypi_gpiomem 12288 0
bcm2835_isp 28672 0
bcm2835_mmal_vchiq 36864 3 bcm2835_codec,bcm2835_v4l2,bcm2835_isp
v4l2_mem2mem 45056 2 bcm2835_codec,rpivid_hevc
videobuf2_dma_contig 24576 3 bcm2835_codec,rpivid_hevc,bcm2835_isp
videobuf2_memops 16384 2 videobuf2_vmalloc,videobuf2_dma_contig
vc_sm_cma 40960 2 bcm2835_mmal_vchiq,bcm2835_isp
videobuf2_v4l2 32768 5 bcm2835_codec,bcm2835_v4l2,rpivid_hevc,v4l2_mem2mem,bcm2835_isp
videodev 307200 6 bcm2835_codec,videobuf2_v4l2,bcm2835_v4l2,rpivid_hevc,v4l2_mem2mem,bcm2835_isp
snd_bcm2835 28672 0
snd_soc_hdmi_codec 24576 1
drm_display_helper 16384 1 vc4
cec 53248 1 vc4
drm_dma_helper 24576 2 vc4
drm_kms_helper 212992 2 drm_dma_helper,vc4
videobuf2_common 69632 9 bcm2835_codec,videobuf2_vmalloc,videobuf2_dma_contig,videobuf2_v4l2,bcm2835_v4l2,rpivid_hevc,v4l2_mem2mem,videobuf2_memops,bcm2835_isp
snd_soc_core 303104 2 vc4,snd_soc_hdmi_codec
mc 81920 7 videodev,bcm2835_codec,videobuf2_v4l2,videobuf2_common,rpivid_hevc,v4l2_mem2mem,bcm2835_isp
snd_compress 28672 1 snd_soc_core
snd_pcm_dmaengine 16384 1 snd_soc_core
snd_pcm 147456 5 snd_bcm2835,snd_soc_hdmi_codec,snd_compress,snd_soc_core,snd_pcm_dmaengine
snd_timer 40960 1 snd_pcm
snd 114688 6 snd_bcm2835,snd_soc_hdmi_codec,snd_timer,snd_compress,snd_soc_core,snd_pcm
nvmem_rmem 12288 0
rfkill 32768 1
uio_pdrv_genirq 16384 0
uio 20480 1 uio_pdrv_genirq
binfmt_misc 24576 1
i2c_dev 24576 0
piControl 167936 0
ad5446 16384 0
ti_dac082s085 12288 0
mcp320x 20480 0
iio_mux 12288 0
mux_gpio 12288 0
mux_core 24576 2 mux_gpio,iio_mux
gpio_74x164 12288 0
spi_bcm2835aux 16384 0
spi_bcm2835 24576 0
pibridge 65536 1 piControl
gpio_max3191x 20480 1 piControl
crc8 12288 1 gpio_max3191x
industrialio 102400 5 ad5446,iio_mux,ti_dac082s085,piControl,mcp320x
drm 643072 8 gpu_sched,drm_kms_helper,drm_dma_helper,v3d,vc4,drm_shmem_helper,drm_display_helper
fuse 143360 1
dm_mod 143360 0
drm_panel_orientation_quirks 24576 1 drm
backlight 28672 2 drm_kms_helper,drm
ip_tables 32768 0
x_tables 53248 1 ip_tables
ipv6 585728 40

cat /boot/firmware/config.txt
# For more options and information see
# http://rptl.io/configtxt
# Some settings may impact device functionality. See link above for details

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

# Automatically load initramfs files, if found
auto_initramfs=1

# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d
max_framebuffers=1

# Don't have the firmware create an initial video= setting in cmdline.txt.
# Use the kernel's default instead.
disable_fw_kms_setup=1

# Run in 64-bit mode
arm_64bit=1

# Disable compensation for displays with overscan
disable_overscan=1

# Run as fast as firmware / board allows
arm_boost=1

[all]
dtoverlay=dwc2,dr_mode=host

Hope you will find something...
Chris

[nicolaiB]

The device is not properly initialized (factory reset is missing). Therefore the operating system does not know what device tree overlay to apply and the piControl driver cannot work.

Normally the factory reset is prompted upon first login. You can do it also manually with the following command:

sudo /usr/sbin/revpi-factory-reset connect <SERIAL> <MACADDRESS>

(replace <SERIAL> and <MACADDRESS> with the data from your device, you can find these information on the device front plate).

Hope this helps.

Nicolai

[ChrGui]

Now it works.
Thanks a lot Nicolai.

[alina104]

The error can be due to incorrect device configuration, missing drivers, or hardware issues.