We are trying to port our current setup from a raspberry pi to a Colibri iMX8X and a Aster carrier board.
The product description says “The Aster Carrier Board has headers compatible with Arduino Uno and Raspberry Pi (RPi) maker boards, thus enabling users to use a variety of 3rd party modules/add-on boards like Arduino Shields and Raspberry Pi adapter boards.”… however we are struggling to find any straightforward documentation on this.
We seem to understand that the the GPIO pins can be accessed through sysfs which would make the port quite easy. We can see the GPIO seems to be mapped differently (see GPIO (Linux)). But even using the method described there, we don’t seem to be able to access the correct pins.
Is there somewhere at some layer of the OS where the GPIO pinout is mapped?
Also we have some drivers for a raspberry pi hat that communicates via SPI through the GPIO headers. Would this need to be recompiled with the Toradex toolchain?
Is there any other useful resource that can help with the transition from RPI to the Aster carrier board?
You can check the available drivers on your image by running zcat /etc/config.gz | grep -i driver_name. If your driver names are not listed there, you’ll probably need to recompile the image. Do you know which drivers would you need already?
I’ll try to find articles and posts on the community on the meantime.
Yes we are able to access GPIO using the suggested method!
However we have now the problem that it seems like there is no driver for the spi controller on the TorizonCore kernel for the our Aster/iMX8Xsetup. Do we need to build our own image of TorizonOS to enable it?
Do you know what drivers would you need on the Kernel? I can try to double-check it for you. If they’re indeed not enabled, the best option would be for you to compile your own image of TorizonCore to test and check if everything works Building External Kernel Modules With Torizon | Toradex Developer Center. Then, we can ask the team to enable them by default on the next builds.
Sorry for the delay - we managed to make the spi comms work.
The issue was that the spi device would not show up at all under /dev/ …
we managed to test spi comms reflashing the unit with the Embedded Linux image and then manually edit the overlay file under /boot/overlays.txt adding colibri-imx8x-eval_spidev_overlay.dtbo to it. And it all seems to work well.
In the long run, we want to use TorizonCore, but we will have to create a ad-hoc image with the right overlays.
We were just hoping to be able to quickly prototype and test the hardware using the default image, without having to build our own…but we managed somehow!