My apologies if this is a regular question, but this is driving me to bad pieces.
What we have here is
ToolChain pk51 Prof Developers kit Version 8.12 ToolChain Path C:\Keil\C51\Bin\ C Compiler C51.EXE v8.12 Assembler A51.exe v8.01 Linker/Locator LX51.exe v4.25 Librarian LibX51.exe v4.24
I am not sure how much else you may need.
I have an application which lives on an 8051 derivative controller. I can compile it ok, and the initial testing in the simulation was ok. So we ( more than one folks out here ) put it on the controller.
We use a Ulink 2.0 kinda -- its marked ULINK 2.1
Okay --- Once compiled for target and loaded on, we set some breakpoints in the text pane, flipped into debug and......
Sometimes the application starts immediately as if the run button got clicked. Other times one can push the reset button and then hit the go button. In either case, the process does not heed halt messages and will not stop at any breakpoints that were set earlier. You do not see the red square you put near a line -- you see a grey ghost.
We tried other PCs to run this procedure. Only one machine does not have the "set breakpoint" menu greyed out. Its the only one that can do debug on target. Our other three have set breakpoint greyed out while running on target, and its possible to start a run, but breakpoints are ignored.
The C51 project options window for the working machine as well as the problem children were compared and differing options were modified. This did not result in any improvement. We also tried different machines in case it was hardware. The good box runs ok, the rest do not. since we are all running the same machine ( a dell with windows xp ) I think it may be a sw option we did not see or set.
Any and all assistance in this matter is greatly appreciated. Flames cheerfully ignored. Accolades acknowledged. Even Better - What works will be posted back to share with the long suffering people!
You said your process is: 1. Set breakpoints; 2. Enter Debug mode.
What happens if you make that: 1. Enter Debug mode; 2. Set breakpoints.
?
I had a problem a while ago where there appeared to be some conflict between the uLink and something else on the PC: http://www.keil.com/forum/14502/
>>> Learned while testing.
I plugged the PC in, and went looking for a driver id.
and found nothing....
So i kept poking into the other usb ports. Suddenly, one lights up the screen with a message "Human interface device detected" The keil ulink turns up in the device manager as ulink
I confirmed - all 3 pcs are using the same drivers.
We are refocusing attention on build options - what exactly are we supposed to be building with?
<<<
Will reread your link --- I am getting time outs like you did after code load and start from debug on target.
Once the machine says it saw the Human interface, the greyed out options for setting break points had become active. It ignored whatever I set, but the options were in black.
So loading code followed by entering debug followed by setting breakpoints is only kinda working. The box is ignoring all breakpoints. --d