We can't use the original docker service file on voxl as a few extra steps are required for docker to run on our platform. Both the installation of the voxl-docker-support package and execution of voxl-configure-docker-support.sh try to stop and disable docker.service as it gets in the way.
Instead it is replaced by our own service files which should be enabled by the voxl-configure-docker.sh script. What is the output you see when you run this script?
You need to make a little wiring harness to connect the JLink to J2
You don't need to the debug console (pins 2/3) for flashing, but if you are making a harness might as well and you can use it for debugging bootup if needed.
Thank you, it works now. I did not think about using my local mavros as connection link between voxl and QGroundControl.
I changed the port. The original issue was a binary installed mavros which crashed when using a gcs_url. So I thought it was a configuration problem but building mavros from source and running with your proposed configuration worked. Thank you again!
Our flight controller is a little unique in that it can't be powered off USB so yes, it will lose power and connection during the standard process. (The reason being our Flight Controller shares the 5V rail with the companion computer and 500mA off USB won't suffice!)
Can you connect the Flight Core to QGroundControl using USB, and then go to the MAVLink console? You can run rc_input status from there and check if you see anything:
