lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
<lanefu>
i wonder if that helps with like the later production PBP's that were having armbian alergies
<Armbian-Discord>
<rpardini> I think more is needed to get PBP itself in shape (no idea, really) but not-breaking other boards is a win already.
<Armbian-Discord>
<rpardini> The pbp DT is still messed-up, I think.
<Armbian-Discord>
<ManoftheSea> Geez, why am I having so much trouble with it then?
<Armbian-Discord>
<ManoftheSea> The Helios
<Armbian-Discord>
<ManoftheSea> I tried armbian's uboot with 6.1.2, and still no sata disks. Fancontrol was working, though.
<Armbian-Discord>
<ManoftheSea> I gave up on it, went back to armbian 21.0¿ That isn't updating
<Armbian-Discord>
<Tonymac32> I haven't updated mine in a looooong time
<Armbian-Discord>
<Tonymac32> well, I have 22.02 on it
<Armbian-Discord>
<Tonymac32> unknown bootloader age though
troglodito has quit [Ping timeout: 252 seconds]
troglodito has joined #armbian-rockchip
<Armbian-Discord>
<shineworld> I'm getting crazy with Opi4LTS and serial TTY using CH340 on W10.
<Armbian-Discord>
<shineworld> I've tried all "current" img for the board.
<Armbian-Discord>
<shineworld> I've tried 5 different CH340 devices.
<Armbian-Discord>
<shineworld> I've tried to build a "trunk" img from sources.
<Armbian-Discord>
<shineworld> Same results.
<Armbian-Discord>
<shineworld> Incoming text (from Opi4LTS) are fine.
<Armbian-Discord>
<shineworld> Outcoming chars, during editing, are corrupted.
<Armbian-Discord>
<shineworld> Some time a pressed char is not captured, or is captured but return a odd char as eco as in image.
<Armbian-Discord>
<shineworld> Do you have any idea about that ?
Armbian-Discord has quit [Remote host closed the connection]
Armbian-Discord has joined #armbian-rockchip
<Armbian-Discord>
<shineworld> I've tried in Linux with kermit but same thing...
<Armbian-Discord>
<Werner> Just pure guess. Maybe due to a flaw a wrong error message is displayed and the reason for rejection is actually that it is too weak? try something like qawsed123
<Armbian-Discord>
<Tenkawa> What serial settings are you using and adapter?
<Armbian-Discord>
<shineworld> I followed instructions so:
<Armbian-Discord>
<shineworld> speed = 1500000
<Armbian-Discord>
<shineworld> data bits = 8
<Armbian-Discord>
<shineworld> stop bits = 1
<Armbian-Discord>
<shineworld> parity = None
<Armbian-Discord>
<shineworld> flow control = None
<Armbian-Discord>
<shineworld> The adapter is CH340 HW-597
<Armbian-Discord>
<shineworld> In W10 I've checked that is latest driver (3.5.2019.1)
<Armbian-Discord>
<rpardini> hmm. make sure jumper cables between uart and SBC are the shortest possible
<Armbian-Discord>
<shineworld> Ah connected VCC to 3.3v output in the USB converter
<Armbian-Discord>
<rpardini> nah. don't plug VCC. plug only ground and tx / rx
<Armbian-Discord>
<rpardini> I don't know that adapter, but in general, for SBCs you don't need VCC at all; the UART is powered via USB from host, and the SBC powers itself. You just need GND and TX / RX.