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

Simulator Works ... Hardware Doesn't

Michael Bartholomew

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
  • 0 in reply to Mahmood Elnasser

    I verified that I have an endless loop

    while(1){
};

    When I removed it the simulator did end up starting over at c:0x0000.

    I'm looking at the Watchdog, but the user's guide says that ROMless devices (like the 80C320) default to disabled.

    My problem debugging this, is that I have to do it blind on the target hardware. I do not have an ICE nor is there a serial port available.

Reply
  • 0 in reply to Mahmood Elnasser

    I verified that I have an endless loop

    while(1){
};

    When I removed it the simulator did end up starting over at c:0x0000.

    I'm looking at the Watchdog, but the user's guide says that ROMless devices (like the 80C320) default to disabled.

    My problem debugging this, is that I have to do it blind on the target hardware. I do not have an ICE nor is there a serial port available.

Children
  • 0 in reply to Michael Bartholomew

    Just an update...it was a watchdog issue; however, it is an external watchdog. It turns out the hardware did not take advantage of the internal watchdog feature of the Dallas 80C320 but instead used a XICOR X25043 CPU Supervisor with watchdog timer.
    So now my focus is to look at the bit addressing or mapping. The variable in the code may not have been mapped correctly to a bit addressable address.
    Thanks for the input.