• State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 21 subscribers
  • Views 1977 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

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

Load file to specific memory area

M. Sure

Hi
i try to use the debugger script in order to stimulate data into my ADC peripheral. this is the script i wrote:

/* Map the user specific memory space */
MAP S:0, S:0xFFFF READ WRITE

/* Store the content of the S: Space */
LOAD INPUTDAT.HEX S:0, S:0xFFFF

/* Define a global variable for indexing */
DEFINE unsigned int GetValIdx

/* Define a breakpoint at specific location */
BS 0xff000449, 1, "G_Data= ((100*_RBYTE (S:0 + GetValIdx++)+10*_RBYTE (S:0 + GetValIdx++)+_RBYTE (S:0 + GetValIdx++))<<2"
GetValIdx++

the problem is that although file "INPUTDAT.HEX" exists in the same folder where the project is located, the file is not loaded into the specific memory area S:

more than that, when i try to manually change the values in S: through the memory map window, my changes are ignored with the following error message:
*** error 57: illegal address (C:0x0001)

as mentioned before i try to change S:0x0001, not C:0x0001

Parents
  • 0 in reply to ImPer Westermark

    thnx Per
    you indeed made your point. i'm using HEX format which is called (in the application i'm using to generate it) "Intel Hex Code-8 bit".
    it looks like this:
    :02000004F80002
    :1000000031353031333131323731323831303731C7
    :1000100032333133313132333132363132333132BE
    :1000200038313134313131313135313231313237AA
    :100030003133313132323131383131373131373199
    . .
    . :090900003131343131343131342C
    :00000001FF

    i can manage to find which header i should use in order to locate the file to the place in the memory i intend to.

    i'm working with SiLab 8051F931 which has 64KB code and 4KB RAM

    the mapping includes I:, C: and X:

    can i use, when working in debug mode with USB debug adapter, the S: memory space? can the debugger work with virtual memory that is located outside the micro (i mean in the PC)?

    i have plenty of free memory in C: in case it's required i can locate the data i need over there, but if possible i'd like to use S: (assuming it is indeed virtual, external to the chip).

Reply
  • 0 in reply to ImPer Westermark

    thnx Per
    you indeed made your point. i'm using HEX format which is called (in the application i'm using to generate it) "Intel Hex Code-8 bit".
    it looks like this:
    :02000004F80002
    :1000000031353031333131323731323831303731C7
    :1000100032333133313132333132363132333132BE
    :1000200038313134313131313135313231313237AA
    :100030003133313132323131383131373131373199
    . .
    . :090900003131343131343131342C
    :00000001FF

    i can manage to find which header i should use in order to locate the file to the place in the memory i intend to.

    i'm working with SiLab 8051F931 which has 64KB code and 4KB RAM

    the mapping includes I:, C: and X:

    can i use, when working in debug mode with USB debug adapter, the S: memory space? can the debugger work with virtual memory that is located outside the micro (i mean in the PC)?

    i have plenty of free memory in C: in case it's required i can locate the data i need over there, but if possible i'd like to use S: (assuming it is indeed virtual, external to the chip).

Children
No data