Loss of ttyAMA0 with 4.2.0

[ns2b]

Hello All,
I don't know if I can accurately explain this, but I'm going to try.

I have one of those jumbo spot hotspots using a chinese radio boards that has worked fine all the way up to 4.1.8.
It started out on a pi zero W - a while back put it on a pi zero 2W - no problems.

I upgraded the system to 4.2.0, upgrade radio firmware to 1.6.1 - initially no problems.
A day later I'm making a tweak in the configuration screen and then MMDVMhost won't start
with the associated red "D-Star" indicator. "D-Star Net" still green. I finally discover that
/dev/ttyAMA0 is showing as a link to /dev/pts/0 instead of it's normal config.

No worries, I'll re-image and try again. Same scenario occurs.

Maybe my pi zero 2W is funky. Put the radio board back on a pi zero W, re-image, same scenario again.

So I'm back to the radio board on the pi zero 2W running 4.1.8 - for now if it ain't broke, don't fix it.

I should also comment that this is DStar only. I have a DMR hotspot using the same kind of hardware
that has performed flawlessly since it was upgraded.

Anyone else seen this?

Bob, NS2B

[ns2b]

Update:

Just had the same thing happen on my DMR hotspot.

Make an update on the configuration screen.

/dev/ttyAMA0 becomes linked to /dev/pts/0 and the hotspot ceases to function.

Bob, NS2B

[MW0MWZ]

Can you check what kind of display you have set on the config page, and let me know if you do indeed have a display attached ?

[ns2b]

I have OLED Type 3 selected and it is indeed there and working.

Bob, NS2B

[MW0MWZ]

NextionDriver is the software that will do that, but it should not imact the system when you don't need it to.
I have added an extra check to stop it running when not required.

Update -> Apply changes on the config page -> reboot

Let me know if the problem is gone after that.

[ns2b]

Hmmm....

It seems to be running home to making /dev/ttyAMA0 a link to/dev/pts/0

Do you suppose there's something in my restored config that's doing that?

I'll try just starting from scratch without restoring my config.

Bob, NS2B

[ns2b]

Ok the dstar hotspot was rebuilt from scratch on 4.2.0

But this time I chose to the leave the display set at None
for now. It's a tiny display that I NEVER look at so no loss.

So far so good...

Thanks,
Bob, NS2B

[ns2b]

Well, unfortunately it did it again.

This time with a freshly loaded 4.2.0 with NO DISPLAY selected.

I went to configuration, enabled Wires-X passthrough. Hit apply.

/dev/ttyAMA0 is now linked to /dev/pts/0

I can temporarily fix it by recreating the node and doing an update to restart services,
but if I reboot the hotspot it reverts to /dev/ttyAMA0 linked to /dev/pts/0

Bob, NS2B

[W3KIT]

/dev/ttyAMA0 is now linked to /dev/pts/0

I can temporarily fix it by recreating the node and doing an update to restart services,
but if I reboot the hotspot it reverts to /dev/ttyAMA0 linked to /dev/pts/0

Bob, NS2B

Bob,

I have 7 pi-star hotspots with 4.2.0 at the QTH, they did not have this issue. However, I just tried 4.3.0 I do have the same issue. Not sure why or how ttyAMA0 was symlinked to /dev/pts/0 serial console. I think if I burn a fresh copy, set up I think I can talk forever as is. But if I run the update and reboot - thing just fell apart.

If you have an addition info or fix please let me know. I hope can do the same if/when I figure it out.

Seem like a random error, combination with hardware (pi and hat). I am using generic hat on this on. The rest of my hats are mix, zumspot, generic and DVMega. Those with 4.2.0 does not have this issue.

BTW, I am using Rpi 3 model A+ / generic STM32 hat from Amazon.

73, Kit

[ns2b]

Hi Kit,

Well here's my latest.

I had set my display type to None, but I had failed to set it's associated port to none.
I've done that now and reboots go without issue now.

I'm running a chinese hs_hat on a pi zero 2W.

Bob, NS2B