Debug (simulation) freeze with hardware functions

[MrMotorola]

Using version 3.6 in debugger mode for an AT89S8253, I attempt to F8 (step over) this code:

Code: Select all

void main()
{
    ...
    eeprom_data = EEPROM_Read(0x0000);
    ...

Upon hitting the EEPROM_Read() call, the debugger goes into the read function, and never returns. This is to be expected, since the call does not have actual hardware to act upon!

I'm curious as to how to best "simulate" when stepping through hardware calls? Set the PC to another location after the function (can the debugger even do this?) Comment the function out? Write a "debug" function that returns some value without actually calling the function?

A debugger that is aware that one is calling an "impossible" hardware function would be nice! (Future feature??)

Best regards,
Charles in Colorado

[stefan.filipovic]

Hi,

Welcome to the MikroE forum.

Set the PC to another location after the function (can the debugger even do this?)

No, you cannot do this in the simulator, I'm afraid.

Code: Select all

Comment the function out? Write a "debug" function that returns some value without actually calling the function?

I believe the second case would be better.

Thank you for the feedback, I'll forward this to our developers for consideration.

Kind regards,

[MrMotorola]

Thank you for the welcome and the response, Stefan. I am enjoying your products!