2023-06-13, 11:37 AM (This post was last modified: 2023-06-13, 11:44 AM by baltika_no_9.)
Sadly Luckbert I don't understand what you mean.
The device (HAT) is not displayed to me! < what do you mean, where are you expecting to see it displayed?
Why does the manual procedure above not work? Are there error messages?
First of all, thank you for trying to understand what my problem is.
Normally the device is displayed in the tab "devices" and the further procedure is described by you and in the documentation.
My problem is that the device is not displayed. The connection that you see on the sceenshot is from a manual input in SK. (as soon as you create a connection in SK it is also displayed in the app).
I hope that it is now a little better expressed by me.
The connection shown in the screenshot can not be changed in the serial app and in SK I can not enter/change an alias.
Entschuldigung für mein Englisch. Es ist "deepl.com english"
PN bitte auf german.
2023-06-13, 12:38 PM (This post was last modified: 2023-06-13, 12:42 PM by baltika_no_9.)
Ah I think I see now!
If you had not added the connection yourself in SK then the line showing ttyAMA0 in the Serial Page would not be there, is that right?
I assume you have bluetooth disabled?
You can try to assign an alias by creating a symbolic link as follows: (here I am assuming the name "hat" as an example but it can be anything in lower case)
2023-06-13, 03:18 PM (This post was last modified: 2023-06-13, 05:22 PM by Luckbert.
Edit Reason: update
)
What can I say?
Even with a fresh OP-OS the same behavior shows up. I have run the Moitessier HAT 1/2 hack. The device "ttyAMA0" does not appear as a device in the "serial App".
So my problem persists.
Jürgen
EDIT:
After updating, the HUT is visible again.
I will use the new system. But I leave the defective OS on a SD. Maybe we can still find a solution or can use it for testing.
Thanks to baltika!
Entschuldigung für mein Englisch. Es ist "deepl.com english"
PN bitte auf german.