Can't seem to find gpiod.h for Verdin imx8m-plus build

Evets · April 14, 2023, 2:09pm

I have an Verdin iMX8m-plus board, with a Verdin Dev board. This is a makefile c++ project. I am trying to compile code using VSC that uses the <gpiod.h> file. But it isn’t found when I try to compile. This isn’t a linking issue, it’s a compilation issue.
I have libgpiod-dev:arm64 libgpiod2:arm64 in the devpackages setting, and libgpiod-dev:arm64 libgpiod2:arm64 in the devices setting in the Torizon extension.

If I use #include <gpiod.h>, I get an error saying it can’t be found. What is missing in my extension?
Steve

hfranco.tx · April 14, 2023, 4:23pm

Hi @Evets,

Are you using the ApolloX version (new version) or the Toradex Torizon Support version?

Here I’m using ApolloX and I added both packages to torizonPackages.json and it worked. Here is my packages file:

{
    "deps": [
        "libgpiod2"
    ],
    "devDeps": [
        "libgpiod-dev"
    ]
}

And my sample code:

#include <stdio.h>
#include <gpiod.h>

int main()
{
    printf("Simple test\n");
    return 0;
}

And it worked without any errors. Can you make sure these packages are added to your file?

Best Regards,
Hiago.

Evets · April 14, 2023, 4:35pm

Hi @hfranco.tx ,

I am using ApolloX v2, but I do not see a torizonPackages.json file. Where is it located?

I do have that listed in the devpackages setting in the torizon extension.

Steve

eric.tx · April 14, 2023, 5:03pm

@Evets,

It should be an auto generated file under your project. Here is a screenshot of a new project.

-Eric

Evets · April 14, 2023, 5:06pm

Hi @eric.tx
I was using the torizon support early access extension. I switched a few days ago, but I didn’t disable the other extension. Do I need to recreate the project? I tried that and I got an error about “command createFromTemplate not found”. Do I need to unload the early access extension?

I am getting this list of things that are not installed, Docker, docker compose, and powershell. I have it installed on my WSL Ubuntu 20.04, am I supposed to install this on the target device?

Also, it can’t seem to find the device, but I can ssh into it just fine. I put in the IP address manually, and it shows under the connected devices but it says it’s not connected.

Steve

eric.tx · April 14, 2023, 7:05pm

Hey @Evets,

For clarity, you have the same project files that you used for the Torizon Support Early Extension as you have them open in the Apollo (V2)? I do not believe this would not work as the formats for the extensions are different.

Sorry for the edit needed. I forgot the word “not”

-Eric

Evets · April 14, 2023, 8:29pm

@eric.tx
Yes, that is the case. It’s a makefile project, so all I have to do is transfer the projects settings over.
But I can’t get V2 to work. See below:

Here is what I get when I load the project with ApolloX only installed.

[04-14 18:32:30.081] Activating ApolloX Torizon …
[04-14 18:32:30.081] Resolving host IP address …
[04-14 18:32:30.108] Host IP address OK
[04-14 18:32:30.138] ERROR :: Docker is not installed. Please install Docker: Install Docker Engine | Docker Documentation
[04-14 18:32:30.172] ERROR :: Docker compose is not installed. Please install Docker compose Overview | Docker Documentation
[04-14 18:32:30.181] ERROR :: PowerShell Core is not installed. Please install: Install PowerShell on Linux - PowerShell | Microsoft Learn
[04-14 18:32:30.211] git OK
[04-14 18:32:30.222] ERROR :: avahi-resolve is not installed.
[04-14 18:32:30.233] ERROR :: nmap is not installed.
[04-14 18:32:30.242] ERROR :: iputils-ping is not installed.
[04-14 18:32:30.250] file OK
[04-14 18:32:30.280] ERROR :: sshpass is not installed.
[04-14 18:32:30.288] ERROR :: net-tools is not installed.
[04-14 18:32:31.264] Error trying to install git iputils-ping nmap avahi-utils file sshpass net-tools
[04-14 18:32:31.264] ERROR :: GIT not installed, is not possible initialize project template subsystem
[04-14 18:32:31.266] Checking connected devices …
4-14 18:32:31.266] Scanning Torizon devices …
[04-14 18:32:31.283] ERROR :: Errors during the initialization of ApolloX Torizon Extension.
[04-14 18:32:31.283] HOUSTON WE HAVE A PROBLEM!
[04-14 18:32:31.284] PLEASE READ THE LOGS!
[04-14 18:32:31.284] No device selected as default
[04-14 18:32:31.284] Please select a registered device as default device
[04-14 18:32:34.431] Debian bookworm packages list load OK

