• State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 21 subscribers
  • Views 2420 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

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

uLink2 initialization file - map command?

steve kerich

Hi

I am using a cortex m3 arm from microsemi and I am trying to get the uLink2 debugger to load and debug my code. I have the standard on board 64K of nvm (addr 0) which is only good for start up really and 2GB of DDR RAM memory (0xA0000000) where my application will run.

I have tried to tell the debugger about this RAM memory that starts at 0xA0000000 with the following debugger initialization file but it seems to be totally ignoring it and giving me a error 129: MapMem - map size truncated to 128MB. If i try to load the symbols after this completes whatever it is doing, the uVision/uLink2 IDE hangs and I have to kill it.

RESET MAP
MAP  0xA0000000, 0xA07FFFFF  READ WRITE EXEC
MAP  0xA0800000, 0xA0FFFFFF  READ WRITE EXEC
MAP  0xA1000000, 0xA17FFFFF  READ WRITE EXEC
MAP  0xA1800000, 0xA1FFFFFF  READ WRITE EXEC

Does anyone ideas as to what I have done wrong or what I can do to allow my code to be loaded?

Parents
  • 0

    I'm confused, you mean 2 Gbit, 256 MByte, because 2GB isn't going to fit at 0xA0000000, and 256MB is 0x10000000

    The 128MB is a HARD limit Keil has used, only they can provide an answer to why that number was chosen.

    RESET MAP
MAP  0xA0000000, 0xA7FFFFFF  READ WRITE EXEC
MAP  0xA8000000, 0xAFFFFFFF  READ WRITE EXEC

    7FFFFF -> 8MB-1
    7FFFFFF -> 128MB-1

Reply
  • 0

    I'm confused, you mean 2 Gbit, 256 MByte, because 2GB isn't going to fit at 0xA0000000, and 256MB is 0x10000000

    The 128MB is a HARD limit Keil has used, only they can provide an answer to why that number was chosen.

    RESET MAP
MAP  0xA0000000, 0xA7FFFFFF  READ WRITE EXEC
MAP  0xA8000000, 0xAFFFFFFF  READ WRITE EXEC

    7FFFFF -> 8MB-1
    7FFFFFF -> 128MB-1

Children
  • 0 in reply to Westonsupermare Pier

    Yes you are correct. Keil tech support told me that I only needed/should MAP the memory I was actually using and not all of the available memory which is what I tried to do in 128MB chunks.

    I had tried this first and it didn't make any difference.

    RESET MAP
    MAP 0xA0000000, 0xA7FFFFFF READ WRITE EXEC
    MAP 0xA8000000, 0xAFFFFFFF READ WRITE EXEC

    What I posted was not correct. It was another desperate attempt to get this to work with a smaller build I made. Sorry about the confusion.

    Does Kiel monitor this forum at all? I am not getting much help from tech support on this

    I have a case open for past 2 or 3 weeks but still have not gotten an answer as to why MAP is not working.

  • 0 in reply to steve kerich

    This is not an official support venue, staff have been known to post here, and lurk.