martinayotte

@kutysam, I don't think that patch is the only requirement, since I've tried it several weeks ago, but driver was still failing.
 

We should probably add that patch to Armbian until Mainline is merging it ...
 

I've got the RTL8723bs working using a temporary build of 4.12 ...
 
 

I've got the RTL8723bs working using a temporary build of 4.12 ...
 
 

Like many other boards, even if you have many /dev/ttyS*, it doesn't mean the actual UARTs are enabled in the DeviceTree.
You should probably look in the DTS (or decompile DTB into DTS) to figured out.
When a UART is detected at boot time, you will see it in "dmesg" which will show on which /dev/tttyS* it will be attached.
BTW, if not enabled, UARTs can also be enabled using overlays ...

Yes, Zador is right ! We shouldn't "trash" the WIPs, but simply hide them and make them visible with EXPERT=yes.
Otherwise, it will be a pain even for experts ...
 

We may still want those to be accessible for internal testing purposes, so hiding "Show WIP" button (unless, for example, EXPERT=yes hidden option is supplied) may be a better solution

Ok ! AP6212 is now working on OPiWin :
- Replaced reg_eldo1 by reg_dldo2.
- Adding RSB/AXP settings in defconfig.
Commit is done, next nigthly build will provide those changes.
 

Ok ! AP6212 is now working on OPiWin :
- Replaced reg_eldo1 by reg_dldo2.
- Adding RSB/AXP settings in defconfig.
Commit is done, next nigthly build will provide those changes.
 

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.

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.

I've mesured on C13, VCC-CPUX is at 1.127V

I've installed Ayufan build xenial-mate-pinebook-bspkernel-0.4.2-47.img.xz and it effectively seems to be fixed.
I've closed/flipped the screen and left it in suspend mode, and I opened back 4 hours later, battery was still around same 94% level seen previously.
 
EDIT : about 8 hours later, my pinebook is around 81% charged/unplugged, it was probably around 92% when I resumed halt an hour ago.
 
BTW, one thing I start hating : the trackpad is too much sensitive : I try to avoid touching it, and I'm still using external mouse, because I hate those pads anyway, but even not using this pad, while typing on keyboard, if my fingers are too near of the pad, it product a mouse-click event and I'm doing bad typos ...

The OPiZero DT in 4.11 wasn't enabled and didn't have PHY assigned. I added a patch in Armbian builds.
Either you wait for next nightly build, or add this patch and build it yourself :

Now that I've done builds for NanoPiM1Plus2 and BananaPiM2Plus, along with the previous series OPiZeroPlus-H3/OPiZeroPlus-H5/OPiWin/OPiPrime, and that all of those boards has the same symptoms of missing AP6212 (+/- some have mmc-sdio appear, some not), I've continue my search for hints.
To my discovery, I found the following quote in http://linux-sunxi.org/Sinovoip_Banana_Pi_M2%2B
I hope that is not true any more ...

@tkaiser, yes, I've already took a look at this link, since you provided it in another thread.
Unfortunately, I couldn't find any discrepancy with my latest commits.
Since I've received a NanoPi M1 Plus this week, I will check with our Armbian build if the AP6212 is working there.
If not, I will grab their branch to figure out ...
 

systemctl disable bluetooth ... or whatever the service is named ...
And then reboot, or do "systemctl stop bluetooth".

acpid need to be configured to take action, such triggering external scripts for shutdown.
In the meantime, try it with "evtest /dev/input/event0", I've done that and events are coming from PL3 where the button is connected.
 
EDIT : Be aware that you will only be able to shutdown the kernel, but since the OPiOne doesn't have any PMIC, it won't shutdown the power.

If it is like other OpenWrt, there should be accessible using sysfs, ie : /sys/class/gpio, doing such commands :
echo 20 > /sys/class/gpio/export echo out > /sys/class/gpio20/direction echo 1 > /sys/class/gpio20/value  

To isolate the issue, maybe you should try to do a simple loopback test first, a jumper between 8 and 10, and use minicom or picocom to get local echo.
 
BTW, in the case of Mainline, without having other uart enabled other than debug uart0, when I load overlay for uart2, it comes up as /dev/ttyS1, since debug is on /dev/ttyS0.
 

No !
Edit /etc/rc.local and add "/home/YOUR_USERNAME_HERE/OctoPrint/venv/bin/octoprint &" before the "exit 0"
 

Not having a USB-TTL to do debugging is like a carpenter not having any hammer ...

Booting from SPI-NOR doesn't need other things than the u-boot-sunxi-with-spl.bin in the flash, which a bit less than 500K.
The kernel itself along uinitrd and dtb should be located elsewhere.
I've never try to boot in NFS or TFTP yet, but booting from USB drive just works fine.
(BTW, pushing u-boot-sunxi-with-spl.bin into flash isn't done by nand-sata-install, nand-sata-install is used to copy sdcard into other storage such USB drive or eMMC)

For flashing the SPI-NOR, you need to get "mtd-utils", either from apt-get or from sources.
You need to add in the /boot/armbianEnv.txt the following overlay :
overlays=spi-jedec-nor Then, reboot, and check if SPI-NOR appears by doing "cat /proc/mtd". If you have mtd partitions, then install u-boot-spl using this command (check previous partitions to make sure u-boot is mtd0) :
flashcp /usr/lib/linux-u-boot-dev-orangepipc_5.27_armhf/u-boot-sunxi-with-spl.bin /dev/mtd0 Next steps are for copying your sdcard into you already inserted usb drive by using nand-sata-install. After copy finished, edit the boot.cmd from your usb drive, this means probably /mnt/boot/boot.cmd if drive mounted in /mnt.
Change all "mmc" words by "usb" and add on top of boot.cmd the line "setenv devtype usb", save it and recompile it with "mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr".
Then, shutdown the board, remove the sdcard, and re-power the board. Check the boot log using USB-TTL adaptor. If everything fine, you should get into the login prompt. Bingo !
 
 

The fact that you are seeing spidev in lsmod doesn't mean nothing wrong occured.
Check the kernel logs with "dmesg | grep spidev"