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

Simulator Works ... Hardware Doesn't

I am currently working on converting an application originalldeveoped using the Archimedes tool kit V4, to Keil.
The device is a Dallas 80C320.
I have successfully ported the code and it runs using the uVision2 simulator.
When I download the HEX-80 file to the actual hardware, the chip constantly resets.
I took the simple "hello world" progam and had the same results.
Any clues?

Parents
  • What it does is to prevent the processor from trying to execute the blank ROM beyond the end of the real code.
    What actually happens if you don't include the endless loop is that the blank rom location is invalid instruction and microcontroller considers it NOP, it keeps NOPping till end of ROM and starts again, this looks like chip resetting.

    Mahmood

Reply
  • What it does is to prevent the processor from trying to execute the blank ROM beyond the end of the real code.
    What actually happens if you don't include the endless loop is that the blank rom location is invalid instruction and microcontroller considers it NOP, it keeps NOPping till end of ROM and starts again, this looks like chip resetting.

    Mahmood

Children