• State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 22 subscribers
  • Views 2573 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

const DATA at absolute address in CODE seg

John Penvenne

Hi all, My goal is to put a few constants in the code segment at compile time so they are stored in the program flash when the SiLabs 'F122 is initialized via JTAG.

const UCHAR code ucTBD = TBD_VAL;

seems to work but I'd like to put the data at a known address so I can read it explicitly with a MOVC-type flash read. But

const UCHAR code ucTBD _at_ 0x6000 = TBD_VAL;

is unacceptable because an absolute specifier is illegal.

Without the "_at_", the linker puts the data down with the ISR vectors but I need it to reside in flash space that I am comfortable modifying.

It seems to work if I declare ucTBD inside a function and assign an absolute location to that function. Is that an acceptable and reliable method?

Thanks in advance for any advice,
John

Ref:
typedef unsigned char UCHAR;
#define TBD_VAL (0x00)

Parents
  • 0 in reply to Drew Davis

    "This feature is often requested on the board."

    A common reason is for a version code - placed at a known location so that it can easily be found on a PROM programmer.

    However, I don't see anything in the original post that actually requires fixing at an absolute address.

    Perhaps John could explain?

Reply
  • 0 in reply to Drew Davis

    "This feature is often requested on the board."

    A common reason is for a version code - placed at a known location so that it can easily be found on a PROM programmer.

    However, I don't see anything in the original post that actually requires fixing at an absolute address.

    Perhaps John could explain?

Children
No data