martinayotte

BSD is not using DeviceTree DT, it is using FEX/BIN. So, you will need to use bin2fex to decompile script.bin (after having done a backup first), edit the the resulting script.fex to enable I2C buses, and recompile using the fex2bin into script.bin. But be aware that people on Armbian forum isn't inclined to give much support of builds that are not from Armbian, we consider BSD as crappy builds !

Apologize for some previous noise ... Ok ! I did the right build, now the u-boot is Ok, but it missing the sun50i-h5-nanopim1plus2.dtb. This means the WIP target is incomplete ! I will have to finish it, probably like I did for other H5 recently. But this means that my whole goal of trying to see if AP6212 is working on this board can't help, because I will probably end up with same things as other H5.

Ohhh ! Confusing ... Also, checking the silkscreen on the board, I see it has small checkboxes with 1 and 2, but none of them are mark. So same PCB for both like ZeroPlus ... I'm redoing the new right build

Yes ! I've got the idea while you were answering : why not trying to boot an OPiZeroPlus-H5 on this board ? Success ! ... This means the Armbian_5.27_Nanopim1plus_Debian_jessie_dev_4.10.11.img is complete crap ! We will have to check this target completely ... EDIT : I will redo a build and inspect all the steps of u-boot compile (since I didn't keep the log, and have built some other H5) ...

Exactly, nothing shows in picocom.

If it is Mainline, it will be appreciated, thanks. If not, it is useless.

Yes ! Binary file /dev/fd/63 matches

Are you using Armbian Mainline build or a crappy BSD from manufacturer ?

To help diagnose the issues I'm facing with AP6212 with other boards, I've decide to build an image for the newly received NanoPiM1Plus. It produced the following image : Armbian_5.27_Nanopim1plus_Debian_jessie_dev_4.10.11.img I've plugged an USB-TTL on the board, it booted until the login prompt. Trying the usual root/1234 failed, looking at FriendlyArm site, although I'm not using their image, but an Armbian freshly built, I've try their passwd : root/fa It logged ... looking for AP6212 traces, I've seen some "bcmsdh_sdmmc_probe" ... Doohh ? I did "uname -a" : again, Doohh ? : Linux FriendlyARM 3.10.65 #4 SMP PREEMPT Fri Mar 24 11:33:57 CST 2017 Coming to the conclusion : it booted from the eMMC, ignoring the SDCard present in the crappy socket !!! Looking at /dev/mmc*, the SDCard is under mmcblk1, mount it, trying to change boot.cmd for proper mmc, "mkimage" is not present in their crappy BSD. Doing it from my PC ... insert sdcard again, no u-boot at all (the first try above was probably false contact ignoring sd), no way to boot from sd, remove sd card and booting again the BSD. Conclusion : I start hating this board ! I don't want to spend hours without having an Armbian...

@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 ...

By default, I2C buses are not enabled in the main DT, except for the s_i2c . To enable other i2C buses, you need to add overlays in the /boot/armbianEnv.txt overlays=i2c0 i2c1 i2c2 Then, reboot. After you will have 4 buses in /dev/i2c-*. You can then scan the buses with "i2cdetect -y n", where "n" is the bus number.

@tkaiser, unfortunately, on both my OPiZeroPlus-H5 and OPiPrime, your brute-force approach didn't work. As I said in some development thread, it doesn't even reach the point where the firmware is loaded, even brcmfmac isn't probed during DT parsing. And the mmc-sdio, although loaded on OPiPrime, it isn't even loaded on OPiZeroPlus and OPiWin. So, that's why I've said "AP6212 WiFi still not working on any Mainline (OPiZeroPlus*/OPiPrime/OPiWin), we still investigate" ... EDIT: BTW, since I don't own a NanoPiNeoAir, could you share you booting log so I can compare the sequence with my OPis ?

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

AP6212 WiFi still not working on any Mainline (OPiZeroPlus*/OPiPrime/OPiWin), we still investigate ... The only one working is Legacy OPiZeroPlus-H3.

Did you tried installing those : apt-get install libwxbase3.0-0 libwxgtk3.0-0 libwxgtk-media3.0-0 libwxgtk-webview3.0-0

You mean "And now it's working" ...

@tkaiser This AR100 code seem to perform a hard reset on SoC, I don't think real shutdown can be accomplish with it, especially that there is no PMIC. The best I can see is that it could control a additional GPIO pin where users could attach some kind SSR to control the power line.

You're right, there are 2 versions of this python library, one for PC and one for Zero, where only the mapping.h file should differ.

Why are you trying to use swig on wiringpi ? If you wish to use python instead of C library, there is an python library : https://github.com/duxingkei33/orangepi_PC_gpio_pyH3

I presume you're right ! But I never used acpid before, so I'm learning at the same time as you, although I probably won't use it as I mentioned yesterday "OPiOne doesn't have any PMIC, it won't shutdown the power". I will still look at it when I get change, simply to get the knowledge.

Just checking an Legacy sitting in my image folder (because I'm usually using only Mainline), I could see that the driver is already present in my Armbian_5.24_Orangepizero_Debian_jessie_3.4.113.img. So, it should be in OPiPC image too ... Take a look in path such the following for both driver and firmware : /lib/modules/3.4.113-sun8i/kernel/drivers/net/wireless/rtl8188eu/8188eu.ko /mnt/lib/firmware/rtlwifi/rtl8188eufw.bin

Yes, I've forgotten that one, although I've used it a year ago for the Plus2E ... I'm was than able to access mmc2 with "ls mmc 1". But unfortunately I was still not able to boot, simply because I forgot that both SPL and U-Boot needed that, not only u-Boot. I'm currently redoing new build... EDIT : new build tested successfully ...

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.

So, the log above shows that it is connecting to it...

I don't see any errors in the above, although I'm not familiar with what OctoPrint is used to provide as output. Is the IP address 192.168.0.104 is your printer ?