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
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
<DC-IRC>
[Discord] <torte_34905> @emulators @gin_kage : The "usermod" command is the obvious key, but don't underestimate the "systemctl" commands: Without them, there would be a login prompt at the serial port, which will interfere with the connected devices every now and then, resulting in frequent misbehaviour. Can be fun to debug.😄
<DC-IRC>
[Discord] <torte_34905> As you have already found out, using the original DTB file on recent Armbian images for Makerbase boards will enable WiFi (that should work with MKS-PI, MKS-KLIPAD50 and probably MKS-SKIPR images).
<DC-IRC>
[Discord] <dtdtdtdt> talking about mainline uboot here, hope someone will have a guess to what's wrong
<DC-IRC>
[Discord] <dtdtdtdt> since v2024.10 I can't access serial flash in uboot,
<DC-IRC>
[Discord] <dtdtdtdt> talking about mainline uboot here, hope someone will have a guess to what's wrong
<DC-IRC>
[Discord] <dtdtdtdt> since v2024.10 I can't access serial flash in uboot
<DC-IRC>
[Discord] <dtdtdtdt> on rock pi 4c that is. One issue was that freq was bumped to 108MHz from 10MHz, got that sort of sorted out. The bigger issue is this that in u-boot specific tweaks to the board (rk3399-rock-pi-4-u-boot.dtsi) leds section was added. If I comment out the whole "/" node I can read the flash but if not flash is inaccessible with error "jedec_spi_nor flash@0: unrecognized JEDEC id by <clipped message>
<DC-IRC>
[Discord] <dtdtdtdt> tes: ff, ff, ff Failed to initialize SPI flash at 1:0 (error 0)"
<DC-IRC>
[Discord] <dtdtdtdt> here's that relevant file attached