Posts by LuRu

LuRu · Orange Pi 3 - irregular system freezing LuRu August 10, 2021 at 2:11 PM

I have had a problem with LibreELEC / Kodi installed on the Orange Pi 3 board for a very long time (from the very beginning).

The problem is that the whole system freezes. In this state, the board stops responding to any command, does not respond to the ping, the SSH session is interrupted and the image on the monitor freezes.

The board responds only to the power button and, of course, to the power off. This problem occurs intermittently, usually within one hour of startup.

I needed to find out whether the cause of the described problem is the nature of HW or SW.

First, I tried to replace everything that could be replaced (SD card, cable, power supply). Unfortunately, no change.

Then I tried to install Kodi in Armbian OS. It was unusable (very slow, just an old version of Kodi).

Finally, I installed the Android 7 OS on the SD card and then Kodi. This is a combination you can live with, at least on a small monitor.

I let it run for a week and everything was fine. The problem did not occur. I am aware that this is not entirely sufficient proof that the board is OK. But I only have one piece.

What should I do ?

kodi.log

serial_console.log

LuRu · Two new addons for Orange Pi (Allwinner) boards LuRu July 9, 2021 at 7:40 AM

I found out that there is an bug in the OPi.GPIO library (and therefore also in the virtual.opi-tools add-on). There does not work properly callbacks when mode == GPIO.BOARD.

Links to download the corrected version are in the initial post of this topic.

LuRu · Two new addons for Orange Pi (Allwinner) boards LuRu July 7, 2021 at 7:54 AM

Quote from jernej

Fix is submitted: Allwinner: linux: Enable GPIO sysfs by jernejsk · Pull Request #5481 · LibreELEC/LibreELEC.tv · GitHub

Great!

I compiled a devel build with the above modification and it works.

Thank you very much for your support!

LuRu · Two new addons for Orange Pi (Allwinner) boards LuRu July 6, 2021 at 5:09 PM

Thank you for the answer. I have three different boards:

1) Orange Pi PC (H3, 1GB DDR3 SDRAM)

2) Orange Pi Lite 2 (H6, 1GB LPDDR3 SDRAM, no Ethernet)

3) Orange Pi 3 (H6, 2GB LPDDR3 SDRAM)

I use them all for LibreELEC, but due to the specification, my favorite is the Orange Pi 3. This is the board on which I performed the described debugging.

LuRu

So I made another debug version and found out even more information.

The problem is in the function

Code

struct gpios *new_gpio(unsigned int gpio)
{
  struct gpios *new_gpio;

  new_gpio = malloc(sizeof(struct gpios));
  if (new_gpio == 0)
    return NULL;  // out of memory

  new_gpio->gpio = gpio;
  if (gpio_export(gpio) != 0) {
    free(new_gpio);
    return NULL;
  }
  new_gpio->exported = 1;

  if (gpio_set_direction(gpio,1) != 0) { // 1==input
    free(new_gpio);
    return NULL;
  }

  if ((new_gpio->value_fd = open_value_file(gpio)) == -1) {
    gpio_unexport(gpio);
    free(new_gpio);
    return NULL;
  }

  new_gpio->initial = 1;
  new_gpio->bouncetime = 0;
  new_gpio->lastcall = 0;

  if (gpio_list == NULL) {
    new_gpio->next = NULL;
  } else {
    new_gpio->next = gpio_list;
  }
  gpio_list = new_gpio;
  return new_gpio;
}

Display More

specifically in section

Code

  new_gpio->gpio = gpio;
  if (gpio_export(gpio) != 0) {
    free(new_gpio);
    return NULL;
  }


/************* /sys/class/gpio functions ************/
int gpio_export(unsigned int gpio)
{
    int fd, len;
    char str_gpio[4];

  if ((fd = open("/sys/class/gpio/export", O_WRONLY)) < 0)
        return -1;

    len = snprintf(str_gpio, sizeof(str_gpio), "%d", gpio);
    if(OPiGPIODebug)
        printf("\n /sys/class/gpio/export %d \n",gpio);

    write(fd, str_gpio, len);
    close(fd);
    return 0;
}

Display More

So now it looks much clearer.

There is no sys/class/gpio directory in LibreELEC (maybe just for Allwinner?).

For comparison - in the case of Raspberry Pi this directory exists ...

Can this be fixed?

LuRu

I understand that I have provided little information.

I made a debug version and now I have some information.

This problem is in the following function:

Code

