Can only access 16K RAM out of 64K

Comments

2 comments

  • Avatar
    Charles Laine

    On further investigation, with placement in RAM2, it compiles and runs, stepping, ok, if I am not using any debug_ calls.  On looking at the linker map I see that values for ___RAM_Size and ___RAM_Address refer to the 16K address space.  Is there perhaps somewhere else that I have to specify the 64K address space?

    0
    Comment actions Permalink
  • Avatar
    Charles Laine

    Ok, guys, after an intensive learning curve I've caught up on the architecture and addressing issues and bye and large understand what's going on.  I accept that I'm not going to be able to access 48k of my 64k ram in a seamless way.  That's not the end of the world, I can easily use the __read_extended and __write_extended functions to get access to my 48k which is only accessible through 20 bit addressing.

    When I say easily that's perhaps an overstatement.  It would be much easier and faster if I could debug such code using the MSP430 Core Simulator, but unfortunately the simulator also declines to let me access simulated high-address 48k memory with the extended functions.   Unless, of course, there is something else that I am missing.  :-)

    0
    Comment actions Permalink

Please sign in to leave a comment.