04:50 <DC-IRC> [Discord] <Werner> What do you mean by workable serial port? It has a debug serial via uart

05:31 <DC-IRC> [Discord] <gambl0r> Hammdist: check the user manual, it gives clear instructions on how to use serial via UART

05:42 <Hammdist> iirc all you get when connecting to the serial port is garbled data bytes from the orange pi 5 specifically. its serial port support is borked. I believe I've tried it myself in the past (a while ago though so ...) are you sure you can confirm it's working?

05:46 <DC-IRC> [Discord] <Werner> Yes. Opi5 debug serial console works just fine. 1500000 baud, everything else default. When you get garbage this often comes from faulty adapters or wrong baud rate

05:47 <DC-IRC> [Discord] <Werner> make sure your adapter can handle this speed. It might not complain when setting but don't work properly either.

05:48 <Hammdist> ok I will check the adapter datasheet

05:49 <DC-IRC> [Discord] <Werner> I think cp2104 or ft232 can do these speeds. cp2102 for example is only good enough for allwinner or amlogic since they are only at 115200 baud.

06:00 <Hammdist> btw symptom I was experiencing with the "garbled" serial port is that data sent to the opi was getting there fine but data received from the opi was garbled. I concluded it can't be the baud rate setting due to this asymmmetry. does anything explain it?

06:01 <Hammdist> fe since I had the opi boot into a shell I was able to send "dmesg" and get back a garbled blob clearly in response to having sent a command that produces output

06:27 <DC-IRC> [Discord] <Werner> That's odd. Have you tried a different adapter?

06:58 <DC-IRC> [Discord] <rpardini> Indeed, I've nothign this bot shows "one of the commits" (random?) in the PR instead of the PR title itself.

06:58 <DC-IRC> [Discord] <rpardini> Indeed, I've noticed this bot shows "one of the commits" (random?) in the PR instead of the PR title itself.

06:59 <DC-IRC> [Discord] <johnthecoolingfan> I think it shows the last commit

07:02 <DC-IRC> [Discord] <Werner> `git show -s --format=%s`

07:02 <DC-IRC> [Discord] <Werner> https://github.com/armbian/build/blob/0041cc70dbaa125bdd661747b4d7d6c3e39667d1/.github/workflows/merge-announce.yml#L20

08:20 <DC-IRC> [Discord] <Github> ✅ **Merged** into [armbian/build](<https://github.com/armbian/build>) by [igorpecovnik](<https://github.com/igorpecovnik>) - [Link](<https://github.com/armbian/build/commit/cafe0ff79fb69320e6c94719bef5679ec85c5ac5>): *Rockpi-S: enable automatic u-boot flashing upon package install*

08:20 <DC-IRC> [Discord] <Github> ✅ **Merged** into [armbian/build](<https://github.com/armbian/build>) by [igorpecovnik](<https://github.com/igorpecovnik>) - [Link](<https://github.com/armbian/build/commit/9b822824bbae904075c85d404bf1ab8aaa98df2f>): *thinkpad-x13s: arm64-sc8280xp: enable RTW88 in-kernel USB drivers*

10:46 <Hammdist> 10c4:ea60 Silicon Labs CP210x UART Bridge <-- is this capable or incapable of talking to an orange pi 5? it comes with a 3ft +ish signals cable that seems like it might be too long to me for high speeds

14:00 <DC-IRC> [Discord] <menu> Hammdist: CP2102/9 (only one i can find a datasheet for) specifies `max baud: 921600`, so it's probably the UART adapter not keeping up

14:01 <DC-IRC> [Discord] <menu> do you know if the baud rate can be dropped (relatively easily)?

14:07 <DC-IRC> [Discord] <Werner> I don't think so. Otherwise my guess is this would have been unified across all socs long time ago

14:11 <DC-IRC> [Discord] <menu> i know towboot intentionally unifies baud rate, i *think* it's possible with uboot as well, although once kernel handover happens it will change

14:12 <DC-IRC> [Discord] <menu> - adding `GRUB_SERIAL_COMMAND="serial --speed=57600"` to `/etc/default/grub` and rebuilding grub works, but i don't know how to do that on a system that isn't booting

14:33 <DC-IRC> [Discord] <Werner> Hm maybe the baud rate is part of the kernel command line? Need to check the boot script. Other possible scenario is that the rate is set in uboot config and then hardcoded into the binary

14:37 <DC-IRC> [Discord] <menu> my understanding is that it's baked-in to uboot, but the kernel command should be easily mutable; `armbianEnv.txt` *might* be able to set the baud rate?

14:39 <DC-IRC> [Discord] <Werner> No, that variable isn't read from the script what it seems. This is from an sunxi devices: `if test "${console}" = "display" || test "${console}" = "both"; then setenv consoleargs "console=ttyS0,115200 console=tty1"; fi`

16:09 <Hammdist> I will ask in the u-boot channel whether it is possible to specify the baud rate for uart

16:10 <Hammdist> I think I may be able to compile u-boot and just cut and paste it onto the sd card

16:12 <Hammdist> btw does u-boot init the graphics on orange pi 5?

16:12 <Hammdist> I see nothing on the screen. does this mean it did not even get to loading u-boot?

16:14 <DC-IRC> [Discord] <Werner> Most boards lacking HDMI support at uboot stage. So not seeing anything is common

16:23 <DC-IRC> [Discord] <menu> Hammdist: is the heartbeat LED working?

16:41 <Hammdist> no heartbeat

16:41 <Hammdist> does that come from u-boot or linux already?

16:42 <DC-IRC> [Discord] <Werner> Linux. Therefore it's a good indicator that the kernel was loaded

16:42 <DC-IRC> [Discord] <Werner> Cannot tell if it dropped to initramfs though

16:42 <Hammdist> or wasn't loaded, in my case. ok. well at any rate I am compiling u-boot with a custom baud rate

21:21 <DC-IRC> [Discord] <Github> ⤴️ **Pull request** to [armbian/documentation](<https://github.com/armbian/documentation>) by [igorpecovnik](<https://github.com/igorpecovnik>) - **Please review!** 👉 [Link](<https://github.com/armbian/documentation/pull/611>): *Update dependencies*