Is there a way to test a minimOSD without connecting it to an APM?
A while back I bricked an APM when I (I think) switched the power while plugging in my MinimOSD (+ -> -). Now, the APM has been replaced but I would like to test the minimOSD before plugging it into the new APM. I'm guessing it is fried also, but I may have bricked the APM another way, so I would like to try to test the OSD to see if it is salvageable The last thing I want to do is brick the new APM with a screwed up minimOSD (if that's even possible).
I actually wanted to know the answer to this. Too bad no one answered you. I'm currently sitting here with two MinimOSDs--a jDrones and a 3DRobots and neither one works. The 3DR I think I destroyed by overheating it when soldering the jumpers, and then the jDrones now has a corrupted bootloader, though I don't think it even worked before that happened.
Did you ever figure it out?
No I haven't figured this out, but I haven't thought much about this since I resorted to this posting. With an osd that works, I might try to see if some sort output is on-screen without an APM attached. If that's the case, then it should be a simple test, if not... maybe somebody can chime in.
Thanks for refreshing this thread... I had totally put this problem underneath several others. :)
Another question (for you) is, can you re-flash the bootloader on an MinimOSD??
Did you try and read it using the minimosd tool via a FTDI cable ?
Oh my gosh, this would be a good first step, wouldn't it. I tried last night and it was a no go. It gave me errors about the boot loader. I soldered the pins on to connect a USBasp, but left my programmer at my office. I'll try to reflash the atmega tonight. Thanks.
Last night I had some success. I want to remind you of the state it was in before. Constantly flashing orange light, could not communicate at all.
I plugged in the programmer and used AVRDUDE to reset the fuses. Those code lines are:
avrdude -c usbasp -p m328p -U lfuse:w:0xFF:m
avrdude -c usbasp -p m328p -U hfuse:w:0xDA:m
avrdude -c usbasp -p m328p -U efuse:w:0x05:m
I then went into the Arduino software and immediately noticed that the orange light was behaving normally again. I set my com port, the proper board, and the programmer (USBASP). I then proceeded to burn the bootloader. It succeeded.
After that, feeling really pleased, I burned the firmware using Arduino. This, for the first time, completed!
And then the orange light stopped flashing. uploaded a sketch that clears the eeprom and then tried again. All of these succeeded. But no orange light.
I went into the GUI for this particular firmware (KV Team for MultiWii) and it recognized the board but I could not write any options. And the orange light never flashed.
So we're back to typical voodoo and nonsense, which is why I hate computers. I want to say that I am a person who hates computers but also owns several programmers, like the USBasp! Whatever the case, I will never know if the board is actually broken because of the power surge, or if it still has hope and I just don't know how to keep pushing the Arduino programming.
This sucks. But it should give you hope. I certainly brought it mostly back from the dead. But "fully dead" and "partly dead" are still "not alive."