View previous topic :: View next topic |
Author |
Message |
bschriek
Joined: 18 Dec 2007 Posts: 80
|
ICD-U64 EEprom problems 12f675 |
Posted: Mon May 25, 2009 8:52 am |
|
|
I have some troubles with storing data into the EEprom of a 12F675
CCloader does not accept the following instruction:
#rom 0xf2100={0x85}
According the CCloader File Info the file is CORRUPT.
Adress F2100 is out of range.
Other programmers don't have any problem with the Eeprom data table.
When I remove the #rom command I can program the controller without any problem.
What can I do?
You can try it by just adding the following command to your code
#rom 0xf2100={0x85}
Best regards,
Bas |
|
 |
PCM programmer
Joined: 06 Sep 2003 Posts: 21708
|
|
Posted: Mon May 25, 2009 2:02 pm |
|
|
Quote: | #rom 0xf2100={0x85}
According the CCloader File Info the file is CORRUPT.
Adress F2100 is out of range. |
Download the 12F675 Programming Specification from this page:
http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en010114
Look at this section on page 20:
Quote: | 4.3.2 EMBEDDING DATA EEPROM CONTENTS IN HEX FILE |
What does it say is the EEPROM address ? |
|
 |
bschriek
Joined: 18 Dec 2007 Posts: 80
|
Hello |
Posted: Tue May 26, 2009 1:11 am |
|
|
When the "f" is removed from the EEprom command the CCS Device Programmer accepts the command.
This works fine #rom 0xf2100={0x85} for a Galep programmer but the CCS Device programmer doesn't accept.
This works fine #rom 0x2100={0x85} for both the Galep and the CCS Device Programmer
What's the meaning of the "f" character?
Thank you for your help,
Bas |
|
 |
PCM programmer
Joined: 06 Sep 2003 Posts: 21708
|
|
Posted: Tue May 26, 2009 3:00 am |
|
|
It is bits 16-19 of an address and it does not belong there.
The address is 0x2100, not 0xF2100. |
|
 |
bschriek
Joined: 18 Dec 2007 Posts: 80
|
|
Posted: Tue May 26, 2009 3:49 am |
|
|
OK thank you. |
|
 |
|