[resolved] Naze32 auto bootloader problem

[presidenten]

A weird problem started happening a few days ago. Whenever I plug in the usb and press connect in the chrome baseflight application, all leds light up indicating bootloader mode and I cant connect.

A similar thing happens when I have my multiwii osd (minimosd) connected to rx when I plug in the battery. All leds light up and I cant arm or do anything with my radio.

I can get around the first issue by plugging in my battery to power up the hex before i plug the naze into my computer with
usb. I have tried reflashing the latest firmware using the chrome baseflight app, and erasing everything in the process without getting rid of the problem.

I can also get around the second problem by first plugging in the battery and then when powered up connecting the osd tx to the naze rx.

It is quite a hassle though, so I was wondering if anyone has had the same problem, and in that case, how did you fix it?

Or maybe Timecop knows instantly whats up by looking at the problem description???

[waltr]

You better post the exact firmware version as per CLI if you any help from TC.

[timecop]

Yes, running OSD together with USB is definitely not supported.

[presidenten]

Firmware version: Afro32 CLI version 2.2 Aug 3 2014 / 21:51:54
Board: full naze32


I guess I was a bit unclear. Running with OSD and plugging in USB is two separate scenarios

Scenario 1:
Osd _NOT_ plugged into serial pins. Trying to connect with usb lights up all leds and then this happens:

Code: Select all

21:00:26 -- Serial port successfully opened with ID: 6
21:00:36 -- No configuration received within 10 seconds, communication failed
21:00:36 -- Serial port successfully closed

Plugging in battery and then usb works. As you will see in scenario 2 I cant have the osd plugged in when connecting the battery as it instantly triggers bootloader mode.

Scenario 2:
Having osd plugged in when connecting battery (NO USB this time ... only connecting to get out to fly) all leds light up, and then radio wont arm or anything.
Plugging in battery when serial cables are not connected works. Then plugging in serial cables afterwards makes osd work.


So, as far as I can see, when the naze is getting serial tx when it powers up, no matter if it is through the usb port or through the rx pin, it goes into booloader mode. ...if this is what it means when all the leds are on.

Any ideas? I have not had this issue before. I noticed it a few days ago when I tried to connect my osd for the first time. Then when I wanted to connect to add the aux switch for osd mode I noticed the usb problem as well.

[timecop]

Something is sending 'R' to your hardware when you plug it in.

[presidenten]

Something is sending 'R' to your hardware when you plug it in.

Hmm ... Ill connect the osd to an arduino and check serial output. It will be a few days until I have time to do this though. Ill get back on the issue....

[timecop]

Just change your 'reboot_char' (or something smilar, do 'set reboot' or 'set reset' from 'R" to something else, like Z or some other character.

[presidenten]

Just change your 'reboot_char' (or something smilar, do 'set reboot' or 'set reset' from 'R" to something else, like Z or some other character.

...Sorry, Im a bit of a n00b here. Is it something I can do from the cli interface? Or do I have to edit some config.h file or anything similar in the firmware?

I dont find 'reset' or 'reboot' among the cli variables (https://github.com/multiwii/baseflight/wiki/CLI-Variables)..?

Edit: Found it ...

set reboot_character = 90

Set it to Z. No problem anymore