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

Phytec KC167CR debug problems

Hi all.

I am experiencing some problems with debugging my code on my Phytec evaluation board. I run the RTX166 Traffic-example.

I'm using Keil Monitor-166 with the KC167CR config. In the description of this config, I am recommended to reserve memory 8H-0BH, 0ACH-0AFH. External memory is set to ROM: 0x0 - 0x10000 and RAM:0x10000 - 0x20000.

When doing rebuild all for target RTX Tiny, the linker gives me the warning:

Warning L4: Memory space overlap from 0000ACH.0 to 0000B0H.0

This is probably due to the memory reservations I did before. Should I remove the reservation?

If I remove 0ACH-0AFH from reserve memory, It builds fine and everything seems OK. When I now start the debugger, it loads fine, but running the program ends with some rubbish to the serial #1 screen, some LED's lighting up, and then it all comes to a dead end. I can't debug or nothing.

I suspect there is something wrong with my memory adressing, but I'm somewhat green to this, and I would really appreciate some help!

Regards,
Ray


Parents
  • The problem with the Traffic example is that it uses an interrupt driver serial interface and the Monitor uses the same serial interface again for communication.

    The reserveration is the memory overlap conflict that you are facing. Remove the 0xAC-0AF memory reservation and disable under
    Options for Target - Debug - Use Monitor -Stop Program Execution via Serial Interface.

Reply
  • The problem with the Traffic example is that it uses an interrupt driver serial interface and the Monitor uses the same serial interface again for communication.

    The reserveration is the memory overlap conflict that you are facing. Remove the 0xAC-0AF memory reservation and disable under
    Options for Target - Debug - Use Monitor -Stop Program Execution via Serial Interface.

Children
No data