jks

Short version: Old behavior restored so external apps, including those using kiwiclient et al, should work as before. But Kiwi web interface uses new changes as described below.

I have some plans for this. But it will take some work/time.

From the CHANGE_LOG file. Not a lot new here. Except for days of tedious checking for memory errors (buffer overruns) and memory leaks to rule out a possible cause of the Windows 10 audio problems.

From the CHANGE_LOG file:

Please read this post if you see the error message "Git clone damaged!" as the result of using the "check now" button on the admin update tab. Or if this error appears in the admin log tab when the Kiwi tries to do an update. Or if in general your updates are failing to complete.

With increasing frequency we've seen some Kiwis running Debian 8 unable to update. The step that copies files from Github.com fails. This problems seems to occur with slower Internet connections. And by that I don't mean a slow "last mile" connection but a slow data transfer path between the Kiwi and whatever Github.com mirror server you happen to end up with when updating.

This problem started in Europe but has now spread to the USA. Even people with 50 Mbps fiber connections see it if their transfer speeds to the Github mirror during the update is less than roughly 1 MB/s (8 Mbps). Google offers many suggestions on various git/cURL parameters to change to prevent these problems. And for a while these worked and we incorporated them into the latest releases. But now even those don't seem to work anymore.

If your clone is legitimately damaged then on the admin console tab you can try the "re-clone sources" button. But if that fails then you probably have this transfer fail issue.

Re-flashing your Kiwi with the Debian 11 Kiwi image seems to solve the problem. Why this is true is unknown. The problem is that creating a microSD card with the image to re-flash with is not trivial. And you will lose all of your customizations unless you follow a more complicated procedure to move them from the Debian 8 environment to Debian 11.

Here are your options:

• You haven't made changes to the dx labels you care about and don't mind re-entering all the admin page customizations. That is, you don't care about saving any of the configuration on your Debian 8 based system. In that case just create an SD card with the Kiwi Debian 11 image and re-flash your Kiwi as described here: http://kiwisdr.com/info/#id-net-reflash
• The above instructions mention that if you are unable to make the procedure work then as a last resort we can send you a microSD card through the mail. But please only ask us for this as a last resort.
• If you only care about saving changes you've made to the dx labels then save them first by using the "export" function on the admin dx tab to download a JSON or CSV file to your computer running the browser. You can "import" them later once you're running Debian 11.
• To save the full admin configuration, including dx labels, follow the more complicated procedure described in this post: https://forum.kiwisdr.com/index.php?p=/discussion/3096/debian-11-upgrade-for-kiwis-using-beaglebone-green-black/p1

It's a real shame our efforts to place a T1-1 on the Kiwi-2 failed (it made matters worse for reasons that were never fully understood, but no doubt due to the cramped conditions on the board). But you can bet a T1-1, and more, will be present on Kiwi-3 where there will not be the space constraints.

@ok1iak Well, here we are. Over two years later. I had not forgotten about this. For various reasons I decided now was the time to give it a try.

This is an extremely early result. There are all kinds of problems. Currently, all I can get semi-reliably without too many glitches is a wideband output of 240 kHz. I'm pretty sure more can be done with some optimization. There is no CIC filtering in the FPGA yet, so there is aliasing.

To get SDR++ working as quickly as possible on my Mac the easiest thing to do was write a very quick and dirty SpyServer implementation (partial) from the public spec. That's why below it says "SpyServer", "Int16" and "RTL-SDR". But it really is connected to a Kiwi-2 on the special SpyServer port 5555. I have not tried SDR# yet. This Kiwi is on the other side of the world from me. So it is streaming at 240 kHz over the Internet successfully.

You can't make any Kiwi user connections when the Kiwi is configured for wideband mode. But you can make an admin connection. Lots and lots of work to do before this is ready for any sort of release.

Believe it or not, this was probably a power supply problem. We've seen over the years that writing SD cards requires a substantial amount of extra peak current. So a power supply that operates a Beagle + Kiwi board normally may not also be able to power an SD write operation on top of that.

This explains why running a Beagle + SD write alone (without the Kiwi board) worked. The current saved from not having the Kiwi board was enough to handle the SD write peak currents.

I have updated the operating guide instructions to mention this issue.

Please make sure your Kiwi is adequately grounded. So the antenna input protection circuitry has a path to drain any charge it is intercepting. Ideally this would be on the antenna coax near the RF in SMA connector. Or from the Kiwi metal case.

The ground connection from a switch mode power supply is likely not earth grounded and the Ethernet cable is transformer coupled with capacitive bypass.