CCS C Software and Maintenance Offers
FAQFAQ   FAQForum Help   FAQOfficial CCS Support   SearchSearch  RegisterRegister 

ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

CCS does not monitor this forum on a regular basis.

Please do not post bug reports on this forum. Send them to CCS Technical Support

ICD-U40 mysterious errors programming EEProm :-(

 
Post new topic   Reply to topic    CCS Forum Index -> General CCS C Discussion
View previous topic :: View next topic  
Author Message
grunwald



Joined: 12 Jan 2004
Posts: 3
Location: germany

View user's profile Send private message Visit poster's website

ICD-U40 mysterious errors programming EEProm :-(
PostPosted: Thu Jan 15, 2004 4:08 am     Reply with quote

Hello,

I use PCWH 3.184 to compile for a PIC18LF452 running at 3.3V with 20MHz. To debug and program the pic I use the integrated ICD-U40 interface V2.7 and the ICD Firmware 1.20 for PIC 16 and PIC 18.

My EEPROM declaration looks like the following:
#rom int8 0xF00000 = { 0xaa }
#rom int8 0xF00001 = { 0xab }
...
#rom int8 0xF000FF = { 0x11 }

The compilation is no problem. But if the Debugwindow programs the Device via the ICD-U40 the following errors Occur at the following Adresses:
0xF00043
Error: Could not write to target data EEPROM: Did noch ack message 45
0xF00087
Error: The ICD did not return the request amount of data
0xF000CC
Error: Could not write to target data EEPROM: Did noch ack message 45

If I change the order of the adress definitions in the sourcecode like the following,
there is no problem transfering the data to the PIC. Perhaps there is a timeout problem in the ICD-40 software or firmware??

...
#rom int8 0xF00044 = { 0xab }
#rom int8 0xF00043 = { 0x22 }
#rom int8 0xF00045 = { 0xac }
...
#rom int8 0xF00088 = { 0xab }
#rom int8 0xF00087 = { 0x33 }
#rom int8 0xF00089 = { 0xac }
...
#rom int8 0xF000CD = { 0xab }
#rom int8 0xF000CC = { 0x44 }
#rom int8 0xF000CE = { 0xac }
...

Could You please tell me what to do to bring my code back in order again?

PS. The ICD Control Program is of the Opinion that the PIC is running at
4.85V?!? But it IS running with 3.3V! I do not hope this is the problem
...

Thank You for Your support,
Bernd Grunwald
bgpartri



Joined: 12 Dec 2003
Posts: 6
Location: Vancouver, Canada

View user's profile Send private message Visit poster's website

PostPosted: Thu Feb 12, 2004 5:35 pm     Reply with quote

I'm getting the same problem. I will see if I can get it to work by rearranging it.

18F452 and 3.178, 3.184 tested
bgpartri



Joined: 12 Dec 2003
Posts: 6
Location: Vancouver, Canada

View user's profile Send private message Visit poster's website

PostPosted: Thu Feb 12, 2004 6:40 pm     Reply with quote

Yes, it works if you make it non-contiguous.

#ROM 0xF000C4 = { 0x696C, 0x6574, 0x6445, 0x7469, 0x4C20,
0x776F, 0x5320, 0x4550, 0x6964, 0x2074,
0x6948, 0x6867, 0x5320, 0x0050
}
#ROM 0xF0007A = { 0x6863, 0x7420, 0x206F, 0x654D, 0x6574,
0x7372, 0x7753, 0x7469, 0x6863, 0x7420,
0x206F, 0x6546, 0x7465, 0x6F4C, 0x2077,
0x5053, 0x6948, 0x6867, 0x5320, 0x4550,

#ROM 0xF0003E = { 0x6374, 0x2068, 0x6F74, 0x4F20, 0x5343,
0x6964, 0x2074, 0x6F43, 0x766E, 0x7265,
0x4576, 0x6964, 0x2074, 0x6142, 0x6B63}
0x6977, 0x6374, 0x2068, 0x6F74, 0x4320,
0x5343, 0x7465, 0x7075, 0x6544, 0x6966,
0x656E, 0x4720, 0x7361, 0x6F43, 0x736E,
0x7265, 0x6176, 0x6974, 0x6D73, 0x6142,
0x6B63, 0x696C, 0x6574, 0x7753, 0x7469}
Display posts from previous:   
Post new topic   Reply to topic    CCS Forum Index -> General CCS C Discussion All times are GMT - 6 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group