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> [Discord] <menu> @efectn as promised:
<DC-IRC> [Discord] <menu> - `Edge (6.13rc5)` https://paste.armbian.de/zukajecodu
<DC-IRC> [Discord] <menu> - `Current (6.12.8)` https://paste.armbian.de/asiluxamef
<DC-IRC> [Discord] <menu> - `Vendor (6.1.84)` https://paste.armbian.de/tikenibisu
<DC-IRC> [Discord] <menu> - - `0bc2:231a` should be superspeed/USB3
<DC-IRC> [Discord] <menu> - - `054c:0ce6` should be highspeed/USB2, it is a composite device
<DC-IRC> [Discord] <menu> @efectn as promised:
<DC-IRC> [Discord] <menu> - `Edge (6.13rc5)` https://paste.armbian.de/zukajecodu
<DC-IRC> [Discord] <menu> - `Current (6.12.8)` https://paste.armbian.de/asiluxamef
<DC-IRC> [Discord] <menu> - `Vendor (6.1.84)` https://paste.armbian.de/tikenibisu
<DC-IRC> [Discord] <menu> - - `0bc2:231a` should be superspeed/USB3
<DC-IRC> [Discord] <menu> - - `054c:0ce6` should be highspeed/USB2, it is a composite device
<DC-IRC> [Discord] <menu> all outputs of `lsusb -vvvv`, no devices were moved or changed between tests
<DC-IRC> [Discord] <gospod13337> You just posted something about USB3 while I was going to ask if USB3 works?
<DC-IRC> [Discord] <gospod13337> Because latest armbian on OPI5, usb drive is working on a USB2 port, while on USB3 port I get in dmesg "cant enable, maybe usb cable bad?"
<DC-IRC> [Discord] <gospod13337> Also tried usbc port with usbc>usbA adapter and looks like there isnt even any power through that port
juri_ has quit [Ping timeout: 244 seconds]
juri_ has joined #armbian-rockchip
<DC-IRC> [Discord] <gospod13337> Is it possible that a simple USB3 is still not working on OPI5 after all this time?
<DC-IRC> [Discord] <menu> USB3 is currently broken on oPi 5, i've not had it working since 5.10
<DC-IRC> [Discord] <menu> this specific issue occurred with one of my USB drives, the other will happily drop down to USB2 (or even 1.1)
<DC-IRC> [Discord] <rpardini> u-boot/mainline: is there a way one can have a `-u-boot.dtsi` file that applies to multiple boards?
<DC-IRC> [Discord] <rpardini> in specific, the NanoPC-T6 "LTS variant" seems to be missing a `-u-boot.dtsi`, I'm wondering if there's a smarter way than just duplicating...
<DC-IRC> [Discord] <kwiboo> Mainline U-Boot has support for both the T6 LTS and non-LTS version using same defconfig, it sets correct fdtfile and load correct control fdt for the board variant at runtime
<DC-IRC> [Discord] <rpardini> oh indeed it does and works perfectly.
<DC-IRC> [Discord] <kwiboo> For your specific question, no only on soc and arch level to my knowledge
<DC-IRC> [Discord] <rpardini> but, there's a `arch/arm/dts/rk3588-nanopc-t6-u-boot.dtsi` but not a `arch/arm/dts/rk3588-nanopc-t6-lts-u-boot.dtsi`
<DC-IRC> [Discord] <rpardini> I found that out by trying to (as always...) enable UMS/Gadget, but it seems the saradc stuff also suffers.
<DC-IRC> [Discord] <kwiboo> If <board>-u-boot.dtsi is missing, <soc>-u-boot.dtsi would be included, and if that is missing <arch>-u-boot.dtsi
<DC-IRC> [Discord] <kwiboo> hum, could you be using vendor SPL and mainline u-boot proper? SPL should check what model and load the correct fdt from FIT payload
<DC-IRC> [Discord] <kwiboo> As I am typing I realise that could possible be an actual issue, and a board-u-boot.dtsi could be needed for the secondary board
<DC-IRC> [Discord] <kwiboo> I only have the non-LTS version of the T6, so have not been able to do full runtime test on a LTS version
<DC-IRC> [Discord] <rpardini> yeah I've only the LTS -- and been trying to make it UMS by changing the non-LTS dtsi, assuming that would apply to both -- it doesn't.
<DC-IRC> [Discord] <rpardini> it's not a big problem -- the dtsi is only bootph-xxx and a single vdd-microvolts for saradc
<DC-IRC> [Discord] <rpardini> it's only when I added the classic `&usb_host0_xhci { dr_mode = "peripheral"; }` in there that I noticed.
<DC-IRC> [Discord] <rpardini> also I realize I'm probably too late for 2025.01 by a few hours...?
<DC-IRC> [Discord] <kwiboo> probably, do not think it would count as a release blocker, but probably in good time for 2025.04
<DC-IRC> [Discord] <rpardini> yeah. it's perfect otherwise, and for Armbian I can just do a single `cp` and workaround it.
<DC-IRC> [Discord] <rpardini> wonder though if some other recent multi-dtb boards could be in the same situation, opi3b namely
<DC-IRC> [Discord] <kwiboo> maybe the board dts should drop dr_mode=host if it is used, have not looked closly, and sardac should work in U-Boot proper, bootph props should mainly be needed for SPL
<DC-IRC> [Discord] <rpardini> yeah I tried to convince Justin to keep it in otg mode in the kernel DT, but failed
<DC-IRC> [Discord] <rpardini> seems like I'm the only one with a gadget obcession
<DC-IRC> [Discord] <kwiboo> other multi-dtb boards could also be affected, will take a look for the boards/defconfigs I have added
<DC-IRC> [Discord] <rpardini> excellent, thanks for everything. it's awesome!
<DC-IRC> [Discord] <kwiboo> look like I added u-boot.dtsi for both radxa zero 3 and opi3b, so they should probably not be affected, will take a closer look at T6
<DC-IRC> [Discord] <efectn> Thanks will check them
<DC-IRC> [Discord] <kwiboo> @rpardini for nanopc-t6 the usb_host0_xhci is not enabled in 2025.01 dts/upstream so should not really be affected for the imminent u-boot release, and the other spi nor flash node with bootph-some-ram should only be needed with ENV_IS_IN_SPI_FLASH enabled
<DC-IRC> [Discord] <rpardini> Confirm. It's definitely not a blocker for release.
<DC-IRC> [Discord] <kwiboo> so no critical release bug, but I can send a patch for 2025.04 that adds a lts-u-boot.dtsi that just include the non-lts u-boot.dtsi, similar to the other multi-dtb configs I have added
<DC-IRC> [Discord] <rpardini> I've sent https://github.com/armbian/build/pull/7662 -- I already had `ENV_IS_IN_SPI_FLASH` back from 2024.10 in there
<DC-IRC> [Discord] <rpardini> also, your `checkdtb.py` told me to enable `CONFIG_DM_PMIC_FAN53555` so I did 😉
<DC-IRC> [Discord] <kwiboo> hehe, yeah, it should probably be enabled for more boards, I have some local code to add support for the rk860 pmic's that should be sent upstream
<DC-IRC> [Discord] <kwiboo> @rpardini send a patch: https://lore.kernel.org/u-boot/20250106182232.3741304-1-jonas@kwiboo.se/
<DC-IRC> [Discord] <rpardini> awesome, thanks!
<DC-IRC> [Discord] <kwiboo> thanks for reporting!
<DC-IRC> [Discord] <rpardini> just for sheer completeness, I pulled devicetree-rebasing from 6.13-rc5, and now the USB3 Type-A port (in the front) also works.
<DC-IRC> [Discord] <rpardini> ```
<DC-IRC> [Discord] <rpardini> 1 Hub (5 Gb/s, 0mA)
<DC-IRC> [Discord] <rpardini> | U-BHCI Host Controller
<DC-IRC> [Discord] <rpardini> |
<DC-IRC> [Discord] <rpardini> +-2 Mass Storage (5 Gb/s, 0mA)
<DC-IRC> [Discord] <rpardini> SanDisk USB Extreme Pro 133116796170
<DC-IRC> [Discord] <rpardini> ```
_whitelogger has joined #armbian-rockchip
<DC-IRC> [Discord] <gospod13337> Armbian is currently ob 6.12, while on rk3588 mainline status page it says USB3 should be merged in 6.10
<DC-IRC> [Discord] <gospod13337> Do i understand it wrong by thinking it should be working already?
<DC-IRC> [Discord] <gospod13337> Armbian is currently on 6.12, while on rk3588 mainline status page it says USB3 should be merged in 6.10
<DC-IRC> [Discord] <menu> it *should* be working, and i believe does work on other RK3588/s, i unfortunately do not understand *why* it doesn't work :(
<DC-IRC> [Discord] <gospod13337> @amazingfate sorry for ping. Should USB3 be working on OPI5?
<DC-IRC> [Discord] <gospod13337> @nicod_sbc @spooky8086 sorry for ping 😄
<DC-IRC> [Discord] <igorpec> please don't do that.
<DC-IRC> [Discord] <spooky8086> :girl_Wtf_what_confused_huh_anime:
<DC-IRC> [Discord] <efectn> Update it to 6.13, your problem will be solved
<DC-IRC> [Discord] <gospod13337> That needs to be done outside armbian-config?
<DC-IRC> [Discord] <efectn> Can you send dmesg output as well
<DC-IRC> [Discord] <efectn> Are you using stable or nightly repos?
<DC-IRC> [Discord] <menu> for all three?
<DC-IRC> [Discord] <gospod13337> Imo stable
<DC-IRC> [Discord] <efectn> 6.1 and 6.13
<DC-IRC> [Discord] <efectn> You can switch to nightly and install rockchip64 edge kernel packages
<DC-IRC> [Discord] <gospod13337> Is that called "rolling release" in armbian-config?
<DC-IRC> [Discord] <menu> will do when i next have physical access
<DC-IRC> [Discord] <efectn> yes
<DC-IRC> [Discord] <gospod13337> Is home assistant in armbian supervised or docker core?
<DC-IRC> [Discord] <gospod13337> Is home assistant in armbian-config supervised or docker core?
<DC-IRC> [Discord] <gospod13337> Great, i switched to rolling release and now it wont boot. Thank god I backed up home assistant
<DC-IRC> [Discord] <efectn> Do you have usb uart ttl converter
<DC-IRC> [Discord] <gospod13337> I think so somewhere
<DC-IRC> [Discord] <igorpec> supervised
<DC-IRC> [Discord] <igorpec> i am using it in production
<DC-IRC> [Discord] <gospod13337> I manually installed supervised (which now wont boot :P)
<DC-IRC> [Discord] <gospod13337> Is your supervisor updatable?
<DC-IRC> [Discord] <gospod13337> You are running on odroid n2+?
<DC-IRC> [Discord] <gospod13337> Where can i find sources for supervisor_fix.sh?