AutoQuad Forum

Hi Felix,

I had also this error almost every time when I first reset the AQ in boot mode (only red LED is ON) then click flash firmware and then clich OK. From my experience with QGC, I seen that I can always flash from first time if following this steps:
1. Select firmware
2. Click "Flash firmware" button
3. ONLY NOW reset AQ in BOOT mode
4. Click "OK" in the confirmation window.

Regards,
Sergiu

Sergiu, thank you, that method worked after a couple of attempts.
Whew, I thought I was going to be frozen in time

Regards,
- Felix

Also had this problem on a fresh board.
Should add to the wiki

Hello,

I am trying to flash a new board with DIMU 1.1 already mounted.

On my OSX I receive the following error:




On my Windows 8.1 machine I receive this error:




OK, here is what I tried to avoid the problem:
- Tried method 2 (First Click “Flash firmware” button, only now reset AQ in BOOT Mode"
- Tried different hex files
- Tried many times
- Searched the forum and WIKI


Finally, I gave up.

Comments appreciated.

Cheers,
Stefan

I would start by trying another USB/serial adapter or look for connection problems in the wiring - the SERIAL_ERR_NODATA error could indicate a connection problem ...

Are you keeping the bootloader jumper closed the whole time, or just at bootup? You need to keep it closed until flash starts.

Hello Jussi,

Thank you for your quick reply.

- I have checked the connections with the voltmeter, looks fine.
- I removed the jumper at the moment the flash procedure started.

However, the result is still unchanged. Alas, I haven't got another USB/serial adapter.

Thanks anyway.

Stefan

Wondering, thought bootloader is on 57600 baud. Normal the qgc should choose this by them self.

Hello Sandmen,

I tried all available baud settings including 57600. Seems that qgc on OSX does not force 57600 baud. I have just tried a native WIN7 PC. Same result.
As I have now two new AQ6 DIMU sitting here which are producing the same negative result I do, for the moment, rule out a bad board situation. Hence, either I am too stupid (which I never rule out) or there is something wrong with the connection. As posted, the cable itself seems to be fine. Maybe the Flyduino USB UART - CP2012 is the culprit. If not advised differently I will get a replacement and see what happens.