jks

That way you can get in and set the Debian root password. Then ssh / putty login should work. I'll remove the hack on a subsequent release.

This is because for real-time GPS data this code needs to run PLL loop filter code at 1 kHz.

See Andrew's description here: http://www.aholme.co.uk/GPS/Main.htm

I don't think my simulation code is fast enough to do this in real-time. Anyway, the simulation code only simulates both the GPS FPGA logic (e.g. sdgps/a_ise/gps_iq15_1/demod.v) and the embedded processor together. It does not know how to work with the GPS logic running in the actual FPGA but the embedded processor simulated. But this embedded processor is quite simple and shouldn't be much of a problem to get working on the Zynq.

There is another problem to consider. My old "sdgps" project that you have running is targeted for a Spartan-6. But also for the Xilinx ISE toolchain. I believe Zynq requires the newer Vivado toolchain. So you will have to make some adjustment, e.g. instead of a .ucf format file for the FPGA pin mappings you will need a .xcf format file. And the definitions for the required Xilinx IP blocks is a little different. The GPS part of the newer KiwiSDR project targets the Artix-7 which of course requires Vivado. So you will find a .xcf file there and the Vivado-compatible IP block definitions.

After this is working there is the question of moving the C/C++ code off the Beagle into the Arm processor of the Zynq. But that is a separate consideration.

And now for something new: The "sdgps" project just outputs to the terminal as you know. And the GPS in the KiwiSDR project has this nice web interface as part of the admin page. What I've been working on the last few days is a version of the KiwiSDR project that has most of the "SDR" code removed. This will leave just the GPS code. There will be fewer files, it will compile much faster and be much easier to understand. The KiwiSDR project is currently at https://github.com/jks-prv/Beagle_SDR_GPS so I will make a new project called https://github.com/jks-prv/Beagle_GPS in a few days. I'm not sure if this will help you for using the Zedboard but I've had several requests for a version of the Kiwi for people who just want to do GPS development / experimentation and don't care about SDR.

I need to do a little more cleanup before releasing v1.139 with the new IQ mode. The changes are on the Kiwi at kiwisdr.sk3w.se:8073 if anyone wants to try it. I'd like to know if the Windows version of Dream works.

That reminds me that I've been meaning to create a "gallery" of waterfall / spectrum screen caps of common interference sources. Lots of situations have been identified now: BPL, xDSL, electric fences, different SMPSs, the Ethernet problem, ADC overload, ...

It might be ADSL or broadband-over-powerline (BPL). Note how the spectrum is obviously "notched" around the 30m, 20m, 17m and 15m ham bands (purple segments in band display). That's the service provider trying to keep hams happy, but failing dreadfully in this case. If you rotate the loop does the noise null at all?

I think it might also be several independent noise sources. I've seen those strong 0 - 30 MHz lines that look like static crashes before. I think they come from seriously defective switch mode power supplies.

Anything in /root/Beagle_SDR_GPS will be overwritten with a software update. So do not edit the files in /root/Beagle_SDR_GPS/unix_env/kiwi.config Files here are templates that are copied to /root/kiwi.config exactly once if they don't exist. Because the /root/kiwi.config directory is outside of the /root/Beagle_SDR_GPS directory structure it will not be effected by an update, and it is safe to edit them (and making a backup copy is a good idea).

Bonnie, I edited your post slightly to reflect this.

1) How are you wiring the Beagle SPI to the Zedboard? Are you using the same SPI pins as go from Beagle to Kiwi FPGA? This is tricky because those same pins are used to download/program the Kiwi FPGA. Did you somehow electrically isolate the Kiwi FPGA from those SPI pins? Otherwise you have to depend on the Kiwi FPGA power-up state to leave those pins in high-impedance mode. It is possible this is okay even if you did not isolate the pins.

2) Did you disable the code in the Kiwi server that programs the Kiwi FPGA?

3) Admin page not connecting: In the browser open the "javascript console window" and look for error messages. Each browser has a different way of doing this. On Firefox from the top menu bar select: Tools > Web Developer > Web Console and then make sure the Console tab is selected.

4) Do you get any error messages on the Beagle console when you run the Kiwi server?

A: JORN, Over-the-horizon-radar (OTHR) from Australia. Note the short intro tone in the middle of the passband. This distinguishes it from similar sounding signals like (for me) the Tiger radars of the SuperDARN network etc.

http://www.iarums-r1.org/iarums/radar-2013.pdf [10MB file]

E, G: FSK/RTTY

Would need to hear it or see zoomed in. But you're probably right.

Others: Correct I believe. The best blog I know discussing HF digital modes: http://i56578-swl.blogspot.com