-
Posts
3892 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by martinayotte
-
-
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
-
Quote
And not it's working
You mean "And now it's working" ...
-
-
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 ?
-
your screenshot seems to show that your have DNS issue with host bpi-iot-ros-ai, but I don't understand the relationship with "sudo".
About the "dd" command, it worked succesffully since it displayed at the end "2807037952 bytes copied" ...
-
BTW, this is not a page from Armbian web site ...
-
Without any SD inserted :
U-Boot SPL 2017.01-rc1-g5df570f-dirty (Apr 25 2017 - 10:01:27) DRAM: 512 MiB Failed to set core voltage! Can't set CPU frequency Trying to boot from MMC2MMC Device 1 not found spl: could not find mmc device. error: -19 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ###
And booting from SD, but stopping before kernel to get into U-Boot shell, "mmcinfo" just shows the MMC0, no MMC2 detected.
It probably require an additionnal patch for SPL itself.
-
I've added new patches for OrangePi-ZeroPlus and commited them.
Like for OPiPrime done yesterday, the OrangePi-ZeroPlus WiFi still not working.
I don't know why yet, although is more encouraging than OPiPrime, since at least the driver comes up in "lsmod" in the OrangePi-ZeroPlus, while for the Prime it didn't.
Also another issue : OrangePi-ZeroPlus has an eMMC, I was able to do "nand-install-sata", but I'm unable to boot from it, although the MMC2 DT is part of U-Boot, for some reasons, it doesn't scan it.
-
You ran "/home/YOUR_USERNAME_HERE/OctoPrint/venv/bin/octoprint" manually and you got some errors ?
I'm not familiar with OctoPrint, but maybe you can tell here what was the error ...
-
I don't know if "/home/YOUR_USERNAME_HERE/OctoPrint/venv/bin/octoprint &" for some other reasons, but the /etc/rc.local is for sure working.
Just to prove that, you can do "date > /tmp/lastboot.log &", and you will see that this is actually executed.
So, check your OctoPrint installation, maybe something wrong there ....
Strange build behavior for NanoPi M1 Plus
in Advanced users - Development
Posted
Yes !
Binary file /dev/fd/63 matches