martinayotte

Members
  • Content Count

    3177
  • Joined

  • Last visited

About martinayotte

  • Rank
    Embedded member

Recent Profile Visitors

5008 profile views
  1. Simply reboot with SDCard and re-run nand-sata-install again ...
  2. Since V3s and H3 have both their pins controller at the same address, ie pinctrl@1c20800, any library for H3 should be able to handle it. Personally, I'm using this python library https://github.com/duxingkei33/orangepi_PC_gpio_pyH3 which using C code under the hood, see here : https://github.com/duxingkei33/orangepi_PC_gpio_pyH3/blob/master/pyA20/gpio/gpio_lib.c So, you can do quite the same to initialize /dev/mem and setting up the directions and values...
  3. Sure ! But I doubt the power saving will be big, perhaps few mA ...
  4. You have to remember that all Rockchip SoC give priority boot order to eMMC against SDCard. I don't own a Firefly, so I don't know if there switch or jumper or test points to disable eMMC to allow SDCard been booted. Once you will be able to boot SDCard, installing Armbian on the eMMC will give you a interruptible U-Boot where you can hit <spacebar> to get promt and choose boot device using "setenv devnum <X>", either eMMC or SDCard, followed by "run mmc_boot".
  5. Picture is not good enough, but it looks like an RTL8723 module ...
  6. martinayotte

    M4 V2

    You probably need to decompile M4v2 DT, and after having commented the "mmc-hs400-1_8v;" and "mmc-hs400-enhanced-strobe;" and recompiled DTB,
  7. You not only need to add overlays to /boot/armbianEnv.txt, but also parameters, check /boot/dtb/rockchip/overlay/README.rockchip-overlays : ### spi-spidev Activates SPIdev device node (/dev/spidevX.Y) for userspace SPI access, where X is the bus number and Y is the CS number SPI 0 pins (MOSI, MISO, SCK, CS): GPIO3_A5, GPIO3_A4, GPIO3_A6, GPIO3_A7 SPI 1 pins (MOSI, MISO, SCK, CS): GPIO1_A7, GPIO1_B0, GPIO1_B1, GPIO1_B2 SPI 2 pins (MOSI, MISO, SCK, CS): GPIO1_C0, GPIO1_B7, GPIO1_C1, GPIO1_C2 SPI 3 pins (MOSI, MISO, SCK, CS): GPIO2_B2, GPIO2_B1, GPIO2_B3, GPIO2_B4 Parameters: param_spidev_spi_bus (int) SPI bus to activate SPIdev support on Required Supported values: 0, 1 param_spidev_spi_cs (int) SPI chip select number Optional Default: 0 Supported values: 0, 1 Using chip select 1 requires using "spi-add-cs1" overlay param_spidev_max_freq (int) Maximum SPIdev frequency Optional Default: 1000000 Range: 3000 - 100000000
  8. martinayotte

    M4 V2

    This is because you have an old version of picocom, you can build more recent one using https://github.com/npat-efault/picocom
  9. martinayotte

    M4 V2

    Press several times <spacebar> until u-boot stop and provide a command prompt.
  10. Change /boot/armbienEnv.txt to have both "verbosity=7" and "console=serial", you will get more details ...
  11. Hi Michael, Here some hints about what I'm doing in my own custom builds : There is a script in userpatches/customize-image.sh, I've added the following code into Main() function, for specific distro, in my case "stretch" : stretch) eval 'LC_ALL=en_US.UTF-8 LANG=en_US.UTF-8 chroot $CACHEDIR/$SDCARD /bin/bash -c "DEBIAN_FRONTEND=noninteractive apt-get -y -q \ --no-install-recommends install joe ntpdate p7zip-full mtd-utils cifs-utils pigz dcfldd nmap zip python-serial python-setuptools python-httplib2 python-openssl strace libtool pkg-config autoconf-archive bison flex avrdude dfu-util pcscd python-pyscard"' \ ${PROGRESS_LOG_TO_FILE:+' | tee -a $DEST/debug/debootstrap.log'} \ ${OUTPUT_DIALOG:+' | dialog --backtitle "$backtitle" --progressbox "Installing Armbian system..." $TTY_Y $TTY_X'} \ ${OUTPUT_VERYSILENT:+' >/dev/null 2>/dev/null'} # your code here Although I've never done it, it could probably done in the same userpatches/customize-image.sh, doing to changes or copies assuming the path "$CACHEDIR/$SDCARD" ...
  12. I don't see relationship between USB and HDMI ...
  13. I've sorted out patches that were preventing builds, but there still some patches where chunks failed without disturbing builds, let says, for OPi3/OPiLite2/OPiOnePlus/PineH64 as well as H3/H5 ones . Yes, maybe end of the month is a good target ...
  14. It is planned, I'm already using it for my local builds ...