I have the first 3 installed on WSL, as well as Windows. Not sure why it is saying all that.
And like I said, I can’t create a new project with V2, it fails right away with that issue. about not finding the command…

Steve

Evets · April 14, 2023, 8:41pm

I have looked up the ApollowX V2 documentation, but I can’t get it to find the board, but if I put it in manually, I can connect to it, and I can connect to it using a ssh terminal. Is there something that has to be installed on the Target board first to get it to recognize that it’s a target?

Thanks!
Steve

Evets · April 14, 2023, 10:07pm

I am no longer finding V2 of ApolloX. V2 is needed to work with 64 bit correct? or is it still limited to 32 bit? It is only showing v0.0.70.

eric.tx · April 17, 2023, 1:44pm

@Evets,

If they device is connected to the network and you can ssh into it. The device should be recognized via the VS Code extension. There is no code to upload to the device to make it recognizable.

ApolloX is the V2 VS Code extension.

Eric

Evets · April 17, 2023, 1:49pm

@eric.tx

The extension still says this only works for the 32bit version of Torizon. Is this the case? Before, I couldn’t install it, but now I can, even though that warning is still there. Maybe that is why it is not connecting?

Steve

eric.tx · April 17, 2023, 2:50pm

@Evets ,

Where is this error coming from? Can you link more of the error?

The directions for connecting to a device are found here:

You should be able to connect to the network and then the device.

-Eric

Evets · April 17, 2023, 3:38pm

Hi @eric.tx ,
OK, I have it loaded and the dev board is on my network. I try to use the “Network devices refresh” as instructed in the docs. It just sits there with the Trizon: Scanning Torizon devices… with nothing showing up as shown here.

If I manually add the IP address, I can get it to connect, as shown in @04-17 15:06:58:.205 timestamp. (I had removed the manual connection at 04-17 14:55:06.381) as shown here:

Also, you can see the reported version of v0.0.70 shown at the top of each picture.

And yes, if I open a terminal, I can do that (or also an outside ssh connection via a cmd window). I used the “Torizon: create new single container project”, (my only choice it gives me). results in this:

It also doesn’t seem to open any ports to the device, as you can see as if there were something open, it shows them.
Trying to run, gives me all sorts of errors as it doesn’t seem to open any ports or create a docker file.
RunOutput from terminal.zip (4.3 KB)

If I am missing something, please let me know what I am missing.
This last output was doing a “start from scratch” GPIO test. The problem I originally stated was from a Torizon extension (early access, or normal one). I had the ApolloX loaded but apparently not actually working, because the early access was loaded. But in any case, I couldn’t get the other extension to pull in the gpiod.h file, using the early access. I thought v2 was working at that point.

So in actuality, I would like to solve the original problem, rather than go down this V2 rabbithole.

Thanks,
Steve

eric.tx · April 17, 2023, 7:09pm

@Evets,

I believe there are a few issues here.

It looks like you are still connected to the V1 Dev Container: Torizon_GPIO (lower left corner). The two versions are not compatible, so developing in V1 is not transferable to V2. You will want to close this.

If you are working in V2, you will also need to launch VScode from the WSL. Are you doing this? you can often just type ‘code’ into the CLI of WSL and it should open.

If you want to stay in V1, this is possible, but you should rebuild/reload the SDK. This is achievable by F1 + “Torizon:Rebuild SDK and reload in container”

-Eric

Evets · April 17, 2023, 8:32pm

HI @eric.tx ,
At this moment, I am out of the ApolloX altogether and using the Early support extension, trying to get back to where everything compiles but gives me the error about not finding gpiod.h.

I did load VSCode from WSL. Didn’t know I could do this. I can’t do ApolloX v1 because it’s a 32bit version and this needs to be a 64 bit program.

If I DO run using v2, it compiles fine but when it tries to launch I get:

—> [Warning] The requested image’s platform (linux/arm64) does not match the detected host platform (linux/amd64) and no specific platform was requested

—> Running in 940ea075f832

Usage: usermod [options] LOGIN

Options:

-b, --badnames allow bad names

-c, --comment COMMENT new value of the GECOS field
-d, --home HOME_DIR new home directory for the user account
-e, --expiredate EXPIRE_DATE set account expiration date to EXPIRE_DATE
-f, --inactive INACTIVE set password inactive after expiration
to INACTIVE

-g, --gid GROUP force use GROUP as new primary group
-G, --groups GROUPS new list of supplementary GROUPS

-a, --append append the user to the supplemental GROUPS
mentioned by the -G option without removing
the user from other groups
-h, --help display this help message and exit
-l, --login NEW_LOGIN new value of the login name

