Jump to content

martinayotte

Members
  • Posts

    3892
  • Joined

  • Last visited

Posts posted by martinayotte

  1. Unfortunately, with Armbian_5.32_S9xxx_Ubuntu_xenial_3.14.29_server_20170820.img.xz, there is no modules for AP6212, either it is part of kernel or not present at all, although the /lib/firmware/ap6212 is present.

    "dmesg" doesn't reveal much.

    Anyway, with the intermittent reboots and boot loops occurring in the middle of some apt-get I had this morning, I'm convince that this board is probably defective.

     

  2. Thanks, @balbes150 !

    Using @kicker22004 patches, I got the Armbian_5.32_S9xxx_Ubuntu_xenial_3.14.29_server_20170820.img.xz image booting ! ;)

    But unfortunately, on-board WiFi not detected ...

    Trying some Mainline images didn't lead to some success, staying stuck at "Starting kernel ..." !

     

    EDIT : even the Armbian_5.32_S9xxx_Ubuntu_xenial_3.14.29_server_20170820.img.xz start doing some reboot loop now. I think my board is simply defective, FriendlyArm maybe simply send me this sample from "rejected" one ...

    (It will return in the drawer to collect dust :angry:)

     

  3. 40 minutes ago, TonyMac32 said:

    If you still get the loop with a custom image, the u-boot blob isn't being written to the correct position on the card, so the first stage bootloader isn't seeing it. Now I don't know why you might be able to get to a u-boot prompt "after a while".  That doesn't sound healthy

    The boot loop wasn't with balbes image, but with FriendlyELEC image ... So, not stable enough, I decided to build a C2, and will report back if it is working better.

     

  4. Grrrrr ! :angry:

     

    Even this FriendlyELEC nanopi-k2_ubuntu_core_xenial-20170718.img.zip image just enter in a boot loop for awhile, but after several trys, I've finally got the prompt ...

     

    Thanks, Zador for the hints, I will take a lot at that !

    Unfortunately, I think it will take a lot of efforts ...

     

    EDIT : Grrrrr ! :angry: After a reboot, the boot loop came back again ...

  5. I have a NanoPi-K2 sitting in the dust since awhile.

    I decided to try some images from @balbes150, such as Armbian_5.32_S9xxx_Ubuntu_xenial_3.14.29_server_20170820.img.xz or even some other such Armbian_5.27_S9xxx_Debian_jessie_4.13.0-next-20170731+_server.img.xz, but none of them is even starting to load u-boot ... :wacko::(

     

    It is only producing such output on debug serial :

     

    GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:F3;USB:8;LOOP:1;EMMC:800;NAND:81;SD:0;READ:0;CHK:F3;USB:8;LOOP:2;EMMC:800;NAND:81;SD:0;READ:0;CHK:F3;USB:8;

    I don't know much about Amlogic, what I'm missing ?

     

  6. 8 minutes ago, zador.blood.stained said:

    AFAIK some USB ports are shared with the USB-SATA converters

    Yes, that is my conclusion seeing the above picture :

    This USB connector is directly in parallel with the header pins connected to the converter, allowing people to use the board on other SBC using male-male cable like in the picture.

    I don't have such cable, so I can't verify that ...

    That means this connector should always left empty while the board been used with OPiZero, meaning only one USB is available.

     

    If we can get schematic on day, that will prove all this conclusion ...

  7. BTW, I've never tried those USB until now (I'd only tested the mSATA) ...

    Without using any overlays, since my DT was already enabling them, the one near the SATA connector is working, but not the near audio jack !

    Doing "dmesg" reveal flood of "device descriptor read/64, error -71" and the mSATA is disappearing ...

     

    This weird behaviour make me think that we still waiting for the schematic, still cannot be found anywhere ! :(

     

    While searching the schematic, I've found pictures where this USB on the audio jack side is kind of connected as OTG not HOST :

    HTB1umZJRVXXXXXfXFXXq6xXFXXX6.jpg?size=3

     

     

  8. This seams the scenario where both ETH and WLAN are connected on the same subnet, and when disconnecting the ETH, it break the whole routing, because the default gateway is gone.

    It is never a good thing to have the same subnet for both ETH and WLAN, because in fact, doing an SSH on WiFi for example, the packets coming from WLAN, but reponses will go back thru ETH, therefore disconnecting ETH will freeze the SSH...

     

  9. Well ! you first need to figure out about pyA20 library, don't try the other libraries until you get the fist one done !

    On my OLIMEX board (I don't have any Cubieboard ...) both include coming from the same kernel tree, so they should have the same timestamp. If your are not the same timestamp, you have done ugly kernel updates ... Maybe a fresh images could help !

    root@micro:~# ll /usr/include/linux/i2c*
    -rw-r--r-- 1 root root 2427 Jun 26 16:14 /usr/include/linux/i2c-dev.h
    -rw-r--r-- 1 root root 6772 Jun 26 16:14 /usr/include/linux/i2c.h

     

  10. CubieBoard2 is based on AllWinner A20 SoC, so it should work, although you maybe need to check/tweak the header pinout accordingly in pyA20/gpio/mapping.h, although the PD25 is already present.

    So, simply grab a ZIP snapshot, unzip it, and install it using "cd pyA20-master ; sudo python setup.py install" ...

     

  11. Looking more deeply to the library, I found that it is a bit more complex than I thought to make it run on a A20 board.

    Doing a bit more search, I found out something easier :

    https://github.com/AiratNig/DHT22-DHT11_Orange-Pi_Python

    installed on top of the PyA20 library from :

    https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/Python/pyA20/pyA20

     

    EDIT : I found also that one, again on top of pyA20 : https://github.com/ionutpi/DHT22-Python-library-Orange-PI

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines