Hi @Portisch, is it possible that I leave my device running to let you inspect? H96max w2 (s905w2 with aic8800 wifi)? Thanks.
dmesg | paste
http://ix.io/4HiT
ce-debug
http://ix.io/4HiX
journalctl -l | paste
http://ix.io/4HiY
pcie@f5000000 {
compatible = "amlogic, amlogic-pcie-v2", "snps,dw-pcie";
reg = <0x0 0xf5000000 0x0 0x400000 0x0 0xfe02c000 0x0 0x2000 0x0 0xf5400000 0x0 0x200000 0x0 0xfe02a000 0x0 0x2000 0x0 0xfe002044 0x0 0x10>;
reg-names = "elbi", "cfg", "config", "phy", "reset";
interrupts = <0x0 0x8d 0x4>;
#interrupt-cells = <0x1>;
bus-range = <0x0 0xff>;
#address-cells = <0x3>;
#size-cells = <0x2>;
interrupt-map-mask = <0x0 0x0 0x0 0x0>;
interrupt-map = <0x0 0x0 0x0 0x0 0x1 0x0 0x8f 0x1>;
device_type = "pci";
ranges = <0x81000000 0x0 0x0 0x0 0xf5600000 0x0 0x100000 0x82000000 0x0 0xf5700000 0x0 0xf5700000 0x0 0x1900000>;
num-lanes = <0x1>;
pcie-num = <0x1>;
clocks = <0x8 0x2d 0x8 0x126 0x8 0x128 0x8 0x3d>;
clock-names = "pcie_refpll", "pcie", "pcie_phy", "pcie_hcsl";
gpio-type = <0x2>;
pcie-apb-rst-bit = <0xe>;
pcie-phy-rst-bit = <0xd>;
pcie-ctrl-a-rst-bit = <0xc>;
pwr-ctl = <0x0>;
power-domains = <0x18 0x7>;
pcie-ctrl-sleep-shift = <0xf>;
pcie-hhi-mem-pd-shift = <0x1a>;
pcie-hhi-mem-pd-mask = <0xf>;
pcie-ctrl-iso-shift = <0xf>;
status = "okay";
reset-gpio = <0x1b 0x39 0x0>;
};
@vpeter @Portisch
single.dts (87.3 KB)
Use the image from here:
After update, replace dtb.img with this dtb:
sc2_s905x4_4g_1gbit.dtb (72.2 KB)
After reboot run the cmds:
udevadm info /sys/bus/pci/devices/* | paste
lspci | paste
dmesg | paste
ifconfig | paste
##############################################
# CoreELEC #
# https://coreelec.org #
##############################################
CoreELEC (vpeter): 21.0-Omega_devel_vpeter (Amlogic-ne.aarch64)
Machine model: Amlogic
CoreELEC dt-id: sc2_s905x4_4g_1gbit
CoreELEC:~ # udevadm info /sys/bus/pci/devices/* | paste
Unknown device “/sys/bus/pci/devices/*”: No such device
CoreELEC:~ # lspci | paste
CoreELEC:~ # dmesg | paste
http://ix.io/4Ho7
CoreELEC:~ # ifconfig | paste
http://ix.io/4Ho8
CoreELEC:~ # mount -rw -o /flash | paste
http://ix.io/4Hoe
pcie@f5000000 {
compatible = "amlogic, amlogic-pcie-v2", "snps,dw-pcie";
reg = <0x0 0xf5000000 0x0 0x400000 0x0 0xfe02c000 0x0 0x2000 0x0 0xf5400000 0x0 0x200000 0x0 0xfe02a000 0x0 0x2000 0x0 0xfe002044 0x0 0x10>;
reg-names = "elbi", "cfg", "config", "phy", "reset";
interrupts = <0x0 0x8d 0x4>;
#interrupt-cells = <0x1>;
bus-range = <0x0 0xff>;
#address-cells = <0x3>;
#size-cells = <0x2>;
interrupt-map-mask = <0x0 0x0 0x0 0x0>;
interrupt-map = <0x0 0x0 0x0 0x0 0x1 0x0 0x8f 0x1>;
device_type = "pci";
ranges = <0x81000000 0x0 0x0 0x0 0xf5600000 0x0 0x100000 0x82000000 0x0 0xf5700000 0x0 0xf5700000 0x0 0x1900000>;
num-lanes = <0x1>;
pcie-num = <0x1>;
clocks = <0x8 0x2d 0x8 0x126 0x8 0x128 0x8 0x3d>;
clock-names = "pcie_refpll", "pcie", "pcie_phy", "pcie_hcsl";
gpio-type = <0x2>;
pcie-apb-rst-bit = <0xe>;
pcie-phy-rst-bit = <0xd>;
pcie-ctrl-a-rst-bit = <0xc>;
pwr-ctl = <0x0>;
pcie-ctrl-sleep-shift = <0xf>;
pcie-hhi-mem-pd-shift = <0x1a>;
pcie-hhi-mem-pd-mask = <0xf>;
pcie-ctrl-iso-shift = <0xf>;
status = "okay";
reset-gpio = <0x1b 0x35 0x0>;
};
I’m giving up (I think again?). I have nothing from helping you and looks like you always demand something.
It will take as long it needed. And no, probably can’t be fixed tonight. But now it will take even longer. Please don’t use my nick again in your messages!
1 Like
It is recommended to brush the latest ne version every night edition.
CoreELEC:~ # mount -o rw,remount /flash
CoreELEC:~ # fdtput -t s /flash/dtb.img /soc/pcie@f5000000 status okay
CoreELEC:~ # sync
CoreELEC:~ # reboot
CoreELEC:~ # lspci | paste
CoreELEC:~ # udevadm info /sys/bus/pci/devices/* | paste
Run the preceding command to check whether the pcie link can be obtained.
If the log link is obtained, please post the link and wait for it to be adapted.
@Tuxino
In my H96max w2 box (wifi aic8800), the dts file looks like:
aml_wifi: aml_wifi {
compatible = "amlogic, aml-wifi";
status = "disabled";
irq_trigger_type = "GPIO_IRQ_LOW";
//dhd_static_buf; /* if use bcm wifi, config dhd_static_buf */
//pinctrl-0 = <&pwm_e_pins>;
//pinctrl-names = "default";
pwm_config = <&wifi_pwm_conf>;
};
&aml_wifi{
status = "okay";
interrupt-gpios = <&gpio GPIOX_7 GPIO_ACTIVE_HIGH>;
power_on-gpios = <&gpio GPIOX_6 GPIO_ACTIVE_HIGH>;
};
wifi_pwm_conf:wifi_pwm_conf{
pwm_channel1_conf {
pwms = <&pwm_ef 0 30541 0>;
duty-cycle = <15270>;
times = <7>;
};
pwm_channel2_conf {
pwms = <&pwm_ef 2 30500 0>;
duty-cycle = <15250>;
times = <10>;
};
};
sd_emmc_a: sdio@fe088000 {
compatible = "amlogic,meson-axg-mmc";
reg = <0x0 0xfe088000 0x0 0x800>,
<0x0 0xfe00016c 0x0 0x4>,
<0x0 0xfe00400c 0x0 0x4>;
interrupts = <GIC_SPI 176 IRQ_TYPE_LEVEL_HIGH>;
status = "disabled";
clocks = <&clkc CLKID_SD_EMMC_A>,
<&clkc CLKID_SD_EMMC_A_CLK_MUX>,
<&clkc CLKID_SD_EMMC_A_CLK>,
<&xtal>,
<&clkc CLKID_FCLK_DIV2>;
clock-names = "core", "mux0", "mux1",
"clkin0", "clkin1";
card_type = <3>;
mmc_debug_flag;
cap-sdio-irq;
keep-power-in-suspend;
//use_intf3_tuning;
resets = <&reset RESET_SD_EMMC_A>;
};
I checkout the /sys/kernel/debug/pinctrl/fe000000.apb4:pinctrl@4000-pinctrl-meson/pinmux-pins, it looks like
pin 48 (GPIOX_0): device fe088000.sdio function sdio group sdio_d0
pin 49 (GPIOX_1): device fe088000.sdio function sdio group sdio_d1
pin 50 (GPIOX_2): device fe088000.sdio function sdio group sdio_d2
pin 51 (GPIOX_3): device fe088000.sdio function sdio group sdio_d3
pin 52 (GPIOX_4): device fe088000.sdio function sdio group sdio_clk
pin 53 (GPIOX_5): device fe088000.sdio function sdio group sdio_cmd
pin 54 (GPIOX_6): GPIO periphs-banks:484
pin 55 (GPIOX_7): UNCLAIMED
pin 56 (GPIOX_8): UNCLAIMED
pin 57 (GPIOX_9): UNCLAIMED
pin 58 (GPIOX_10): UNCLAIMED
pin 59 (GPIOX_11): UNCLAIMED
But the android counterpart has GIPOX_7 definition.
pin 48 (GPIOX_0): device fe088000.sdio function sdio group sdio_d0
pin 49 (GPIOX_1): device fe088000.sdio function sdio group sdio_d1
pin 50 (GPIOX_2): device fe088000.sdio function sdio group sdio_d2
pin 51 (GPIOX_3): device fe088000.sdio function sdio group sdio_d3
pin 52 (GPIOX_4): device fe088000.sdio function sdio group sdio_clk
pin 53 (GPIOX_5): device fe088000.sdio function sdio group sdio_cmd
pin 54 (GPIOX_6): GPIO periphs-banks:484
pin 55 (GPIOX_7): GPIO periphs-banks:485
What did I miss in dts file for GPIOX_7 to be claimed in CoreElec?
CoreELEC 21.0-Omega_alpha3 on Tvbox Tanix x4 s905x4.
Immediately after entering the WiFi password, the following
message is displayed: Error. Operation timeout.
After selecting the Access point checkbox, the interface is
automatically refreshed and the field is automatically deleted.
CoreELEC:~ # dmesg | paste
http://ix.io/4HVr
It’s been a month since this publication has not received a response. I would like you to tell me, if possible, if the fact that the wifi does not work is due to the unavailability of the driver or any other reason. I find it strange that bluetooth works and not wifi. I appreciate your effort and dedication, thank you for everything.
I did check now your messages and I found minimum 3 different Wifi chips in your log.
Do you use multiple different devices?
One time the pid 8888, one time the 4339 and one time the 4330 . No idea what you are doing.
Please make a new log and tell us exactly what log to wich device is related to:
udevadm info /sys/bus/sdio/devices/* | paste
Also a Android dmesg log would be helpful to easy define the used WiFi driver.
Thanks for responding. I have made several comments about different machines, but currently I refer to a very specific one:
CoreELEC:~ # udevadm info /sys/bus/sdio/devices/* | paste
http://ix.io/4HYE
CoreELEC:~ # dmesg | paste
http://ix.io/4HYG
dtb.img.gz (51.6 KB)
Then you can’t expect a answer at all. Our glass bowl will not show us you r currently used device with what Wifi chip is assembled.
Also you need to tell us what nightly you use: CE-20.3 or CE-21?
T95w2 (Amlogic s905w2)
[CoreELEC-Amlogic-ne.aarch64-20.3-Nexus_nightly_20230927
Please update with this file: 230.66 MB file on MEGA
After update make a new log dmesg | paste and check if wifi is now working.
Tanix X4 running:
CoreELEC (official): 20.3-Nexus_nightly_20230927 (Amlogic-ne.aarch64)
Machine model: Amlogic
CoreELEC dt-id: sc2_s905x4_4g
Looking to see if you guys can help me get my Asus USB-BT500 Bluetooth dongle working please.
CoreELEC:~ # lsusb | paste
CoreELEC:~ # dmesg | paste
Thx. Not work:
CoreELEC (community): 20.3-Nexus_devel_20231002145450 (Amlogic-ne.aarch64)
Machine model: Amlogic
CoreELEC dt-id: s4_s905w2_2g
CoreELEC:~ # dmesg | paste
http://ix.io/4HZb
Then you need to provide Android dmesg log.
please try again with this image: