g4klx / MMDVMHost

The host program for the MMDVM
GNU General Public License v2.0
378 stars 275 forks source link

Error after update "Unable to read the firmware version after six attempts" #465

Open ducarpit opened 6 years ago

ducarpit commented 6 years ago

Hi, i have just updating my MMDVMHost but unfortunatly, after the Raspberry reboot, i got this error:

M: 2018-10-11 18:33:08.932 Opening the MMDVM
E: 2018-10-11 18:33:21.747 Unable to read the firmware version after six attempts

Why? Before the update it worked fine! I controlled the tty port and it seems OK. Thanks a lot

Christian

fabriciocs commented 5 years ago

Iam getting the same

2018-11-11 23:21:09.243 MMDVMHost-20180916 is starting
M: 2018-11-11 23:21:09.243 Built 19:34:12 Nov 11 2018 (GitID #9444eca)
I: 2018-11-11 23:21:09.243 General Parameters
I: 2018-11-11 23:21:09.243     Callsign: G9BF
I: 2018-11-11 23:21:09.243     Id: 123456
I: 2018-11-11 23:21:09.243     Duplex: yes
I: 2018-11-11 23:21:09.243     Timeout: 180s
I: 2018-11-11 23:21:09.243     D-Star: enabled
I: 2018-11-11 23:21:09.243     DMR: enabled
I: 2018-11-11 23:21:09.243     YSF: enabled
I: 2018-11-11 23:21:09.243     P25: enabled
I: 2018-11-11 23:21:09.243     NXDN: enabled
I: 2018-11-11 23:21:09.243     POCSAG: enabled
I: 2018-11-11 23:21:09.243 Modem Parameters
I: 2018-11-11 23:21:09.244     Port: /dev/ttyS0
I: 2018-11-11 23:21:09.244     Protocol: uart
I: 2018-11-11 23:21:09.244     RX Invert: no
I: 2018-11-11 23:21:09.244     TX Invert: yes
I: 2018-11-11 23:21:09.244     PTT Invert: no
I: 2018-11-11 23:21:09.244     TX Delay: 100ms
I: 2018-11-11 23:21:09.244     RX Offset: 0Hz
I: 2018-11-11 23:21:09.244     TX Offset: 0Hz
I: 2018-11-11 23:21:09.244     RX DC Offset: 0
I: 2018-11-11 23:21:09.244     TX DC Offset: 0
I: 2018-11-11 23:21:09.244     RF Level: 100.0%
I: 2018-11-11 23:21:09.244     DMR Delay: 0 (0.0ms)
I: 2018-11-11 23:21:09.244     RX Level: 50.0%
I: 2018-11-11 23:21:09.244     CW Id TX Level: 50.0%
I: 2018-11-11 23:21:09.244     D-Star TX Level: 50.0%
I: 2018-11-11 23:21:09.244     DMR TX Level: 50.0%
I: 2018-11-11 23:21:09.244     YSF TX Level: 50.0%
I: 2018-11-11 23:21:09.244     P25 TX Level: 50.0%
I: 2018-11-11 23:21:09.244     NXDN TX Level: 50.0%
I: 2018-11-11 23:21:09.244     POCSAG TX Level: 50.0%
I: 2018-11-11 23:21:09.244     RX Frequency: 435000000Hz (435000000Hz)
I: 2018-11-11 23:21:09.245     TX Frequency: 435000000Hz (435000000Hz)
M: 2018-11-11 23:21:09.245 Opening the MMDVM
E: 2018-11-11 23:21:22.058 Unable to read the firmware version after six attempts
dl1mx commented 5 years ago

Same here from time to time, also after reboot with power off:

M: 2018-11-17 16:48:57.620 MMDVMHost-20180916 is starting
M: 2018-11-17 16:48:57.620 Built 11:28:30 Nov 11 2018 (GitID #17a158e)
I: 2018-11-17 16:48:57.620 General Parameters
I: 2018-11-17 16:48:57.620     Callsign: DL1MX
I: 2018-11-17 16:48:57.620     Id: 2623344
I: 2018-11-17 16:48:57.620     Duplex: no
I: 2018-11-17 16:48:57.620     Timeout: 180s
I: 2018-11-17 16:48:57.620     D-Star: disabled
I: 2018-11-17 16:48:57.620     DMR: enabled
I: 2018-11-17 16:48:57.620     YSF: enabled
I: 2018-11-17 16:48:57.620     P25: disabled
I: 2018-11-17 16:48:57.620     NXDN: disabled
I: 2018-11-17 16:48:57.620     POCSAG: disabled
I: 2018-11-17 16:48:57.620 Modem Parameters
I: 2018-11-17 16:48:57.620     Port: /dev/ttyUSB0
I: 2018-11-17 16:48:57.621     Protocol: uart
I: 2018-11-17 16:48:57.621     RX Invert: no
I: 2018-11-17 16:48:57.621     TX Invert: yes
I: 2018-11-17 16:48:57.621     PTT Invert: no
I: 2018-11-17 16:48:57.621     TX Delay: 100ms
I: 2018-11-17 16:48:57.621     RX Offset: 0Hz
I: 2018-11-17 16:48:57.621     TX Offset: 0Hz
I: 2018-11-17 16:48:57.621     RX DC Offset: 0
I: 2018-11-17 16:48:57.621     TX DC Offset: 0
I: 2018-11-17 16:48:57.621     RF Level: 100.0%
I: 2018-11-17 16:48:57.621     DMR Delay: 0 (0.0ms)
I: 2018-11-17 16:48:57.621     RX Level: 50.0%
I: 2018-11-17 16:48:57.621     CW Id TX Level: 50.0%
I: 2018-11-17 16:48:57.621     D-Star TX Level: 50.0%
I: 2018-11-17 16:48:57.621     DMR TX Level: 50.0%
I: 2018-11-17 16:48:57.621     YSF TX Level: 50.0%
I: 2018-11-17 16:48:57.621     P25 TX Level: 50.0%
I: 2018-11-17 16:48:57.621     NXDN TX Level: 50.0%
I: 2018-11-17 16:48:57.621     POCSAG TX Level: 50.0%
I: 2018-11-17 16:48:57.621     RX Frequency: 433625000Hz (433625000Hz)
I: 2018-11-17 16:48:57.621     TX Frequency: 433625000Hz (433625000Hz)
M: 2018-11-17 16:48:57.622 Opening the MMDVM
E: 2018-11-17 16:49:10.446 Unable to read the firmware version after six attempts

Device is available:

marco@sdrpi:~ $ dmesg | grep USB0
[    4.846510] usb 1-1.1.3: FTDI USB Serial Device converter now attached to ttyUSB0
marco@sdrpi:~ $ ls -la /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 0 Nov 17 17:49 /dev/ttyUSB0
marco@sdrpi:~ $
ducarpit commented 5 years ago

Finally, i solved my problem: i reinstalled the official kernel with "sudo apt-get install --reinstall raspberrypi-kernel" and then reboot. I can suggest to not use "rpi-update"..... That's all

SA7BNT commented 5 years ago

I have the same issue like DL1MX I always make a " sudo make deploy" to resolve the "Unable to read the firmware version after six attempts" Don´t know where it comes from.

phl0 commented 5 years ago

Seems like flashing the firmware without root permissions causes issues ...

phl0 commented 5 years ago

@dl1mx Is your user "marco" member of the group "dialout"?

bi7jta commented 5 years ago

I got this problem in low probability , maybe related to power supply, cause the STM32F103 serial port RXD/TXD not work again, look like MCU burn, replace it can work again. Are there any suggestions for improvement and avoidance? @g4klx

dl1mx commented 5 years ago

Yes: dialout:x:20:pi,marco,mmdvm,root,www-data

The reinstal from ducarpit corrected it and after a reboot the modem was found again. Last update was "rpi-update", so this seems to make problems.

ducarpit commented 5 years ago

@dl1mx in the past i used to update with rpi-update too....but after that i prefer update only with thw official kernel....

avatasia commented 3 years ago

hotspot is connected to the pi with gpio ( ttyAmA0), if the port is used by other , for example, display, then firmware version can't be read. nextion driver can be connect with port (modem). no need ttyNextionDriver or ttyAmA0.