Keep container running for px4 update in Jamal-pro

Removed old shell commands which were for the update with old
bootloader and didn't work anymore.

Added "tail -f /dev/null" to keep the container running in drone
so the px4 binaries are available when the update happens.

Tools/px_uploader.Dockerfile

@@ -2,24 +2,8 @@ FROM python:alpine3.14
 
 ARG saluki_fpga_directory
 ARG SALUKI_FILE_INFO_JSON=saluki_file_info.json
-
-# run this with something like:
-#
-#   $ docker run --rm -it --network=host --device=/dev/ttyS7:/dev/px4serial px4-fw-updater \
-#     --udp-addr=192.168.200.101 \
-#     --udp-port=14541 \
-#     --port=/dev/px4serial \
-#     --baud-bootloader=2000000 \
-#     px4_fmu-v5_ssrc.px4
-
-# This gets built in environment with somewhat unorthodox paths:
-# - The build context is at /
-# - The repository itself is mounted in /px4-firmware/
-# - Built firmware files are in /bin/
-#
-# ("/" above is relative to GH action runner home dir)
-# (see .github/workflows/tiiuae-pixhawk.yaml)
-
+ARG PX4_EXPORT_DIR
+ENV PX4_EXPORT_DIR=$PX4_EXPORT_DIR
 
 COPY $saluki_fpga_directory /firmware/fpga
 COPY $SALUKI_FILE_INFO_JSON /$SALUKI_FILE_INFO_JSON

Tools/px_uploader.entrypoint

@@ -1,13 +1,16 @@
 #!/bin/sh -e
 
-aframe=""
-if [ ! -z "$AIRFRAME" ]; then
-	aframe="--airframe ${AIRFRAME}"
+# export px4 files if the container is started with the PX4_EXPORT_DIR
+if [ -n "$PX4_EXPORT_DIR" ]; then
+    echo "Exporting PX4 files to $PX4_EXPORT_DIR"
+    echo "/px4:"
+    ls -al /px4/
+    echo "$PX4_EXPORT_DIR:"
+    ls -al $PX4_EXPORT_DIR
+    cp -r /px4/* $PX4_EXPORT_DIR
+    echo "done"
 fi
 
-mode=""
-if [ ! -z "$FLIGHT_MODE" ]; then
-	mode="--flightmode ${FLIGHT_MODE}"
-fi
-
-/bin/px_uploader.py --port=/dev/px4serial --udp-addr=192.168.200.101 --baud-flightstack=57600,115200,1000000,2000000 --baud-bootloader=2000000 px4_fmu-v5x_ssrc-*.px4 ssrc_saluki-v1_default-*.px4 ssrc_saluki-v2_default-*.px4
+# keep the container running so px4 update can get the
+# px4 firmware files from the container
+tail -f /dev/null