A really tricky one I have not come across before:
- two NEW minims won't talk to GUI via FTDI cable.
- ok, bootloader issue! I used USBasp and Arduino to clear EEPROM and burn bootloader.
- still no connection to GUI via FTDI cable (BUT another minim connects justs fine, so FTDIs and cables are ok): bootloader problem
- now I used an Arduino Mini Pro board to connect the two minims (one at a time) to GUI. Bingo: no problem! Firmware loaded, I can read and write to the minims. Problem solved?
- sadly no! Put the minims into my quad and no OSD, just plain video.
- and: the minims with firmware on that connect just fine to GUI via Arduino Pro Mini still show bootloader issue when I try to connect to GUI via FTDI cable.
What is going on?????
Notes: I used three minims of same type (Witespy), two new ones out of the satchel with problems, another one with same date printed on that works fine. I used two FTDI cables. My FTDI cables work fine with the third minim, they are not bricked.
This is intriguing me and turned into some sort of detective story. I even looked at the voltages supplied to the minims. The FTDI supplies 4.8v, the Mini Pro only 4.3v. Is this important? But when I jumper the FTDI down to 3.3v I still get the same bootloader issue trying to connect to GUI. The bootloader issue is there though even with just the FTDI connected to GUI without the minim. So it doesn't tell you a lot....
Replies