Closed daviddawe1982 closed 1 year ago
Update it now is working with CubicSDR on the S1G but not HF and when I say working it is running so slow that it can not be used
OK - I figured it out - it can't install the kernel module. The question is why.
pi@pisdr:~/projects/cariboulite/build $ sudo ./cariboulite_test_app 02-17 17:59:59.573 1485 1485 I CARIBOULITE Setup cariboulite_init_driver_minimal@cariboulite_setup.c:560 driver initializing 02-17 17:59:59.573 1485 1485 I CARIBOULITE Setup cariboulite_init_driver_minimal@cariboulite_setup.c:569 Initializing signals 02-17 17:59:59.573 1485 1485 I CARIBOULITE Setup cariboulite_setup_signal_handler@cariboulite_setup.c:687 setting up signal handler 02-17 17:59:59.574 1485 1485 I CARIBOULITE Setup cariboulite_setup_io@cariboulite_setup.c:202 Setting up board I/Os 02-17 17:59:59.574 1485 1485 I IO_UTILS_Main io_utils_setup@io_utils.c:26 initializing pigpio 02-17 17:59:59.765 1485 1485 I IO_UTILS_Main io_utils_setup@io_utils.c:39 pigpio version 79 02-17 17:59:59.765 1485 1485 I IO_UTILS_SPI io_utils_spi_init@io_utils_spi.c:321 configuring gpio setups 02-17 17:59:59.765 1485 1485 D CARIBOULITE Setup cariboulite_init_driver_minimal@cariboulite_setup.c:583 Initializing FPGA 02-17 17:59:59.765 1485 1485 I FPGA caribou_fpga_init@caribou_fpga.c:116 configuring reset and irq pins 02-17 17:59:59.765 1485 1485 I FPGA caribou_fpga_init@caribou_fpga.c:124 Initializing io_utils_spi 02-17 17:59:59.765 1485 1485 I CARIBOU_PROG caribou_prog_init@caribou_prog.c:84 FPGA is already configured and running 02-17 17:59:59.766 1485 1485 I CARIBOU_PROG caribou_prog_init@caribou_prog.c:87 device init completed 02-17 17:59:59.766 1485 1485 D CARIBOULITE Setup cariboulite_init_driver_minimal@cariboulite_setup.c:596 Programming FPGA FPGA Versions: System Version: 01 Manu. ID: 01 Sys. Ctrl Version: 01 IO Ctrl Version: 01 SMI Ctrl Version: 01 02-17 17:59:59.767 1485 1485 I FPGA caribou_fpga_program_to_fpga@caribou_fpga.c:188 FPGA already operational - not programming (use 'force_prog=true' to force update) 02-17 17:59:59.767 1485 1485 D CARIBOULITE Setup cariboulite_init_driver_minimal@cariboulite_setup.c:609 FPGA Digital Values: led0: 0, led1: 0, btn: 1, CFG[0..3]: [1,1,1,1] 02-17 17:59:59.767 1485 1485 I CARIBOULITE Setup cariboulite_init_driver_minimal@cariboulite_setup.c:622 Detecting Board Information 02-17 17:59:59.768 1485 1485 I HAT hat_print_board_info@hat.c:703 # Board Info - Category name: hat 02-17 17:59:59.768 1485 1485 I HAT hat_print_board_info@hat.c:704 # Board Info - Product name: CaribouLite RPI Hat 02-17 17:59:59.768 1485 1485 I HAT hat_print_board_info@hat.c:705 # Board Info - Product ID: 0x0001, Numeric: 1 02-17 17:59:59.768 1485 1485 I HAT hat_print_board_info@hat.c:706 # Board Info - Product Version: 0x0001, Numeric: 1 02-17 17:59:59.768 1485 1485 I HAT hat_print_board_info@hat.c:707 # Board Info - Product UUID: 0882a4a2-4d2f-4b43-94fb-969e8640dfc5, Numeric serial: 0xD156B664 02-17 17:59:59.768 1485 1485 I HAT hat_print_board_info@hat.c:708 # Board Info - Vendor: CaribouLabs LTD 02-17 17:59:59.769 1485 1485 I CARIBOULITE Setup cariboulite_print_board_info@cariboulite_setup.c:753 # Board Info - Product Type: CaribouLite FULL 02-17 17:59:59.769 1485 1485 I CARIBOULITE Setup cariboulite_init_submodules@cariboulite_setup.c:272 initializing submodules 02-17 17:59:59.769 1485 1485 D CARIBOULITE Setup cariboulite_init_submodules@cariboulite_setup.c:276 INIT FPGA SMI communication 02-17 17:59:59.769 1485 1485 I CARIBOU_SMI caribou_smi_init@caribou_smi.c:442 initializing caribou_smi 02-17 17:59:59.771 1485 1485 D CARIBOU_SMI_MODULES caribou_smi_check_modules@caribou_smi_modules.c:98 Unloading smi-stream module 02-17 17:59:59.792 1485 1485 D CARIBOU_SMI_MODULES caribou_smi_check_modules@caribou_smi_modules.c:111 Loading smi-stream module 02-17 17:59:59.810 1485 1485 E CARIBOU_SMI caribou_smi_init@caribou_smi.c:460 couldn't open smi driver file '/dev/smi' 02-17 17:59:59.810 1485 1485 E CARIBOULITE Setup cariboulite_init_submodules@cariboulite_setup.c:280 Error setting up smi submodule 02-17 17:59:59.810 1485 1485 D CARIBOULITE Setup cariboulite_release_submodules@cariboulite_setup.c:436 CLOSE FPGA communication 02-17 17:59:59.810 1485 1485 I IO_UTILS_SPI io_utils_spi_remove_chip@io_utils_spi.c:475 removing an spi device with handle 0 02-17 17:59:59.810 1485 1485 I IO_UTILS_SPI io_utils_spi_remove_chip@io_utils_spi.c:475 removing an spi device with handle 1 02-17 17:59:59.810 1485 1485 I CARIBOU_PROG caribou_prog_release@caribou_prog.c:122 device release completed 02-17 17:59:59.810 1485 1485 E FPGA caribou_fpga_close@caribou_fpga.c:225 caribou_fpga_close: dev not initialized 02-17 17:59:59.810 1485 1485 I CARIBOULITE Setup cariboulite_release_io@cariboulite_setup.c:240 Releasing board I/Os - closing SPI 02-17 17:59:59.810 1485 1485 I CARIBOULITE Setup cariboulite_release_io@cariboulite_setup.c:243 Releasing board I/Os - io_utils_cleanup 02-17 17:59:59.832 1485 1485 E CARIBOULITE Test main@cariboulite_test_app.c:68 driver init failed, terminating...
and dmesg reports - could it be the PI Zero 2W does not have sufficient memory
[ 2228.628645] smi-stream-dev soc:smi_dev: smi-stream-dev: smi-stream dev removed [ 2228.704659] smi-stream-dev: smi_stream_dev_probe [ 2228.705451] smi-stream-dev: creating a device and registering it with sysfs [ 2228.705903] smi-stream-dev soc:smi_dev: initialised [ 2228.707228] smi-stream-dev soc:smi_dev: SMI device opened. [ 2228.717032] cariboulite_tes: page allocation failure: order:10, mode:0x40cc0(GFP_KERNEL|__GFP_COMP), nodemask=(null),cpuset=/,mems_allowed=0 [ 2228.717140] CPU: 0 PID: 1810 Comm: cariboulite_tes Tainted: G C O 5.15.84-v8+ #1613 [ 2228.717156] Hardware name: Raspberry Pi Zero 2 W Rev 1.0 (DT)
Progress. Take the same SD card, put it in a PI4 - all works. So, it would appear, at the moment at least, the SDR is not compatible with the Pi Zero 2 it was designed to be used with. I don't know if this is fixable. I hope so because you can't get a PI4 these days and the form factor and low power consumption was attractive.
Just tried running as headless and still no good. But I did notice that we are maxing out the CPU, wondering if that gives any hints as to what's going on. The image is CubicSDR running on Windows and SSH into RPI running SoapySDRServer and HTOP
This was due to me using R1 branch on Zero 2w, switched to main and it's running now..
I have finally got to the point with PiSDR where I can run cariboulite_test_app without problems and also run SoapySDRServer --bind.
The SDR server is seen as CaribouLite S1G[bd0e0b9a] and CaribouLite HiF[bd0e0b9b] in CubicSDR but as soon as I try to run I get the following.
All appears to be good apart from "SMI reading operation returned timeout"