asxalex

Aha, it turns out to be my hardware failure: I connected a triode and an LED on the wl_reg_on, trying to use which to indicate the wl_reg_on is on. But at the same time, the triode and LED makes the wl_reg_on is always low. I solder them off, and ap6212 works fine now. By the way, my sdio wifi is still recognized as mmc2. I bought a orangepi zero plus 2 a few days ago, and it recognized sdio wifi as mmc2 too. Much sorry for my hardware mistake and much thanks for your patience and help!

I changed the wifi_pwrseq outside, and the "dmesg | grep mmc" changed a bit: [ 0.000000] Kernel command line: root=UUID=aee206b3-d10b-44e7-af35-710d9422045d rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=1 ubootpart=e3d022de-01 ubootsource=mmc usb-storage.quirks= sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1 [ 2.766391] sunxi-mmc 1c0f000.mmc: Linked as a consumer to regulator.2 [ 2.767303] sunxi-mmc 1c0f000.mmc: G

That‘s what i wrote about MMCs in the dts file under arch/arm/boot/dts: #include "sun8i-h3-orangepi-pc.dts" / { model = "Xunlong Orange Pi PC Plus"; compatible = "xunlong,orangepi-pc-plus", "allwinner,sun8i-h3"; aliases { /* ethernet0 is the H3 emac, defined in sun8i-h3.dtsi */ }; }; &emac { /* LEDs changed to active high on the plus */ /delete-property/ allwinner,leds-active-low; }; &mmc1 { vmmc-supply = <&reg_vcc3v3>; vqmmc-supply = <&reg_vcc3v3>; mmc-pwrseq = <&wifi_pwrseq>; bus-width = <4>; non-removable; status

But, I did wire eMMC on MMC2 and ap6212a on MMC1, as the schematic shown below, and the eMMC works fine right now, but the ap6212a is not detected by armbian. 1.png 2.png

yes, i wired WL_REG_ON of ap6212a chip to PL7 of H3. I got the following content while running "dmesg | grep -i mmc" [ 0.000000] Kernel command line: root=UUID=f63dff6a-7de3-4946-b0b0-45be11430249 rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=1 ubootpart=7502a43b-01 ubootsource=mmc usb-storage.quirks= sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1 [ 2.766162] sunxi-mmc 1c0f000.mmc: Linked as a consumer to regul

Hi all! I make a board base on H3 CPU, I got a 8G EMMC under mmc2, and a ap6212a chip under mmc1. It boots successfully with the "armbian orange-pi-pc-plus", the emmc works fine while the wifi does not work, so, i changed the dts's mmc1 section based on the file 'sun8i-h3-orangepi-pc-plus.dts' in 'arch/arm/boot/dts/' directory, the mmc1 is changed to as follows: &mmc1 { vmmc-supply = <&reg_vcc3v3>; vqmmc-supply = <&reg_vcc3v3>; mmc-pwrseq = <&wifi_pwrseq>; bus-width = <4>; non-removable; status = "okay"; /* * Expli

As mentioned above, how can is specify the version of kernel and u-boot when i build the image(in https://github.com/armbian/build) from scratch? Thanks in advance!