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

how do you configure off-chip code and xdata memory in target options?

Hello,
I'm having trouble understanding a demo code I'm working with.

The chip is d 71M6543 from teridian, which has 64k flash,
And 5k xdata.

It is an SOC, so the data and code memory are shared between two cores.

In the 'target' tab of the project options, under off-chip code memory,
Thr range is set to 0x0400 to 0xFC00

While for off-chip xdata memory, the range is set to:
0x0520 to 0x0EE0

This range is smaller than the maximim adressable memory for the chip.

What is the implication of this values to the code been compiled by keil?

Thanks.

Parents
  • Normally, there are no implications. The tools don't care about the values you specify in the project, as long as the target has the corresponding memory available at the specified ranges.

    When playing with boot loaders, it's normal to have projects that only specifies a subset of the memory range as available for the build. One subset for the boot loader. Another subset for the application (or potentially multiple applications).

    And making use of pointers or absolutely located variables, you can also make access to memory outside of the ranges specified in the project.

    The biggest issue is if your interrupt vector table gets placed where the processor core expects it.

Reply
  • Normally, there are no implications. The tools don't care about the values you specify in the project, as long as the target has the corresponding memory available at the specified ranges.

    When playing with boot loaders, it's normal to have projects that only specifies a subset of the memory range as available for the build. One subset for the boot loader. Another subset for the application (or potentially multiple applications).

    And making use of pointers or absolutely located variables, you can also make access to memory outside of the ranges specified in the project.

    The biggest issue is if your interrupt vector table gets placed where the processor core expects it.

Children
No data