Hello, I would like to automatize my tests. For this, I am calling the Keil debugger via the dll. In my program I use debugger variables. The problem is that between 2 runs, already defined variables/breakpoints/watchpoints/functions are not cleared. I found how to remove watch and breakpoints, also functions. But, no way to remove a variable!? More generally, is there a way to be sure to have a clean environment? Delete project.uvgui.username????? (seems violent to me...)
Regards, Gelika
Hi,
where exactly is a variable shown?
There are commands to remove breakpoints, variables from the watch windows, and a lot more. For example this: http://www.keil.com/support/man/docs/uv4/uv4_cm_watchkill.htm
We would need to understand what exactly is restored that you do not want?
HEllo, The variable is shown nowhere. I defined it using "DEFINE INT myvar" in the debugger command line window. I haven't seen any "window" where it is possible to see variables? Anyway, I'm not using the GUI, I'm calling Keil via the DLL with a python script (to automatise the tests)
Testing forum post; please disregard.
Scott,
we need to know which version of the tools you are using and what target debugger is connected.
I have not seen that the #define variables are restored when a debug session is started. So far, I was unable to duplicate your issue.
How do you start the debugger in your Phyton script?
Hello, So, meanwhile I reinstalled completely the toolset (5.16a, which I was already using but from another drive). Looks like having the installation on one drive and the working data on another is messing up everything in Keil. I also changed the way of starting the debugger. It looks like now, this issue is solved: no more variables when the debugger is started.
In my opinion it could be worth for Keil investigating these drive issues because it's not very comfortable to re install the toolset each time a new project is on another drive...
Gelinka,
we have many projects that are not on the same drive as the MDK installation itself.
This should be a specific problem in your setup. What errors did you got?
Reinhard
I normally use "system drive" and "data drive" with no issues seen.
Hello Reinhard, My reinstalling the toolset is related to other issues, one of them being the "search in files" feature for which I opened a ticket in the support tool some time ago. Another one was a problem of editing a file from the project, with another editor (also opened a ticket): in my installation there was no reload of the file and then no recompilation of the project. Even worse, if the file was open in the Keil editor, the file was overwritten and I lost my changes... Both issues were not reproducible at Keil, and I can't send my source code. My colleague using the same files has no issues anyway.
Now it may well be that the issues are linked to a specific project, which somehow got broken when I copied it from a colleague instead of creating it myself (same code but different computer types). At this point I was not yet able to find the time to recreate the projects from scratch. What is for sure is that I lost the "uvision" icon during this reinstallation, so there is still something broken. I'm lost. "it's commpiling, it's running on the board"-> I gave up debugging my installation. But yes, everything tends towards some windows or install or configuration issue...
Do you and your colleague edit these files across a network? And are the times synchronized across ALL machines properly?
Are your source files located on a File Server? Which File Server are you using?
To simplify reload of external modified files, you may enable the option Automatic reload of external modified files under Edit -> Configuration -> Editor.
Creating a Program Icon is easy:
- Right-click on the desktop and select New
- Choose Shortcut and enter the path to the UV4.EXE (usually C:\Keil_V5\UV4\UV4.exe)
Hello, Apart from the moments where we version our code, all files and installation are local to each computer, also the licensing is somehow node-locked (it's not a network license)
So, if there ever is a timing problem, it's only when doing a "git push", which I haven't done recently...
Have you checked what default program Windows thinks should be used when opening uvision project files? Is it the correct binary?
In my case, .uv2 is of type UV2FILE, and UV2FILE is opened by the command "C:\Keil_v5\UV4\UV4.EXE" "%1"
And as long as no explicit icon has been specified, Windows should pick up the first available icon from the UV4.EXE binary.
But if UV4.EXE points to the wrong path as a result of you having played with multiple concurrent installations, then you can get into troubles.
Oh... :-) Didn't know that "reload" option!!!
And of course it was unchecked in my configuration, so now I corrected this and... YES, that issue is solved!!!! (had to restart Keil though, so I had one moment where I thought it was still not working)
For what concerns the taskbar: the icon is still not appearing, neither in the "taskbar" when uv4 is started, nor on the desktop: I have a shortcut without icon.
Rgds Gelika
OK, thanks Per, Somehow the "open with" was pointing to the right executable, but re-associating it did the trick. Now I have a nice green icon showing in my taskbar. I should try another set of "find in files" to see if that issue is solved too now :-)
Rgds
So, it looks like also my (very old) issue with "find in files" is now giving the right results. For this specific issue, it's not clear what exactly did the trick, but it's solved.
Did your file association really pointed to the right binary? Did you verify the path of the binary? The only way I know how to check without looking for some utility tool is to open the scary registry and check.
But anyway - great that it works for you now :)