diff --git a/docs/Tutorials/CrossCompilationSetup/ArmLinuxTutorial.md b/docs/Tutorials/CrossCompilationSetup/ArmLinuxTutorial.md index 94adf9111a..418bd7c6ce 100644 --- a/docs/Tutorials/CrossCompilationSetup/ArmLinuxTutorial.md +++ b/docs/Tutorials/CrossCompilationSetup/ArmLinuxTutorial.md @@ -21,25 +21,26 @@ dictionary from the build above (`--dictionary ./build-artifacts/ ```sh # For in-person workshops and ARM 64-bit hardware # In: Deployment Folder -fprime-gds -n --dictionary build-artifacts/aarch64-linux/dict/.xml +fprime-gds -n --dictionary build-artifacts/aarch64-linux/dict/.xml --ip-client --ip-address # For ARM 32-bit hardware # In: Deployment Folder -fprime-gds -n --dictionary build-artifacts/aarch64-linux/dict/.xml +fprime-gds -n --dictionary build-artifacts/aarch64-linux/dict/.xml --ip-client --ip-address ``` +> This depends on a flight software deployment that uses TcpServer as the communications driver implementation. In another terminal SSH into the device and run the uploaded software: ```sh ssh @ -sudo deployment/bin/ -a -p 50000 +sudo deployment/bin/ -a 0.0.0.0 -p 50000 ``` -> User should fill in the username and device address above and ensure the executable is supplied the address of the host computer (that ran the GDS). +> User should fill in the username and device address above and ensure the correct executable is supplied. -> If the device does not connect, ensure that the firewall port 50000 is open on the host computer. +> If the device does not connect, ensure that the firewall port 50000 is open on the flight computer. ## Troubleshooting If you are getting errors for missing Libc.c files, make sure when you generate that the logs show that it is using the `/opt/toolchains` path and not `/bin`. You can additionally verify that the correct toolchain is being used by watching -the logs scroll by when you initially `fprime-util generate `. \ No newline at end of file +the logs scroll by when you initially `fprime-util generate `.