Unable to read firmware version

Help and support for ZUMSpot Hardware
Post Reply
KD2KBU
Posts: 10
Joined: Wed Apr 11, 2018 2:48 pm

Unable to read firmware version

Post by KD2KBU »

My Zumspot (Raspberry Pi Zero) is red (Instead of green) under MODES ENABLED on the dashboard.
I ran live logs during a reboot and the following came up (in part)

M: 2019-07-14 19:56:38.888 Opening the MMDVM
E: 2019-07-14 19:56:42.704 Invalid length received from the modem - 254
E: 2019-07-14 19:56:44.508 Invalid length received from the modem - 254
E: 2019-07-14 19:56:46.312 Invalid length received from the modem - 254
E: 2019-07-14 19:56:48.116 Invalid length received from the modem - 254
E: 2019-07-14 19:56:49.921 Invalid length received from the modem - 254
E: 2019-07-14 19:56:51.716 Unable to read the firmware version after six attempts

I have tried to re-flash my firmware, update and upgrade Pi-Star, all with no luck.
It won't work for me.

I would appreciate any help you can offer.

Thanks-
John
User avatar
KE0FHS
Posts: 1122
Joined: Wed Apr 11, 2018 8:40 pm
Location: Colorado, USA
Contact:

Re: Unable to read firmware version

Post by KE0FHS »

If it's an authentic ZUMspot mounted via GPIO, the command you want is:

Code: Select all

sudo pistar-zumspotflash rpi
It's also worth removing the ZUMspot from the GPIO header and then reseating it, just as a double check.

The Radio/Modem Type should be: ZUMspot - Raspberry Pi Hat (GPIO).

One other thing to check, especially if you recently performed a firmware upgrade: Take a look at the frequency selected on the Configuration page. If it is highlighted red, it is in the satellite frequency range and you'll need to select a different frequency.
73, Toshen, KE0FHS
Playing with Pi-Star (unofficial notes about setting up and using Pi-Star):
https://amateurradionotes.com/pi-star.htm
KD2KBU
Posts: 10
Joined: Wed Apr 11, 2018 2:48 pm

Re: Unable to read firmware version

Post by KD2KBU »

Thank you for the suggestions.

It is an authentic Zumspot and the problem began after I tried to update (or upgrade?) the FIRMWARE for the device.
After reading up on it in some other threads, it seems like sometimes, it just takes several attempts to successfully update the FIRMWARE.

I tried a few more times, and it finally took. I am back up and running.

Again, thank you for the quick replies and suggestions. Hope to hear you on the radio!

73
John
KD2KBU
Post Reply