Page 1 of 1

MMDVM hs dual not upgrade

Posted: Sat Jul 28, 2018 1:05 pm
by OK1PMP
Hello,
I bought on ebay MMDVM_HS_Dual_Hat

ImageImage

I want to update the firmware by using the command

Code: Select all

sudo pistar-mmdvmhshatflash hs_dual_hat
and I will see this result

Image

some ideas?
Thank you

Re: MMDVM hs dual not upgrade

Posted: Sat Jul 28, 2018 1:13 pm
by n9mxq
The big clue here is the line "Failed to init Device" which usually means the pins for upgrades are not connected between the PI and the HAT. Which pins those are on a dual hat I've never heard. But it should point you in the right direction.

Re: MMDVM hs dual not upgrade

Posted: Sat Jul 28, 2018 6:35 pm
by LA6TMA
I've got the same problem with the same dual hat modem. Failed to init the device. The fw update pins are in place. I've tried it on both pi zero w and 3B+ with the same result. :?

Re: MMDVM hs dual not upgrade

Posted: Sun Jul 29, 2018 6:57 am
by LA6TMA
Finally i did manage to figure out how to upgrade the FW. Locate JP1 on the board and shorten JP1. See attached picture.

Re: MMDVM hs dual not upgrade

Posted: Sun Jul 29, 2018 7:31 pm
by OK1PMP
LA6TMA wrote:
Sun Jul 29, 2018 6:57 am
Finally i did manage to figure out how to upgrade the FW. Locate JP1 on the board and shorten JP1. See attached picture.
The update was successful ;)
Thank you

Re: MMDVM hs dual not upgrade

Posted: Sat Sep 14, 2019 5:58 pm
by WB0NRE
If you have a display using the modem port (i.e. display commands are passed through the MMDVM hat to the display e.g. a NEXTION) then set the Pi-Star MMDVM Display Type to "none" and the Port to "none" while performing the firmware update.

Re: MMDVM hs dual not upgrade

Posted: Sat Sep 14, 2019 7:59 pm
by KE7FNS
WB0NRE wrote:
Sat Sep 14, 2019 5:58 pm
If you have a display using the modem port (i.e. display commands are passed through the MMDVM hat to the display e.g. a NEXTION) then set the Pi-Star MMDVM Display Type to "none" and the Port to "none" while performing the firmware update.
There is no reason to bother doing that, because when the firmware update script is run, it shuts down the MMDVMHost processes entirely. So there is absolutely no information going to the modem other than the firmware hex.