Hello all,
I made a huge mistake when attempting to create a custom firmware for the PX4FMU_v3 for the Pixhawk mini. While trying to set up TELEM1 to be used as SYS_COMPANION, I put mavlink stop-all in the rcS file. After uploading it to the board, the board did not boot properly. There are no tones, and the USB connection disconnects not long after connecting as can be seen here
[19468.224457] usb 3-2: Detected FT232RL
[19468.224657] usb 3-2: FTDI USB Serial Device converter now attached to ttyUSB0
[19474.096343] usb 3-6: new full-speed USB device number 90 using xhci_hcd
[19474.237730] usb 3-6: New USB device found, idVendor=26ac, idProduct=0011
[19474.237734] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[19474.237736] usb 3-6: Product: PX4 BL FMU v2.x
[19474.237738] usb 3-6: Manufacturer: 3D Robotics
[19474.237740] usb 3-6: SerialNumber: 0
[19474.238275] cdc_acm 3-6:1.0: ttyACM0: USB ACM device
[19478.834240] usb 3-6: USB disconnect, device number 90
The indicator lights for the Mini are below
In the picture above,
I/O:
- The I/O ACT LED is blinking
- The I/O B/E LED is solid
- The I/O B/E LED is on
FMU: - The FMU B/E led is off
- The FMU Power led is on
This indicates that the boot loader is fine, but there is a problem with the rc initialization.
I assume that the problem is that the rcS script is stopping all outgoing connections on bootup, so I cannot connect through USB or anything. To try to fix this, I created a extras.txt file in /fs/microsd/etc to attempt to start the connections again, but I have had no luck. It is possible that I am not using the proper commands in the extras.txt file, but I am not sure. The content of the file is below.
mavlink start -d /dev/ttyS0 -r 1000
mavlink start -d /dev/ttyS1 -r 1000
mavlink start -d /dev/ttyS2 -r 1000
Does anyone have any suggestions? Please and thank you.