Robert
I thought i send a reply but something went wrong...
Why do you not like to load the FPGA every time you are starting the RPI?
IMaybe in the reply i was not explicit enough, iam talking about an automatic job to load the FPGA during RPI startup.
This approach is not different between a start from a memory module or the RPI. Hope this is answering the question beter.
(further more : no need of valuable resources in the FPGA for remote updating of the gateware and setting up issues with programming devices from different computers containg different operating systems)
You are right the speed of SPI (as used in the standalone release) port is far to less to get more receivers ... i tried to use a more parallel approach by using multiple GPIO pins (as used in the emulator release) which improved it.
For implementing a ethernet bus different implementations are possible.
1. implementing the openhpsdr protocol version 1 or 2 in the FPGA.
pihpsdr can run on the RPI and is able to connect to the Radioberry using the P-1.
running on a different computer in your network a DSP program which implements the P-1
2. implementing the openhpsdr protocol in a higher level language like C or Java by using the data stream via ethernet packets iso of getting the bulk IQ data from GPIO/SPI.
Having on a Tinkerboard or RPI-4 a 1GB/s ethernet module you can easy connect to your radio by remote control programs like vnc
or using the ethernet port or wifi for other ideas of using your radio.
3. Doing some nice streams experiments or combination of things
By having the RPI and the Radioberry sticked together gives some nice possibilities...
For instance using local audio which can be transfered from the protocol to the RPI using the SPI port which is available in config 1.
Maybe you have idea of making use of the combinations of possiblities.
Hope this makes things clear. And as always have fun !
73 Johan
PA3GSB
Op woensdag 2 oktober 2019 21:32:16 UTC+2 schreef rentwist: