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

AT89C51RD2 with KEIL and Proteus VSM 7.1

I am using AT89C51RD2 with KEIL and Proteus VSM 7.1 SP2.
The problem i am facing is:
I am using "Small" memory model for AT89S52 (256 bytes RAM).
Due to Address Overflow (Lot of variables), now I am using AT89C51RD2 (256 + 1792 bytes on-chip XRAM)
So i have selected "Compact" memory model to use XRAM.
Now Compiler Side there is no problem, Keil succesfully Creates HEX files.
But when i am simulating this hex file with Proteus there is Blank Display
and nothing at all.

Proteus Simulation log gives message:
[HD44780]Controller received data whilst busy.

What is the problem ?

Same code creates this problem if "Compact" memory model is selected.

Please Help !

Parents
  • "So i have selected 'Compact' memory model to use XRAM."

    No, you don't need to change the memory model at all.

    The memory model simply specifies the default memory spaces - so all you need to do is to add the 'xdata' specifier to those variables that you specifically want to put into XDATA

    "i am simulating this hex file with Proteus "

    Proteus is not a Keil product - you need to contact Proteus support!

    "What is the problem ?"

    It is completely impossible to tell, as you've given absolutely no details of what your system is trying to do, how this display is connected to the controller, etc, etc...

Reply
  • "So i have selected 'Compact' memory model to use XRAM."

    No, you don't need to change the memory model at all.

    The memory model simply specifies the default memory spaces - so all you need to do is to add the 'xdata' specifier to those variables that you specifically want to put into XDATA

    "i am simulating this hex file with Proteus "

    Proteus is not a Keil product - you need to contact Proteus support!

    "What is the problem ?"

    It is completely impossible to tell, as you've given absolutely no details of what your system is trying to do, how this display is connected to the controller, etc, etc...

Children