write_eeprom locking up 18F2620

[evsource]

Hi,

I just upgraded from an 18F2520 to 18F2620. All I had to do with the code was change the header file for the chip (and a Brownout fuse value that was different). The code compiles, and everything seems to run fine except all my write_eeprom functions. As soon as it is called, the chip locks up and stays that way until the WDT does its thing.

I've looked through the datasheet, and the only thing I can see different between the chips with regard to the EEPROM is that the 2620 has 1024 bytes instead of 256. I thought maybe the write_eeprom function had to get a 16 bit value, and tried that, but as I expected, that didn't do anything.

Any ideas on what I could be missing?

[evsource]

Well, I jumped the gun posting. It turns out it *was* a fuse setting.

I'm using a bootloader, and the fuses set in the CCS code are not actually written to the chip. The fuse values come from the bootloader program. I haven't been able to nail down exactly what fuse setting it was that was causing the mentioned problem (along with some other bugs I was finding). I just went in and edited the fuse values in the ICSP program to match the fuse values that my CCS code was producing (to make a long story short, I programmed just the raw CCS program using the ICSP onto my chip, and everything ran fine. I opened the CCS program's hex file in the ISCP programmer to see what fuse values it had set, which included several values not specified in the code, i.e. all the fuse values. I then duplicated all those fuse values into my bootloader hex file, and voila!).

So hopefully if anyone sees any weird behavior similar to mine while using a bootloader, they might try what I did and get the problem fixed.