Failed to open serial port

[roboticsai]

I'm trying to flash rosflight on px4pilot following this tutorial. But after i load the local rosflight_NAZE_Release.hex file and Short the boot pins on your flight controller, unplug it, and and plug back in.
. i get the above error.

[superjax]

which error?

[superjax]

also, what is the CPU on px4pilot?

[prasgane]

@superjax I had the same problem @roboticsai is having. I was trying to flash a Flip32 F4 board with ROSFlight v1.3.0 (downloaded the .hex file from here). I used CleanFlight to flash the firmware and saw a Programming: SUCCESSFUL message but after flashing the firmware, the blue light would stop blinking and only the green flight would stay on. When you try to run the rosflight node, it would say something like failed to open serial port.

I fixed this by building the firmware from source as mentioned here and flashing the hex generated from this using CleanFlight (not the terminal). I would check if the .hex file is valid in the Releases page is still valid and if it works.

Edit: I am starting to think that its because I was trying to flash F1 firmware (rosflight_NAZE_Release.hex) on a F4 board. Think I should have flashed rosflight_REVO_Release.hex . Maybe @superjax can confirm this?

Prashant

[superjax]

Yeah, mixing up F1(NAZE) and F4(REVO) firmware definitely won't work. It'll say the flash was successful, but it won't run.

[superjax]

Another quick diagnostic is to watch dmesg while plugging in the flight controller. You should see messages as the device registers itself with the usb drivers.

dmesg -w

[prasgane]

Do you think it would be possible to upload the F4 firmware to the Release page? For someone following the instructions on the Flight Controller Setup page, its not really clear the REVO means F4 board and NAZE means F1. Additionally, since you are encouraging users to move to the F4 boards, it would make more sense to have the REVO version on that page than the NAZE version.

[bsutherland333]

I believe this has been done.