I have successfully updated my KiwiSDR to V1.486

clitangclitang
in Problems Now Fixed

Points to ponder:

  1. Having had your KiwiSDR V1.486 flashed to your SD by belenaEtcher which has also validated the flashing process, don't look around and check-see your SD card about the file, as you would nothing there except zeros and a prompt " the volume does not contain a recognized file system " which might be mistaken for a corrupted SD card, leading you into a vicious and also futile reflashing cycle dealing with " a corrupted SD card. " The suspected corrupted SD card is actually where your new KiwiSDR version is now located, whose integrity could be verified using your Windows Disk Management that would detect your SD card and files as " healthy " So all you should do is to leave it at that and go about reflashing your KiwiSDR from this SD card.
  2. Give your KiwiSDR a good reset-flashing: a good reset-flashing means you should allow long enough time, like about twenty seconds by pressing the reset button above the SD slot on board before powering it up, when your KiwiSDR could respond and kick in the flashing process that might last from four to seven minutes before all lights were out.
  3. With your KiwiSDR updated to v1.486, you are on your way to auto-updating when your KiwiSDR is connected to WiFi. Congrats!


«1

Comments

  • jksjks
    edited August 2022
    1. Yes, our documentation explains this. That the sd card will become a "flasher". An sd card that, when booted from on the Beagle, will simply cause a bootable copy of the Kiwi distribution to be installed on the Beagle on-board eMMC flash memory.
    2. Since you ended up with v1.486 you must have used the Debian 10 image for BBG/BBB. Because of changes to U-boot in later versions of Debian some people have reported that the Beagle "boot" button needs to be used to get the sd card to boot. But apparently only the first time. Times after that it should boot from the sd without use of the boot button. This is the behavior of the Kiwi Debian 8 sd flasher image. We never had to use the boot button with Debian 8 images.
    3. Gosh, I hope you're not trying to use WiFi on the Beagle. It's nothing but trouble. You can try it later, but for an update to the latest version (v1.553 currently) I would strongly suggest using a wired Ethernet connection.


  • clitangclitang

    It's KiwiSDR v1.486 on Debian version 10.11and now put online via a wired broadband for updating. I was wondering how long it will take before my KiwiSDR gets updated to v1.553 and if there is a manual way to do that.

  • jksjks

    When you power-up the Kiwi with an Ethernet connection that has Internet service an automatic update should start automatically. Here's how you can tell: Connect to the admin page. Perhaps at kiwisdr.local:8073/admin or by ip address if kiwisdr.local doesn't work for you. Click on the Update tab on the top line. Click the blue Check Now button. It will say what version you are running, if it is current or not, and if an update is in progress.

    To monitor the progress of an update: Click on the Console tab on the top line. Click the Connect button. In the enter shell command field at the page bottom type m blog (make build log). You should then see many scrolling messages from the update build process. The Kiwi server will automatically restart when the build completes.

  • clitangclitang
    https://forum.kiwisdr.com/index.php?p=/discussion/comment/14786#Comment_14786 
    CONSOLE: open connection
root@kiwisdr:~/Beagle_SDR_GPS# m blog
======== checking for update
Thu 11 Aug 2022 06:05:09 AM UTC
2c2
< VERSION_MIN = 552
---
> VERSION_MIN = 553
m blog

    this is what I see at m blog, then nothing happened.

  • jksjks

    According to that you're already running v1.522

    What does the Check Now button say on the Update tab?

  • clitangclitang

    Installed version: v1.486, built Jan 18 2022 01:12:00

    Available version: v1.553


    This is what " check now " button gets. Incidentally, I got this with " m blog ", after force bulid:

    CONSOLE: open connection
