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!
very explicit, and then I have an application which lives on an 8051 derivative controller.
???
Erik
Some replies !!
Ok -- Support licenses run for one year after purchase. The support for what we have has run out. management folk have yet to decide where we go with this. Most likely not with the current product. The stuff we are working on is entering end of life
I have an application which runs on an 8051 derivative controller is an adequate description of the chip and the c based application that lives there. The app and the board have demonstrated many times their ability to be debugged via a attached PC connected to a KEIL JTAG pod. ( ulink 2.1)
Our difficulty is the following -- only one of the three development PC's can connect to the target -- the other two can download code and run, however there is no ability to establish breakpoints - as stated above.
The reason for this post was to find out if anybody had experienced the same problem and overcome it. Right now, I am copying and then comparing the files in the keil directory with my install.
Before being able to tell if it's the same problem, don't you think we'd need to know if we're talking about the same chip?!
Why can't you say what chip it is?? There aren't that many 8051s with JTAG, so it shouldn't take too many guesses...
"there is no ability to establish breakpoints - as stated above"
You didn't confirm whether that's no ability at all, or just that the particular sequence described above doesn't work.
You seem to be running on multiple PC. Do you have multiple license? Did you do a full install or did you copy from one PC to the others? Bradford
Way cool -- let me answer
We all ran the install, then we all entered the license strings ( one string per user )as per the manual.
The chip we are using on the controller is: uPSD3454EB
I will point out -- only one PC of the 3 we have licenses on can run and debug on the target using the ulink 2.1 JTAG pod. The other 2 cannot. They are all running the same XP -- I have yet to check on drivers for the USB.
Target hardware is 100% identical. All three PCS were run against it. Only one does debug.
PC Hardware may not be perfectly identical. I am chasing this as well.
>>> in the meantime.....
I copied the full contents of the KEIL directory from the PC that works ( the one that can debug ) to a stick. Running a full directory comparison with mine ( which can download but cannot debug ) has shown some file differences. They resolve out as different features for the editor, as well as tools we use for post processing. ( my tools live elsewhere )
>>? data continues to kerpuffle by here...
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
View all questions in Keil forum