• State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 22 subscribers
  • Views 1758 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

Why IDATA in MAIN

erik malund

I am trying to find the best places to save some DATA storage to use it in a more speed sensitive area.
Looking at the map, I see the following:

            TYPE    BASE      LENGTH    RELOCATION   SEGMENT NAME
            -----------------------------------------------------

            * * * * * * *   D A T A   M E M O R Y   * * * * * * *
            REG     0000H     0008H     ABSOLUTE     "REG BANK 0"
            REG     0008H     0008H     ABSOLUTE     "REG BANK 1"
            REG     0010H     0008H     ABSOLUTE     "REG BANK 2"
            DATA    0018H     0003H     UNIT         _DATA_GROUP_
            IDATA   001BH     0005H     UNIT         ?ID?AVMAIN
            BIT     0020H.0   0001H.2   UNIT         ?BI?AVMAIN
Main has NO idata storage and one BIT.
I verified the idata, there is no @r in the assembler source.
what is the IDATA attributed to main?

Erik

Parents
  • 0 in reply to Drew Davis

    Does anyone know if there is a way to get the compiler to create separate segments for variables in a single source file as Drew describes? I usually wind up forcing variables into the space below 0x20 using the _at_ keyword - but suffer from the infamous 'can't initialise variables declared with _at_' problem.

    Stefan

Reply
  • 0 in reply to Drew Davis

    Does anyone know if there is a way to get the compiler to create separate segments for variables in a single source file as Drew describes? I usually wind up forcing variables into the space below 0x20 using the _at_ keyword - but suffer from the infamous 'can't initialise variables declared with _at_' problem.

    Stefan

Children
No data