root@kiwisdr:~/Beagle_SDR_GPS# m blog
======== checking for update
Thu 11 Aug 2022 07:56:40 AM UTC
fatal: unable to access 'https://github.com/jks-prv/Beagle_SDR_GPS.git/': Failed to connect to github.com port 443: Connection timed out

    What should be done about this, please?

  • jksjks

    Are you in China or Russia?

  • jksjks

    That was a serious question, btw. Made just a few minutes before I had to retire for the day.

    Not having access to GitHub.com is a serious problem since that's where the Kiwi sources are kept. Note that this failure is not a DNS lookup issue (which we've had problems with in the past) since it is a timeout. Presumably the lookup worked.

    On the admin page, console tab, try doing a ping -c3 1.1.1.1 and ping -c3 github.com and ping -c3 kiwisdr.com to see if you can reach these sites. If you can't then there is a serious problem with your Internet connectivity.

  • clitangclitang 
    CONSOLE: open connection
root@kiwisdr:~/Beagle_SDR_GPS# ping -c3 1.1.1.1 
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=51 time=285 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=51 time=259 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=51 time=270 ms
 
--- 1.1.1.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 5ms
rtt min/avg/max/mdev = 258.988/271.263/285.168/10.766 ms
root@kiwisdr:~/Beagle_SDR_GPS# ping -c3 github.com
PING github.com (20.205.243.166) 56(84) bytes of data.
 
--- github.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 54ms
 
root@kiwisdr:~/Beagle_SDR_GPS#

    this is my ping results.

  • clitangclitang
    https://forum.kiwisdr.com/index.php?p=/discussion/comment/14791#Comment_14791
    https://forum.kiwisdr.com/index.php?p=/discussion/comment/14791#Comment_14791

    Installed version: v1.486, built Jan 18 2022 01:12:00

    Available version: v1.553

  • clitangclitang

    I am on v1.486 and " check now " found v1.553 available but updating hasn't been done, just yet.

  • clitangclitang

    KiwiSDR persistently stayed on V1.486 and updating remains unaccomplished. What seems to be the problem?

  • jksjks

    It seems GitHub.com can't be pinged anymore.

    What happens when you try:

    cdp

    git show origin:Makefile | head -n 2


  • clitangclitang 
    CONSOLE: open connection
root@kiwisdr:~/Beagle_SDR_GPS# cdp
root@kiwisdr:~/Beagle_SDR_GPS# git show
commit 4180f4f14778211feb87f94c0e20923c5b3b0e69 (HEAD -> master, origin/master, origin/HEAD)
Merge: fd73dc59 3e70b410
Author: jks-prv <jks-prv@users.noreply.github.com>
Date:   Mon Aug 15 08:40:54 2022 +1200
 
    Merge pull request #681 from jks-prv/develop
    
    v1.554
 
oot@kiwisdr:~/Beagle_SDR_GPS#


  • clitangclitang

    Any problems with this?

  • clitangclitang

    Wondered if this pull was in process and automatically.

  • jksjks

    No problem with that. Although since v1.555 was just released the git log has progressed a little bit.

    To see the recent git log use the gcoms alias, i.e.

    cdp

    gcoms

    The "develop" branch is used as a staging area for the release under development.

  • clitangclitang 
    CONSOLE: open connection