int add_edge_detect(unsigned int gpio, unsigned int edge, unsigned int bouncetime)
// return values:
// 0 - Success
// 1 - Edge detection already added
// 2 - Other error
{
  pthread_t threads;
  struct epoll_event ev;
  long t = 0;
  struct gpios *g;

  // check to see if this gpio has been added already
  if (gpio_event_added(gpio) != 0)
    return 1;

  // create epfd if not already open
  if ((epfd == -1) && ((epfd = epoll_create(1)) == -1))
    return 2;

  if ((g = new_gpio(gpio)) == NULL)
    return 2;

  gpio_set_edge(gpio, edge);
  g->bouncetime = bouncetime;
  // add to epoll fd
  ev.events = EPOLLIN | EPOLLET | EPOLLPRI;
  ev.data.fd = g->value_fd;
  if (epoll_ctl(epfd, EPOLL_CTL_ADD, g->value_fd, &ev) == -1) {
    remove_edge_detect(gpio);
    return 2;
  }
  // start poll thread if it is not already running
  if (!thread_running) {
    if (pthread_create(&threads, NULL, poll_thread, (void *)t) != 0) {
       remove_edge_detect(gpio);
       return 2;
    }
  }
  return 0;
}

Display More

Specifically, where after executing g = new_gpio(gpio) the result is NULL.

But I still don't know why this only happens in the LibreELEC OS, while in Armbian it works properly.

LuRu · Two new addons for Orange Pi (Allwinner) boards LuRu July 5, 2021 at 2:04 PM

I wanted to use the virtual.opi-tools add-on even more.

I wanted to add some buttons and test their status using a python.

I can easily read the status of buttons (statically) with a command like state01 = GPIO.input(button01).

But I need to use a callback and it doesn't work.

I have the command GPIO.add_event_detect(button01, GPIO.BOTH, callback = buttonCallback) in my script.

As soon as the interpreter reaches the specified line, I get an error message RuntimeError: Failed to add edge detection

I don't know how to solve it.

I installed Armbian on the same board and there the exact same script works as expected. The OPi.GPIO library is also installed from the same source (GitHub - Pako2/OrangePi.GPIO: RPi.GPIO drop-in replacement library for Orange Pi Boards).

Does anyone have any idea what to do with it?

Note: I have LE version nightly-20210703-9059fe9 installed

LuRu · Orange Pi 3 and i2c LuRu April 23, 2021 at 3:19 PM

Great, it's finally working.

So probably the problem was that my LE was installed some time ago (although upgraded to the last night version).

Thank you again for your extraordinary support and patience.

LuRu · Orange Pi 3 and i2c LuRu April 22, 2021 at 2:51 PM

Quote from LuRu

But it looks like it will still be many hours of work before LCDproc will work. There is little information on how to debug it.

So I'm surprised at how fast it went. The LCD display already shows the current Kodi informations !

Now I would like to do the correct way to enable the i2c bus via overlays. But I probably can't do it without help.

Could any OPi 3 owner help me?

LuRu · Orange Pi 3 and i2c LuRu April 22, 2021 at 12:51 PM

Thank you for your extraordinary helpfulness and willingness to help. However, it still doesn't work, even though I used your working binary file (and it looked so promising ...).

I even tried the line

FDTOVERLAYS /overlays/sun50i-h6-ir.dtbo

or

FDTOVERLAYS /overlays/sun50i-h6-spdif.dtbo

Both of these files existed (so they were included in the installation image) in the /overlays folder. I thought it should work. But it still behaves the same - the boot fails.

So out of desperation I decompiled the file sun50i-h6-orangepi-3.dtb, edited it

Code

        i2c@5002000 {
            compatible = "allwinner,sun50i-h6-i2c", "allwinner,sun6i-a31-i2c";
            reg = <0x5002000 0x400>;
            interrupts = <0x0 0x4 0x4>;
            clocks = <0x4 0x4a>;
            resets = <0x4 0x19>;
            pinctrl-names = "default";
            pinctrl-0 = <0x26>;
            status = "okay";
            #address-cells = <0x1>;
            #size-cells = <0x0>;
            phandle = <0x63>;
        };

Display More

and then compiled again. It works !

Code

##############################################
#                 LibreELEC                  #
#            https://libreelec.tv            #
##############################################

LibreELEC (community): nightly-20210421-5aaf229 (H6.arm)
LibreELEC:~ # i2cdetect -l
i2c-1    i2c           mv64xxx_i2c adapter                 I2C adapter
i2c-2    i2c           DesignWare HDMI                     I2C adapter
i2c-0    i2c           mv64xxx_i2c adapter                 I2C adapter
LibreELEC:~ # i2cdetect -y 0
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
LibreELEC:~ # i2cdetect -y 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- 27 -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
LibreELEC:~ # i2cdetect -y 2
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: 30 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
LibreELEC:~ #

Display More

But I'm not happy about it, I'd rather it worked the way over overlays.

