 | Discussion Forum |  |
|
|
Memory display with monitor166Next Thread | Thread List | Previous Thread Start a Thread | Settings | Details | Message |
|---|
Read-Only Author George Mylonas Posted 6-Nov-2000 02:11 GMT Toolset C166 |  Memory display with monitor166 George Mylonas Hi
I just managed to interface an external fast RAM to my C167CR. The base address is 0x50000 \CS2 selectable.
Using the MONITOR166 and the "load" command I load two files into the memory at base addresses 0x54000 and 0x56000 respectively. When I display the memory contents (using the "d" command during debugging) I find that nothing is writen at 0x54000 and that at 0x56000 my file is writen correctly.
1. What I see when using the "d 0x54000, 0x58000" are the real contents of my hardware memory?
2. Why I'm able to see entries only at 0x56000 and beyond, and nothing written at 0x54000?
Could those possibly be problems with my memory hardware or its some issue related to the way that monitor166 works?
Thanks
George
| | Read-Only Author Keil Support Posted 6-Nov-2000 03:41 GMT Toolset C166 |  RE: Memory display with monitor166 Keil Support I haven't seen that particular problem, but there was a problem with the monitor when accessing memory above 0x40000. If you have a recent version of the tools you shouldn't experience this problem.
Then, it could in fact be a hardware problem.
Check the following support solution for details on the update to the monitor:
http://www.keil.com/support/docs/1453.htm
Keil Support | |
Next Thread | Thread List | Previous Thread Start a Thread | Settings |
|