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

Running a simulation without the debugger and IDE

Hi,

Does anybody know if it is possible to run a simulation, with all its functionality, but without the IDE being launched? (No GUI)

The aim here is to debug the windows application that communicates with this simulated device, and not the device code itself.

If possible, can it be done using the demo version, or do I need to purchase a full software license for it?

Many thanks in advance!
Shahar.

Parents
  • The simulator will process cycle-for-cycle. But that isn't the same as running in real time. If your PC is only fast enough to run the simulation at half real time, then that is what will happen. The simulator output will then count 1 second of real-time execution every 2 seconds wall-time for you.

    When the simulation is only tested against debugger test scripts, then they will have their actions scaled accordingly. When mapping a PC serial port into your simulated processor, then you may get into troubles because of processing speed of the virtual system in relation to the expectations of the Windows application that communicates with the virtual machine.

Reply
  • The simulator will process cycle-for-cycle. But that isn't the same as running in real time. If your PC is only fast enough to run the simulation at half real time, then that is what will happen. The simulator output will then count 1 second of real-time execution every 2 seconds wall-time for you.

    When the simulation is only tested against debugger test scripts, then they will have their actions scaled accordingly. When mapping a PC serial port into your simulated processor, then you may get into troubles because of processing speed of the virtual system in relation to the expectations of the Windows application that communicates with the virtual machine.

Children
  • I am aware of the time accuracy issue you have mentioned.

    Regarding the serial port mapping, I didn't experience actual communication faults, but only slightly delayed replies from the virtual system, compared to the hardware target.

    "When the simulation is only tested against debugger test scripts, then they will have their actions scaled accordingly"

    Can you please elaborate on that?
    (If it matters, please note that I don't use those C-scripts that are run from the uVision command line, or from anywhere else.)

    Thanks.