-L, --lock lock the user account
-m, --move-home move contents of the home directory to the
new location (use only with -d)
-o, --non-unique allow using duplicate (non-unique) UID
-p, --password PASSWORD use encrypted password for the new password

-R, --root CHROOT_DIR directory to chroot into
-P, --prefix PREFIX_DIR prefix directory where are located the /etc/* files
-s, --shell SHELL new login shell for the user account
-u, --uid UID new UID for the user account
-U, --unlock unlock the user account

-v, --add-subuids FIRST-LAST add range of subordinate uids

-V, --del-subuids FIRST-LAST remove range of subordinate uids
-w, --add-subgids FIRST-LAST add range of subordinate gids
-W, --del-subgids FIRST-LAST remove range of subordinate gids
-Z, --selinux-user SEUSER new SELinux user mapping for the user account

I forgot to add. I get these messages when loading the system using V2:

04-17 20:50:32.960] Activating ApolloX Torizon …
[04-17 20:50:32.961] Resolving host IP address …
[04-17 20:50:32.999] Host IP address OK
[04-17 20:50:33.011] ERROR :: Docker is not installed. Please install Docker: Install Docker Engine | Docker Documentation
[04-17 20:50:33.029] ERROR :: Docker compose is not installed. Please install Docker compose Overview | Docker Documentation
[04-17 20:50:33.042] ERROR :: PowerShell Core is not installed. Please install: Install PowerShell on Linux - PowerShell | Microsoft Learn
[04-17 20:50:33.052] git OK
[04-17 20:50:33.077] ERROR :: avahi-resolve is not installed.
[04-17 20:50:33.091] ERROR :: nmap is not installed.
[04-17 20:50:33.104] ERROR :: iputils-ping is not installed.
[04-17 20:50:33.114] file OK
[04-17 20:50:33.124] ERROR :: sshpass is not installed.

Docker is installed
Docker compose is installed
and sshpass is installed,
even though it says they are not.
I am running Ubuntu 20.04 in WSL2
Steve

lucas_a.tx · April 17, 2023, 10:32pm

Hi @Evets ,

Let me clarify a few points, just to make sure we’re talking about the same thing:

The image below shows ApolloX: it is version 2 of our IDE extension. In this context there is no V1 of ApolloX.
The image below shows version 1 of the IDE extension: it can only refer to either “Toradex Torizon Support” or “Toradex Torizon Support (Early Access)”. If you’re not using ApolloX, then you’re using V1 of our extension.

v1977×164 26.2 KB
ApolloX is used with VSCode connected to WSL2. V1 should not be used with VSCode connected to WSL2.
If you used ApolloX and want to return to V1 you have to disable/uninstall ApolloX, and also do the following:
- On VSCode, press F1, then go to “Preferences: Open User Settings (JSON)”
- Comment/remove the line that starts with DOCKER_HOST": "tcp://<ip-address>"
If you want to keep using ApolloX instead just disable/uninstall any V1 of the extension beforehand.

At this moment, I am out of the ApolloX altogether and using the Early support extension, trying to get back to where everything compiles but gives me the error about not finding gpiod.h.

You said you are not using ApolloX anymore, but these logs you posted:

[04-17 20:50:32.960] Activating ApolloX Torizon …
[04-17 20:50:32.961] Resolving host IP address …
[04-17 20:50:32.999] Host IP address OK
[04-17 20:50:33.011] ERROR :: Docker is not installed. Please install Docker: Install Docker Engine | Docker Documentation
[04-17 20:50:33.029] ERROR :: Docker compose is not installed. Please install Docker compose Overview | Docker Documentation
[04-17 20:50:33.042] ERROR :: PowerShell Core is not installed. Please install: Install PowerShell on Linux - PowerShell | Microsoft Learn
[04-17 20:50:33.052] git OK
[04-17 20:50:33.077] ERROR :: avahi-resolve is not installed.
[04-17 20:50:33.091] ERROR :: nmap is not installed.
[04-17 20:50:33.104] ERROR :: iputils-ping is not installed.
[04-17 20:50:33.114] file OK
[04-17 20:50:33.124] ERROR :: sshpass is not installed.

are from ApolloX. What version of the extension are you using: V1 or ApolloX?

We need to be sure of this as the procedures on how to run a C/C++ project with libgpiod change a lot depending on the version of the extension:

If you intend to use V1, we have an article in our developer page explaining how to create a C/C++ project with it and adding the gpiod library: C/C++ Development and Debugging on TorizonCore Using Visual Studio Code | Toradex Developer Center . To summarize:

Close any connections to WSL2 or dev containers you might have by clicking on the lower left corner of the VSCode window, then selecting Close Remote Connection.
Press F1, then select “Torizon/C-C++: Create new C/C++ application”. Choose a Makefile-based project, then follow the on-screen instructions and let VSCode reload inside of a dev container
Add libgpiod-dev:arm64 to the devpackages settings, and add libgpiod2 to the extrapackages settings.
Press F1, then select “Torizon: Rebuild SDK and Reload in Container”. Wait for the operation to complete
Add your code to the project. The text editor might complain about gpiod.h not being found. If you did the steps above, ignore the warning.
Change Makefile so it has -lgpiod when compiling the relevant source files.
Make the GPIO pins visible to the container: C/C++ Development and Debugging on TorizonCore Using Visual Studio Code | Toradex Developer Center . Choose the GPIO bank you will be using.
Deploy and debug: C/C++ Development and Debugging on TorizonCore Using Visual Studio Code | Toradex Developer Center

If you intend to use ApolloX, as you’re using so far:

Close any connections to dev containers you might have by clicking on the lower left corner of the VSCode window, then selecting Close Remote Connection.
Then, connect VSCode to WSL2.
Make sure you followed the steps here to setup ApolloX, until the Creating a new Single Container Project step: GitHub - toradex/torizon-experimental-torizon-ide-v2-docs: VS Code Torizon Integrated Development Environment Documentation (Choose a C++ project instead of the C# the example uses)
Add the libgpiod packages to torizonPackages.json, as @hfranco.tx explained before.
Add your code to the project. The text editor might complain about gpiod.h not being found. If you did the steps above, ignore the warning.
Change Makefile so it has -lgpiod when compiling the relevant source files.
Change docker-compose.yaml so that the container has access to the GPIO pins. As an example, adding gpiochip0 will look like:

devices:
  - "/dev/gpiochip0:/dev/gpiochip0"

Replace gpiochip0 with the GPIO bank you will be using. More details about the compose-file can be seen here: Services top-level elements | Docker Docs

Follow the Remote Debug step: GitHub - toradex/torizon-experimental-torizon-ide-v2-docs: VS Code Torizon Integrated Development Environment Documentation

See if these steps help you.

Best regards,
Lucas Akira

Evets · April 18, 2023, 12:12am

Hi @eric.tx ,
Thank you for your patience. I didn’t understand when I first loaded ApolloX that it was a replacement for the other extension. So, I have been using v1, most of this time, with the exceptions of the occasional try of v2 without much success.
So I went back to v1 and am using the early access version. I did as you ask going back to v1, although there was no DOCKER_HOST": “tcp://” in the JSON file.
I have the #include <gpiod.h> in one of my files, as a test. When it compiles I get:
fatal error: gpiod.h: No such file or directory
13 | #include <gpiod.h>

Which is what I was getting in the beginning when I wrote up this ticket. I have the -lgpiod in my Makefile, but this addition, only effects linking, not compilation, and it complains that it can’t find it. I have searched my target device to see if there is a gpiod.h file there, and it doesn’t find one.

When I take the #include <gpiod.h> out of my cpp file, I get:

/usr/lib/gcc-cross/aarch64-linux-gnu/10/…/…/…/…/aarch64-linux-gnu/bin/ld: cannot find -lgpiod
collect2: error: ld returned 1 exit status
make: *** [Makefile:105:] Error 1

As it can’t find the library either. And now since I played around with v2, I am getting this error using v1 when I try to run:
—> [Warning] The requested image’s platform (linux/arm64) does not match the detected host platform (linux/amd64) and no specific platform was requested
—> Running in 2109e5e9d8e5

e[91mUsage: usermod [options] LOGIN

Options:
e[0m
e[91m -b, --badnames allow bad names
-c, --comment COMMENT new value of the GECOS field
-d, --home HOME_DIR new home directory for the user account
e[0m
e[91m -e, --expiredate EXPIRE_DATE set account expiration date to EXPIRE_DATE
-f, --inactive INACTIVE set password inactive after expiration
to INACTIVE
-g, --gid GROUP force use GROUP as new primary group
-G, --groups GROUPS new list of supplementary GROUPS
-a, --append append the user to the supplemental GROUPS
mentioned by the -G option without removing
the user from other groups
-h, --help display this help message and exit
e[0m
e[91m -l, --login NEW_LOGIN new value of the login name
-L, --lock lock the user account
-m, --move-home move contents of the home directory to the
new location (use only with -d)
-o, --non-unique allow using duplicate (non-unique) UID
-p, --password PASSWORD use encrypted password for the new password
-R, --root CHROOT_DIR directory to chroot into
-P, --prefix PREFIX_DIR prefix directory where are located the /etc/* files
-s, --shell SHELL new login shell for the user account
-u, --uid UID new UID for the user account
-U, --unlock unlock the user account
e[0m
e[91m -v, --add-subuids FIRST-LAST add range of subordinate uids
-V, --del-subuids FIRST-LAST remove range of subordinate uids
-w, --add-subgids FIRST-LAST add range of subordinate gids
-W, --del-subgids FIRST-LAST remove range of subordinate gids
-Z, --selinux-user SEUSER new SELinux user mapping for the user account
e[0m
e[91m
e[0m
And then it stops and brings up launch.json.

Not sure why this isn’t working anymore.

Steve

lucas_a.tx · April 18, 2023, 2:43pm

Hi @Evets ,

So I went back to v1 and am using the early access version. I did as you ask going back to v1, although there was no DOCKER_HOST": “tcp://” in the JSON file.

OK, no problem if don’t have the line starting with DOCKER_HOST, just skip the step about it if that’s the case.

I have the #include <gpiod.h> in one of my files, as a test. When it compiles I get:
fatal error: gpiod.h: No such file or directory
13 | #include <gpiod.h>

A library not being found in compilation time in V1 of the extension means that the SDK container doesn’t have it. I’ll go more into details below.

Which is what I was getting in the beginning when I wrote up this ticket. I have the -lgpiod in my Makefile, but this addition, only effects linking, not compilation, and it complains that it can’t find .

Yes, that’s right. I mentioned about the link parameter just to guarantee this part is correct.

I have searched my target device to see if there is a gpiod.h file there, and it doesn’t find one. When I take the #include <gpiod.h> out of my cpp file, I get:
/usr/lib/gcc-cross/aarch64-linux-gnu/10/…/…/…/…/aarch64-linux-gnu/bin/ld: cannot find -lgpiod
collect2: error: ld returned 1 exit status
make: *** [Makefile:105:] Error 1

You won’t find anything related to libgpiod in your target device, at least not directly. Let me explain:

In V1 of the extension, C/C++ projects use what is called an SDK container, which is an environment in your host computer made to cross-compile your code that will be deployed to the target SoM. All packages specified in devpackages will be installed in this SDK container, but you need to rebuild it each time you update devpackages.

Therefore, if you can’t compile your project due to a missing library, it most likely means that the SDK container for whatever reason doesn’t have the lib in question.

Just to be sure, did you add libgpiod-dev:arm64 to devpackages and rebuild your SDK container with F1 → “Torizon: Rebuild SDK and reload in container”, like shown in the picture below?

After selecting the option above you also have to choose yes in a confirmation pop-up that appears on the lower right of the VSCode window:

After doing that VSCode should restart. Wait until both the dev container and the extension load again before trying to debug.

With this I was able to compile and debug a sample gpiod app that blinks an LED connected to a GPIO pin.

Hope this helps you.

Best regards,
Lucas Akira

Evets · April 18, 2023, 6:08pm

@lucas_a.tx
Yes, I am aware of the need for rebuilding of the SDK, and I do it quite often. And yes, I have libgpiod-dev:arm64 in the extension under “Custom Properties/devpackages” and have had that since the beginning. I still can’t get it to find the gpiod.h file.
I have to ask, are you using the same target as I have? iMX8m plus? Up until now, I’ve been able to get most things to work, although I had some trouble with CAN since I couldn’t get it to load the can-dev lib as specified in the example, but I haven’t tried too much with that. I don’t have any actual calls for GPIO statements in my code yet,. as that was the next step.

Even worse is I can’t seem to get back to where I was beginning yesterday, where I could compile and deploy my code to the target system. If I pull the gipod.h out and remove the lgpiod from the linking I was able to get to the debugger on the target system. But now it appears it can’t connect because the container is wrong? Please see the above statement.

If you have any other suggestions to get this running again, I’d appreciate it.

Thanks,
Steve

Evets · April 18, 2023, 6:40pm

HI @lucas_a.tx
I went back though my docker checks to verify everything is working, and this is where things get weird. Under Configure Build Environment for Torizon Containers | Toradex Developer Center
it says the return for this command “docker run --rm -it arm64v8/debian arch” should be only “aarch64”, but when I run it, I get that, but also some pretext:
docker run --rm -it arm64v8/debian arch
WARNING: The requested image’s platform (linux/arm64/v8) does not match the detected host platform (linux/amd64) and no specific platform was requested
aarch64
Which is what I am seeing when I try to run debug my target. Is this a clue? What would cause this? I didn’t get this originally, I’m pretty sure.

Steve