I am currently messing around with MTK GPS stuff and the binary protocol.
Assuming my APM2.0 GPS has the 1.6 loaded, i want to upgrade the GPS FW. Since the gps is directly mounted to the mainboard i don't know how to do it.
The APM wiki http://code.google.com/p/ardupilot/wiki/MediaTek gives no hints.
EDIT: SOLUTION FOUND:
I included a zip file with all the needed files and a complete guide below.
It contains basically the same files than the previous version but an extended guide and the source code.
Added German guide.
FTDI Hardwareflash on APM 2.0 (Set your FTDI to 5V, if you have one of these Breakoutboards)
1. Download the zip below to have all the files needed - and a flashguide.
2. Load MP and save all your parameters to a file (if desired).
3. Do Arduino / eeprom clear on your main CPU so that no serial traffic can disturb the process. Do not omit this step. It won't work with the arduino still talking on the serial line - i tested it. P.s. You can also use the precompiled hex from my post here: http://diydrones.ning.com/xn/detail/705844:Comment:1094234
4. Unpower APM for soldering. If FTDI connection is already established, powercycle to reset GPS to its' default state.
5. Locate the external GPS port (UART1). If you have not the right plug (like me) you have some solder pads right behind it. You will need GND/RX/TX. Look at this picture for the right connection: http://diydrones.com/forum/attachment/download?id=705844%3AUploaded...
Note: I labeled RX and TX relative to the GPS not the CPU (like printed on the PCB). I showed 3 points where you can get access to the important datalines, besides the obvious connectionport (that would be number 4:)).
6. Power APM Board, fire up the flashing soft and follow the documentation -> Point 8 in MTKFlashGuide2.pdf or point 7 in MTKFlashGuide2German.pdf. Reading the complete pdf is also ok.
7. Reload Arducopter FW on mainboard and reload your saved settings (if desired). Perhaps recheck calibrations (ACC etc.)
UPDATE 21/01/2013 - 02/03/2013
Here is a Must Try List - if you have a persisting flash problem (Thanks Anton for the idea)
- http://diydrones.ning.com/xn/detail/705844:Comment:1094071 (Thanks Anton)
- http://diydrones.ning.com/xn/detail/705844:Comment:1094290 (Thanks William Stoner)
- http://diydrones.com/xn/detail/705844:Comment:1097033 (Thanks Isaac)
- http://www.diydrones.com/xn/detail/705844:Comment:1097725 (Thanks Chris Webb // Mac running VMWare WinXP)
- http://diydrones.ning.com/xn/detail/705844:Comment:1140259 (Thanks "exaustgas" // Win serial port)
- http://diydrones.com/xn/detail/705844:Comment:1146635 (Thanks Cody // serial port in flashutil config)
- Try to rule out a driver/win firewall/administrator/viruskiller thing
Due to the outstanding work of Perecastor here: http://diydrones.ning.com/xn/detail/705844:Comment:1149155
We have a French guide now as well !!
I took the liberty to put it here as well.
Graham you can unbrick your GPS with a power cycle and then use the standard v1,0.0 flashtool and the procedure described here. Look at the image Randy has posted and attach the jumper after you install the blinky program
Thanks Craig, I bricked it a while ago (before APM2 came along) and have tried everything I can think of (and find on the 'net) to fix it. The blue LED is permanently on solid and the unit is completely unresponsive. I've tried with FDTI and the serial cable that came with the 3DR radios.Rx and Tx are connected correctly.
The other two work OK but again I cannot flash them, they do not respond to anything, not even basic command sentences, all they do is output GPS data. They are still on v1.4.
The one on my APM2 is fine but I'm waiting for a component to fix the APM2 to get it working again (don't ask...:))
Based on the great findings from the research of Craig Elder and Michael Oborne on the "can not flash" issue - i updated the zip file from the frontpost with a new guide!
The files are basically the same and the eeprom_clear - step is omitted (not neccessary). This time the sources are included in the zip archive.
I have an APM1 that is about 1 year old with the externally attached Mediatek GPS. I haven't used it for a while (since Arducopter 2.4 or so). Do I absolutely need to update the Mediatek FW in order to use Arducopter 2.8.1?
In the guide Rob mentions that "UpdateGPS.hex" can be used with APM1. Has anyone succesfully tried it?
And finally, since UpdateGPS.hex turns the APM into an FTDI adapter, would it be possible to use it to also update the MinimOSD FW?
The current Arducopter 2.8.1 in its stock version (hexfile loaded with MP) will not understand the output of the FW upgraded Mediatek GPS (1.9). So don't upgrade MTK FW yet, if you want to use stock - 2.8.1.
The "turnings your apm into a ftdi" - thing switches both ends (computer and serial/gps) to 38400Baud. So it will not work with minimosd (115KBaud) for that reason. Changing it to 115KBaud (and a different port) is simple but i doubt it will do the trick because during flashing the arduino of minimosd the real ftdi needs to do stuff on other lines (DTR etc). Maybe pressing reset on the minimosd when flashing starts could be a solution - i don't know.
Added German guide.
Not having a ublox, I think it is still better than an fw upgraded mediatek. You should be able to upgrade all your 3drobotics mtk 3329 with the new 1.9FW and see an improvement (except for the disabled one with ublox :)). But i would wait till arducopter 2.9.x is ready.
I haven't tried yet, but either way thank you very much for the great contribution and the extended and detailed handbook.
Happy new year!
Herzlichen Dank, Anderl!
I hope the guide is not too big so you will not have to do that: http://www.youtube.com/watch?feature=player_detailpage&v=4uZRYO...