Mysensors Gateway on OrangePi (Zero) (opi)



  • @marceloaqno You were right, I wasn't using the correct branch. Your instructions though did not work for me

    root@opi-pc-1:~# git clone https://github.com/marceloaqno/MySensors/tree/spidev marceloaqno-spidev
    Cloning into 'marceloaqno-spidev'...
    fatal: repository 'https://github.com/marceloaqno/MySensors/tree/spidev/' not found
    

    Anyway, I found another way:

    git clone https://github.com/marceloaqno/MySensors.git marceloaqno-spidev
    cd marceloaqno-spidev/
    git pull origin spidev
    ./configure
    make
    

    This time it compiled successfuly, but when I fired up mysgw all I got was:

    mysgw: Starting gateway...
    mysgw: Protocol version - 2.2.0-beta
    

    with no other output.
    Just to be sure we're on the same note, what is the wiring schematic I should use? When I first started to tinker with RF24 on OPi I found at least two wiring schematics.
    For reference here's the gpio readall on my OPi PC:

     +-----+-----+----------+------+---+-Orange Pi+---+---+------+---------+-----+--+
     | BCM | wPi |   Name   | Mode | V | Physical | V | Mode | Name     | wPi | BCM |
     +-----+-----+----------+------+---+----++----+---+------+----------+-----+-----+
     |     |     |     3.3v |      |   |  1 || 2  |   |      | 5v       |     |     |
     |  12 |   8 |    SDA.0 | ALT5 | 0 |  3 || 4  |   |      | 5V       |     |     |
     |  11 |   9 |    SCL.0 | ALT5 | 0 |  5 || 6  |   |      | 0v       |     |     |
     |   6 |   7 |   GPIO.7 | ALT3 | 0 |  7 || 8  | 0 | ALT4 | TxD3     | 15  | 13  |
     |     |     |       0v |      |   |  9 || 10 | 0 | ALT4 | RxD3     | 16  | 14  |
     |   1 |   0 |     RxD2 | ALT5 | 0 | 11 || 12 | 0 | ALT3 | GPIO.1   | 1   | 110 |
     |   0 |   2 |     TxD2 | ALT5 | 1 | 13 || 14 |   |      | 0v       |     |     |
     |   3 |   3 |     CTS2 | ALT5 | 0 | 15 || 16 | 0 | ALT3 | GPIO.4   | 4   | 68  |
     |     |     |     3.3v |      |   | 17 || 18 | 0 | ALT3 | GPIO.5   | 5   | 71  |
     |  64 |  12 |     MOSI | ALT4 | 0 | 19 || 20 |   |      | 0v       |     |     |
     |  65 |  13 |     MISO | ALT4 | 0 | 21 || 22 | 0 | ALT5 | RTS2     | 6   | 2   |
     |  66 |  14 |     SCLK | ALT4 | 0 | 23 || 24 | 0 | ALT4 | CE0      | 10  | 67  |
     |     |     |       0v |      |   | 25 || 26 | 0 | ALT3 | GPIO.11  | 11  | 21  |
     |  19 |  30 |    SDA.1 | ALT4 | 0 | 27 || 28 | 0 | ALT4 | SCL.1    | 31  | 18  |
     |   7 |  21 |  GPIO.21 | ALT3 | 0 | 29 || 30 |   |      | 0v       |     |     |
     |   8 |  22 |  GPIO.22 | ALT3 | 0 | 31 || 32 | 0 | ALT5 | RTS1     | 26  | 200 |
     |   9 |  23 |  GPIO.23 |  OUT | 0 | 33 || 34 |   |      | 0v       |     |     |
     |  10 |  24 |  GPIO.24 |  OUT | 1 | 35 || 36 | 0 | ALT5 | CTS1     | 27  | 201 |
     |  20 |  25 |  GPIO.25 | ALT3 | 0 | 37 || 38 | 0 | ALT5 | TxD1     | 28  | 198 |
     |     |     |       0v |      |   | 39 || 40 | 0 | ALT5 | RxD1     | 29  | 199 |
     +-----+-----+----------+------+---+----++----+---+------+----------+-----+-----+
     | BCM | wPi |   Name   | Mode | V | Physical | V | Mode | Name     | wPi | BCM |
     +-----+-----+----------+------+---+-Orange Pi+---+------+----------+-----+-----+
    


  • @mihai.aldea

    Just a question the command "gpio readall" does that does show the actual status of the system, or is it just a fixed table that is printed on screen....

    Look at mine:

    root@orangepizero:~# gpio readall
     +-----+-----+----------+------+---+-Orange Pi+---+---+------+---------+-----+--+
     | BCM | wPi |   Name   | Mode | V | Physical | V | Mode | Name     | wPi | BCM |
     +-----+-----+----------+------+---+----++----+---+------+----------+-----+-----+
     |     |     |     3.3v |      |   |  1 || 2  |   |      | 5v       |     |     |
     |  12 |   8 |    SDA.0 | ALT5 | 0 |  3 || 4  |   |      | 5V       |     |     |
     |  11 |   9 |    SCL.0 | ALT5 | 0 |  5 || 6  |   |      | 0v       |     |     |
     |   6 |   7 |   GPIO.7 | ALT3 | 0 |  7 || 8  | 1 | OUT  | TxD3     | 15  | 13  |
     |     |     |       0v |      |   |  9 || 10 | 0 | ALT5 | RxD3     | 16  | 14  |
     |   1 |   0 |     RxD2 | ALT5 | 0 | 11 || 12 | 0 | ALT3 | GPIO.1   | 1   | 110 |
     |   0 |   2 |     TxD2 | ALT5 | 0 | 13 || 14 |   |      | 0v       |     |     |
     |   3 |   3 |     CTS2 | ALT3 | 0 | 15 || 16 | 0 | ALT3 | GPIO.4   | 4   | 68  |
     |     |     |     3.3v |      |   | 17 || 18 | 0 | ALT3 | GPIO.5   | 5   | 71  |
     |  64 |  12 |     MOSI | ALT4 | 0 | 19 || 20 |   |      | 0v       |     |     |
     |  65 |  13 |     MISO | ALT4 | 0 | 21 || 22 | 0 | OUT  | RTS2     | 6   | 2   |
     |  66 |  14 |     SCLK | ALT4 | 0 | 23 || 24 | 0 | ALT4 | CE0      | 10  | 67  |
     |     |     |       0v |      |   | 25 || 26 | 0 | ALT3 | GPIO.11  | 11  | 21  |
     |  19 |  30 |    SDA.1 | ALT4 | 0 | 27 || 28 | 0 | ALT4 | SCL.1    | 31  | 18  |
     |   7 |  21 |  GPIO.21 | ALT3 | 0 | 29 || 30 |   |      | 0v       |     |     |
     |   8 |  22 |  GPIO.22 | ALT3 | 0 | 31 || 32 | 0 | ALT3 | RTS1     | 26  | 200 |
     |   9 |  23 |  GPIO.23 |  OUT | 0 | 33 || 34 |   |      | 0v       |     |     |
     |  10 |  24 |  GPIO.24 |  OUT | 1 | 35 || 36 | 0 | ALT3 | CTS1     | 27  | 201 |
     |  20 |  25 |  GPIO.25 |  OUT | 1 | 37 || 38 | 0 | ALT5 | TxD1     | 28  | 198 |
     |     |     |       0v |      |   | 39 || 40 | 0 | ALT5 | RxD1     | 29  | 199 |
     +-----+-----+----------+------+---+----++----+---+------+----------+-----+-----+
     | BCM | wPi |   Name   | Mode | V | Physical | V | Mode | Name     | wPi | BCM |
     +-----+-----+----------+------+---+-Orange Pi+---+------+----------+-----+-----+
    

    It is the same... and shows 40 pins while the OPI Zero only has 26.......
    There are some small differences between our tables in the naming column... so i guess it really reads the status / names of the pins.. Anyhow still strange that 40 pins are shown instead of 26 for the zero..



  • @marceloaqno: are you planning to create a pull request? also, like @Reza suggested i think it would be smart to gather all information somehwhere, unfortunately mysensors does not seem to have a wiki. can we write an article somehow? i could take care of that.


  • Code Contributor

    @mihai.aldea sorry about the github link mistake.

    @pansen Yes, I will.

    Is the orientation of the pins correct in the image?
    0_1483990616295_Orange-Pi-Zero-Description.jpg



  • @marceloaqno

    Nope pinout is reversed!,

    The link below shows the correct one!
    https://oshlab.com/orange-pi-zero-pinout/


  • Code Contributor

    @Tag Oops, did I get it right this time (I reuploaded the image)?



  • @marceloaqno

    Build the RF24 lib, without erros on the OPI Zero. and am now able to start the tools and radio seems to be recognised!. (was a faulty breadboard wire.... 😞 )

    Used the follwing to for the radio:

    RF24 radio(2,0);
    

    Output from gettingstarted:

    root@orangepizero:~/rf24libs/RF24/examples_linux# ./gettingstarted
    RF24/examples/GettingStarted/
    STATUS           = 0x00 RX_DR=0 TX_DS=0 MAX_RT=0 RX_P_NO=0 TX_FULL=0
    RX_ADDR_P0-1     = 0x0000000000 0xff00000000
    RX_ADDR_P2-5     = 0xff 0xff 0xff 0xff
    TX_ADDR          = 0xffffffffff
    RX_PW_P0-6       = 0xff 0xff 0xff 0xff 0xff 0xff
    EN_AA            = 0xff
    EN_RXADDR        = 0xff
    RF_CH            = 0xbc
    RF_SETUP         = 0xff
    CONFIG           = 0xff
    DYNPD/FEATURE    = 0xff 0xff
    Data Rate        = 1MBPS
    Model            = nRF24L01
    CRC Length       = 16 bits
    PA Power         = PA_MAX
    
     ************ Role Setup ***********
    Choose a role: Enter 0 for pong_back, 1 for ping_out (CTRL+C to exit) 
    >
    

  • Code Contributor

    @Tag Could you fill this table with your current setup?

    nRF24L01 | OrangePi  | OrangePi
             | phyPin    | GPIO
    _________|_______________________
    VCC      | 3V3-PWR   | 3V3-PWR
    GND      | GND       | GND
    CSN      |           |
    CE       |           |
    MOSI     | 19        | 15
    SCK      | 23        | 14
    MISO     | 21        | 16
    


  • @marceloaqno

    Sure here it is,

    nRF24L01 | OrangePi  | OrangePi
             | phyPin    | GPIO
    _________|_______________________
    VCC      | 3V3-PWR   | 3V3-PWR
    GND      | GND       | GND
    CSN      | 24        | 13
    CE       | 22        | 2
    MOSI     | 19        | 15
    SCK      | 23        | 14
    MISO     | 21        | 16
    

    Radio seems to be recognised, still need to test data transfer...


  • Code Contributor

    I created the draft for the official article: https://www.mysensors.org/build/orange


  • Mod

    @marceloaqno and everyone else involved in this effort: great work! I love when people come together to solve a problem.



  • @marceloaqno
    @mfalkvidd @Tag @pansen @Reza @mihai.aldea @hausinger

    Wooow woow woow !!!

    Only few days "off" and the problem to make work Mysensors on OPI are solved.

    So many many thanks to all people here that have been involved to make that OPI good little boards can work with Mysensors.

    This is the proof that when good people join can reach the most difficult achievements and all humanity can benefit.

    Awesome work !

    Regards



  • @marceloaqno

    Great work!!! the GPIO part most probably needs some additions for OPI zero on the topic of the spidev1.0 driver and the GPIO pins, send it to you once i got everything documented.

    Really many thanks for your hard work here!!



  • This post is deleted!


  • @marceloaqno
    thank you. but i have error:

    root@OrangePI:~# ls /sys/class/gpio/export
    ls: cannot access /sys/class/gpio/export: No such file or directory
    root@OrangePI:~# modprobe gpio-sunxi
    root@OrangePI:~# ls /sys/class/gpio/export
    ls: cannot access /sys/class/gpio/export: No such file or directory
    
    

    in class folder i dont have gpio folder (i use a orangepi one with ubuntu os )
    0_1484050121184_lll;l.jpg

    i



  • @Reza

    You need to create the files after each boot.

    After the modprobe, Issue this command:

    sudo for A in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16; do echo "$A" > /sys/class/gpio/export ; done
    

    This will get you the files.



  • root@OrangePI:~# git clone https://github.com/marceloaqno/MySensors.git orangepi               Cloning into 'orangepi'...
    remote: Counting objects: 13858, done.
    remote: Compressing objects: 100% (50/50), done.
    remote: Total 13858 (delta 17), reused 0 (delta 0), pack-reused 13808
    Receiving objects: 100% (13858/13858), 9.68 MiB | 79.00 KiB/s, done.
    Resolving deltas: 100% (8304/8304), done.
    Checking connectivity... done.
    root@OrangePI:~# cd orangepi/
    root@OrangePI:~/orangepi# git pull origin spidev
    From https://github.com/marceloaqno/MySensors
     * branch            spidev     -> FETCH_HEAD
    Updating 570b607..63e1a81
    Fast-forward
     Makefile                                          |  16 +++
     MyConfig.h                                        |   4 +
     MySensors.h                                       |   2 +-
     configure                                         |  79 ++++++++++---
     core/MyHwLinuxGeneric.cpp                         |  17 +++
     core/MyHwLinuxGeneric.h                           |  12 +-
     core/MyHwRPi.cpp                                  |   1 +
     core/MyHwRPi.h                                    |  28 -----
     core/MyMainLinux.cpp                              |  30 ++---
     drivers/{RPi => BCM}/SPI.cpp                      |  10 +-
     drivers/{RPi => BCM}/SPI.h                        | 116 ++++++++++++-------
     drivers/{RPi => BCM}/Wire.cpp                     |   0
     drivers/{RPi => BCM}/Wire.h                       |   1 +
     drivers/Linux/Arduino.h                           |  22 +++-
     drivers/Linux/GPIO.cpp                            | 119 ++++++++++++++++++++
     drivers/Linux/GPIO.h                              |  47 ++++++++
     drivers/Linux/Stream.h                            |   1 +
     drivers/Linux/compatibility.cpp                   |  11 +-
     drivers/{RPi/rpi_util.cpp => Linux/interrupt.cpp} | 144 +++++-------------------
     drivers/Linux/interrupt.h                         |  45 ++++++++
     drivers/RF24/RF24.cpp                             |   4 +-
     drivers/RF24/RF24.h                               |   2 +-
     drivers/RPi/RPi.cpp                               |  59 ++++++++++
     drivers/RPi/RPi.h                                 |  22 ++++
     drivers/RPi/piHiPri.c                             |  49 --------
     drivers/RPi/rpi_util.h                            |  76 -------------
     drivers/RPi/wiring.cpp                            |  72 ++++++++++++
     drivers/RPi/wiring.h                              |  24 ++++
     drivers/SPIDEV/SPI.cpp                            | 223 +++++++++++++++++++++++++++++++++++++
     drivers/SPIDEV/SPI.h                              | 178 +++++++++++++++++++++++++++++
     30 files changed, 1054 insertions(+), 360 deletions(-)
     rename drivers/{RPi => BCM}/SPI.cpp (100%)
     rename drivers/{RPi => BCM}/SPI.h (62%)
     rename drivers/{RPi => BCM}/Wire.cpp (100%)
     rename drivers/{RPi => BCM}/Wire.h (99%)
     create mode 100644 drivers/Linux/GPIO.cpp
     create mode 100644 drivers/Linux/GPIO.h
     rename drivers/{RPi/rpi_util.cpp => Linux/interrupt.cpp} (63%)
     create mode 100644 drivers/Linux/interrupt.h
     create mode 100644 drivers/RPi/RPi.cpp
     create mode 100644 drivers/RPi/RPi.h
     delete mode 100644 drivers/RPi/piHiPri.c
     delete mode 100644 drivers/RPi/rpi_util.h
     create mode 100644 drivers/RPi/wiring.cpp
     create mode 100644 drivers/RPi/wiring.h
     create mode 100644 drivers/SPIDEV/SPI.cpp
     create mode 100644 drivers/SPIDEV/SPI.h
    root@OrangePI:~/orangepi# ./configure
    [SECTION] Detecting target machine.
      [OK] machine detected: SoC=H3, Type=unknown, CPU=armv7l.
    [SECTION] Detecting SPI driver.
      [OK] SPI driver detected:SPIDEV.
    [SECTION] Detecting init system.
      [OK] init system detected: systemd.
    [SECTION] Saving configuration.
    [SECTION] Cleaning previous builds.
    [OK] Finished.
    root@OrangePI:~/orangepi# make
    gcc -MT build/drivers/Linux/log.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_LINUX -DMY_DEBUG -DLINUX_SPI_SPIDEV -DLINUX_ARCH_ORANGEPI  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -I./drivers/SPIDEV -c drivers/Linux/log.c -o build/drivers/Linux/log.o
    g++ -MT build/drivers/Linux/IPAddress.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_LINUX -DMY_DEBUG -DLINUX_SPI_SPIDEV -DLINUX_ARCH_ORANGEPI  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -I./drivers/SPIDEV -c drivers/Linux/IPAddress.cpp -o build/drivers/Linux/IPAddress.o
    g++ -MT build/drivers/Linux/noniso.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_LINUX -DMY_DEBUG -DLINUX_SPI_SPIDEV -DLINUX_ARCH_ORANGEPI  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -I./drivers/SPIDEV -c drivers/Linux/noniso.cpp -o build/drivers/Linux/noniso.o
    g++ -MT build/drivers/Linux/GPIO.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_LINUX -DMY_DEBUG -DLINUX_SPI_SPIDEV -DLINUX_ARCH_ORANGEPI  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -I./drivers/SPIDEV -c drivers/Linux/GPIO.cpp -o build/drivers/Linux/GPIO.o
    g++ -MT build/drivers/Linux/Print.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_LINUX -DMY_DEBUG -DLINUX_SPI_SPIDEV -DLINUX_ARCH_ORANGEPI  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -I./drivers/SPIDEV -c drivers/Linux/Print.cpp -o build/drivers/Linux/Print.o
    g++ -MT build/drivers/Linux/EthernetClient.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_LINUX -DMY_DEBUG -DLINUX_SPI_SPIDEV -DLINUX_ARCH_ORANGEPI  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -I./drivers/SPIDEV -c drivers/Linux/EthernetClient.cpp -o build/drivers/Linux/EthernetClient.o
    g++ -MT build/drivers/Linux/SerialPort.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_LINUX -DMY_DEBUG -DLINUX_SPI_SPIDEV -DLINUX_ARCH_ORANGEPI  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -I./drivers/SPIDEV -c drivers/Linux/SerialPort.cpp -o build/drivers/Linux/SerialPort.o
    g++ -MT build/drivers/Linux/Stream.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_LINUX -DMY_DEBUG -DLINUX_SPI_SPIDEV -DLINUX_ARCH_ORANGEPI  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -I./drivers/SPIDEV -c drivers/Linux/Stream.cpp -o build/drivers/Linux/Stream.o
    g++ -MT build/drivers/Linux/compatibility.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_LINUX -DMY_DEBUG -DLINUX_SPI_SPIDEV -DLINUX_ARCH_ORANGEPI  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -I./drivers/SPIDEV -c drivers/Linux/compatibility.cpp -o build/drivers/Linux/compatibility.o
    g++ -MT build/drivers/Linux/interrupt.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_LINUX -DMY_DEBUG -DLINUX_SPI_SPIDEV -DLINUX_ARCH_ORANGEPI  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -I./drivers/SPIDEV -c drivers/Linux/interrupt.cpp -o build/drivers/Linux/interrupt.o
    drivers/Linux/interrupt.cpp: In function ‘void* interruptHandler(void*)’:
    drivers/Linux/interrupt.cpp:107:26: warning: ignoring return value of ‘ssize_t read(int, void*, size_t)’, declared with attribute warn_unused_result [-Wunused-result]
       (void)read (fd, &c, 1) ;
                              ^
    g++ -MT build/drivers/Linux/SoftEeprom.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_LINUX -DMY_DEBUG -DLINUX_SPI_SPIDEV -DLINUX_ARCH_ORANGEPI  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -I./drivers/SPIDEV -c drivers/Linux/SoftEeprom.cpp -o build/drivers/Linux/SoftEeprom.o
    g++ -MT build/drivers/Linux/EthernetServer.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_LINUX -DMY_DEBUG -DLINUX_SPI_SPIDEV -DLINUX_ARCH_ORANGEPI  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -I./drivers/SPIDEV -c drivers/Linux/EthernetServer.cpp -o build/drivers/Linux/EthernetServer.o
    g++ -MT build/examples_linux/mysgw.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_LINUX -DMY_DEBUG -DLINUX_SPI_SPIDEV -DLINUX_ARCH_ORANGEPI  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -I./drivers/SPIDEV -c examples_linux/mysgw.cpp -o build/examples_linux/mysgw.o
    In file included from ./MySensors.h:294:0,
                     from examples_linux/mysgw.cpp:74:
    ./drivers/RF24/RF24.cpp:39:11: error: Not supported on this platform.
      hwDigitalWrite(MY_RF24_CS_PIN, level);
               ^
    ./drivers/RF24/RF24.cpp:44:11: error: Not supported on this platform.
      hwDigitalWrite(MY_RF24_CE_PIN, level);
               ^
    ./drivers/RF24/RF24.cpp:388:11: error: Not supported on this platform.
      hwPinMode(MY_RF24_CE_PIN,OUTPUT);
               ^
    ./drivers/RF24/RF24.cpp:389:11: error: Not supported on this platform.
      hwPinMode(MY_RF24_CS_PIN,OUTPUT);
               ^
    ./drivers/RF24/RF24.cpp:37:32: warning: unused parameter ‘level’ [-Wunused-parameter]
     LOCAL void RF24_csn(const bool level)
                                    ^
    ./drivers/RF24/RF24.cpp:42:31: warning: unused parameter ‘level’ [-Wunused-parameter]
     LOCAL void RF24_ce(const bool level)
                                   ^
    ./drivers/RF24/RF24.cpp: In function ‘uint8_t RF24_spiMultiByteTransfer(uint8_t, uint8_t*, uint8_t, bool)’:
    ./drivers/RF24/RF24.cpp:56:11: error: ‘LOW’ was not declared in this scope
      RF24_csn(LOW);
               ^
    ./drivers/RF24/RF24.cpp:99:11: error: ‘HIGH’ was not declared in this scope
      RF24_csn(HIGH);
               ^
    ./drivers/RF24/RF24.cpp: In function ‘void RF24_startListening()’:
    ./drivers/RF24/RF24.cpp:235:10: error: ‘HIGH’ was not declared in this scope
      RF24_ce(HIGH);
              ^
    ./drivers/RF24/RF24.cpp: In function ‘void RF24_stopListening()’:
    ./drivers/RF24/RF24.cpp:241:10: error: ‘LOW’ was not declared in this scope
      RF24_ce(LOW);
              ^
    ./drivers/RF24/RF24.cpp: In function ‘void RF24_powerDown()’:
    ./drivers/RF24/RF24.cpp:251:10: error: ‘LOW’ was not declared in this scope
      RF24_ce(LOW);
              ^
    ./drivers/RF24/RF24.cpp: In function ‘bool RF24_sendMessage(uint8_t, const void*, uint8_t)’:
    ./drivers/RF24/RF24.cpp:269:10: error: ‘HIGH’ was not declared in this scope
      RF24_ce(HIGH);
              ^
    ./drivers/RF24/RF24.cpp:276:10: error: ‘LOW’ was not declared in this scope
      RF24_ce(LOW);
              ^
    ./drivers/RF24/RF24.cpp: In function ‘bool RF24_initialize()’:
    ./drivers/RF24/RF24.cpp:395:10: error: ‘LOW’ was not declared in this scope
      RF24_ce(LOW);
              ^
    ./drivers/RF24/RF24.cpp:396:11: error: ‘HIGH’ was not declared in this scope
      RF24_csn(HIGH);
               ^
    Makefile:114: recipe for target 'build/examples_linux/mysgw.o' failed
    make: *** [build/examples_linux/mysgw.o] Error 1
    root@OrangePI:~/orangepi#```


  • @Tag

    root@OrangePI:~/orangepi# sudo for A in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16; do echo "$A" > /sys/class/gpio/export ; done
    -bash: syntax error near unexpected token `do'
    root@OrangePI:~/orangepi# ```


  • @Tag said:

    sudo for A in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16; do echo "$A" > /sys/class/gpio/export ; done

    orangepi one have 40 pins


  • Code Contributor

    @Reza Is there /sys/class/gpio/export file on your OPi?



  • @marceloaqno
    no i have not folder "gpio" in my orangepi



  • @marceloaqno It still doesn't work on my OPi Zero 😕

    root@opi-zero-1:~/orangepi# bin/mysgw -d
    mysgw: Starting gateway...
    mysgw: Protocol version - 2.2.0-beta
    mysgw: MCO:BGN:INIT GW,CP=RNNG---,VER=2.2.0-beta
    mysgw: TSM:INIT
    mysgw: TSF:WUR:MS=0
    mysgw: !TSM:INIT:TSP FAIL
    mysgw: TSM:FAIL:CNT=1
    mysgw: TSM:FAIL:PDT
    mysgw: Received SIGINT

    I do have the /sys/class/gpio/export and I ran for A in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16; do echo "$A" > /sys/class/gpio/export ; done

    For the record, here's my OS:

    BOARD=orangepizero
    BOARD_NAME="Orange Pi Zero"
    VERSION=5.24
    LINUXFAMILY=sun8i
    BRANCH=default
    ARCH=arm
    PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
    NAME="Debian GNU/Linux"
    VERSION_ID="8"
    VERSION="8 (jessie)"
    ID=debian
    HOME_URL="http://www.debian.org/"
    SUPPORT_URL="http://www.debian.org/support"
    BUG_REPORT_URL="https://bugs.debian.org/"
    

  • Code Contributor

    @mihai.aldea The gateway does the exporting when needed, you don't need to run:
    for A in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16; do echo "$A" > /sys/class/gpio/export ; done

    Could you send the output of this command?

    ls -lah /dev/spidev*
    


  • @marceloaqno

    Still issues here:

    root@orangepizero:~/orangepi/bin# ll /dev/spi*
    crw------- 1 root root 153, 0 Jan  9 22:51 /dev/spidev0.0
    crw------- 1 root root 153, 1 Jan  9 22:51 /dev/spidev1.0
    

    Then:

    ./configure --spi-spidev-device=/dev/spidev1.0
    

    added to examples_linux/mysgw.cpp

    #define MY_RF24_CE_PIN 2
    #define MY_RF24_CS_PIN 13
    

    end enabled radio debugging:

    output:

    root@orangepizero:~/orangepi/bin# ./mysgw -d
    mysgw: Starting gateway...
    mysgw: Protocol version - 2.2.0-beta
    mysgw: MCO:BGN:INIT GW,CP=RNNG---,VER=2.2.0-beta
    mysgw: TSM:INIT
    mysgw: TSF:WUR:MS=0
    mysgw: RF24:write register, reg=0, value=14
    mysgw: RF24:write register, reg=3, value=3
    mysgw: RF24:write register, reg=4, value=95
    mysgw: RF24:write register, reg=5, value=76
    mysgw: RF24:write register, reg=6, value=39
    mysgw: RF24:write register, reg=16, value=115
    mysgw: RF24:write register, reg=29, value=6
    mysgw: RF24:read register, reg=6, value=39
    mysgw: RF24:read register, reg=5, value=76
    mysgw: RF24:write register, reg=2, value=2
    mysgw: RF24:write register, reg=1, value=0
    mysgw: RF24:write register, reg=28, value=3
    mysgw: RF24:flushRX
    mysgw: RF24:flushTX
    mysgw: RF24:write register, reg=7, value=112
    mysgw: TSM:INIT:TSP OK
    mysgw: TSM:INIT:GW MODE
    mysgw: RF24:write register, reg=2, value=3
    mysgw: RF24:write register, reg=1, value=1
    mysgw: RF24:STRT LIS
    mysgw: RF24:write register, reg=0, value=15
    mysgw: RF24:write register, reg=10, value=0
    mysgw: TSM:READY:ID=0,PAR=0,DIS=0
    mysgw: MCO:REG:NOT NEEDED
    mysgw: RF24:read register, reg=23, value=17
    Illegal instruction
    root@orangepizero:~/orangepi/bin# 
    

    Almost there?



  • @marceloaqno
    in "orangepi one"(ubuntu os) there is not gpio folder in sys/class. but i think after run "modprobe gpio-sunxi" built a folder that name is "gpio_sw" and in this folder there are this files: normal_led,pa3,pa6,pa8 and 9,10,13,14,15,21 ,...



  • @Reza Is it too complicated to switch to Debian?



  • @mihai.aldea said:

    Is it too complicated to switch to Debian?

    you told me i change my os ? to armbian ?



  • @Reza
    More info on armbian.com

    I use the debian jessie, works like a charm!



  • @Reza I wouldn't even dream of not using Armbian on OrangePi and NanoPi. Compared to Raspbian it's years ahead in terms of optimization and tidyness. Armbian is the reason I'm avoiding RPi when possible. So go ahead and install a proper OS for your OPi. Not sure if Xenial or Debian, maybe we should wait for @marceloaqno to respond to my comment with the running OS.



  • @Tag
    i worked with armbiam before. but my question is with armbian my problem is resolve ?



  • That I can not say.



  • @Tag said:

    I use the debian jessie, works like a charm!

    ok i change my os and test again. thank you



  • I confirm it's not working on the OPi PC where TMRh20 works.



  • @marceloaqno said:

    @Tag Oops, did I get it right this time (I reuploaded the image)?

    Got it spot on!! looks great!



  • i have problem with compile source domoticz(i must use source domoticz for my changes) in armbian, so i have to use ubuntu.
    @marceloaqno can you help me to run mysensors gateway in orangepi one (ubuntu os).thank you



  • Hi All,

    I put together the steps to get MySensors running on the OrangePi Zero:
    Take note of the SPI part, 1 typo and you will not see /dev/spidev1.0

    • Install sunxi-tools:
      These tools are required to make changes in the boot area of the system
    sudo apt-get update
    sudo apt-get install sunxi-tools
    
    • How to add /dev/spidev1.0 (which is required since /dev/spidev0.0 is used for the onboard NAND flash)
    cd /boot
    bin2fex /boot/script.bin /root/myscript.txt
    

    Now edit /root/myscript.bin and add/change the following so it looks exactly like the part below:

    [spi0]
    spi_used = 1
    spi_cs_bitmap = 1
    spi_mosi = port:PC00<3><default><default><default>
    spi_miso = port:PC01<3><default><default><default>
    spi_sclk = port:PC02<3><default><default><default>
    spi_cs0 = port:PC03<3><1><default><default>
    	
    [spi1]
    spi_used = 1
    spi_cs_bitmap = 1
    spi_cs0 = port:PA13<2><1><default><default>
    spi_sclk = port:PA14<2><default><default><default>
    spi_mosi = port:PA15<2><default><default><default>
    spi_miso = port:PA16<2><default><default><default>
    	
    [spi_devices]
    spi_dev_num = 2
    	
    [spi_board0]
    modalias = "spidev"
    max_speed_hz = 33000000
    bus_num = 0
    chip_select = 0
    mode = 0
    full_duplex = 1
    manual_cs = 0
    	
    [spi_board1]
    modalias = "spidev"
    max_speed_hz = 33000000
    bus_num = 1
    chip_select = 0
    mode = 0
    full_duplex = 1
    manual_cs = 0
    
    • Then recompile the script file:
    fex2bin /root/myscript.txt /boot/script.bin
    

    Reboot the system

    reboot
    

    2 device files should exist now:

    root@orangepizero:~# ls -l /dev/spi*
    crw------- 1 root root 153, 0 Jan 11 16:31 /dev/spidev0.0
    crw------- 1 root root 153, 1 Jan 11 16:31 /dev/spidev1.0
    

    Load the gpio module

    modprobe gpio-sunxi
    

    To load the module gpio-sunxi automagically load at boot time, add gpio-sunxi to /etc/modules

    echo gpio-sunxi >> /etc/modules
    
    • Now it is time to install the GW.
    cd /root
    git clone https://github.com/marceloaqno/MySensors.git orangepi 
    cd orangepi/ 
    git pull origin spidev
    ./configure --spi-spidev-device=/dev/spidev1.0
    make
    

    Working like a charm!

    If you tested "/bin/mysgw -d" and all works as expected, make the installation permanent:

    make install
    

    Additional
    If you want to read data into a controller using a device file (i.e Mycontroller) use the build string below

     ./configure --spi-spidev-device=/dev/spidev1.0  --my-gateway=serial --my-serial-is-pty --my-serial-pty=/dev/ttyMySensorsGateway
    

    Hope this helps!! have fun!!


  • Code Contributor

    @Tag great! Thanks for the detailed explanation 👏
    I will add to the instructions page



  • out of curiousity: this all relates to 3.x kernel in armbian right? which has proprietary stuff in there?

    i read somewhere that mainline 4.10 SPI is "work in progress"



  • @pansen
    Yes correct, for OPI Zero only ARMbian 3.x is available as a download image.
    I used the debian jessie one


  • Code Contributor

    Instructions page updated, let me know if there is any mistake.



  • @marceloaqno

    looks great!! thx!!👍



  • Excellent work !!! It finally works, I believe the slight mistake was with the damn SPI device ID. Now that I've enabled /dev/spidev1.0 everything works perfect. Really nice job and awesome commitment to showing people that it's time for them to pull their heads out of their a.... and spend less for way more awesome boards because let's face it, RPi has the greatest community support but it's a nothing more than an expensive closed source crappy board.



  • @mihai.aldea
    Great!!, found out the SPI0 is used for the NAND flash, once you add SPI1 to the script.bin, also the need board paragraph with bus 1 needs to be added otherwise it will not work.... anyway great you got mysensors up and running!!
    About the RPI, i like both boards, and in my opinion the enormous success of the RPI is responsible, for the large collection of OPI boards that is available these days 😉



  • There are few who know that lots of asian compaines were producing SBC's long before RPi ever existed. RPi has to take credit for the SBC boom, but the connaisseurs will always prefer a top notch SBC that costs less than half of an RPi and is piled with features. Take the OPi Zero for instance, it's way smaller than RPi 3, has half the RAM and doesn't have Bluetooth. But you can buy 4 OPi Zeros with the money you'd spend on an RPi 3.
    Anyway it's an endless debate here, I'm just glad I could help a bit bringing this to life, even though you and @marceloaqno did the heavy lifting.


  • Hardware Contributor

    Thank you for the hard work guys, I have a fresh orange pi zero and I will install armbian and try this hack as soon as possible. Looks like a great way to have an ultra compact&cheap controller + gateway system !


  • Code Contributor

    Support for OrangePi is now part of the official MySensors development repository.
    In the official version, it is necessary to define the CE and CS pins, as the default ones will not work. This will change in the future, but more work needs to be done to better detect the different types of Orange Pi and other H3 soc boards.
    For now, if you have set your system in the same way as the wiring instructions, use:

    ./configure --spi-spidev-device=/dev/spidev1.0 --my-transport=nrf24 --my-rf24-ce-pin=2 --my-rf24-cs-pin=13
    


  • @marceloaqno

    Thank you for your hard work and continued support on this!!



  • @mihai.aldea
    It's working on my OPi One with Armbian. MySensors and TMRh20 works!

    Only in ./MySensors: bin
    Only in ./MySensors: build
    diff -ruBdX ex ./_MySensors/drivers/RF24/RF24.cpp ./MySensors/drivers/RF24/RF24.cpp
    --- ./_MySensors/drivers/RF24/RF24.cpp<>2017-01-28 10:24:03.557215399 +0200
    +++ ./MySensors/drivers/RF24/RF24.cpp<->2017-01-28 10:58:51.757543157 +0200
    @@ -29,7 +29,7 @@
     LOCAL RF24_receiveCallbackType RF24_receiveCallback = NULL;
     #endif
    .
    -#ifdef LINUX_SPI_BCM
    +#if defined (LINUX_SPI_BCM) || (LINUX_SPI_SPIDEV)
     uint8_t spi_rxbuff[32+1] ; //SPI receive buffer (payload max 32 bytes)
     uint8_t spi_txbuff[32+1] ; //SPI transmit buffer (payload max 32 bytes + 1 byte for the command)
     #endif
    @@ -56,7 +56,7 @@
     <----->RF24_csn(LOW);
     <----->// timing
     <----->delayMicroseconds(10);
    -#ifdef LINUX_SPI_BCM
    +#if defined (LINUX_SPI_BCM) || (LINUX_SPI_SPIDEV)
     <----->uint8_t * prx = spi_rxbuff;
     <----->uint8_t * ptx = spi_txbuff;
     <----->uint8_t size = len + 1; // Add register value to transmit buffer
    diff -ruBdX ex ./_MySensors/Makefile.inc ./MySensors/Makefile.inc
    --- ./_MySensors/Makefile.inc<->2017-01-28 10:49:53.990638008 +0200
    +++ ./MySensors/Makefile.inc<-->2017-01-28 11:12:57.601198157 +0200
    @@ -1,5 +1,5 @@
     SOC=H3
    -CPPFLAGS=-march=armv7-a -mtune=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_LINUX -DMY_DEBUG -DLINUX_SPI_SPIDEV.
    +CPPFLAGS=-march=armv7-a -mtune=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_LINUX -DLINUX_SPI_SPIDEV -DMY_RF24_CE_PIN=7 -DSPI_S
     LDFLAGS=-pthread.
     PREFIX=/usr/local
     CC=gcc
    


  • Hi all

    I want to give feedback here.

    Today i tried to build a orange pi gateway with a connected usb - rs485 converter on it. And what should I say - It worked without problems. Many thanks to you all 🙂
    Great



  • Hi to all, I don't know if this is the right thread, but I'm trying to use an odroid c1 as a gateway. I'm posting here because I think you all could help me.
    The original thread I have done is this one
    https://forum.mysensors.org/topic/6083/odroid-c1-as-getaway
    Feel free to go over there and give me advises.


 

255
Online

8.8k
Users

9.5k
Topics

100.2k
Posts