Using ISIS as a simulator ?

Go To Last Post
5 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hey everyone,

I'm using ISIS for more advanced simulation than AS5 can provide.
Usually when I used it I loaded the ELF file and I could step through the program and see the source code too.

For some reason it stopped working. When I run ISIS simulation it says "No source line at PC address [PC=xxxx]."

If I have a delay code (using _delay_ms) it shows the delay.h file in the source code window constantly.

I have checked the AS5 project options, and debugging is set to maximum (-g3) and optimization too (-O3).

Any idea what causes it ?
I remember it once worked and displayed the source code inside ISIS.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Have you tried ISIS support?

Leon Heller G1HSM

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

You have exactly the same debugging situation with ISIS or any other simulator / debugger.

It can only work with the debug info given by avr-gcc.

Write a proper external delay_ms() function. I can not see any point in using those inline macros for _delay_ms(). You are hardly worrying about overhead when wasting cycles!

David.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

What's wrong with the _delay_us/ms macro ? Why shouldn't I use it ?

I managed to fix ISIS, it seems that ISIS is picky about the path of the file. The ISIS design file MUST be in the same directory as the .c files.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

There is nothing wrong with the _delay_us() macro. It does what it says on the tin. IMHO it is unwise to use macros for milliseconds. From a debug point of view.

David.