Jump to content

SergioAiello

Members
  • Posts

    11
  • Joined

  • Last visited

Everything posted by SergioAiello

  1. not important question: between Zero2 and zero3 I would choose Zero3: performances are similar, but Zero3 is newer. Why Armbian decided to not support it? BR, S.
  2. I did not find the build for Orange Pi Zero 3 Vice versa I found the build for Orange Pi Zero2 Both SBCs are equipped with Allwinner H6 CPU (H618 for the board Zero 3 and H616 for the board Zero2). Is the build for Orange Pi Zero2 compatible with Orange Pi Zero 3 as well?
  3. Additionally the cmd gpioRead stops working after ISR setup printf (" main1 - %d\n", digitalRead (2)); wiringPiISR (2, INT_EDGE_BOTH, myInterrupt1) ; printf (" main2 %d\n", digitalRead (2)); output: root@MansaConsMon:/home/lapamo15/GPIO/wiringOP# ./ottobre2023 main1 - 1 main2 - 0 Waiting ... And 'gpioRead' output will not change even if the INPUT toggles between 3.3 and 0V Note: the interrupt function detects correctly the input changes, but the 'digitalRead' output is always LOW Interrupt function triggered by the rising edge. Signal level at input '2' is 3.3V (measured by a tester) and the command 'gpio read 2' output is '0' (which should be '1'). It seems there is a conflict between 'wiringPiISR' and 'digitalRead'.
  4. Hello Andrea, I have the same wiringOP version and also in my case it seems the Orange Pi pulls the input UP by default without considering the SW setup cmd (pullUpDnControl(0, PUD_DOWN);) --- By the way I'm using a OPi ZERO. Is there somebody that can help with a solution or just a workaround? At the moment I've added a pull-down resistor of 1.8kOhm. Therefore the two voltage states are 1.0 and 2.1 (instead of 0 and 3.3). It works but I'm wondering if it is possible to improve. Many thanks!
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines