Search found 9 matches

Thanks to CCS tech support for the following:

The #ID CHECKSUM directive spreads the checksum as
follows in memory <PIC18F1X20>:

0x200000....checksum hexadecimal character #1 in the low ...

Just updating the post, the compiler update did not change anything.

Let me go back and give a little more detail first.....

My goal is to be able to identify the current programming of the processor via a run time function that will read the same checksum value tha ...

In the last post, I noted that the data values are separated

:020000040020DA
:08 0000 00 01F0 09F0 07F0 0AF0 1D

?indicating that there appear to be 16 bits in the id memory locations 200000. ...

BTW, read the thread. Doing it from inside the program will probably work by using romCheck=getenv("ID")?

First, the format of the hex file:
In extended addressing mode I have not found any exampl ...

Hello;

I have looked at prev posts on this and have not found my answer. More than likely I have not looked hard enough.

I am using CCS v3.178 compiler, MPLAB 6.51, ccsmplab plugin v6.
I have ...

HELLO;

I AM LOOKING AT THE 18F1320 SPECIFICALLY AT THE NEW POWER MANAGEMENT MODES USING THE INTERNAL RC. I AM INTERESTED IN HALTING THE PROCESSOR BUT KEEPING TIMER1 COUNTING AT A 31.5KHZ RATE. IT ...

Thanks for reading. Hope this helps anyone who is interested.

Apparently when the MPLAB folks say to need to read the EEPROM they are talking about reading it with the PROGRAMMER. So after you prog ...

Hello;

I do not think I have a problem writing/reading to EEPROM with PIC16F877 in PICDEM2+ however when I look at the EEPROM window in MPLAB I cannot see the real (or my imagined) contents of th ...