root@kiwisdr:~/Beagle_SDR_GPS# gcoms
14fb6ca 2022-08-25 Merge pull request #682 from jks-prv/develop
0d128c39 2022-08-25 v1.555
cbe92f7d 2022-08-25 build process: improved error messages
a8dd8faf 2022-08-25 iframe extension: support HTML/Javascript
44284170 2022-08-25 BBAI-64: available main memory 2 GB => 4 GB
e8034163 2022-08-25 lint
4180f4f1 2022-08-15 Merge pull request #681 from jks-prv/develop
3e70b410 2022-08-15 v1.554: misc improvements
1ed219b5 2022-08-15 console command buttons, GPS/ADC correction menu
25ae3676 2022-08-15 lint
602f2f80 2022-08-15 TDoA: add "show all results" checkbox
fd73dc59 2022-08-10 Merge pull request #680 from jks-prv/develop
06670e81 2022-08-10 v1.553
1a783724 2022-08-09 Merge pull request #679 from jks-prv/develop
74a6d40e 2022-08-09 debugging for ip_blacklist problem
58e2cf03 2022-08-09 Merge pull request #678 from jks-prv/develop
323b3c41 2022-08-09 debugging for ip_blacklist problem
27c19caf 2022-08-09 Merge pull request #677 from jks-prv/develop
14191b0f 2022-08-09 debugging for ip_blacklist problem
a0db0e2c 2022-08-09 lint
480a6bd5 2022-08-07 Merge pull request #676 from jks-prv/develop
d841fef3 2022-08-07 v1.552: WSPR fixes
a400d8f6 2022-08-07 Merge pull request #675 from jks-prv/develop
:

    But I need to know the updating status and when it is expected to complete.

  • jksjks

    To see if there is an update available just go to the admin page, update tab. Click the Check now button. If you get an error message instead of the update status go to the console tab and click the check gitHub.com button. If this gives an error then there is a problem with your Internet connectivity.

    If the check now button says "update available" then restart your Kiwi (control tab, restart button). This assumes you have the Automatically check for / install software updates? switches both set to yes. Otherwise you can force an update by clicking the build now button.

    To monitor the build progress go to the console tab and click the monitor build progress button. Be patient as there are several points in the build where the output will stop for up to a minute or so.

    When the build is finished the Kiwi will automatically restart no matter which method you use.

  • clitangclitang

    I did work through on the first scheme but nothing happened after many hours. And I did try " build " as well but there is no " monitor build progress " button on the interface with V1486.

  • jksjks

    Sorry, I somehow thought you had gotten further than v1.486. So we need to figure out a few things.

    First, in the admin console tab, connect and type git show origin:Makefile | head -n 2 This should reply with:

    VERSION_MAJ = 1

    VERSION_MIN = 556

    If at any point in the following you don't get the expected result, or you get an error message, copy and paste as much of the console window as possible into an email to support@kiwisdr.com

    If the above works then type:

    gup

    This will update the sources from GitHub.com Will take about a minute to run.

    mc

    Cleans the build directory. Doesn't take long.

    m

    The main part of the build. Will take 20 to 30 minutes to run. Should produce output at least every 30 seconds or so. If there is no output after several minutes something is wrong.

    mi

    Does the install of the build. Takes a minute or so.

    If all of the above worked without error messages go to the control tab and click the server restart button. You should be running the latest version after the restart.

  • clitangclitang 
    1 error generated.
make[1]: *** [Makefile:986: ../build/obj_O3/mongoose.o] Error 1
make[1]: Leaving directory '/root/Beagle_SDR_GPS'
make: *** [Makefile:87: all] Error 2
root@kiwisdr:~/Beagle_SDR_GPS# dpkg --configure -a
Setting up man-db (2.8.5-2) ...
Building database of manual pages ...

    By the end, got this error message.

  • jksjks

    Okay, but without seeing the messages that came BEFORE the "1 error generated" I can't tell anything that happened.

    Also, what made you think you needed to do a dpkg --configure -a ? You generally only do that if you are getting serious package system corruption errors. In which case that has to be fixed first before even attempting to compile the Kiwi stuff.

  • clitangclitang 
    1 error generated.
make[1]: *** [Makefile:986: ../build/obj_O3/mongoose.o] Error 1
make[1]: Leaving directory '/root/Beagle_SDR_GPS'
make: *** [Makefile:87: all] Error 2
root@kiwisdr:~/Beagle_SDR_GPS#

    At command m, got this error msg and the building process halted at that. What should be done about this?

  • jksjks
    edited August 2022

    There MUST be more error message before this. What are they??

  • clitangclitang 
    root@kiwisdr:~/Beagle_SDR_GPS# m
disable unwanted services
make: [Makefile:1028: DISABLE_WS] Error 5 (ignored)
make: [Makefile:1029: DISABLE_WS] Error 1 (ignored)
make: [Makefile:1030: DISABLE_WS] Error 5 (ignored)
make: [Makefile:1031: DISABLE_WS] Error 1 (ignored)
apt-get -y install openssl libssl1.1 libssl-dev
Reading package lists... Done
Building dependency tree       

