18f EEPROM problems solved yet?

[Tyler Coen]

Hi,

Does anyone know if the eeprom functions for pic18f devices worked in any of the recent compilier versions? I've noticed many past threads about the issue. I've tried version 3.092 and it's still not working.

Or does anyone have a work around for this problem?

Thanks,

Tyler
___________________________
This message was ported from CCS's old forum
Original Post ID: 5050

[Wenyong Wu]

I think you have to write your own eeprom function. My own functions work perfectly OK. Don't use their functions, they just gave some general eeprom but that doesn't apply to all the eeprom. So, I suggest you to write your own. Just use i2c_read, i2c_write, i2c_start and i2c_stop. These four commands are enough for you for most of the eeprom!

Wenyong Wu

:=Hi,
:=
:=Does anyone know if the eeprom functions for pic18f devices worked in any of the recent compilier versions? I've noticed many past threads about the issue. I've tried version 3.092 and it's still not working.
:=
:=Or does anyone have a work around for this problem?
:=
:=Thanks,
:=
:=Tyler
___________________________
This message was ported from CCS's old forum
Original Post ID: 5056

[Mark]

Look at one of my earlier posts if you are trying to use the internal EEPROM.


:=Hi,
:=
:=Does anyone know if the eeprom functions for pic18f devices worked in any of the recent compilier versions? I've noticed many past threads about the issue. I've tried version 3.092 and it's still not working.
:=
:=Or does anyone have a work around for this problem?
:=
:=Thanks,
:=
:=Tyler
___________________________
This message was ported from CCS's old forum
Original Post ID: 5059

[Tyler Coen]

Many thanks
___________________________
This message was ported from CCS's old forum
Original Post ID: 5061

[Hans Wedemeyer]

Mark Wrote:
:=Look at one of my earlier posts if you are trying to use the internal EEPROM.

My comment and question.
This appears to be another example of a broken version of PCH.

For the people that have 30 day download rights and in my case where the 1 year sub just ran out, do we simply live with a broken product or will CCS allow us to down load at least one version that is not broken !

I understand CCS charging for new features, that is justified. Howevewr when a product does not output code for a built in function it would seem to me it is broken and CCS has an obligation to "make good".

I know it has been possible to call and ask.... the point is that should not be how it's done....

Your comments on this subject would be very welcome...
___________________________
This message was ported from CCS's old forum
Original Post ID: 5075

[burnsy]

Hi Mark,

do you know where your earlier post regarding 18F internal eeprom writing is located? I have looked, but can't seem to find it anywhere.

I am having dramas writing myself. Hanging, and other faults

regards,

Jason
_________________
This is the last code change until its ready....

[PCM programmer]

Do you know that you're responding to a 3-year old post ?

[future]

This explains why he was using an old compiler version.. hahaha

[Mark]

http://www.ccsinfo.com/forum/viewtopic.php?t=10299&highlight=eeprom
http://www.ccsinfo.com/forum/viewtopic.php?t=10319&highlight=eeprom

[burnsy]

Ripper Mark,

thanks very much. I know it was an old post. I looked and looked but could not find it.

cheers,

jason
_________________
This is the last code change until its ready....