• Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 1276 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS error message: Address is out of range

HS FAE Germany
Mastermind 32810 points

Other Parts Discussed in Thread: MSP430F2274

Hello,
I'm debugging on the MSP430F2274. I got following message after successful compiling and linking

Address is out of range. (please see screenshot attached)

What does it mean?

Regards

Holger

  • TI__Guru**** 481071 points

    hmm... a bit vague i agree. I would guess that there is some mismatch between the debugger memory map and the application. You might want to double check the debugger memory map and see if it looks right to you.

    ki

  • TI__Genius 16640 points

    Hi Holger,

    Are you trying to enter the address in the memory view? Perhaps the address is out of range for your device.

    Regards,
    Patrick

  • in reply to Patrick Chuong
    Intellectual 360 points

    All,

    Any clue as to why this "Address out of range" message pops up ? No definite solutions from any one as yet.

    I have only C code and I am programming the USB ezDSP C5515 chip.

    Any solutions will be helpful.

    Thanks.

  • in reply to AV54983
    Prodigy 130 points

    Hello,

    I got the same problem, the "Address is out of range" message. This message appears to the end of the load of the program and each time you stop the execution, but the system seems to work fine.

    I have been working with the CCS since some months and never I got the message before. My system is a motor kit working with the Piccolo DSP, 28035.

    The first time the message has appeared was when I changed the link command file: my program has grown up beyond the FLASHA capacity (default linker command file option, F28035_FLASH.CMD, supplied with the kit) and I changed the target memory to load the program to a new and big FLASHH of 0x3e8000 start address and 0x8000 lenght. I have been trying some configurations more, but the problem is the same. Also I have turned to the old link command file, loading the program to the FLASHA address, but the message goes on appearing.

    It is of no use to check the address in the memory view, because I don't know what is the address that has the problem: the message window doesn't have that information. Also the memory map of the debugger is agree with the memory map of the DSP.

    Regards,