Serial console: Only hieroglyphs :(

Troubleshooting
1

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

  • DietPi version |
    G_DIETPI_VERSION_CORE=9
    G_DIETPI_VERSION_SUB=12
    G_DIETPI_VERSION_RC=1
    G_GITBRANCH=‘master’
    G_GITOWNER=‘MichaIng’

  • Distro version | bookworm

  • Kernel version | Linux SV-ADS-B 5.10.160-legacy-rk35xx #1 SMP Wed Jul 10 09:57:26 UTC 2024 aarch64 GNU/Linux

  • Architecture | arm64

  • SBC model | Radxa ZERO 3 (aarch64)

  • Power supply used | 5.2V 5A

  • SD card used | Samsung Pro Plus

Steps to reproduce

  1. Set in “dietpienv.txt”: consoleargs=console=ttyS2,115200 console=tty1 console=ttyFIQ0,115200
  2. Connect USB2SER to PIN-header
  3. Start Putty-SER or TerraTerm or hTerm on COM2, 115200,n,8,1

Expected behaviour

  • See the console in the terminal like a Raspberry ZERO or similar

Actual behaviour

Extra details

  • Checked different speeds; all the same.

Am I doing something wrong here, or is this a bug?
I’ve never had any problems with this before, whether with the standard Raspberry Pi (2, 3, 4), the Zeros, or even the Banana Zeros.

DLzG, 73 De
Micha

2

Did you try with 1,500,000 baud rate? Also in dietpiEnv.txt. I wonder why ttyS2 is present there. Did you add it manually? ttyFIQ0 should be the default/debug UART used by U-Boot etc. Though I see that there is at least not dedicated debug UART port/pins, so probably ttyS2 is needed, being the common GPIO pins 6+8+10 UART2.

Radxa docs weirdly talk about ttyUSB0 :face_with_spiral_eyes:: UART Serial Console | Radxa Docs

But … quite possible that one of the USB ports (in case likely the power port itself) act as USB UART, which would then indeed appear as ttyUSB0. Such could be seen when powering it via other system’s USB port. E.g. on Windows you’d then see another USB communication being setup. Or … somewhat internally GPIO pins 6-8-10 are attached via USB bus, no idea what’s possible :sweat_smile:.

3

Hello namesake :wink:

No, I hadn’t tried it yet, because most terminal programs don’t support it. Following your suggestion, I set Putty to that value, and sure enough! Despite other settings in the ENV file, it still works at this high data rate…
Then the question naturally arises: what good are the settings in the ENV file if they simply do nothing?

I didn’t change anything except the baud rate.

This also matches my rudimentary knowledge. It’s actually a quasi-standard for these parts…

Could be. The 3E/3W has the option to add a USB port to the header by re-soldering a few resistors. I wanted to use that later… Well, that’ll be fun ^^

I will try that later then; maybe you are right…

EDIT say:
I had the serial terminal running. The following error messages now appear every few minutes (always two lines together). Additionally, I no longer have access to the shell. Input is output as echo, but it no longer responds to input.:

[74589.099520] debugfs: Directory '3c:37:12:5f:4e:e0' with parent 'rc' already present!
[74589.099717] aicwf_sdio mmc2:390b:1: Error while (un)registering debug entry for sta 4
[74684.249680] debugfs: Directory '3c:37:12:5f:4e:e1' with parent 'rc' already present!
[74684.249774] aicwf_sdio mmc2:390b:1: Error while (un)registering debug entry for sta 6
[74704.830954] debugfs: Directory '3c:37:12:5f:4e:e0' with parent 'rc' already present!
[74704.834489] aicwf_sdio mmc2:390b:1: Error while (un)registering debug entry for sta 7
[74716.598744] debugfs: Directory '3c:37:12:5f:4e:e1' with parent 'rc' already present!
[74716.598940] aicwf_sdio mmc2:390b:1: Error while (un)registering debug entry for sta 8

EDIT say also:

root@SV-ADS-B:~# shutdown
Failed to connect to bus: Datei oder Verzeichnis nicht gefunden
root@SV-ADS-B:~#

Both in serial terminal and lan-terminal… What the heck…

shutdown now creates the same error but do what he say and shut down…