martinayotte

Oh !!! Thanks ! That's mean the schematic is wrong since it is stating PL7/PL8 ! I will try PL2/PL3 tomorrow, since it already late tonight here ... The commit in Ambian is done thru a patch which create the DTS. https://github.com/armbian/build/blob/master/patch/kernel/sun50i-dev/add_orangepiwin_dts.patch EDIT : BTW, the DTS changes for WiFi are not committed yet ... Maybe tomorrow if PL2/PL3 works.

I've done that for ZeroPlus-H3/ZeroPlus-H5/NanoPiM1Plus2-H5 Mainline with success ! But still no success with OPiWin on Mainline ... Maybe I've done a mistake somewhere or there is a mistake on schematic ... Could you confirmed me what pins are used on Legacy FEX for WL-PWREN and WL-WAKE ?

Normally, there is a NTP service running on all Armbian. Check if it is running by doing "ps -ef | grep ntp", you should have something like : ntp 720 1 0 May04 ? 00:01:28 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 105:110 if not, try to run it manually to see if any errors ...

Armbian just switched from 4.10 to 4.11 recently, and the built-in 8189fs WiFi of OrangePiPC+ still working fine with nightly builds.

I've only looked at the Ultra schematic, and I didn't find any GPIO attached to it, it seems to be connected to AP-NMI, so I don't know how to specify that in DTS.

BTW, if you wish to share actual/current desktop, vino-server would do the job.

BTW, I've committed a preliminary AP6212 integration for BPiM2+Ultra DTS. But, to my surprise, BPiM2+Ultra WL-WAKEUP is not attached to some GPIO of the R40, so I've left it commented in the DTS. This is may one of the reason with I wasn't able to make it work : the wlan0 appears but doesn't receive it DHCP response. Or this is related to the fact that it is not a "A" version, since I'm now getting the same issue with plain BPiM2+, although it worked last week.

That trick did fix the issue ... Thanks a lot !

Igor, I know that are there in github, it is where I've download them, but there are not in the built image since it seems to install them, from my understanding, from the armbian-firmware-full_5.27_armhf.deb which still older than the commit date.

Good ! But I still don't see the fw_bcm43438a1.bin in neither output/debs/armbian-firmware-full_5.27_arm64.deb or output/debs/armbian-firmware-full_5.27_armhf.deb. So, I still have to manually install it from manual download...

I've tried today this driver from https://github.com/jwrdegoede/rtl8723bs Unfortunately, I didn't get it to work, even after having fixed some of those pacthes_v5, it crash while loading driver.

Ok ! I've finally found some discripancies in DT between H3 and H5 : the reset-gpios default level in wifi-pwrseq of DT. Thoses fixes the OPiZeroPlus2-H5 as well as NanoPiM1Plus2-H5. Next nigthlies should reflect that. (Be aware for those two boards : MicroUSB powering is choking when WiFi get powered. I need some new stronger cables) A side note : OPiWin still not work with the same medecine, as well as the BanadaPi-M2-Ultra ... I will dig further ... EDIT : For those who trying fresh builds, you sill need @tkaiser firmware hack, which is not part of the images yet : download /lib/firmware/ap6212/fw_bcm43438a1.bin and copy it under /lib/firmware/brcm/brcmfmac43430-sdio.bin.

As the Linux-sunxi page you've mentioned : So, in your example, the pin is PA17. If we take another pin, lets say PC12 : it would be 76. If we take another pin, lets say PD5 : it would be 101.

Don't expect HDMI or Analog Video to work yet ... Too early in Mainline development ! Do you have an Debug Serial USB-TTL attached ? It should reach login prompt. For networking, only the Wired is working, no WiFi yet ...

Glad to ear that ! We are hoping to see how those of your boards looks like ...

You don't need any other pins, OneWire is supporting multi-sensors on the same bus, simply put them in parallel.

What do you means ? If your OPi2E doesn't execute any audio software, no body will spy you ... If you're scared, you can also remove it from PCB ...

Do you have the folder /var/log/mysql/ ? If not, create it, and restart mysqld service.

BTW, during migration from 4.10 to 4.11, there were lot of missings for ZeroPlus2-H3, including the eMMC and USB missings ... I've updated the patches and now DT looks better.

Since it is a piezo speaker, not an 8ohms speaker, that should be fine. But in case of 8ohms speaker, you would need an amplifier.

It is me that did the integraton of the new ZeroPlus-H3 DT two weeks ago, but I don' t see why I missed in your comment. (I will check again tomorrow since it it late tonight ...) Did you tried Mainline ? Because in Legacy doesn' t look at DT at all, it is using hte old FEX with script.bin. I didn' t managed any FEX changes since I hate Legacy ... I' m strickly work with Mainline.

Effectively, the WiFi XR819 driver is defective under 4.11, so we leave it disabled for now ...

On Linux, it is probably connected to /dev/ttySx, where x can be from 1 to 7.

@monomial First, it would be nice if you mentioned which kernel are you using, Legacy or Mainline. On my side, I took the effort to bring this board to Mainline more than a week ago, and nand-sata-install worked fine since the beginning. The things that still doesn't work is the AP6212 WiFi. For Bluetooth, I've not even looked at it, since I never use it.

The USB is working on OPiPrime, I'm able to plug an USB SDCard Reader, an USB-SATA Adaptor or even an AVRASP. But maybe for USB Keyboard, it requires some specific drivers which are not part of the build yet.