04:48 <pnill> If anyone else ever searches IRC logs for the H6 and not having a script.bin but wanting to modify the DTB/soc-config... I extracted the boot_package.fex manually by hand, there's an example config file boot_package.cfg in the tools stuff of BSP and then dragonsecboot, if it's not signed with a cert or whatever you can just use that cfg, use the same names you find in boot_package.fex and re-create them.... then run dragonsecboot -pack

04:48 <pnill> boot_package.cfg and it'll build a new boot_package.fex with your changes.

04:50 <pnill> The soc-cfg in the boot_package.cfg just seems to be a bin like the script.bin so you can use bin2fex, then modify it and take it back the other way, the dtb just seems to be a standard dtb.

05:49 <buZz> wouldnt using dtb men no need to use fex?

05:49 <buZz> wouldnt using dtb mean no need to use fex?

05:50 <buZz> fex is old stuff

06:19 <pnill> Idk it uses one for u-boot

06:19 <pnill> and one for the Android setup

06:19 <pnill> seems to use the dtb in the android setup

06:19 <pnill> and fex in the u-boot

08:24 <jernej> smaeul: does analog audio work on D1 with your driver? I plan to reuse it for H616...

13:57 <smaeul> jernej: yes, analog audio works on D1. the RAMP_REG is still mysterious to me. setting some bits in it is required or else there is major distortion

13:58 <smaeul> it looks like R329 is also the same HW, with no headphone part (like H616) and with 5 ADC channels

14:00 <smaeul> I can refactor the driver to work with all three, so we don't start with the newest/most compilicated one (D1) first

14:06 <jernej> smaeul: that would be great!

14:06 <jernej> I tried, but I couldn't make it work on H616

14:26 <valdikss> Does anyone know where to buy FBGA396 A64 reballing stencil template?

14:27 <valdikss> Found on ebay :D "Direct heating 80*80 90*90 A64 CPU BGA396 BGA Stencil Template"

14:27 <jakllsch> heh

14:29 <valdikss> The only one seller on ebay and aliexpress

14:29 <valdikss> US $13.50 + Shipping: US $3.47 :/

14:46 <apritzel> valdikss: you mentioned watchdog issues with USB OTG in mainline U-Boot the other day, with which command was this? "ums" seemed to work fine for me

15:10 <valdikss> apritzel: do "dd if=/dev/sdX bs=1M of=/dev/null" on sufficiently large emmc/flash and wait for 20+ seconds

15:11 <valdikss> apritzel: in my case, the spinner freezes completely while reading is going

15:13 <valdikss> apritzel: and I assume that watchdog is not getting updated. I could be wrong and the board rebooted not due to watchdog.

15:15 <valdikss> apritzel: I've tested only twice, after that all the time disabled the watchdog before running.

15:20 <apritzel> valdikss: mmh, I did copy a lot of data via ums (for at least 30 seconds), but didn't see any issues

15:21 <valdikss> apritzel: hrm, ok

15:21 <apritzel> also it looks like the ums command pets the watchdog correctly

15:21 <apritzel> WATCHDOG_RESET() in cmd/usb_mass_storage.c

15:22 <apritzel> I will retry later

22:19 <pnill> apritzel: Do you know anything about LCD configurations?

22:19 <pnill> mainline or BSP doesn't matter lol.

23:05 <apritzel> pnill: no, nothing at all :-(

23:06 <apritzel> you can hardcode something in U-Boot, but I don't even know if this still works

23:42 <pnill> Was more so wondering how values like the DCLK are calculated than how to implement/integrate lol

23:43 <pnill> I guess a bit of googling and I sort of got an answer that it's related to how large a display is but I don't understand it entirely part of it is the application I'm using it in is weird with LVDS->HDMI and some china board to handle it to a larger display.