Sean Marquez

Thanks @codeflight1, I see the GPS tutorial is for creating a component that defines ports for supplying buffers to a UART driver. Will this port work for I2C as well?

Installing `gcc-arm-linux-gnueabihf` with `apt` on Ubuntu puts the binaries in `/usr/bin`, so I set `RPI_TOOLCHAIN_DIR` to `/usr`. After doing so, I also had to install `g++-arm-linux-gnueabihf` to resolve a CMake...

Is there a way to run the RPI CI build locally? Working on a PR to close this issue

I updated `build-test-rpi.yml` and `RPI.bash` to reflect the recommended installation steps for `gcc-arm-linux-gnueabihf` and `g++-arm-linux-gnueabihf` and pushed to github to trigger the CI, but I'm getting this error I don't...

I tried setting the `RPI_TOOLCHAIN_DIR` environment variable in [raspberrypi.cmake](https://github.com/capsulecorplab/fprime/commit/c16cfac176a1fefa66b7afda1025ba5bf99c9fac), but I'm still getting a CMake error that it can't find the RPI toolchain. Error from [rpi-logs artifact](https://github.com/capsulecorplab/fprime/actions/runs/1613420721): ``` CMake Error...

Apologies for the delay, but replacing the [raspberrypi.cmake](https://github.com/nasa/fprime/blob/devel/cmake/toolchain/raspberrypi.cmake) with [@astroesteban's raspberrypi.cmake](https://github.com/nasa/fprime/issues/1163#issuecomment-1007810914) seems to have resolved the aforemented [cmake error](https://github.com/nasa/fprime/issues/1163#issuecomment-999941989) without having to set the `RPI_TOOLCHAIN_DIR` environment variable. https://github.com/capsulecorplab/fprime/commit/51f50064588159345cfc26838b108d789076bb9e

Desperately attempting to get @astroesteban's [raspberrypi.cmake](https://github.com/nasa/fprime/issues/1163#issuecomment-1007810914) system to work, but ran into #1446

@LeStarch Managed to successfully use @astroesteban's [raspberrypi cmake build system](https://github.com/nasa/fprime/issues/1163#issuecomment-1007810914) to build and run both the blinking LED example and Math components for performing math operations on my Raspberry Pi...

Any particular reason we'd want the toolchain to compile for 64-bit ARM as opposed to 32-bit? I was under the impression it should use the 32-bit, since that's what the...

In either case (32-bit or 64-bit), any preference as to where we want to be downloading the ARM toolchain from? I'm thinking we should update the CI to download/extract/install the...