• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 80 subscribers
  • Views 9773 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.

MSP430 compile error with IAR ( Error[e183] and Fatal Error[e163])

Pete Yo
Prodigy 10 points

I got an error as below:

Error[e183]: Static overlay map generation (-xo) is not supported for the MSP430 processor.

and found a solution

--> In IAR EW430, go to Project -> Options -> Category: Linker -> Tab: List. Uncheck the Static Overlay Map checkbox.

I unchecked the Static Overlay Map checkbox and rebuild all.

But it popped out a nre error:

--> Fatal Error[e163]: The command line symbol "_HEAP_SIZE" in xxx.xcl

-Z(DATA)DATA16_I,DATA16_Z,DATA16_N,HEAP+_HEAP_SIZE=0200-0A00 is not defined.

Can anyone help me??

  • 0
    Guru 58965 points

    I think you are pushing the boundaries of both the MSP430 and IAR for MSP430.

    If you need static overlay and heap, MSP430 is the wrong choice.

  • 0
    Guru 25210 points

    You may need to specify which HEAP, I think it depends on the memory model you select.

    This is how my ram is defined (for a 2618 device):

    -Z(DATA)DATA16_I,DATA16_Z,DATA16_N,DATA16_HEAP+_DATA16_HEAP_SIZE=1C00-5BFF
    -Z(DATA)DATA20_I,DATA20_Z,DATA20_N,DATA20_HEAP+_DATA20_HEAP_SIZE
    -Z(DATA)CSTACK+_STACK_SIZE#

    Heap is really just all the RAM not used for statics and stack, so I disagree with OCW's statement that MSP430 is not appropriate for using heap allocated memory. We have a malloc package we use all the time for allocating memory at runtime.

**Attention** This is a public forum