Hi, I have a simple application such as a microcontroller having internal ROM, an ext. RAM placed from 0x8000-0xEFFF, and an EPROM placed from 0x0000 - 0x1FFF. The EPROM is purposed to hold only display messages defined in the c code such as char const xdata Message[] ="Hello"; I don't want to have any other code in that EPROM. I want besides the genarated program code to have a separate HEX file for these messages ready for the EPROM. For example in format HEX-80. How am I to configure the settings using uVison? I have read the artıcles and the thread: http://www.keil.com/forum/docs/thread2074.asp Also, all related threads or similar. However, I haven't understood: am I able to use XCONST type constants in an external memory and genarate a HEX file only containing them without having a code Banking? So far some of my setings are as follow: Checked boxes: OPTIONS-Device-Use Extended Linker(LX51) instead of BL51 OPTIONS-Target-Use On Chip ROM(0x0-0xFFFF) OPTIONS-Target-Off-chip Xdata Memory 0x8000 size 0x7000 OPTIONS-C51-Misc Controls: XCROM OPTIONS-LX51 Locate-Use Memory Layout from Target Dialog checked User Classes: XCONST (X:0x0000-X:0x3FFF) Thanks in advance for your concern! BR Oktay
Erik, Sorry for inconvinience or for misleading you! My purpose is: The code (interrupt vectors,procedures, functions and all other routines) to be in the On-Chip ROM The variables in the Off-chip Xdata Memory RAM from 0x8000 with size 0x7000 And the discussed subject : constant data ,such as messagess for LCD, in a ROM which is placed in the Off-chip Xdata Memory . So, I need to have 2 HEX files, and the second file is not to be a Code Bank file. ------------------------------------------ Using the XCROM directive and using the char const xdata I succeded to have the program assembled as I want. A problem occured when I run the debugger *** error 65: access violation at C:0x036E : no 'execute/read' permission which I resolved by adjusting the Memory Map for the Code Memory C:0x0, C:0xFFFF to be READ and EXECUTE. The last step is to achive to get, besides the main HEX code, the HEX file containing the CONST defined messages starting from address 0x0 to 0x1FFF. What Andrew has suggested is very close to what I want, but still not complete... Best regards,