Replies: 2 comments 5 replies
-
|
In the container, you need to make sure to upgrade the Python packages. Something like this should do it: |
Beta Was this translation helpful? Give feedback.
-
|
This helped clear the warnings. However, I get the same error about not finding the Makefile, concretely: gmake: Makefile: No such file or directory It is worth mentioning as well that when I run [ERROR] /project/build-fprime-automatic-aarch64-linux already exists. Maybe that existing copy of the Thank you in advance for your help so far! |
Beta Was this translation helpful? Give feedback.
-
|
UPDATE: I ended up cross compiling in a linux machine. New issue: When executing the deployment on the RPI5, I am getting the following warnings at the start and the LED does not blink despite seemingly receiving the commants and logging events correctly... are these two things linked? I do not get this warnings when running the fprime gds locally in the same deployment...
This is the log output I get from the RPI in the ssh shell: [NOTE] Task Permissions: [WARNING] cmdDisp stack size of 65536 is too small, clamping to 131072 |
Beta Was this translation helpful? Give feedback.
-
|
@thomas-bc any ide what might be happening here? I have been debugging but still got nowhere... I tried copying the entire fprime project to the RPI5 instead of just the deployment build artifact but still nothing... |
Beta Was this translation helpful? Give feedback.
-
|
@aliaga17 these warnings would not cause the LED issue, I don't think. Did you triple-confirm the LED is wired correctly and functioning? Could you try confirming whether the GPIO is toggling with a multimeter or something? What model of RaspberryPi is this? Other issue could be the pinout numbering/mapping on your model... |
Beta Was this translation helpful? Give feedback.
-
|
Yes, everything should be well connected. I tried with the multimeter and there is no voltage toggling coming out of the GPIO, nor with the LED connected or with the port in open circuit. I have also tried to open the gpio port using "/dev/gpiochip0" instead of "/dev/gpiochip4", as gpio port 13 appears under that chip when running "gpioinfo" on the rpi (I am using an RPI5). It still didn't change anything... As per the pinout, everything seems to be ok, as when I test the 5V and 3V3 ports of the RPI with the multimeter and with the LED, they work fine and the LED turns on. |
Beta Was this translation helpful? Give feedback.
-
|
Solved! Turns out that running the command "scp -r build-artifacts/aarch64-linux/LedBlinker/ teralink@10.75.14.131:deployment" when there was already a "deployment" folder in the RPI, it was creating a new "LedBlinker" subfolder within the "deployment", thus I was always using the old deployment which had a bug. So basically, I had to delete the previous "deployment" folder in the RPI before copying a new version of the deployment in a newly created "deployment" folder. Thank you @thomas-bc for your help and guidance! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, after following all the cross compilation tutorial to build the led blinker project for a raspberry pi, when running "fprime-util build aarch64-linux" I get the following:
[WARNING] fprime-fpp has unexpected version. Expected: 2.3.1 found 1.2.0
[WARNING] fprime-tools has unexpected version. Expected: 3.6.1 found 3.2.0
[WARNING] fprime-gds has unexpected version. Expected: 3.6.1 found 3.2.0
gmake: Makefile: No such file or directory
gmake: *** No rule to make target 'Makefile'. Stop.
[CMAKE] CMake failed to detect target, attempting CMake cache refresh and retry
[CMAKE] CMake failed to detect target, attempting CMake cache refresh and retry
[ERROR] CMake erred with return code 2
Any help?
Beta Was this translation helpful? Give feedback.
All reactions