C++ GPIO seg fault on Rock64 using Pine64-CPP
#1
I'm trying to run the example.cpp that comes with Pine64-CPP from https://github.com/databit/Pine64-CPP

I am throwing segmentation faults when I run.
 
Initializationsucceeds:
The man-setup() call initialzes the board.  I traced the success path to the following if statement in the setup() function in gpio.cpp
    if((uint64_t)gpio_mem % PAGE_SIZE)
And I also traced the successful  "this->gpioMap =" statement to the one that uses SUNXI_GPIO_BASE
    
In the example code, I initialize the pin with
   man->pinMode (PI_GPIO_24, OUTPUT);
 
The pinMode function in gpio.cpp, launches _setPullupdn with gpio=78 and pud = 1.  As expected
Inside _setPullupdn,  the following is set
     bank= 2
     index = 0
    offset = 28
 
The segmentation fault seems to come from this line in gpio.c
   regval = *(&pio->PULL[0] + index);
 
I have a 4 GB Rock64 running armbian bionic desktop from https://www.armbian.com/rock64/
 
sudo cat /sys/kernel/debug/gpio   gives me

GPIOs 0-31, platform/pinctrl, gpio0:
 gpio-0   (                    |vcc_host_5v         ) out hi    
 gpio-2   (                    |?                   ) out lo    
 gpio-30  (                    |vcc_sd              ) out lo    
 
GPIOs 32-63, platform/pinctrl, gpio1:
 gpio-50  (                    |mdio-reset          ) out hi  
 
GPIOs 64-95, platform/pinctrl, gpio2:
 
GPIOs 96-127, platform/pinctrl, gpio3:
 
GPIOs 510-511, platform/rk8xx-gpio, rk8xx-gpio, can sleep:
 gpio-510 (                    |?                   ) out lo    
 gpio-511 (                    |?                   ) out lo   
 
 
Anyone have any thoughts?
Thanks.
  Reply
#2
So, I never resolved the problems with the Pine64-CPP library but I found an alternate. 

First, I used bash scripts to make sure the Rock64 was working, and I had the right pin addresses.
       https://github.com/Leapo/Rock64-BashGPIO

I used the table table from this website to correctly identify the gpio indices.
        https://github.com/Leapo/Rock64-R64.GPIO...GPIO-Modes
        I used the items from the column lableled GPIO# (ROCK)

Lastly, I used the GPIO Class from the following. 
Even though it is was created for the Raspberry Pi, I found that it correctly manipulated the files in /sys/class/gpio on my Rock64.
      https://github.com/halherta/RaspberryPi-GPIOClass-v2

Note: I have only tested the GPIO read function, since that is what I'm trying to do for my project.

Edit 2/20/19
The GPIO Class approach only worked in C++.  For a C version, I used the sysfs code from this site:
     https://elinux.org/RPi_GPIO_Code_Samples
However, to use the Rock64 GPIO assignments from 100 to 103, I needed to change #define BUFFER_MAX 3 to #define BUFFER_MAX 4. 
This may break things for two digit GPIO assignments.  I didn't really test that
  Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Rock64 running OMV, how to setup RTL8812AU WiFi? electrosam 2 43 Yesterday, 04:03 PM
Last Post: ayufan
  Rock64 for video surveillance martinschm 3 117 07-06-2019, 03:26 AM
Last Post: martinschm
  Rock64 random freezes BTB 3 139 07-01-2019, 10:17 AM
Last Post: Luke
  Purchase Rock64 V3? richardk 3 172 06-28-2019, 05:04 PM
Last Post: Luke
Sad Rock64 Seafile Installation klaus_nase 2 96 06-27-2019, 09:11 AM
Last Post: klaus_nase
  rock64, compile problems "illegal instruction", "memory fault" -> ddr_333Mhz? hunderteins 5 323 06-22-2019, 12:36 PM
Last Post: redfish
  Another non-booting ROCK64 SuburbanDad 13 538 06-19-2019, 01:48 AM
Last Post: mcerveny
  Plastic storage box for Rock64 matwey 1 83 06-18-2019, 10:56 PM
Last Post: tllim
  Rock64 v2 network issues alephnull 1 150 06-07-2019, 03:30 PM
Last Post: alephnull
  Rock64 v3 - POE P1V 1 165 06-07-2019, 12:24 AM
Last Post: tllim

Forum Jump:


Users browsing this thread: 1 Guest(s)