martinayotte

Developers
  • Content count

    1382
  • Joined

  • Last visited

About martinayotte

  • Rank
    Embedded member

Recent Profile Visitors

2176 profile views
  1. martinayotte

    Pine64 PPS working?

    First, let's say that overlay directory is only on Mainline kernel, it doesn't exist on Legacy kernel. Secondly, PPS is simply using a GPIO pin, it could be almost any one, as long as it is available on some header. The current overlay is defaulting to PD4 of the Euler Bus. Doing "dtc -I dtb -O dts /boot/dtb/allwinner/overlay/sun50i-a64-pps-gpio.dtbo" will display it in plain text...
  2. martinayotte

    Orange Pi Plus 2e -- pretty much useless

    https://github.com/duxingkei33/orangepi_PC_gpio_pyH3
  3. martinayotte

    Orange Pi Plus 2e -- pretty much useless

    This is true for most of the SBC with Mainline since it still under development by BootLin people ... ( some reading here : https://bootlin.com/ )
  4. martinayotte

    OPI Zero, UART2 RTS CTS don't work

    Since the Armbian doesn't have a recent "next" build in https://dl.armbian.com/orangepizero/ , you will need to build your own image using procedures explained here : https://docs.armbian.com/Developer-Guide_Build-Preparation/
  5. martinayotte

    OPI Zero, UART2 RTS CTS don't work

    I've done this fix to patches : https://github.com/armbian/build/commit/e0382d1ad2e5ac2c8d4dda814949f989812be18c#diff-33d9868ed154988dc938219a3df6f54d But I've not got chance to test it. BTW, this is for the "sunxi-next" builds ... (I will do the same for "sunxi-dev" today)
  6. martinayotte

    Pine64 no network

    Your first screenshot shows "fs_devread read error" followed by "File not found" ... This means that your image on SDCard was badly written ! Make sure you use Etcher to write images and don't use crappy sdcards ...
  7. martinayotte

    armbian for orange pi one

    Take a USB-Storage dongle, plug it on RaspberryPi USB, mount it, there will be plenty of storage space ...
  8. There are many ways to use GPIO. You can use classic sysfs, ie : /sys/class/gpio You can also take the python Pine64 library : https://github.com/swkim01/RPi.GPIO-PineA64 You can even use that one since it has been ported for H5 with proper 64bits pointers : https://github.com/herzig/orangepi_PC_gpio_pyH5 EDIT : There is also this one coming from A64-OlinuXino : https://files.pythonhosted.org/packages/29/a8/e9ce35c362e6340713bbbffcf260c4ffca87b404d9811e5d400f33e6c5c8/pyA64-0.1.0.tar.gz
  9. Personnally, I don't know which ones since I've never use such configuration. But you can leave the internal XR819 as AP while adding an USB WiFi dongle for the STA, you will then get both wlan0 and wlan1.
  10. XR819 is the WiFi chip used on OPiZeroH2+. Most Armbian hate that chip since it provide poor performance, and driver is a bit crappy. STA means STATION and AP means AccessPoint. So, if you wish to have both at the same time, I doubt the driver and/or chip support both mode at the same time ... What you can do is attach a second WiFi thru USB.
  11. I doubt any version of XR819 allows STA+AP at the same time ...
  12. martinayotte

    Protect OrangePi from gpio file injection

    You should detailed what is that famous board and how it is connected to OPi headers. If you have it connected only on dual-header, there is no USB there, so no injection possible on those pins ...
  13. martinayotte

    Protect OrangePi from gpio file injection

    As I said "How a GPIO connection could interact with a Linux filesystem ?" ... Impossible ! Believe me, your issue must be somewhere else : bad PSU or bad SDCard !
  14. martinayotte

    Protect OrangePi from gpio file injection

    Euuh ??? How a GPIO connection could interact with a Linux filesystem ? Maybe you should explain in more details your observations ...
  15. The "bs=" means "block size", it has nothing to do with "sector size" of a file system. It is only the size of the buffer used between reading the source and writing destination. Of course, a bs=4M will do the transfers faster than a bs=4096, which is not the same since the later means 4096 bytes.