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!
One more time. Do you have three different licenses? Remember the LIC is tied to your NIC and disk drive to create a magic number as the license enable.
Can you compile and LINK on all three computers?
Are you attempting to run from a Wireless Stick as a NIC device?
Can you run the code on the simulator with full breakpoint control (eliminates the uLink and target problems)?
Have you tried to slow the uLink clock speed?
Are you running the same uLink driver with the same settings?
Have you tried to run the uLink from a self powered USB hub. Some laptops just won't run the uLink in a stable mode. Power or clock speed, I don't know but I know that a self powered hub will often correct a laptop problem. Might be the same problem here.
I don't remember any specific uLink problems with V8.12 Bradford
One More Time ------
We have three systems that work. That requires 3 licenses. The code is too big to run minus a license. ( real small maybe. But this stuff has seen size and is big )
>>>Can you compile and LINK on all three computers?
Hmmm --- a theme here.
Yes we can compile and link on all 3 machines. If a link involving the simulator is used ( we have compiler options we need to do that kind of thing ) the simulation will run. We really want to test on the hardware as the target is better equipped for determining satisfaction of customer requirement.
As stated before - we cannot run with breakpoints on the target.
>> Are you attempting to run from a Wireless Stick as a NIC device?
No. The USB stick was used to copy the keil installation and several of the workspaces. The files were compared between working machine ( we only have one that can debug on target ) and the other two ( which cannot debug on target.) That comparison has yielded some results that are up for test this morning.
>> Can you run the code on the simulator with full breakpoint control (eliminates the uLink and target problems)?
As stated in the original post and in this one a few lines above( maybe not large enough or clear enough - sorry ), in simulation we have no problems with full breakpoint control. We have problems on the target.
>> Have you tried to slow the uLink clock speed?
No. As the uLink is not a roadblock on all 3 PCs. As is the box works. In looking for areas of common cause among all three PCs, I was left with Workspace settings and Kiel Installation vectors. That is the area of current investigation. Commonality of systems is likely not the source of the current difficulty. I am gunning for any diference vectors.
>> Are you running the same uLink driver with the same settings?
This was confirmed in the PMA. All three were checked for what driver they use. Its the same one for all three systems. Again one functions ok on target, the other two can upload and start a run. They cannot debug.
>>>Have you tried to run the uLink from a self powered USB hub. Some laptops just won't run the uLink in a stable mode. Power or clock speed, I don't know but I know that a self powered hub will often correct a laptop problem. Might be the same problem here.
I cannot look at this now, as I have to find a hub. I will keep this in mind as it may be useful in a bit.
>>I don't remember any specific uLink problems with V8.12 Bradford
Me either, but then this is 4 months with Keil
Oh boy --
Just performed full reinstall of keil uVison 3 on my system.
One key file seems to be missing -- ul2lpc9.dll is found in the c51/bin directories of the machines which can run on the target.
With a full install completed on keil, I just added the c51 product ( i saved my license string )
That file is not in this install.
The general appearance of the tools.ini file is that the v8 entry was made at a later date, perhaps as a later addition. No clue here.
My initial take is to see if the new install works ok at all on the target. If I am back to where I was, well --- I tried.
Whats left?
I am simply going to copy the file into the current install and see what happens
Daniel; Don't leave us hanging! Did the re-install correct your problems? Bradford
First Up:
My apologies as I have not reached a complete solution yet.
This is what I did get:
In examining folks machines and licenses, I kept seeing a reference to a v8 item in the license file, as well as a dll I did not have. Simply adding the dll had no effect.
While doing a full tilt re-install, my sorrow showed in that my c51/bin directory was the same as before. Looking further seemed worthless, however I still looked around. I still had 8.12 software
The local Mentor for this subsystem discovered he had a second cd. It has the same date ( 8/2008) as the first CD. Still, a try seemed minor so it was engaged on.
It had 8.16a SW on it. This one placed the missing DLL in the bin directory as well as applying the v8 in my Tools.ini file. Some md5s in the bin directory did not match what I had seen in my before directory. The bins were different
Hope for a success bloomed..... We retired to the Hardware lab to test out this development...
I get the menu allowing breakpoints while in run. It is not greyed out. However, the machine did not acknowledge a stop command. The message displayed on the output window was ulink timeout. We had to disconnect the machine from power supply and turn off keil to get the PC back.
What i am doing at this point is reviewing the link posted earlier to find out a few things on time outs. One point that is here that is real unique- We have the only 5 volt keil ulinks ever made.
Will try to keep you folks posted as things resolve. Anything you can tell me on timeouts would be appreciated.
--dan