forum.pistar.uk

JumboSpot w/Pi0 3.4.17 with mmdvm hs hat v. 1.4.27. Couple days ago I notice my JumboSpot will not longer initialize the mmdvm hs hat. Tried several sudo pistar-mmdvmhshatflash hs_hat commands and receive at the end an error code "Failed to init device". Below is the log file for reference. The OLED screen also is blank. All was working well a few days ago. So I think the mmdvm hs hat board has failed but it does show the green and red blinking lights. On the pi config dashboard, the Modes Enable has D-Star in red. Network States D-Star Net is green. Radio Info Trx is blank now.

Any trouble shooting tips appreciated.

Thxs
73
Kell
KI7UXT

Log File:
pi-star@pi-star(ro):~$ sudo pistar-mmdvmhshatflash hs_hat
Press any key to write the hs_hat firmware to this modem or Ctrl-C to quit...
Flashing your hs_hat modem to the latest version
--2020-02-17 08:41:55-- http://github.com/juribeparada/MMDVM_HS/releases/downlo
ad/v1.4.17/install_fw_hshat.sh
Resolving github.com (github.com)... 192.30.255.113
Connecting to github.com (github.com)|192.30.255.113|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://github.com/juribeparada/MMDVM_H ... 1.4.17/ins
tall_fw_hshat.sh [following]
--2020-02-17 08:41:55-- https://github.com/juribeparada/MMDVM_HS/releases/downl
oad/v1.4.17/install_fw_hshat.sh
Connecting to github.com (github.com)|192.30.255.113|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-production-release-asset ... com/805897
11/51a5d200-825a-11e9-8565-ea668ba43c2f?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-C
redential=AKIAIWNJYAX4CSVEH53A%2F20200217%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-
Date=20200217T164155Z&X-Amz-Expires=300&X-Amz-Signature=077f29ac07dc7726c115cac6
8efe64e16952f3e5d424bce8b48484109a569a9d&X-Amz-SignedHeaders=host&actor_id=0&res
ponse-content-disposition=attachment%3B%20filename%3Dinstall_fw_hshat.sh&respons
e-content-type=application%2Foctet-stream [following]
--2020-02-17 08:41:55-- https://github-production-release-asset-2e65be.s3.amazo
naws.com/80589711/51a5d200-825a-11e9-8565-ea668ba43c2f?X-Amz-Algorithm=AWS4-HMAC
-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20200217%2Fus-east-1%2Fs3%2Faws4
_request&X-Amz-Date=20200217T164155Z&X-Amz-Expires=300&X-Amz-Signature=077f29ac0
7dc7726c115cac68efe64e16952f3e5d424bce8b48484109a569a9d&X-Amz-SignedHeaders=host
&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dinstall_fw_h
shat.sh&response-content-type=application%2Foctet-stream
Resolving github-production-release-asset-2e65be.s3.amazonaws.com (github-produc
tion-release-asset-2e65be.s3.amazonaws.com)... 52.216.109.251
Connecting to github-production-release-asset-2e65be.s3.amazonaws.com (github-pr
oduction-release-asset-2e65be.s3.amazonaws.com)|52.216.109.251|:443... connected
.
HTTP request sent, awaiting response... 200 OK
Length: 2909 (2.8K) [application/octet-stream]
Saving to: ‘/tmp/mmdvmhshatfirmware/flash.sh’

/tmp/mmdvmhshatfirm 100%[=====================>] 2.84K --.-KB/s in 0.002s

2020-02-17 08:41:56 (1.16 MB/s) - ‘/tmp/mmdvmhshatfirmware/flash.sh’ saved [2909
/2909]

FINISHED --2020-02-17 08:41:56--
Total wall clock time: 2.4s
Downloaded: 1 files, 2.8K in 0.002s (1.16 MB/s)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 609 100 609 0 0 1323 0 --:--:-- --:--:-- --:--:-- 1323
100 48712 100 48712 0 0 37779 0 0:00:01 0:00:01 --:--:-- 2817k
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 | 700.00 KiB/s, done.
Resolving deltas: 100% (72/72), done.
Checking connectivity... done.
Raspberry Pi 2 or Pi Zero W 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.


Flashing your hs_hat modem complete, press any key to reboot your Pi-Star System
...
Session closed.

Thank you KE7FNS for the info, I'll start diving in further per your notes.

KE7FNS,
I turned on logging on the pistar admin dashboard, and I think you are correct that there is a communications problem b/w the pi 0 and mmdvm hs hat board. See last two entries in the below log.

