any problem, lemme know. I'm running bullseye 64 bit here. I'm still taking some breath to update to bookworm...
my packages for wiringpi for bullseye 64 bit are here:
- Rafael
toggle quoted message
Show quoted text
On 11/2/23 18:16, Dave, N1AI wrote:
To reply to my own post in case it helps anyone else, I found the problem was permissions were incorrect on |/dev/gpiomem|.
The whole sequence was:
|pi@sbitx:~/sbitx$ ./sbitx sbitx v2.0 sqlite3 opening returned 0 wiringPiSetup: Unable to open /dev/mem or /dev/gpiomem: Permission denied. Aborting your program because if it can not access the GPIO hardware then it most certianly won't work Try running with sudo? pi@sbitx:~/sbitx$ ls -l /dev/gpiomem crw------- 1 root root 238, 0 Nov 2 10:16 /dev/gpiomem pi@sbitx:~/sbitx$ sudo chown root.gpio /dev/gpiomem pi@sbitx:~/sbitx$ sudo chmod g+rw /dev/gpiomem pi@sbitx:~/sbitx$ ls -l /dev/gpiomem crw-rw---- 1 root gpio 238, 0 Nov 2 22:25 /dev/gpiomem pi@sbitx:~/sbitx $ ./sbitx sbitx v2.0 sqlite3 opening returned 0 synchronised to NTP server (50.205.57.38) at stratum 2 time correct to within 13 ms polling server every 64 s Checking for valid NTP time ...Syncing RTC to 2023-11-02 17:22:16 Initialized the waterfall rx_pitch set to 590 bridge compesation = 100 *Error: field[#kbd_] not found. Check for typo? #Remote is listening Reading rtc...RTC time is : year:2023 month:11 day:2 hour:17 min:22 sec:16 time_delta = 1698945732 rtc julian: 1698960136l -14400 done! |
The steps that fixed it were:
|sudo chown root.gpio /dev/gpiomem sudo chmod g+rw /dev/gpiomem |
The weird part is the same permission issue was present on the sdcard that I cloned from, and the same fix applied to the sdcard fixed that issue there as well. I still can't figure out what caused the permission problem. I have no idea if it had anything to do with using |rpi-clone| or not.
The bottom line is I am where I wanted to be a day or so ago. I can boot the rpi4 in the sbitx either on the sdcard or on the external usb-nvme stick. If I power down and disconnect the usb-nvme cable then it falls back to running from the sdcard.
Next I'd like to move forward to the debian bullseye release and run in 64 bit mode on a different usb3-nvme device. That will be a nice step forward.
-- Regards, Dave, N1AI