Products Download Events Support
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.
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.
Toolset C51
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 motorwerks to the target -- the other two can download code and run, however there is no ability to establish breakpoints - as stated above. motorwerks
Posted 7-Jan-2011 17:39 GMT
I will point out -- only one PC of the 3 we have licenses motorwerks 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.
I copied the full contents motorwerks 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 )
Posted 7-Jan-2011 19:29 GMT
Posted 10-Jan-2011 16:48 GMT
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. motorwerks ( my tools live elsewhere )
Read-Only
Only One is able to download code to our target, and use the Keil debugger on the target. The other two can download code, but not debug. The software on the PC displayed greyed motorwerks out menu options for setting breakpoints as well as not acknowledging a breakpoint or stop run at all.
RE: Recapping and PMA
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.
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.
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.
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.
No. As the uLink is not a roadblock on all 3 PCs. As is the box works. In looking for areas of common motorwerks 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 motorwerks is likely not the source of the current difficulty. I am gunning for any diference vectors.
This was confirmed in the PMA. All three were checked for what driv
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.
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.
Toolset C51
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 motorwerks to the target -- the other two can download code and run, however there is no ability to establish breakpoints - as stated above. motorwerks
Posted 7-Jan-2011 17:39 GMT
I will point out -- only one PC of the 3 we have licenses motorwerks 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.
I copied the full contents motorwerks 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 )
Posted 7-Jan-2011 19:29 GMT
Posted 10-Jan-2011 16:48 GMT
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. motorwerks ( my tools live elsewhere )
Read-Only
Only One is able to download code to our target, and use the Keil debugger on the target. The other two can download code, but not debug. The software on the PC displayed greyed motorwerks out menu options for setting breakpoints as well as not acknowledging a breakpoint or stop run at all.
RE: Recapping and PMA
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.
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.
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.
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.
No. As the uLink is not a roadblock on all 3 PCs. As is the box works. In looking for areas of common motorwerks 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 motorwerks is likely not the source of the current difficulty. I am gunning for any diference vectors.
This was confirmed in the PMA. All three were checked for what driv
No comments:
Post a Comment