Closed GoogleCodeExporter closed 9 years ago
I had the same problem.
The problem cause with me is that the hex file contains data for addresses in
the range of the original interrupt vector table. Causing it to be overwritten
in the PIC. When using the bootloader, you should use the remapped IVT area and
not touch the original IVT.
I worked around this by adding the following code:
/* don't allow overwriting reset vector, interrupt vectors and bootloader */
if (addr < 0x2800) {
DEBUGMSG("IVT area, skipping");
return ERR_NONE;
}
at the top of the "issueBlock" function in hex.c.
This is not a nice fix, since it hardcodes the start of the program area in the
application, but it works for me.
Original comment by dr.obliv...@gmail.com
on 3 Sep 2010 at 3:23
hi,
is there anyway to see how to write hex files to PIC24FJ64GB002 or PIC18F2550
on youtube.com!!!!
i don't understand how to MCHPFSUSB v1.3
http://ww1.microchip.com/downloads/en/DeviceDoc/Release%20Notes%20for%20MCHPFSUS
B%20v1.3.htm
this the firs time i try, but i don't no how to begin!!!!
Original comment by yhu...@gmail.com
on 9 Nov 2010 at 5:42
Inappropriate hex file addresses cannot be detected by flashing code. This
should be fixed at the hex file generation end.
Original comment by fnargwibble
on 30 Jun 2014 at 7:32
Original issue reported on code.google.com by
yamamo2s...@gmail.com
on 10 Jun 2010 at 5:34Attachments: