The KiwiSDR 2 online store is open for orders! Please visit kiwisdr.nz
Please visit kiwisdr.com (documentation) and kiwisdr.nz (online store)

jks

About

Username
jks
Joined
Visits
30,984
Last Active
Roles
Member, Administrator, Moderator
Points
279

Reactions

555Helpful491Awesome

  • Is it possible to transform kiwi sdr on Xilinx Zynq FPGA a single chip solution [for GPS only]

    jksjks
    Hi. Yes, what you want to do is possible. But it is a lot of work. It is maybe easier to start with the GPS code that does not have the Kiwi SDR code parts: http://www.jks.com/sdgps/sdgps.html This code just runs a program on the Beagle that prints messages with no web interface and no complications of all the Kiwi SDR code.

    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?

    Navnath123

  • CPU load is inversely proportional to the number of receivers?

    jksjks
    It's not that simple. The Kiwi is a very complicated realtime system. There is a careful balance of resources to minimize the cost of the device while maximizing the number of supported channels. This means there is sometimes a tradeoff between FPGA resources and Beagle cpu cycles.

    What you're seeing at first is the GPS acquisition process (very Beagle FFT intensive) being paused when the first connection occurs. And with no connections the audio data pump between FPGA and Beagle is shut off causing a big reduction in system time due to fewer SPI transfers.

    The %load number you show looks like user time only. You have to consider system (kernel) time as well. I see numbers like this:

    #recv %user %sys %idle %busy
    0 96 3 0 100
    1 60 18 20 80
    2 41 23 33 67
    3 41 22 33 67
    4 46 22 30 70

    This is about optimal. For no connections you want to spend all available cycles acquiring new GPS sats for maintaining ADC clock calibration. When there are corrections you want to have some cycles leftover for the portion of extension code that runs on the Beagle.

    dl2sba

  • IBP Button to track beacons

    jksjks
    Peter's IBP scanner is now a built-in extension in the v1.123 release.

    VE3SUN

  • Vote rigging on sdr.hu

    jksjks
    Martin: Done. I forgot you had multiple, switchable antennas.

    Ron: See comments #25 and 26 in this thread. It's an experiment and not many Kiwis have been "rated" yet (the GPS tag is automatic however).

    G8JNJ

  • V1.107 - Daily restart [restart after update also added]

    jksjks
    Okay, in v1.108 there is now an option to reboot the Beagle, rather than simply restart the server, after an update. See the update tab on the admin page.

    G8JNJ