Hello SharkRF folks,
I am having a frustrating new issue with upgrading from v80 to v81, and updating the database on my OpenSpot 2 which has worked fine for over a year now.
I powered up my OpenSpot 2 after about 2 weeks of downtime. It almost immediately informed me that there were both firmware and database upgrades available. I also heard the voice announcements that it was connecting to Brandmeister, but it doesn't appear that it made the back-end connections to DAPNET that I had pre-configured.
Device info:
Hardware version: 1.0
Firmware version: v80 ★
Callsign database version: N/A ★
Bootloader version: v7
At the time, I had all of the auto-update options checked. I clicked the "Upgrade" button, and hit "Upgrade firmware" but I believe it was already downloading the database, and perhaps the firmware as well.
The progress bar in the upgrade window indicated that it was trying to update the database, but very regularly, about the time that the progress reached 2%, it would abort and start over again. While this is happening, the "Upgrade database" and "Upgrade firmware" buttons in the UI vanish, except for about 1 second periods when the attempts to download failed.
I had the OpenSpot 2 connected to a Wi-Fi AP and the OS2 UI was showing -52 dBm so I don't think there's any issue with Wi-Fi signal strength or stability. I am also using business APs at home, not a sketchy home router for my Wi-FI.
I tried switching to an unused default profile to minimize the likelihood that other network traffic was somehow disrupting the downloads, but the upgrade abort loop continued.
I searched the forums and found a report from 2019 where a user was concerned that web page updates in the UI were disrupting his firmware upgrade, and my reading of it is that he might have been experiencing a similar failure mode to the one I am currently experiencing. That was one of the first thoughts I had. I even went to the trouble of turning off "autoscroll" on the log, but it didn't make a difference in the timing of the aborts of the upgrade process. It's about every 10-15 seconds.
I then executed a manual firmware upgrade process with a USB-C cable and mounting the BOOTLOADER filesystem volume. The version numbers on the downloadable file are the same as one I downloaded a long time ago, which gave me pause, but I went through the process with the same result.
Now I have done a 30-second press of the reset button, associated the OpenSpot 2 to my Wi-Fi network, and entered my callsign in the setup screen, and the exact same upgrade loop-and-abort process is continuing.
I looked for manual firmware upgrade files for v81, the version that my OpenSpot 2 is trying to download, but I only found one binary for the legacy OpenSpot (v1) product, and the one in the OpenSpot 2 instructions that I used to drop in the BOOTLOADER volume.
I would appreciate any help you might be able to give me in recovering the state of my OpenSpot2.
Alternatively, is there a mechanism to drop an actual firmware upgrade file into the BOOTLOADER volume? I don't mean the srf-osw-1.0-0080.bin file, as that doesn't look like it has changed in a year or more. I am referring to an actual binary for the v81 image.
Thank you all very much for your help!
Edit: I tried to attach a log file in which you can see the repeated attempts and failures to download firmware but the forums keep telling me that .txt is an invalid extension, even after I removed ".txt" from the file name. I apologize for the length.
----log begins---
04:08:42 httpsrv[0]: websocket opened with token 72f22668
04:08:42 httpsrv[0]: websocket opened with token 72f22668
04:08:44 httpcln: received 416 bytes (100% 0s)
04:08:44 nvmm: verinfo dl ok
04:08:44 nvmm: new fw available: 81
04:08:44 nvmm: new data available
04:08:44 nvmm: new fw available: 81
04:08:44 nvmm: new data available
04:08:44 nvmm-dl:
https://img.sharkrf.com/api/v1/images/6213635de713c44ec488f5fe/blob
to 00010000
04:08:44 nvmm-dl: try 1/5
04:08:44 httpcln warn: ca GSR2.der load
04:08:44 httpcln warn: ca dst-root-ca-x3.der load
04:08:46 nvmm-dl: got nvd header (data compressed: 0)
04:08:47 httpcln: received 1454 bytes (0% 1s)
04:08:49 httpcln: received 19290 bytes (1% 3s)
04:08:50 httpcln: conn closing (5686)
04:08:50 httpcln: disconnected
04:08:50 nvmm-dl: data size error
04:08:50 nvmm-dl: not retrying
04:08:50 nvmm: checking part FRW header
04:08:50 nvmm: part FRW header not found
04:08:50 nvmm: downloading verinfo
04:08:50 httpcln warn: ca GSR2.der load
04:08:50 httpcln warn: ca dst-root-ca-x3.der load
04:08:52 httpcln: received 416 bytes (100% 0s)
04:08:52 nvmm: verinfo dl ok
04:08:52 nvmm: new fw available: 81
04:08:52 nvmm: new data available
04:08:52 nvmm: new fw available: 81
04:08:52 nvmm: new data available
04:08:52 nvmm-dl:
https://img.sharkrf.com/api/v1/images/6213635de713c44ec488f5fe/blob
to 00010000
04:08:52 nvmm-dl: try 1/5
04:08:52 httpcln warn: ca GSR2.der load
04:08:52 httpcln warn: ca dst-root-ca-x3.der load
04:08:54 nvmm-dl: got nvd header (data compressed: 0)
04:08:54 httpcln: received 792 bytes (0% 0s)
04:08:56 httpcln: received 18706 bytes (1% 2s)
04:08:58 httpcln: conn closing (5686)
04:08:58 httpcln: disconnected
04:08:58 nvmm-dl: data size error
04:08:58 nvmm-dl: not retrying
04:08:58 nvmm: checking part FRW header
04:08:58 nvmm: part FRW header not found
04:08:58 nvmm: downloading verinfo
04:08:58 httpcln warn: ca GSR2.der load
04:08:58 httpcln warn: ca dst-root-ca-x3.der load
04:08:59 httpcln: received 416 bytes (100% 0s)
04:08:59 nvmm: verinfo dl ok
04:08:59 nvmm: new fw available: 81
04:08:59 nvmm: new data available
04:08:59 nvmm: new fw available: 81
04:08:59 nvmm: new data available
04:08:59 nvmm-dl:
https://img.sharkrf.com/api/v1/images/6213635de713c44ec488f5fe/blob
to 00010000
04:08:59 nvmm-dl: try 1/5
04:08:59 httpcln warn: ca GSR2.der load
04:08:59 httpcln warn: ca dst-root-ca-x3.der load
04:09:01 nvmm-dl: got nvd header (data compressed: 0)
04:09:02 httpcln: received 1454 bytes (0% 0s)
04:09:04 httpcln: received 23670 bytes (1% 2s)
04:09:04 httpcln: conn closing (5686)
04:09:04 httpcln: disconnected
04:09:04 nvmm-dl: data size error
04:09:04 nvmm-dl: not retrying
04:09:04 nvmm: checking part FRW header
04:09:04 nvmm: part FRW header not found
04:09:04 nvmm: downloading verinfo
04:09:04 httpcln warn: ca GSR2.der load
04:09:04 httpcln warn: ca dst-root-ca-x3.der load
04:09:06 httpcln: received 0 bytes (0% 0s)
04:09:06 httpcln: received 416 bytes (100% 0s)
04:09:06 nvmm: verinfo dl ok
04:09:06 nvmm: new fw available: 81
04:09:06 nvmm: new data available
04:09:06 nvmm: new fw available: 81
04:09:06 nvmm: new data available
04:09:06 nvmm-dl:
https://img.sharkrf.com/api/v1/images/6213635de713c44ec488f5fe/blob
to 00010000
04:09:06 nvmm-dl: try 1/5
04:09:06 httpcln warn: ca GSR2.der load
04:09:06 httpcln warn: ca dst-root-ca-x3.der load
04:09:08 nvmm-dl: got nvd header (data compressed: 0)
04:09:08 httpcln: received 1454 bytes (0% 0s)
04:09:10 httpcln: received 22210 bytes (1% 2s)
04:09:11 httpcln: conn closing (5686)
04:09:11 httpcln: disconnected
04:09:11 nvmm-dl: data size error
04:09:11 nvmm-dl: not retrying
04:09:11 nvmm: checking part FRW header
04:09:11 nvmm: part FRW header not found
04:09:11 nvmm: downloading verinfo
04:09:11 httpcln warn: ca GSR2.der load
04:09:11 httpcln warn: ca dst-root-ca-x3.der load
04:09:13 httpcln: received 416 bytes (100% 0s)
04:09:13 nvmm: verinfo dl ok
04:09:13 nvmm: new fw available: 81
04:09:13 nvmm: new data available
04:09:13 nvmm: new fw available: 81
04:09:13 nvmm: new data available
04:09:13 nvmm-dl:
https://img.sharkrf.com/api/v1/images/6213635de713c44ec488f5fe/blob
to 00010000
04:09:13 nvmm-dl: try 1/5
04:09:13 httpcln warn: ca GSR2.der load
04:09:13 httpcln warn: ca dst-root-ca-x3.der load
04:09:15 nvmm-dl: got nvd header (data compressed: 0)
04:09:15 httpcln: received 1454 bytes (0% 0s)
04:09:17 httpcln: received 22210 bytes (1% 2s)
04:09:18 httpcln: conn closing (5686)
04:09:18 httpcln: disconnected
04:09:18 nvmm-dl: data size error
04:09:18 nvmm-dl: not retrying
04:09:18 nvmm: checking part FRW header
04:09:18 nvmm: part FRW header not found
04:09:18 nvmm: downloading verinfo
04:09:18 httpcln warn: ca GSR2.der load
04:09:18 httpcln warn: ca dst-root-ca-x3.der load
04:09:20 httpcln: received 0 bytes (0% 0s)
04:09:20 httpcln: received 416 bytes (100% 0s)
04:09:20 nvmm: verinfo dl ok
04:09:20 nvmm: new fw available: 81
04:09:20 nvmm: new data available
04:09:20 nvmm: new fw available: 81
04:09:20 nvmm: new data available
04:09:20 nvmm-dl:
https://img.sharkrf.com/api/v1/images/6213635de713c44ec488f5fe/blob
to 00010000
04:09:20 nvmm-dl: try 1/5
04:09:20 httpcln warn: ca GSR2.der load
04:09:20 httpcln warn: ca dst-root-ca-x3.der load
04:09:22 nvmm-dl: got nvd header (data compressed: 0)
04:09:22 httpcln: received 1454 bytes (0% 0s)
04:09:24 httpcln: received 22210 bytes (1% 2s)
04:09:25 httpcln: conn closing (5686)
04:09:25 httpcln: disconnected
04:09:25 nvmm-dl: data size error
04:09:25 nvmm-dl: not retrying
04:09:25 nvmm: checking part FRW header
04:09:25 nvmm: part FRW header not found
04:09:25 nvmm: downloading verinfo
04:09:25 httpcln warn: ca GSR2.der load
04:09:25 httpcln warn: ca dst-root-ca-x3.der load
---log ends---
