iar link error e72

Damon

Other Parts Discussed in Thread: CC2530, Z-STACK

Hi all,

I found someone has met this kind of problem. But I still do not know how to solve the problem. Can anyone tell me how to solve it carefully?

Fatal Error[e72]: Segment XDATA_HEAP must be defined in a segment definition option (-Z, -b or -P)

Fatal Error[e72]: Segment ZIGNV_ADDRESS_SPACE must be defined in a segment definition option (-Z, -b or -P)

Thank you!

over 13 years ago

0 Igor Sherer over 13 years ago

Guru 31280 points

Hi,

Seems like you are trying to compile and link an old project with new linker configuration file.

What is the project you are work with (also what is the stack/framework), what is the target

device? Where is the linker configuration file taken from?

0 Damon over 13 years ago in reply to Igor Sherer

Intellectual 845 points

Hi Sherer,

the iar version is 8.10, and the zstack version is 2.5, the *.xcl file is TI's. the chip number is CC2530.

Thank you!

0 Igor Sherer over 13 years ago in reply to Damon

Guru 31280 points

What is the project name?

0 Damon over 13 years ago in reply to Igor Sherer

Intellectual 845 points

SampleApp

0 Igor Sherer over 13 years ago in reply to Damon

Guru 31280 points

Hey,

One last question, it isn't compiling just out-of-the-box?

0 Damon over 13 years ago in reply to Igor Sherer

Intellectual 845 points

hi Sherer,

I can not understand what do you mean?

0 Igor Sherer over 13 years ago in reply to Damon

Guru 31280 points

Hi,

I mean, just after you have installed the Z-stack 2.5..., you have opened the SampleApp

project (w/o doing any modifications) in IAR 8.10, tried to compile it, and then you got those

error messages?

0 Damon over 13 years ago in reply to Igor Sherer

Intellectual 845 points

oh, no, I have added my own modules. I have defined a very large array: char array[2176]. I do not know where should i place it.

0 Igor Sherer over 13 years ago in reply to Damon

Guru 31280 points

Such as?

Try to remove your modules one by one and see what module causes the error/s

0 Damon over 13 years ago in reply to Igor Sherer

Intellectual 845 points

The module who uses the large array causes the error. I do not know how to correct it. Can you help me?

0 Igor Sherer over 13 years ago in reply to Damon

Guru 31280 points

What is the size of the large array?

0 Damon over 13 years ago in reply to Igor Sherer

Intellectual 845 points

char array[2176];

0 Igor Sherer over 13 years ago in reply to Damon

Guru 31280 points

Hey,

This array is too large.

Just for the sake of experiment, reduce your array from 2176 bytes, to let's say 20 bytes, then compile

the project again. After compilation is done, expand the "output" directory in your project, open a .map

file, and jump to the end of it. There you'll see sort of table, pay attention on the XDATA memory, now

add to this value more 2156 bytes, the result is probably exceeds the 8KBytes of CC2530 RAM.

Are you really need such an large array, maybe you can think of a way to reduce it?

Moreover, OSAL has a heap memory, therefore you can allocate quite a large array (let's say 600 bytes)

by using OSAL services?

0 Damon over 13 years ago in reply to Igor Sherer

Intellectual 845 points

I really need to use so large array.

Thank you Sherer!

0 Damon over 13 years ago in reply to Damon

Intellectual 845 points

Hi Igor,

I think that maybe I should place the large array into the flash memery. Do you know how to place a data into the flash and how to read out?

Thank you!

Damon

0 Igor Sherer over 13 years ago in reply to Damon

Guru 31280 points

Hi,

There are two options:

Using OSAL NV services, refer to OSAL.API document, section 10.
Pay attention, that you (your application) are allowed to use only the space
allocated for the Application, that is 0x0401 – 0x0FFF.
The downside of using OSAL_NV services is these functions (read/write)
are blocking, and can take quite a long time, especially writing.
Read the DN200 - Using Constants in Code with Z-stack.

But you should consider to reduce the length of this array, it is more efficient.

Also, you have the dynamic memory allocation (such as osal_mem_alloc) at your

disposition, you might consider using this too (refer to Heap Memory Management.pdf

to learn more about this feature)

0 Damon over 13 years ago in reply to Igor Sherer

Intellectual 845 points

I have so many things to learn from you, my teacher.

Thank you very much, my dear friends!

Damon

0 Green jerome over 12 years ago in reply to Damon

Prodigy 30 points

Sorry,I do not know your solutions for the above error.Could you expain it carefully again?

0 Igor Sherer over 12 years ago in reply to Green jerome

Guru 31280 points

Hi,

More info would be great... :)

0 Green jerome over 12 years ago in reply to Igor Sherer

Prodigy 30 points

My problem is still the error[72]:Segment ZIGNV_ADDRESS_SPACE must be defined in a segment definition option (-Z, -b or -P).now I can‘t solve it.

The device I used is cc2530, Z-stack 2.4,GenericApp.

0 Igor Sherer over 12 years ago in reply to Green jerome

Guru 31280 points

What is the version of IAR.

0 Green jerome over 12 years ago in reply to Igor Sherer

Prodigy 30 points

7.6

0 Igor Sherer over 12 years ago in reply to Green jerome

Guru 31280 points

Ok,

So far I see no cause for the problem.

What is the linker file in use?
What are the modification you made (if any) to the genericApp?

Zigbee & Thread

Zigbee & Thread forum

iar link error e72