Jump to content

JulianR

Members
  • Content Count

    8
  • Joined

  • Last visited

Everything posted by JulianR

  1. Hi, sorry for the late answer, I was in vacation. I am using the latest version (Tinker_Board_2-Debian-Buster-v2.0.4-20211222). I get the right status if I just read and link the pin to 3.3v/GND. Also it always stays to the latest connected voltage when reading after disconnecting.
  2. I am using the Tinkerboard 2 and wiringPi. The pullup/pulldown seems not to work for all pins. For example here I use pin 5 (pyhsical 18) and set it to pulldown. But As you can see below the value is still 1. The weird thing is that if I pull the pin up/down by connecting it for a short time to 3,3V/GND the pin always stays at the value that I connected it to no matter what pull mode I set. Here the terminal commands/output: gpio mode 5 input gpio mode 5 down gpio readall +-----+-----+---------+------+---+--Tinker--+---+------+---------+-----+-----+ | CPU | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | CPU | +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+ | | | 3.3v | | | 1 || 2 | | | 5v | | | | 73 | 8 | GPIO2B1 | IN | 1 | 3 || 4 | | | 5v | | | | 74 | 9 | GPIO2B2 | IN | 1 | 5 || 6 | | | 0v | | | | 8 | 7 | CLKOUT2 | CLK | 0 | 7 || 8 | 1 | IN | GPIO2C1 | 15 | 81 | | | | 0v | | | 9 || 10 | 1 | IN | GPIO2C0 | 16 | 80 | | 83 | 0 | GPIO2C3 | IN | 1 | 11 || 12 | 0 | IN | GPIO3D0 | 1 | 120 | | 85 | 2 | GPIO2C5 | IN | 0 | 13 || 14 | | | 0v | | | | 84 | 3 | GPIO2C4 | IN | 0 | 15 || 16 | 1 | OUT | GPIO2C6 | 4 | 86 | | | | 3.3v | | | 17 || 18 | 1 | IN | GPIO2C7 | 5 | 87 | | 40 | 12 | MOSI.1 | SPI | 0 | 19 || 20 | | | 0v | | | | 39 | 13 | MISO.1 | SPI | 1 | 21 || 22 | 0 | IN | GPIO3D4 | 6 | 124 | | 41 | 14 | SCLK.1 | SPI | 1 | 23 || 24 | 1 | OUT | GPIO1B2 | 10 | 42 | | | | 0v | | | 25 || 26 | 0 | IN | GPIO0A6 | 11 | 6 | | 71 | 30 | GPIO2A7 | IN | 1 | 27 || 28 | 1 | IN | GPIO2B0 | 31 | 72 | | 126 | 21 | GPIO3D6 | IN | 0 | 29 || 30 | | | 0v | | | | 125 | 22 | GPIO3D5 | OUT | 1 | 31 || 32 | 0 | IN | GPIO4C2 | 26 | 146 | | 150 | 23 | GPIO4C6 | OUT | 1 | 33 || 34 | | | 0v | | | | 121 | 24 | GPIO3D1 | IN | 0 | 35 || 36 | 1 | IN | GPIO2C2 | 27 | 82 | | 149 | 25 | GPIO4C5 | IN | 0 | 37 || 38 | 0 | IN | GPIO3D3 | 28 | 123 | | | | 0v | | | 39 || 40 | 0 | IN | GPIO3D7 | 29 | 127 | +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+ | CPU | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | CPU | +-----+-----+---------+------+---+--Tinker--+---+------+---------+-----+-----+
  3. Yes it is working, I also used the libraray from "https://github.com/TinkerBoard/gpio_lib_c" instead of "/usr/local/share/gpio_lib_c_rk3399"
  4. Thank you for your response. The paths there do not exist on my board (Tinkerboard2). For example physical pin 3 states: "/sys/class/gpio/gpio73". If I do an ls on that path, none of them listed there: $ sudo ls /sys/class/gpio/ export gpio16 gpio25 gpiochip0 gpiochip128 gpiochip32 gpiochip64 gpiochip96 unexport
  5. JulianR

    wiringPi problem

    I have the same problem, did you find a solution for this?
  6. I do have the same problem. Did you find a solution? Is the Tinkerboard project dead? So many topics here do not have solutions/aswers.
  7. Hi there, I am trying to port software from RPI4 to the tinkerboard. We used to access the GPIOs not with WiringPI but manually using "nmap" with a file descriptor ("/dev/mem"). To find the peripheral offset address we were reading this file: "/proc/device-tree/soc/ranges". But I can not find this path or a similar one on the tinkerboard. Can someone help me to get on the right track? Thanks in advance! Julian R.
×
×
  • Create New...