Jump to content

martinayotte

Members
  • Posts

    3892
  • Joined

  • Last visited

Posts posted by martinayotte

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

     

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

     

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

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

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

     

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

     

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

     

  8. Some of you probably saw that I added recently the OrangePi-Prime to the build process.

    Unfortunately, I'm still struggling to get the WiFi.

    It is even worst than the WiFi issue still present on OrangePiWin.

    For the OrangePi-Prime, even the DT doesn't process the WiFi entries, and the mmc1 is still "disabled" in /proc/device-tree at boot time.

    The strange thing is that if I load a small overlay to change the mmc1 status to "okay", the kernel start processing it.

    But, unfortunately, I'm seeing "sunxi-mmc 1c10000.mmc: no support for card's volts" error, although I didn't found obvious errors in vqmmc-supply setting of mmc1.

    I will have to dig further, but start running out of ideas ...

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines