vr2vye / mmdvm_hs_firmware Goto Github PK

When FW updated is installed it is shows Nano_hotSPOT-v1.4.10 20181008.

Would it not be better with MMDVM_HS_Dual_Hat or something to say its a duplex.

Also in the install_fw_duplex.sh it is still showing # Configure latest version FW_VERSION="v1.4.8"

Tom

Just attempted to update my VR2VYE Duplex Board to 1.4.17 and its no longer connecting to the P25 network. Turns green then turns red. Any ideas?

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
`

I am the principal developer of WPSD, and I work closely with G4KLX, Mr. MMDVM himself, among other big DV players.

I am trying to understand what makes your FW different than the official MMSVM_HS firmware, and I also noticed that there is no source code behind your compiled FW bin files.

Me and my team would like to understand what's different in your FW and inspect the code. Where's the raw source code for your firmware? Having access to this (which is required by the GPL 2 license in MMDVM_HS) would allow us to help our users troubleshoot any issues.

If there are no changes to the pristine/original MMDVM_HS source code, let me know so we can tell users to use the more updated official MMDVM_HS firmware.