AdamLaurie / mphidflash

Automatically exported from code.google.com/p/mphidflash
GNU General Public License v3.0
31 stars 19 forks source link

Can't write hex to PIC24FJ64GB002 #1

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
I use PIC24FJ64GB002 and USB Framework v2.7 in Microchip Applications Library.
I wrote the hex of HID Bootloader and I confirmed to be able to wrote 
application hex
with HIDBootloader.exe. The operation is no problem.

Now I think I want to mphidflash on Mac OS X 10.6.3. So I downloaded the latest 
ver.
from SVN and installed.

The writing is maybe OK but the verification is failed. Additionaly an 
application program
doesn't operate.

I attached debug log. Please give me any advice.

Thanks.

Original issue reported on code.google.com by yamamo2s...@gmail.com on 10 Jun 2010 at 5:34

Attachments:

GoogleCodeExporter commented 8 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

GoogleCodeExporter commented 8 years ago
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

GoogleCodeExporter commented 8 years ago
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