• State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 22 subscribers
  • Views 2288 views
  • Users 0 members are here
Options
Related
How was your experience today?
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

memory mapping and linker file for C164CI

Guillaume Anceau

I use a DIP module with an C164 CI.
When I want to add some code and some variables in my excisting program, it does not work anymore. It must be due to the memory mapping and the linker file which are not right configured.

here is the linker: (in monitor mode)

 
SECTIONS(?C_STARTUP_CODE%ICODE (0x01000), ?C_INITSEC (0x01150))

CLASSES(ICODE (0x000200-0x003FFF) , FCODE (0x000200-0x003FFF),
NCONST (0x000200-0x003FFF) , FCONST (0x000200-0x003FFF),
NDATA (0x060000-0x061FFF) , NDATA0 (0x060000-0x061FFF),
FDATA (0x060000-0x061FFF) , FDATA0 (0x060000-0x061FFF), 
HDATA (0x060000-0x061FFF) , HDATA0 (0x060000-0x061FFF),
XDATA (0x060000-0x061FFF) , XDATA0 (0x060000-0x061FFF))

RESERVE(0x04-0x0B,0x0AC-0x0AF,0x0B8-0x0BB,0x6b00-0x7fff,0xE000-0xF9FF,0x3E900-0x3FFFF)

As option in Keil I use:

memory model :Large
no use of on chip ROM
use of on chip RAM

external memory:
RAM 0x40000-0x46AFF
ROM 0x200000-0x23FFFF


Do anyone have the right option that I have to choose to make my program work whatever the code's size is? in monitor mode or in flash mode?

thank you.

Parents
  • 0 in reply to Scott deWolski

    "You need to have two separate projects; one for UV debugging in RAM and another for the final output"

    Unfortunately, uVision doesn't support a structure where the only difference is that one target is, for example, running from RAM, while another runs from ROM.
    In uVision, Targets are completely independent - there is no way to specify a common subset of Target options.
    This is a pain! :-(

Reply
  • 0 in reply to Scott deWolski

    "You need to have two separate projects; one for UV debugging in RAM and another for the final output"

    Unfortunately, uVision doesn't support a structure where the only difference is that one target is, for example, running from RAM, while another runs from ROM.
    In uVision, Targets are completely independent - there is no way to specify a common subset of Target options.
    This is a pain! :-(

Children
No data