Closed GoogleCodeExporter closed 9 years ago
This is because the bootloader expects flashing commands but all it sees is
NMEA stuff coming from the GPS. The Arduino bootloader solves this by timing
out after a while, but the Uno32's doesn't, so it gets stuck in a never ending
loop.
See this related post I wrote in the chipkit forums:
http://www.chipkit.org/forum/viewtopic.php?f=16&t=936
Summing up, there are two options:
1. Insert the gps after the Uno32 has booted up, like you are doing now.
2. Or flash a new bootloader in your Uno32 that fixes this problem. You need a
Pickit3 (or similar debugger) to do that. Grab the .hex from:
https://github.com/chipKIT32/pic32-Ardu ... production.
Original comment by jmart...@gmail.com
on 20 Nov 2012 at 11:56
Sorry, the .hex link was broken in my previous comment:
https://github.com/chipKIT32/pic32-Arduino-Bootloader/tree/master/dist/uno-128k/
production
Original comment by jmart...@gmail.com
on 20 Nov 2012 at 11:59
I actually had to flash
https://github.com/jamarju/pic32-Arduino-Bootloader/tree/master/dist/uno-128k,
but it appears to be working great. Thanks man!
Original comment by ger...@gmail.com
on 27 Nov 2012 at 2:17
Original issue reported on code.google.com by
ger...@gmail.com
on 18 Nov 2012 at 12:31