So far, I have to work with what I have.

But it looks like it will still be many hours of work before LCDproc will work. There is little information on how to debug it.

LuRu · Orange Pi 3 and i2c LuRu April 21, 2021 at 2:17 PM

Quote from jernej

- overlay you're using isn't correct -

Can you please specify in what sense isn't correct?

I did some other experiments. First in Armbian OS.

First I enabled all three i2c buses in armbian-config and switched my interface to i2c2.

It works again. But interestingly, there are even 5 i2c buses at the moment!

Code

root@orangepi3:~# i2cdetect -l
i2c-3    i2c           DesignWare HDMI                     I2C adapter
i2c-1    i2c           mv64xxx_i2c adapter                 I2C adapter
i2c-4    i2c           mv64xxx_i2c adapter                 I2C adapter
i2c-2    i2c           mv64xxx_i2c adapter                 I2C adapter
i2c-0    i2c           mv64xxx_i2c adapter                 I2C adapter
root@orangepi3:~# i2cdetect -y 0
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
root@orangepi3:~# i2cdetect -y 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
root@orangepi3:~# i2cdetect -y 2
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- 27 -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
root@orangepi3:~# i2cdetect -y 3
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: 30 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
root@orangepi3:~# i2cdetect -y 4
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
root@orangepi3:~#

Display More

If I only enable i2c2 in armbian-config, then there are only three i2c buses (i2c-2, i2c-3 and i2c-4).

This means that the two default i2c buses are always at the end (in terms of numbering).

So if I don't have the i2c bus enabled in armbian-config at all, the default buses are numbered 0 and 1.

If I only have bus 0 enabled in armbian-config, the default buses have the numbers 1 and 2.

Then I went back to LE.

Instead of i2c0, I now enabled i2c2 in extlinux.conf.

Unfortunately, it behaves exactly the same as with i2c0. I.e:

A) When the FDTOVERLAYS line is at the end, LE boots, but no i2c bus is added

B) When the FDTOVERLAYS line is moved up, the boot fails

What steps can I take now (debugging?)?

LuRu · Orange Pi 3 and i2c LuRu April 20, 2021 at 5:26 PM

Maybe the mistake is that I took a .dtbo file from an Armbian image (there i2c-0 works properly).

Maybe I should take it elsewhere?

LuRu · Orange Pi 3 and i2c LuRu April 20, 2021 at 5:06 PM

1) In the meantime I tried to move FTDOVERLAYS one line higher and it has a big effect. LE doesn't boot - see picture - it stops like this and does nothing further (I had to return it using "cardreader edit")

2) i2cdetect -l says I have two i2c buses. See picture

LuRu · Orange Pi 3 and i2c LuRu April 20, 2021 at 4:25 PM

I think that's right:

1) There is no other i2c port on the GPIO header

2) I have the same connection when I boot Armbian, and there it works with the command i2cdetect -y 0 (see pictures in the first post)

LuRu · Orange Pi 3 and i2c LuRu April 20, 2021 at 3:53 PM

Thank you for further advice on how to proceed.

Unfortunately, the result is still the same - no detection of the PCF8574 address.

My extlinux.conf file now looks like this:

Code

LABEL LibreELEC
  LINUX /KERNEL
  FDT /sun50i-h6-orangepi-3.dtb
  APPEND boot=UUID=2212-5002 disk=UUID=2047348e-1e45-42ca-a55a-b19a509853fa quiet console=ttyS0,115200 console=tty1
  FDTOVERLAYS /overlays/sun50i-h6-i2c0.dtbo

Is it right ?

What's next ?

LuRu · Orange Pi 3 and i2c LuRu April 19, 2021 at 5:24 PM

Thank you for the advice.

Unfortunately, I have little knowledge in this regard.

I've read about overlays in the wiki, but there is only Raspberry described, no Allwinner.

I took the sun50i-h6-i2c0.dtbo file from Armbian and copied it to the /flash/overlays folder in LE.

But still no detection of the PCF8574 interface address.

How do I know the overlay is loaded?

Does it have to be allowed somewhere else?

LuRu · Orange Pi 3 and i2c LuRu April 19, 2021 at 2:31 PM

I intend to run LCDproc on an Orange Pi 3. I would like to use a display with an HD44780 controller connected via i2c.

I connected PCF8574 to OPi3 and it doesn't work. So I tried the i2cdetect utility and I see that my PCF8574 interface is not detected.

Then I inserted an SD card with the Armbian system into my device and tried the same thing (without any change of connection).

It works so my circuit is correct.

What should I do to make i2c work in LibreELEC?

LuRu

Thank you, I already have it installed (about 2 hours).

I saw your PR was merged.