----------------
make[1]: Leaving directory '/root/Beagle_SDR_GPS'
make[1]: Entering directory '/root/Beagle_SDR_GPS'
clang++-8 -Dv1_556 @../build/gen/Makefile.inc -std=gnu++11 -c -o ../build/obj/prussdrv.o pru/prussdrv.cpp
clang++-8 -Dv1_556 @../build/gen/Makefile.inc -std=gnu++11 -c -o ../build/obj/pru_realtime.o pru/pru_realtime.cpp
clang++-8 -Dv1_556 -Ofast @../build/gen/Makefile.inc -std=gnu++11 -c -o ../build/obj_O3/main.o main.cpp
clang++-8 -Dv1_556 -Ofast @../build/gen/Makefile.inc -std=gnu++11 -c -o ../build/obj_O3/mongoose.o pkgs/mongoose/mongoose.cpp
pkgs/mongoose/mongoose.cpp:178:10: fatal error: 'openssl/ssl.h' file not found
#include <openssl/ssl.h>
         ^~~~~~~~~~~~~~~
1 error generated.
make[1]: *** [Makefile:986: ../build/obj_O3/mongoose.o] Error 1
make[1]: Leaving directory '/root/Beagle_SDR_GPS'
make: *** [Makefile:87: all] Error 2
root@kiwisdr:~/Beagle_SDR_GPS#

    I have had problems at m command, with one error msg generated at the end of the session. What should be done to troubleshoot this?

  • clitangclitang 
    -DUSE_SSL -DVERSION_MAJ=1 -DVERSION_MIN=556 -DKIWI -DKIWISDR -DARCH_sitara -DCPU_AM3359 -DARCH_CPU=AM3359 -DARCH_CPU_S=STRINGIFY(AM3359) -DPLATFORM_beaglebone -
DPLATFORM_beaglebone_black -DDIR_CFG=STRINGIFY(/root/kiwi.config) -DCFG_PREFIX=STRINGIFY() -DBUILD_DIR=STRINGIFY(../build) -DREPO=STRINGIFY(https://github.com/j
ks-prv/Beagle_SDR_GPS.git) -DREPO_NAME=STRINGIFY(Beagle_SDR_GPS)
----------------
make[1]: Leaving directory '/root/Beagle_SDR_GPS'
make[1]: Entering directory '/root/Beagle_SDR_GPS'
clang++-8 -Dv1_556 @../build/gen/Makefile.inc -std=gnu++11 -c -o ../build/obj/prussdrv.o pru/prussdrv.cpp
clang++-8 -Dv1_556 @../build/gen/Makefile.inc -std=gnu++11 -c -o ../build/obj/pru_realtime.o pru/pru_realtime.cpp
clang++-8 -Dv1_556 -Ofast @../build/gen/Makefile.inc -std=gnu++11 -c -o ../build/obj_O3/main.o main.cpp
clang++-8 -Dv1_556 -Ofast @../build/gen/Makefile.inc -std=gnu++11 -c -o ../build/obj_O3/mongoose.o pkgs/mongoose/mongoose.cpp
pkgs/mongoose/mongoose.cpp:178:10: fatal error: 'openssl/ssl.h' file not found
#include <openssl/ssl.h>
         ^~~~~~~~~~~~~~~
1 error generated.
make[1]: *** [Makefile:986: ../build/obj_O3/mongoose.o] Error 1
make[1]: Leaving directory '/root/Beagle_SDR_GPS'
make: *** [Makefile:87: all] Error 2
root@kiwisdr:~/Beagle_SDR_GPS#

    I have kept having problems at m command, in areas as listed right before the " 1 error generated " message.

  • jksjks

    Also, what does ls -la /usr/include/openssl/ssl.h print?

  • clitangclitang 
    root@kiwisdr:~/Beagle_SDR_GPS# ls -la /usr/include/openssl/ssl.h
/bin/ls: cannot access '/usr/include/openssl/ssl.h': No such file or directory
root@kiwisdr:~/Beagle_SDR_GPS#


  • jksjks

    Try reinstalling libssl:

    apt-get reinstall libssl-dev

    ls -la /usr/include/openssl/ssl.h

    If the ls above no longer gives an error then try the m command again and see if it gets further.

Sign In or Register to comment.