• State Not Answered
  • Locked Locked
  • Replies 26 replies
  • Subscribers 21 subscribers
  • Views 3148 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

Loading a bigger program via Keil Monitor

J.D. Chang

Hi,
I like to simulate the program larger than 8KB via Keil monitor, and separate the functions and constant data and put constant data to a extra eeprom.

The steps I did are as follows.
1. My test board has a eeprom for bank-switching.
2. Genrated 2 hex file, bank 1 and common area. (xxx.hex and xxx.h00)
3. Loading xxx.h00 to the eeprom early.
4. Using "Start the debug session" to start the simulation.

Got a Monitor Error and "illegal write access at CODE address ...etc."

Please give a help. Tks.

Parents
  • 0 in reply to Andy Neil

    Bitmap data is always constant for back-ground display. And if the bitmap data is stored by xdata type, the is required to be initialized every time when the system start-up. I don't think It's a smart way to deal with the bitmap data. I also like to manage the bitmap data in data rom. When bitmap data is stored in data ROM, it's like a data table and it's always over there for look-up. So, it's better that bitmap data is stored in data ROM, the external flash.

    Actually, I like to know if Keil monitor can start the debug session by some specific configuration and then access the bitmap data in data rom(I got a illegal access error over here)? Thanks.

Reply
  • 0 in reply to Andy Neil

    Bitmap data is always constant for back-ground display. And if the bitmap data is stored by xdata type, the is required to be initialized every time when the system start-up. I don't think It's a smart way to deal with the bitmap data. I also like to manage the bitmap data in data rom. When bitmap data is stored in data ROM, it's like a data table and it's always over there for look-up. So, it's better that bitmap data is stored in data ROM, the external flash.

    Actually, I like to know if Keil monitor can start the debug session by some specific configuration and then access the bitmap data in data rom(I got a illegal access error over here)? Thanks.

Children
  • 0 in reply to J.D. Chang

    If not, why not just map your bitmap data ROM in XDATA space?...

    Bitmap data is always constant for back-ground display. And if the bitmap data is stored by xdata type, the is required to be initialized every time when the system start-up.

    You can't do that to a ROM mapped as XDATA. How do you propose to write to it?

    Erik

  • 0 in reply to J.D. Chang

    "And if the bitmap data is stored by xdata type, the is required to be initialized every time when the system start-up."

    Not necessarily

    Remember, "XDATA" is not synonymous with "RAM" nor even "Volatile memory".

    As far as the 8051 is concerned, XDATA is merely a memory address space - your hardware may map RAM into that space, or ROM, or memory-mapped peripherals - or some combination.

  • 0 in reply to erik malund

    "About programing w27c512, I did it by another EEPROM programmer not Keil tool early. I don't know..."

    Early, I built a xxx.h00 by bank-switching and download the xxx.h00 in external flash.