nano_hotspot_fw.bin

[plughplover]

I have a number of these units. https://www.mmdvm.club/index.php/archives/209/

They are running the pi-star image specified in that post: https://www.pistar.uk/beta/Pi-Star_NanoPi_V4.1.5_25-Jun-2021.zip

That post also indicates: Modem TYPE : "MMDVM_HS_NPi Hat (VR2VYE) for Nano Pi(GPIO)" update FW : sudo pistar-vyehsflash nano_hs (i.e. /usr/local/sbin/pistar-vyehsflash)

That script tries to download "install_fw_nanohs.sh" from YOUR repository. 1) Since it does not exist in your repository, it fails.

2) That script ALSO has a COMMENTED OUT line that would download that script from "juribeprada" repository.

It does exist in that repository. THAT script would download "nano_hotspot_fw.bin" from juribeprada repository. Your repository does have what appears to be a more recent version of that FW bin file vs juribeprada.

However, due to (1) and (2) above the vyehsflash script is unable to install either version of the FW file.

Why am I trying to update the firmware? These units appear to have a problem with the RF signal they xmit. In both YSF and DMR mode (D-star untested), they will receive signals, transfer to "parrot" via network, receive the "parrot" network response, xmit an RF signal (visible in a spectrum analyzer) BUT the there is never any audio output received by the HTs.

FYI - After examination of the relevant scripts, I attempted to manually install the VR2VYE version of the FW file. This failed, as shown in the following SSH log. Yet another problem?????

`pi-star@pi-star(rw):\~$ cp /boot/install_fw_nanohs.sh . pi-star@pi-star(rw):\~$ ls install_fw_nanohs.sh pi-star@pi-star(rw):\~$ mkdir /tmp/nanohsfirmware pi-star@pi-star(rw):\~$ cp /boot/install_fw_nanohs.sh /tmp/nanohsfirmware/flash.sh pi-star@pi-star(rw):\~$ chmod +x /tmp/nanohsfirmware/flash.sh pi-star@pi-star(rw):\~$ cd /tmp/nanohsfirmware pi-star@pi-star(rw):nanohsfirmware$ ./flash.sh ./flash.sh: line 29: [: =: unary operator expected Downloading latest firmware (stable)... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 9 100 9 0 0 27 0 --:--:-- --:--:-- --:--:-- 27 Cloning into 'STM32F10X_Lib'... remote: Enumerating objects: 193, done. remote: Total 193 (delta 0), reused 0 (delta 0), pack-reused 193 Receiving objects: 100% (193/193), 3.28 MiB | 4.06 MiB/s, done. Resolving deltas: 100% (71/71), done. Raspberry Pi 3 detected stm32flash Arduino_STM32_0.9

http://github.com/rogerclarkmelbourne/arduino_stm32

Using Parser : Raw BINARY Interface serial_posix: 57600 8E1 Failed to init device.

pi-star@pi-star(rw):nanohsfirmware$ sudo shutdown -r now `

[plughplover]

clarification on point (1) above "install_fw_nanohs.sh" is not part of https://github.com/VR2VYE/MMDVM_HS_firmware/releases/latest (i.e. v1.5.2)

It exists in your repository, tagged v1.4.17 (but it uses the fw file from the juribeprada repository)

[evgeny-mezin-epam]

What did the guys from Pistar do ? Commented out the line for hs_hat update in pistar-vyehsflash script....

Instead of solving the issue somehow or give a clear reasoning pi-star is trying to keep silence... @VR2VYE

Meanwhile i see in the logs: M: 2023-02-08 11:47:24.272 Opening the MMDVM E: 2023-02-08 11:47:37.095 Unable to read the firmware version after six attempts

So now my board is not usable at all.. @plughplover - any ideas ?

[evgeny-mezin-epam]

@plughplover managed to fix the issue by manually doing the following:

Logged into SSH of my pi-star

sudo su 
cd /tmp
curl -OL https://raw.githubusercontent.com/VR2VYE/MMDVM_HS_firmware/master/install_fw_nanohs.sh

changed the path to binary in script from https://github.com/juribeparada/MMDVM_HS/releases/download/$FW_VERSION/nano_hotspot_fw.bin to https://github.com/VR2VYE/MMDVM_HS_firmware/releases/download/v1.5.2/nano_hotspot_fw.bin

Stopped all services

sudo pistar-watchdog.service stop
sudo systemctl stop mmdvmhost.timer
sudo systemctl stop mmdvmhost.service
sudo killall MMDVMHost >/dev/null 2>&1

Started the script ./install_fw_nanohs.sh

[plughplover]

It's a bit more involved than that. As I pointed out here https://github.com/AndyTaylorTweet/Pi-Star_Binaries_sbin/issues/55#issuecomment-1315595270 and here https://github.com/AndyTaylorTweet/Pi-Star_Binaries_sbin/issues/55#issuecomment-1315702210 I had to set the gpio pin modes, and also tweak the stm32flash command line to address a timing sensitivity.

This allowed me to reliably flash the mcu. But none of the three images I tried got my unit(s) working. https://github.com/AndyTaylorTweet/Pi-Star_Binaries_sbin/issues/55#issuecomment-1320451804