• Content Count

  • Joined

  • Last visited

Reputation Activity

  1. Like
    pfeerick reacted to James Kingdon in Quick Pinebook Preview / Review   
    The fix for the 64G eMMC module looks promising - the module is now recognized when I boot armbian from sd card using the modified kernel. It's currently formatting the eMMC as the first stage of nand-sata-install...
    The fix is trivial. In drivers/mmc/core/mmc.c, remove or comment out the conditional block at line 317
    card->ext_csd.rev = ext_csd[EXT_CSD_REV];     /**     if (card->ext_csd.rev > 7) {         pr_err("%s: unrecognised EXT_CSD revision %d\n",             mmc_hostname(card->host), card->ext_csd.rev);         err = -EINVAL;         goto out;     }     */ This test has been removed from later releases of the driver and a comment added to indicate that the cards should be backwards compatible so the test is unnecessary.
  2. Like
    pfeerick reacted to linda in pine64-mainline- won't boot after upgrade   
    Thanks a lot for your answers and especially for the suggestion to change the boot.cmd.
    As proposed, I changed two lines concerning the fdtname in the the boot.cmd:
        "load ${devtype} 0 ${fdt_addr_r} ${prefix}dtb/${fdtfile}"
    but leave these line concerning the overlay-setting unchanged
         "if load ${devtype} 0 ${load_addr} ${prefix}dtb/allwinner/overlay/${overlay_prefix}-${overlay_file}.dtbo; then"
         "if load ${devtype} 0 ${load_addr} ${prefix}dtb/allwinner/overlay/${overlay_prefix}-fixup.scr; then"
    and recompile boot.cmd.
    This works for me, also with the allwinner overlay dtbo-file.
  3. Like
    pfeerick reacted to martinayotte in [559] - GPIO Support for H2/H3 boards with a unified WiringPI library in a neat little package   
    Right ! This is true for all 64bits SoC, I've narrowed that on PineA64 too...
    There is not so much "unsigned int" to "unsigned long" conversion required, if I remember : 2 in the gpio_lib.h and 2 in gpio_lib.c.
  4. Like
    pfeerick reacted to Igor in Pine64 SATA disk   
    Via USB, no other way. Any size.
  5. Like
    pfeerick reacted to Igor in More proper testing - better Armbian experience   
    Repository has been populated with the latest full package base. It's a test build of recent build script rework and some more testing and checking would be helpful.
    What is new?
    - kernel sources with our patches and config (please try some onboard kernel compilation testings) Install example:
    apt-get install linux-source-4.12.4-sunxi  - stretch packages
  6. Like
    pfeerick reacted to martinayotte in Using wiringPi & digitalRead yields varying states with a dangling dupont wire   
    Did you use either internal PullUp or external PullUp to 3.3V ?
    If not, the wire is acting as an antenna with random states.
  7. Like
    pfeerick reacted to Igor in Forum upgrade   
  8. Like
    pfeerick reacted to StuxNet in Forgotten password   
    Replace friend with customer and you've lived my life. Good to know you figured it out. Take care.
  9. Like
    pfeerick reacted to martinayotte in New OPi Zero - Yet another high temperature issue...   
    There is no real PMIC on OPiZero, this means the power supply still plugged on the SoC, even after shutdown command.
  10. Like
    pfeerick reacted to thedon in Tiny 3$ lcd on orange pi   
    I get what you are saying but I will wait for the post author to respond since the lcd module he has shown in the first video is same as what I have except that it has a ili9341 chipset; the pins are exactly same and then someone has asked about ili9341 and he gave some specific wiring changes so I have mentioned the board and the pins it has so that there is no confusion;
  11. Haha
    pfeerick reacted to Igor in Forum upgrade   
    It should be fixed now. I hope.
  12. Like
    pfeerick reacted to martin-by in Cubietruck on Ubuntu 16.04 Kernel 4.11.6-sunxi: suddenly no sound   
    Found the workaround: suni4-codec & sun4-sndspdif were not be loaded anymore (why? I do not know). The test with modprobe was positive
    Adding both modules into /etc/modules file and rebooting the system get all function again.
    Best regards from Bavaria,
  13. Like
    pfeerick reacted to zador.blood.stained in Armbian 5.30 on Pine64 really wants a battery to work   
    It looks to be a bug in the ARICS firmware. I reported it to TL LIm, but good luck & have fun waiting for Allwinner to fix (or even acknowledge) anything.
    Obviously comparing the behavior to other releases would be good to see if it depends on u-boot DT (or maybe it's a "feature", not a bug).
  14. Like
    pfeerick reacted to tkaiser in Armbian 5.30 on Pine64 really wants a battery to work   
    Obviously not, it's just that nobody uses a power button since you need a soldering iron for. Simple workaround: don't use the power button, most probably not so simple fix: dive into BSP power management code
    If the problem also occurs with other 'distros' then it might be worth to compare DT and kernel config. But zero priority of course since you're the only Armbian user around having a power button soldered (or connected to EXP header)
  15. Like
    pfeerick reacted to zador.blood.stained in MMC: No card present error on Allwinner boards   
    Board does not boot Armbian from inserted SD card, but may boot other distributions (based on old/legacy u-boot).
    Following or similar output can be grabbed from the serial console:
    U-Boot SPL 2017.01-armbian (Feb 02 2017 - 03:04:04) DRAM: 2048 MiB Trying to boot from MMC1MMC: no card present spl: mmc init failed with error: -123 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### The key message here is "MMC: no card present"
    Most likely cause:
    Malfunctioning microSD slot card detect switch.
    It can be verified either visually (with a magnifying glass) or electronically (with a multimeter) - at least in the slots used on Orange Pi boards and on Pine64 the pin near the switch should be shorted to the ground (i.e. SD slot casing) when card is inserted.
    Illustration (example) of a working switch:

    Verification (with a multimeter):
    Probe 1 - slot pin near the switch (may be different for different slot types, but at least true for Oranges and Pine64)
    Probe 2 - microSD slot casing or other parts connected to GND (not shown on the photo)
    No card - circuit is open
    Card inserted - circuit is shorted
    Photos - card is not inseted on the left and is fully inserted on the right:
    Orange Pi
    Pine64 (switch is more visible)
    Can it be fixed?
    Yes if the switch is not broken completely, by carefully adjusting (bending) the stationary contact (left on the pictures and photos, it usually is a part of the SD slot casing) i.e using a needle so it touches the moving contact (mostly hidden inside the slot on the photos) when card is inserted and not touching it when it is not inserted.
  16. Like
    pfeerick got a reaction from StuxNet in Improve 'Support over Forum' situation   
    @Igor I've edited both announcements a bit, see what you think of the changes. And please, please, please change "Before you think to report a problem with your board running Armbian' to something a little less... sharp? I know I would do that tongue in cheek (and do... hence why you sometimes see strikethroughs in my text)  , but that could be a little less unfriendly... "Before reporting problems with your board running Armbian" or ""Before reporting problems with your board running Armbian, check the following" ... something like that?
  17. Like
    pfeerick reacted to StuxNet in Problem with UART on Orange PI Zero   
    Simply, no. Not that I'm aware of.

    I've personally tested onboard UART and over USB-OTG for days on end. I've not experienced any problems (that weren't of my own doing ;D) Then again, I'm also using a small heatsink and mini 5v fan.
    What are you doing with OPi/Arduino? The reason I ask is because I've experienced 'drop outs' in connection over SSH/UART, etc... (which exhibit similar behavior to what little description you provide) as result of power for various reasons on OPi. 
    Updating/installing/compiling large packages High CPU usage Poor power cable Combination of the above + Heat Are you cooling OPi at all? Heat is a known issue with OPi Zero. Provide logs and/or more description. ie: armbianmonitor -u

    Isn't convincing enough evidence for me to rule out:
    Problem with UART, not necessarily "on Orange PI Zero." Problem with the Arduino's communication to the UART  
  18. Like
    pfeerick got a reaction from Neves Junior in Problem with route on eth0 cable disconnected   
    Um... maybe tell us what your problems actually is? What did you do? Did you have wifi and ethernet running, and then unplug ethernet and this is the result of route -n? 
  19. Like
    pfeerick reacted to Igor in Unable to create bootable SDcard   
    Most if not all of our images are tested. Those assumptions might not stand - stock images use different u-boot which could lead to differences and if you use HDD and power via micro USB you are on the power supply edge by bad design. A tiny difference in boot process could crash / not boot the board.
    Your SD card could be half failed  ... in any case we would need a serial console output to nail the problem down. If you get there.
  20. Like
    pfeerick reacted to tkaiser in ROCK64   
    There's a reason Apple sent truckloads of engineers to USB Implementers forum technical commitees for 'next generation connector' and power delivery specs to avoid such BS (or that Micro USB crap). But it will take some time until we see USB-C everywhere -- especially implemented correctly  
  21. Like
    pfeerick reacted to dkmax in OrangePi Zero high temperature?   
    Just a note that internal human body temperature is 37C, not surface temperature - unless you're bleeding profusely. The interface between internal (37C) and external (ambient) must necessarily be inbetween. This is why we stick the thermometer in our mouth and not on our finger. I would say 32C is the correct reading.
  22. Like
    pfeerick reacted to armbinator in orange pi pc - which USB sata bridge   
    As you can see my setup with hooked up "things", only my lte stick is not attached.
    LOT (list of things)
    SDD Samsung in the (ICY)box.
    Camera attached
    Serial for my terminal
    Network LAN
    Network USB Edimax 300 GB or MB (who cares, hehehe)
    3G Modem working

    Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 032: ID 0e8d:00a5 MediaTek Inc. Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 032: ID 152d:2509 JMicron Technology Corp. / JMicron USA Technology Corp. JMS539 SuperSpeed SATA II 3.0G Bridge Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 7392:7822 Edimax Technology Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I have this precision power supply and had it set to 5.00, where any (but only) external SATA->USB Bridge failed. All of a sudden I had this crazy idea to crank up the voltage a little and voila -> approx at 5.2 I had a crazy dmesg output that the drive had read errors and  cache issues. Then later I got it running at 5.25 and further perform without errors at 5.3. So I set the perfect safe level of no failure to 5.35. So what do you say about that? OPI -> into the bin?
    Now this setup, where it is fully headless (no HDMI/DVI, etc. -> all powered off, the DRAM set to lowest 480, but all cores powered up) we can definitly say on peak performance it uses 5W.
    Peak performance is Modem SMS and internet up/down from and to harddrive and surfing through hotspot.
    all the best and I hope to solve a lot of SATA problems here and gave a real view of performance/consumption.
  23. Like
    pfeerick reacted to chwe in New OPi Zero - Yet another high temperature issue...   
    Do you ever thought about alternatives (Maybe C.H.I.P or Omega 2 are better for battery powered IoT devices. This is a little bit out of my knowledge, not sure if these two are good proposals)? From my experience, the opi 0 is a little bit bitchy as soon as it runs into a undervoltage situation. I realized that the SoC (OPi 0, rev. 1.4) gets really hot (finger test) as soon as there's not enough power to start up the board. I'll investigate this as soon as I have more time and my second OPi 0 arrives (I would be annoyed, if I grill the only one which I have at the moment). 
  24. Like
    pfeerick reacted to zador.blood.stained in Quick Pinebook Preview / Review   
    I would prefer to collect all known issues first, and @tkaiser most likely would prefer if you started a "board bring up" thread.
    Then we should look at the mixer values or maybe extract asound.state from a fresh ayufan build.
  25. Like
    pfeerick reacted to Hamish in Orange Pi Zero /4.11.0-sun8i/ wlan0 is gone   
    I signed up to the forums just so I could add my voice to this ticket.
    I've been using the Orange pi zeros for a couple of months and was really happy with how well the wifi worked as an access point.  So I am a little disturbed to discover that the wifi driver has been disabled and that I need to pin my kernel version (especially since I told thirty other people to get their own Orange pi zero based on my testing...)
    Is there a list of issues with this driver somewhere?