Starting logging, please wait...
I: 2020-02-17 23:08:17.902 This software is for use on amateur radio networks only,
I: 2020-02-17 23:08:17.902 it is to be used for educational purposes only. Its use on
I: 2020-02-17 23:08:17.905 commercial networks is strictly prohibited.
I: 2020-02-17 23:08:17.905 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2020-02-17 23:08:17.905 MMDVMHost-20181107_Pi-Star is starting
M: 2020-02-17 23:08:17.905 Built 09:24:10 Nov 12 2018 (GitID #9444eca)
I: 2020-02-17 23:08:17.905 General Parameters
I: 2020-02-17 23:08:17.905 Callsign: KI7UXT
I: 2020-02-17 23:08:17.905 Id: 3102641
I: 2020-02-17 23:08:17.906 Duplex: no
I: 2020-02-17 23:08:17.906 Timeout: 240s
I: 2020-02-17 23:08:17.906 D-Star: enabled
I: 2020-02-17 23:08:17.906 DMR: disabled
I: 2020-02-17 23:08:17.906 YSF: disabled
I: 2020-02-17 23:08:17.906 P25: disabled
I: 2020-02-17 23:08:17.906 NXDN: disabled
I: 2020-02-17 23:08:17.906 POCSAG: disabled
I: 2020-02-17 23:08:17.906 Modem Parameters
I: 2020-02-17 23:08:17.906 Port: /dev/ttyAMA0
I: 2020-02-17 23:08:17.906 Protocol: uart
I: 2020-02-17 23:08:17.906 RX Invert: no
I: 2020-02-17 23:08:17.906 TX Invert: yes
I: 2020-02-17 23:08:17.906 PTT Invert: no
I: 2020-02-17 23:08:17.906 TX Delay: 100ms
I: 2020-02-17 23:08:17.906 RX Offset: 500Hz
I: 2020-02-17 23:08:17.906 TX Offset: 500Hz
I: 2020-02-17 23:08:17.906 RX DC Offset: 0
I: 2020-02-17 23:08:17.906 TX DC Offset: 0
I: 2020-02-17 23:08:17.906 RF Level: 100.0%
I: 2020-02-17 23:08:17.906 DMR Delay: 0 (0.0ms)
I: 2020-02-17 23:08:17.906 RX Level: 50.0%
I: 2020-02-17 23:08:17.906 CW Id TX Level: 50.0%
I: 2020-02-17 23:08:17.906 D-Star TX Level: 50.0%
I: 2020-02-17 23:08:17.907 DMR TX Level: 50.0%
I: 2020-02-17 23:08:17.907 YSF TX Level: 50.0%
I: 2020-02-17 23:08:17.907 P25 TX Level: 50.0%
I: 2020-02-17 23:08:17.907 NXDN TX Level: 50.0%
I: 2020-02-17 23:08:17.907 POCSAG TX Level: 50.0%
I: 2020-02-17 23:08:17.907 RX Frequency: 434000000Hz (434000500Hz)
I: 2020-02-17 23:08:17.907 TX Frequency: 434000000Hz (434000500Hz)
M: 2020-02-17 23:08:17.907 Opening the MMDVM
E: 2020-02-17 23:08:30.738 Unable to read the firmware version after six attempts

If the TCXO that clocks the AD7021 RF chip is not running you get very similar symptoms.

KE7FNS wrote: ↑Tue Feb 18, 2020 2:48 am Yeah, thats a pretty common issue.

Heres a way you can test the serial port, just make sure you substitute /dev/ttyAMA0 where he uses /dev/ttyS0 (you might also have to install minicom, I can't remember if it is included in the image or not.

Code: Select all

sudo apt install minicom

https://medium.com/@amitasinghchauhan/s ... 7e40da9055

Maybe you have some other hats or RPi's you can swap parts around and see if you can get it running again.

Unfortunately, I do not have any other mmdvmhshat boards or Pi 0 boards to swap around and see if that works. Further, I am a "end user" of products and find myself not having the computer knowledge that all you have. I can run commands in SSH to update/upgrade the Pi 0 and mmdvmhshat boards, but that is about it. Trying to do jumpers to reset the mmdvmhshat to boot loader mode to re-establish the communication link is beyond my skill level. Truly appreciate the help, but at this stage I need to find someone local to my QTH that knows how to do all this stuff.

This evening I re-ran the sudo pistar-update command and notice there were some new files added relating to the mmdvmhshat so I was hopeful that it would fix it self. Oh well. Thanks again KE7FNS for the help.

G8SEZ wrote: ↑Tue Feb 18, 2020 2:51 pm If the TCXO that clocks the AD7021 RF chip is not running you get very similar symptoms.

Thanks Brian for the help as well. Truly appreciate it. 73.

KE7FNS wrote: ↑Wed Feb 19, 2020 3:37 am All that is needed is to first locate the pads for the jumper on the PCB (You haven't mentioned which hat you have, but if you tell me the text that is written on the PCB I'm sure I can dig up a photo of the PCB), then use a pair of metal tweezers or a paper clip and touch the two pads, and then power up the hotspot. Once you apply power, you can remove the tweezers, and then once its booted try to reflash it and see if it makes it further than the init failed area.

I'm not seeing any text on the PCB, so attaching a couple pictures. I'm willing to try, and I'm not worried about running the PCB, as it is not doing me any good in this failed state anyway. Hi hi.

One more pic of the Pi 0 rev 1.1.

Hi,

KI7UXT wrote: ↑Wed Feb 19, 2020 6:33 am One more pic of the Pi 0 rev 1.1.

You're powering your Pi using the wrong USB socket, use the other one (the one next to the corner).


Cheers.
---
Daniel

KI7UXT wrote: ↑Wed Feb 19, 2020 1:43 am

G8SEZ wrote: ↑Tue Feb 18, 2020 2:51 pm If the TCXO that clocks the AD7021 RF chip is not running you get very similar symptoms.

Thanks Brian for the help as well. Truly appreciate it. 73.

It is often possible to fix this but it involves removing the OLED panel as the TCXO in question is underneath it.

If you are not set up for this I would suggest returning the board for a refund if you bought it via ebay or similar.