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

Keil Debug with simulator

Hello everyone,

I'm new to using Keil uVision so I would like to ask some questions about the Keil simulation debug.
As I was reading about the simulation debug tool I discovered this feature is only capable of simulating ARM ISA instruction, not be able to simulate peripheral behavior or external input. After configuring the target to simulation, I successfully started the debug mode. However, when I run my application in debug mode it gets stuck in some part of the code.

Given these points, I would like to ask:

1 - Is It necessary to install an additional tool or program for the simulation to work? Since I don't have much experience using the simulator I don't know if that is expected behavior or a misconfiguration from my side.

2 - I read that ARM has another simulation tool called FVP that is also a simulation tool. what are the differences between FVP and the Debug Simulation?

3- My main goal is to use the simulation debug with the Parasoft C/C++ Test tool to perform some Unit Testing on my application so I would like to know if someone has any literature that I can use as a reference?

Parents
  • this feature is only capable of simulating ARM ISA instruction, not be able to simulate peripheral behavior or external input

    Correct.

    There is some facility for you to write custom simulation - with Debug Functions:

    https://www.keil.com/support/man/docs/uv4/uv4_debug_functions.htm

    Whether that's worth the effort is another question.

    It might be easier to use an actual target board with programmable test equipment to provide stimuli & observe responses ...

    Or just "stub" the hardware interface parts

    when I run my application in debug mode it gets stuck in some part of the code

    You'll need to look into it to see what, exactly, is happening when it gets "stuck"

    Obviously, if your code is waiting for some external event - that is never going to happen.

    My main goal is to use the simulation debug with the Parasoft C/C++ Test tool

    Have you asked them for their advice?

Reply
  • this feature is only capable of simulating ARM ISA instruction, not be able to simulate peripheral behavior or external input

    Correct.

    There is some facility for you to write custom simulation - with Debug Functions:

    https://www.keil.com/support/man/docs/uv4/uv4_debug_functions.htm

    Whether that's worth the effort is another question.

    It might be easier to use an actual target board with programmable test equipment to provide stimuli & observe responses ...

    Or just "stub" the hardware interface parts

    when I run my application in debug mode it gets stuck in some part of the code

    You'll need to look into it to see what, exactly, is happening when it gets "stuck"

    Obviously, if your code is waiting for some external event - that is never going to happen.

    My main goal is to use the simulation debug with the Parasoft C/C++ Test tool

    Have you asked them for their advice?

Children