You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @meexmachina David. I tried to follow #135 investigations recently but no luck. The install.sh seemed to finish ok.
$ cat /boot/firmware/config.txt : pastebin . com / vpYNyuTj
$ lsmod | grep smi bcm2835_smi 20480 0
(No your modules loaded without modprobing manually.)
$ SoapySDRUtil -probe :
Probe device
[INFO] SoapyCaribouliteSession, sessionCount: 0
04-22 13:42:33.949 949 949 I FPGA caribou_fpga_program_to_fpga@caribou_fpga.c:210 FPGA already operational - not programming (use 'force_prog=true' to force update)
04-22 13:42:33.949 949 949 E CARIBOU_SMI caribou_smi_init@caribou_smi.c:539 couldn't open smi driver file '/dev/smi' (No such file or directory)
04-22 13:42:33.949 949 949 E CARIBOULITE Setup cariboulite_init_submodules@cariboulite_setup.c:288 Error setting up smi submodule
04-22 13:42:33.951 949 949 I CARIBOU_PROG caribou_prog_release@caribou_prog.c:122 device release completed
04-22 13:42:33.951 949 949 E FPGA caribou_fpga_close@caribou_fpga.c:247 caribou_fpga_close: dev not initialized
[ERROR] cariboulite_init_driver() failed
Printing 'findCariboulite' Request:
[INFO] Initializing DeviceID: 0, Label: CaribouLite S1G[5e8f6274], ChannelType: S1G
soapy_sighandler caught SIGSEGV
[INFO] soapy_sighandler killing soapy_cariboulite (cariboulite_release_driver)
04-22 13:42:34.070 949 949 E FPGA caribou_fpga_close@caribou_fpga.c:247 caribou_fpga_close: dev not initialized
04-22 13:42:34.070 949 949 E CARIBOULITE Setup cariboulite_release_submodules@cariboulite_setup.c:465 FPGA communication release failed (-1)
04-22 13:42:34.070 949 949 E IO_UTILS_SPI io_utils_spi_close@io_utils_spi.c:340 closing uninitialized device
CaribouLite: Signal [11] received from pid=[968]
Signal [11] caught, with the following information:
signal errno = 0
signal process pid = 968
signal process uid = 0
signal status = 0
signal errno / SIGSEGV / the process access invalid region of memory
SIGSEGV: memory access violation
The text was updated successfully, but these errors were encountered:
Hi @meexmachina David. I tried to follow #135 investigations recently but no luck. The install.sh seemed to finish ok.
$ cat /boot/firmware/config.txt : pastebin . com / vpYNyuTj
$ lsmod | grep smi
bcm2835_smi 20480 0
(No your modules loaded without modprobing manually.)
$ SoapySDRUtil -probe :
The text was updated successfully, but these errors were encountered: