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
javabean has quit [Ping timeout: 246 seconds]
javabean has joined #armbian-rockchip
<DC-IRC> <jackn01> its not the cable
<DC-IRC> <tenkawa42> Well that's a bummer
<DC-IRC> <jackn01> can someone test the hdmi video of the orangepi4 ? (not op4lts)
<DC-IRC> <Tonymac32> Rk3568-odroid family has bad opps for the dvfs. Voltages are too low for the mid range opps, which can Do Weird Things (TM) to the overall table.
<DC-IRC> <rpardini> Hmm. `rk3568-odroid` is just mainline 6.5-rcX, and patches for overlays....
<DC-IRC> <lanefu> Seems like common opp table in mainline hasn't changed in 2 years
<DC-IRC> <rpardini> maybe... this had to do with updated rkbins?
<DC-IRC> <rpardini> btw... speaking of rkbins...
<DC-IRC> <rpardini> does anyone know how to "combine" say `rk3399_ddr_800MHz_v1.30.bin` and `rk3399_usbplug_v1.30.bin` into a single loader for `rkdeveloptool`?
<DC-IRC> <lanefu> I think what's in the kernel are the "wrong values" tony observed when we were chatting last night.
<DC-IRC> <lanefu> `cat` lol
<DC-IRC> <rpardini> really? I can just concatenate them? lol
<DC-IRC> <lanefu> Troll advice but worth a try lol
<DC-IRC> <rpardini> Tried, doesn't work.
<DC-IRC> <rpardini> ```bash
<DC-IRC> <rpardini> $ cat rk3399_ddr_800MHz_v1.30.bin rk3399_usbplug_v1.30.bin > rk3399_ddr_800MHz_v1.30_plus_usbplug_v1.30.bin
<DC-IRC> <rpardini> $ rkdeveloptool db rk3399_ddr_800MHz_v1.30_plus_usbplug_v1.30.bin
<DC-IRC> <rpardini> Opening loader failed, exiting download boot!
<DC-IRC> <rpardini> # Meanwhile this works! (init SPL with xrock from https://github.com/xboot/xrock)
<DC-IRC> <rpardini> $ xrock maskrom rk3399_ddr_800MHz_v1.30.bin rk3399_usbplug_v1.30.bin
<DC-IRC> <rpardini> $ rkdeveloptool wl 0x0 Armbian_xxx.img
<DC-IRC> <rpardini> # works
<DC-IRC> <rpardini> ```
<DC-IRC> <lanefu> xrock is also a cooler name
<DC-IRC> <lanefu> Is it easier to compile?
<DC-IRC> <rpardini> yeah. but it's `xrock write 0x0 armbian.img` does NOT work...
<DC-IRC> <rpardini> If I use it only to init the loader, then use the regular rkdeveloptool to `wl` it works. 🤔
<DC-IRC> <lanefu> That's goofy it just can't init the board?
<DC-IRC> <rpardini> No, I'm just missing some mkimage or such, to combine DDR + usbplug into a single thing.
<DC-IRC> <lanefu> Oh
<DC-IRC> <lanefu> Hey so on another topic.
<DC-IRC> <lanefu> In our new modern way of living in the Armbian builder. Would I still use the BSP folder and BSP functions if I wanna add things like a udev config to a board build?
<DC-IRC> <lanefu> Will def try the new vendor pattern in patch folder dt overlays
<DC-IRC> <rpardini> well that's 2 questions....
<DC-IRC> <rpardini> - for userspace stuff... a bit of personal preference... if you wanna put files in bsp folder, then use a hook to copy them, it's OK. I personally rather use bash heredocs to keep everything together in the same place. more so if it's few lines of udev or some systemd service.
<DC-IRC> <rpardini> - for kernel overlays... a few edge kernels already use the "no patching required" approach, if they have a `0000.patching_config.yaml` in the patch folder; just follow the trail from there (add overlay + add it to Makefile, no patching required).
<DC-IRC> <lanefu> Yes the no patching required method like I saw for mekotronics and t6 is what I was thinking
<DC-IRC> <lanefu> Yeah I guess heredoc inline in the config file is sane for a 3 line udev file
<DC-IRC> <rpardini> Hmm right now we only have `0000.patching_config.yaml` for
<DC-IRC> <rpardini> - rockchip64 / edge
<DC-IRC> <rpardini> - meson64 / edge
<DC-IRC> <rpardini> - rockchip-rk3588 / edge + collabora
<DC-IRC> <rpardini> - rk3568-odroid / edge
<DC-IRC> <rpardini> so yeah edge-y stuff only for now. the convenience is nice, but has caused devs to forget sending Makefile upstream for example.
<DC-IRC> <rpardini> I dunno in the end if people think it is a good idea.
<DC-IRC> <Tonymac32> Nah it's fine
<DC-IRC> <lanefu> speaking of rk3568-odroid.. looks like 6.5.0-rc7 is out now
<DC-IRC> <rpardini> feel free to bump. patches should go down easy
<DC-IRC> <lanefu> word
<DC-IRC> <lanefu> r5s does _gig shaming_ show orange light when connected at 1GB on the 2.5G ports lol
<DC-IRC> <stonededge> Does anyone have a moment to help me debug why my MIPI ILI9881C driver would not work with the attached device tree edits?
<DC-IRC> <stonededge> I can provide dmesg logs as well if required but it seems like the panel is not even being detected
<DC-IRC> <lanefu> i'd suggest https://paste.armbian.com for sharing configs and logs
<DC-IRC> <stonededge> Here’s the Git Diff for the changes I’ve made:
<DC-IRC> <stonededge> Thank you!
<DC-IRC> <stonededge> Oh, & of course I enabled the LCD2 DTBO in armbianEnv.txt just in case:
<DC-IRC> <stonededge> root@orangepi5:/boot# cat armbianEnv.txt
<DC-IRC> <stonededge> verbosity=1
<DC-IRC> <stonededge> bootlogo=true
<DC-IRC> <stonededge> overlay_prefix=rk3588
<DC-IRC> <stonededge> fdtfile=rockchip/rk3588s-orangepi-5.dtb
<DC-IRC> <stonededge> overlays=lcd2
<DC-IRC> <lanefu> I've never made a device tree overlay in my life... does this https://armbian.lane-fu.com/linx/yorjp5wd.c (ignore file extension)
<DC-IRC> <lanefu> remotely look like an overlay for
<DC-IRC> <lanefu> err i guess overlay for _this_? this is the active device tree using the dtc tools n stuff
<DC-IRC> <lanefu> nm i think i got it.. https://armbian.lane-fu.com/linx/6k8exivl.c
<DC-IRC> <lanefu> and by "got it" I mean compiled, but then makes it not boot lol
<DC-IRC> <Tonymac32> I think you need to target the led nodes directly, not just the whole group
<DC-IRC> <c0rnelius77> what leds, the eth ports?
<DC-IRC> <Tonymac32> also just switched from phone to PC
<DC-IRC> <Tonymac32> hang tight
<DC-IRC> <Tonymac32> the R5S has 4 GPIO LED's, three of them are there to show link status
<DC-IRC> <c0rnelius77> ? ```
<DC-IRC> <c0rnelius77> echo 'SUBSYSTEM=="leds", KERNEL=="green:wan", ACTION=="add", ATTR{trigger}="netdev", ATTR{device_name}="eth2", ATTR{link}="1" ATTR{rx}="1" ATTR{tx}="1"' > /etc/udev/rules.d/10-nanopi-led.rules
<DC-IRC> <c0rnelius77> echo 'SUBSYSTEM=="leds", KERNEL=="green:lan1", ACTION=="add", ATTR{trigger}="netdev", ATTR{device_name}="eth0", ATTR{link}="1" ATTR{rx}="1" ATTR{tx}="1"' >> /etc/udev/rules.d/10-nanopi-led.rules
<DC-IRC> <c0rnelius77> echo 'SUBSYSTEM=="leds", KERNEL=="green:lan2", ACTION=="add", ATTR{trigger}="netdev", ATTR{device_name}="eth1", ATTR{link}="1" ATTR{rx}="1" ATTR{tx}="1"' >> /etc/udev/rules.d/10-nanopi-led.rules
<DC-IRC> <c0rnelius77> ```
<DC-IRC> <c0rnelius77> That dts in linus repo looks like the same one I have in my repo or just about. I don't own the board but I'm told that works. Might not to fiddle with it.
<DC-IRC> <c0rnelius77> That dts in linus repo looks like the same one I have in my repo or just about. I don't own the board but I'm told that works. Might need to fiddle with it.
<DC-IRC> <lanefu> fuck you for making that magically work LOL. i tried doing that with udev for 2 hours last night and failed
<DC-IRC> <lanefu> oh well just works for WAN right now lemme debug
<DC-IRC> <Tonymac32> WAN is the built-in, the others are PCIe so somthing might be sideways
<DC-IRC> <lanefu> yeah i tried matching the lan interfaces to my device names and still no dice
<DC-IRC> <lanefu> okay yeah that didn't actually work.. it was my existin device tree modification i had on WAN that was working
<DC-IRC> <lanefu> tell me more
<DC-IRC> <Tonymac32> target = <&led-lan1>;
<DC-IRC> <Tonymac32> etc
<DC-IRC> <Tonymac32> fragment 0,1,and 2
<DC-IRC> <Tonymac32> well hang on
<DC-IRC> <Tonymac32> yeah that's what I meant to say
<DC-IRC> <Tonymac32> example
<DC-IRC> <viraniac> I recently found out that we don't really have to worry about all that syntax and stuff for new dtc compilers. We can create a dts similar to how we create one for the boards. Take the dts that this user created for example https://forum.armbian.com/topic/29580-duo2-6134-sunxi-ov5640-video-capture-kernel-oops/
<DC-IRC> <lanefu> ```root@nanopi-r5s:~# armbian-add-overlay led.dts
<DC-IRC> <lanefu> Compiling the overlay
<DC-IRC> <lanefu> Error: led.dts:9.20-21 syntax error
<DC-IRC> <lanefu> FATAL ERROR: Unable to parse input tree
<DC-IRC> <lanefu> Error compiling the overlay
<DC-IRC> <lanefu> root@nanopi-r5s:~# cat led.dts
<DC-IRC> <lanefu> /dts-v1/;
<DC-IRC> <lanefu> /plugin/;
<DC-IRC> <lanefu> / {
<DC-IRC> <lanefu> compatible = "friendlyarm,nanopi-r5s\0rockchip,rk3568";
<DC-IRC> <lanefu> fragment@0 {
<DC-IRC> <lanefu> target = <&led-wan>;
<DC-IRC> <lanefu> __overlay__ {
<DC-IRC> <lanefu> linux,default-trigger = "stmmac-0:01:link";
<DC-IRC> <lanefu> };
<DC-IRC> <lanefu> };
<DC-IRC> <lanefu> };
<DC-IRC> <lanefu> ```
<DC-IRC> <lanefu> doesn't like the `&led-wan` reference
<DC-IRC> <lanefu> should i use a target `/path/i have no idea`?
<DC-IRC> <viraniac> is their something existing with that led-wan name in the device dts?
<DC-IRC> <lanefu> when i used the armbian device tree editor... this is the section it gives me
<DC-IRC> <lanefu> line 31 I manually edited via teh armbian device tree editor thing an dit worked... so my overlay is trying to duplicate that behavior
<DC-IRC> <Tonymac32> Yeah you need to target the node nane, in the device tree I think it's just lan1/2/3
<DC-IRC> <lanefu> when i used the armbian device tree editor... this is the section it gives me
<DC-IRC> <lanefu> line 31 I manually edited via the armbian device tree editor thing and it worked... so my overlay is trying to duplicate that behavior
<DC-IRC> <lanefu> how do i find the node name
<DC-IRC> <Tonymac32> Original device tree
<DC-IRC> <viraniac> Could you please share your full dts as shown by armbian device tree editor?
<DC-IRC> <Tonymac32> hmmm
<DC-IRC> <lanefu> haha i thikn its dumber than that lol i thikn i got it standby
<DC-IRC> <viraniac> could you please try this https://paste.armbian.com/raw/ekimusawis
<DC-IRC> <viraniac> This is also my first overlay from scratch btw, so it can fail
<DC-IRC> <lanefu> yep standby
<DC-IRC> <rpardini> damn I dunno any answers, but share the pain, also the fact I just do alternative dts for overlays that patch more than 1 thing
<DC-IRC> <viraniac> @lanefu I missed semicolon after the closing brace. That will throw error
<DC-IRC> <lanefu> @viraniac looking good so far
<DC-IRC> <lanefu> yeah i got the semi colon
<DC-IRC> <lanefu> gonan try to add the other 2 and see if you get full credit
<DC-IRC> <viraniac> try this - https://paste.armbian.com/raw/eqibafeyon
<DC-IRC> <Tonymac32> that's equivalent to his first try I think
<DC-IRC> <Tonymac32> Bam and Yoink are official terms
<DC-IRC> <Tonymac32> ok, so three fragments, better path descriptor
<DC-IRC> <viraniac> There is double end quotes at the end of led-lan2 remove one of them
<DC-IRC> <Tonymac32> a little surprised the &led-wan didn't work :/ but I'm sure it's just lack of know-how on my side 😄
<DC-IRC> <viraniac> That will work as well
<DC-IRC> <lanefu> lol confirmed
<DC-IRC> <viraniac> Thats because it was never declared as led-wan: led-wan style
<DC-IRC> <Tonymac32> ah right
<DC-IRC> <lanefu> now
<DC-IRC> <lanefu> I'm so fucking happy
<DC-IRC> <lanefu> thank you all!
<DC-IRC> <lanefu> as you no. there is NO GREATER GRATIFICATION than making lights blink on your terms with SBCs and micro controllers
<DC-IRC> <lanefu> as you know-- there is NO GREATER GRATIFICATION than making lights blink on your terms with SBCs and micro controllers
<DC-IRC> <Tonymac32> haha correct
<DC-IRC> <clever___> i find this more impressive, scaling an image in realtime
<DC-IRC> <clever___> but i did have to start with uart and blinking
<DC-IRC> <lanefu> yeah you're varsity league... i'm peewee
<DC-IRC> <lanefu> and yeah toatlly impressiv elol
<DC-IRC> <clever___> and ive also gone full 3d and shaders
<DC-IRC> <lanefu> does it git rid of that horrible logo 🤣
<DC-IRC> <clever___> the sprite draw order does allow the logo to hide behind the triangle!
<DC-IRC> <lanefu> very cool