Hi all,
I’m running the bench test suite (run_bench_suite.py, sih/flight_mission.py) on a CubeOrange+ under Ubuntu and ran into several issues related to serial port handling. I’d like to check whether these are known and what the recommended workflow is.
Issue 1: Port changes when a test reboots the board
Running ./run_bench_suite.py /dev/ttyACM0: one of the tests reboots the FC, the device re-enumerates as /dev/ttyACM1, and all remaining tests fail because the suite keeps using the old path.
Issue 2: by-id path works for tests but not for flashing
Using /dev/serial/by-id/usb-CubePilot_CubeOrange+_0-if00 avoids Issue 1. However, when the suite is asked to build the current tree and flash before testing, the board enters the bootloader and the by-id path changes to [bootloader by-id name, e.g. usb-CubePilot_CubeOrange+.x_BL_0-if00]. The flashing step then cannot find the board, so I had to build and flash manually via make ... upload.
Issue 3: Inconsistent results between runs
Results are not reproducible between runs; a test that runs in one attempt may not run (or fails) in the next. So far I got one good run on 1.18 and one mostly-working run on 1.17, but could not reproduce them.
Heartbeat is received, but the parameter read times out while 1.17 testing.