Jump to content

martinayotte

Members
  • Posts

    3892
  • Joined

  • Last visited

Posts posted by martinayotte

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

     

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

     

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

  4. 1 hour ago, B3RN0UT said:

    E.g for PD25 this would be ( 4 - 1) * 32 + 25 = 121 + 25 = 146 (since 'd' is the 4th letter).

    Nope ! it should be read as :

    PD25 this would be ( 4 - 1) * 32 + 25 = 96 + 25 = 121

     

    1 hour ago, B3RN0UT said:

    I'm unsure what exactly is the mentioned Pin

    No, it is not header pin number but GPIO name

  5. In Armbian Mainline, the SPI is enabled using an overlay. For that you need to add "overlays=spi-spidev" in /boot/armbianEnvt.txt and then reboot.

    For longsleep images, I think you need to enable the SPI simply by changing 'status="disalbed"' to 'status="okay"' in its DT.

     

  6. The output you've posted earlier :

     root@pine64:~# fdisk -l /dev/sda
    
    Disk /dev/sda: 28.9 GiB, 31043616768 bytes, 60632064 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes

    It seems incomplete since it doesn't show any partition ...

     

    With proper partitioning, it should look like :

    root@pine64:~# fdisk -l /dev/sda
    Disk /dev/sdb: 29.8 GiB, 32026656768 bytes, 62552064 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x000c3d6a
    
    Device     Boot Start      End  Sectors  Size Id Type
    /dev/sda1        2048 61926527 61922432 29.5G 83 Linux

     

  7. The output of "fdisk -l /dev/sda" doesn't show any partition ...

    But strangely, the previous log mentioned you have /dev/sda1.

    Are you sure you provided the complete output of fdisk ?

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines