piVCCU: Can't get piVCCU working for RPI-RF-MOD
I do know piVCCU should be working with HMRPI-RF-MOD, so I must be doing something wrong. I just got a fresh HMRPI-RF-MOD delivered and wanted to tinker with it and my RPi 3B.
I have followed the steps outlined at https://github.com/alexreinert/piVCCU/blob/master/docs/setup/raspberrypi.md. The problem is that piVCCU just doesn’t start and doesn’t recognize the hardware. I do see the AMA0 device though - should I somehow test a raw serial connection?
Before playing around with a million things I got an installation error on a subroutine with status code 255. pivccu-info showed “lxc doesn’t exist” and no HMRF hardware. I now played around some more (see bottom for things I have tried) and have a weird /dev/raw_uart5 for “connected via” which looks wrong.
ls -l /dev/ttyAMA0
crw--w---- 1 root tty 204, 64 Nov 30 23:22 /dev/ttyAMA0
ls -l /dev/serial*
lrwxrwxrwx 1 root root 7 Nov 30 23:22 /dev/serial0 -> ttyAMA0
lrwxrwxrwx 1 root root 5 Nov 30 23:22 /dev/serial1 -> ttyS0
pivccu-info
piVCCU version: 3.53.34-49
Kernel modules: Available
Raw UART dev: Available
Rasp.Pi UART: Assigned to GPIO pins
HMRF Hardware: unknown
Connected via: (/dev/raw-uart5)
Board serial: unknown
Radio MAC: unknown
HMIP Hardware: unknown
SGTIN: unknown
Radio MAC: unknown
State: STOPPED
/boot/cmdline.txt
dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=53e33d80-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
more /boot/config.txt | grep -Ev “^([#\s])”
hdmi_force_hotplug=1
dtoverlay=pi3-disable-wifi
dtparam=eth_led0=14
dtparam=eth_led1=14
dtparam=pwr_led_trigger=none
dtparam=pwr_led_activelow=off
dtparam=act_led_trigger=none
dtparam=act_led_activelow=off
enable_uart=1
core_freq=250
dtoverlay=pi3-miniuart-bt
dtoverlay=pivccu-raspberrypi
sudo dpkg --get-selections | grep pivccu
pivccu-modules-dkms install
pivccu-modules-raspberrypi install
pivccu3 install
systemctl status pivccu.service
● pivccu.service - piVCCU
Loaded: loaded (/lib/systemd/system/pivccu.service; enabled; vendor preset: enabled)
Active: failed (Result: resources) since Mon 2020-11-30 23:09:01 CET; 2min 41s ago
Process: 782 ExecStart=/var/lib/piVCCU3/start_container.sh (code=exited, status=0/SUCCESS)
CPU: 531ms
Nov 30 23:08:25 raspberrypi start_container.sh[782]: <12>Nov 30 23:08:25 piVCCU3: HMIP hardware was not detected
Nov 30 23:08:26 raspberrypi start_container.sh[782]: kernel.sched_rt_runtime_us = -1
Nov 30 23:08:31 raspberrypi start_container.sh[782]: lxc-start: tools/lxc_start.c: main: 366 The container failed to start.
Nov 30 23:08:31 raspberrypi start_container.sh[782]: lxc-start: tools/lxc_start.c: main: 368 To get more details, run the container in foregro
Nov 30 23:08:31 raspberrypi start_container.sh[782]: lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting
Nov 30 23:08:31 raspberrypi systemd[1]: pivccu.service: PID file /var/run/pivccu3.pid not readable (yet?) after start: No such file or directo
Nov 30 23:09:01 raspberrypi systemd[1]: pivccu.service: Daemon never wrote its PID file. Failing.
Nov 30 23:09:01 raspberrypi systemd[1]: Failed to start piVCCU.
Nov 30 23:09:01 raspberrypi systemd[1]: pivccu.service: Unit entered failed state.
Nov 30 23:09:01 raspberrypi systemd[1]: pivccu.service: Failed with result 'resources'.
brctl show
bridge name bridge id STP enabled interfaces
br0 8000.b827eb7ba851 no eth0
docker0 8000.0242ea3ede4d no
I have already tried the following to no avail:
sudo apt-get install --reinstall raspberrypi-bootloader raspberrypi-kernel
sudo apt install lxc bridge-utils systemd
<reboot>
sudo apt-get install --reinstall pivccu-modules-raspberrypi
<reboot>
sudo apt-get install --reinstall pivccu3
I have tried force_turbo and core_freq in the boot config.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 20 (10 by maintainers)
Known issue of Docker: Docker adds some iptables rules, which prevent DHCP packages pass on all bridges, not only on the docker0 bridge.
/dev/raw-uart is correct as the communication needs to be done with a low level kernel module because the normal tty* is much too slow.
The three lines
together with the messages from dmesg are indicating, that all of the kernel stuff is working well.
Even though, no communication with the radio module is possible.
The last thing, you could try is a full power cycle of the Pi with at least 5 minutes without power for the entire system. If that isn’t working, I would guess a hardware issue.