I recently updated CCS to version 4.1.3.00038 and have big problems with my Blackhawk USB2000 since then. It has difficulties programming my F28035 ControlCARD which is sitting on a custom PCB. Before the update everything worked fine. Blackhawk driver version is : 22.214.171.124.When connecting to the target it comes with the following error :Error connecting to the target:Error 0x80000200/-1142Fatal Error during: OCS, Processor blocked debug accesses. An operation was attempted whilethe CPU was in a non-debuggable context. To continue to honor the debugcontext, press Cancel. To force debug access, press Rude Retry.It says press 'Rude Retry' but most of the times only a 'Cancel' and a 'Retry' button are available. Pressing 'Cancel' cancels programming, pressing 'Retry' just results in looping the error popup dialog. Strangely, once in a while a 'Rude Retry' button is available and pressing it will program the DSP just fine. Once it is programmed, everything works as it should and I can run, break and step through the code just fine.The above error alters with the error message below :Error connecting to the target:Error 0x80000200/-1041Fatal Error during: OCS, Device driver: Problem with the Emulation Controller.It is recommended to RESET EMULATOR. This will disconnect each target from the emulator. The targets should then be power cycledor hard reset followed by an emureset and reconnect to each target.Which I tried, but no hard reset of any of the devices (ControlCARD, Custom PCB, Emulator, PC) helps. Until ofcourse a 'Rude Retry' button comes up, then all problems are solved until I need to program again.
Have you tried updating your Blackhawk drivers? I have found that a number of 510 class emulators have required driver updates after updating to 4.1.3. I believe Blackhawk has new drivers available that fix this problem.
If my reply answers your question please mark the thread as answered
Blackhawk driver version is 126.96.36.199.
Software update feature of CCS does not come up with newer driver. Everything is up to date.
However... Going to "Help -> Software Updates -> Manage Configuration" shows that besides 188.8.131.52 also driver version 184.108.40.206 is installed. Can this cause any conflicts and how do I make sure the newest version is used?
The manage configuration dialog will show all the versions that have been installed but in reality you only have one version of the BH drivers as they get overwritten.
220.127.116.11 is the latest version
I have an install that still has the 18.104.22.168 BH drivers. I will try my BH510L (similar emulator) before and after the update to 22.214.171.124 to see if I can get the same error.
My BH510L is working fine with F28035 before and after the BH driver update. I don't have access to a USB2000. I will see if I can pull in someone from BH to help out.
One thing to try:
BHreset_USB2000 shows :
Results in file: log\BHreset_USB2000.logbin\XDSProbe.exe -v -F bhemutbcl.dll -p0x0 -r -o log\BHreset_USB2000.log...SUCCESS: Command reported no errors.Press any key to continue . . .
and BHprobe_USB2000 utilities shows :
Results in file: log\BHprobe_USB2000.logbin\XDSProbe.exe -v -F bhemutbcl.dll -p0x0 -r -o log\BHprobe_USB2000.log...SUCCESS: Command reported no errors.Results in file: log\BHprobe_USB2000.logbin\XDSProbe.exe -v -F bhemutbcl.dll -p0x0 -i -o log\BHprobe_USB2000.log...SUCCESS: Command reported no errors.Results in file: log\BHprobe_USB2000.logbin\XDSProbe.exe -v -f bin\bh-noscantest.cfg -F bhemutbcl.dll -p0x0 -i -o log\BHprobe_USB2000.log...SUCCESS: Command reported no errors.Results in file: log\BHprobe_USB2000.logbin\XDSProbe.exe -v -F bhemutbcl.dll -p0x0 -g -o log\BHprobe_USB2000.log...SUCCESS: Command reported no errors.Press any key to continue . . .
We would have expeted the USB510L to generate the same error; it uses the same 28x files. We are looking into this.
What version of CCS did you upgrade from? (I am assuming that you had v4.1.2 or something previoulsy installed and updated to 4.1.3.00038...and did not install v4.1.3.00038 from scatch on a clean system).
I upgraded from 4.1.2.00027 to 4.1.3.00038.
I think I have nailed the issue.
"Enable silicon real-time mode" was enabled in "Generic Debugger Options -> Real-time Options". If this is enabled while Blackhawk connects to ControlCARD it fails. When not enabled while connecting, all is going well. When programmed and ready to debug, I can enable silicon real-time mode again and it works. I just have to make sure I disable it before loading new software.
Although I can continue working on my project now, I think it is a good idea to fix this "feature" in a future CCS release.
Thanks for all the help.
That must be it, and why we could not duplicate the error. There are other posts with the same resolution to disable real-time mode. http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/51390/182664.aspx
I agree that this should be corrected because the error does not indicate the problem. Hopefully, at a minimum, an error message could be generated for the modes that are not supported when real-time is enabled. For example, when you do a Program Load it would check that real-time flag first, or when you set the flag, it warns you about loading the next time.
Thanks for following through on this to find the cause. I'm sure this thread will be beneficial to other users.
I agree that this seems to be something that needs to be cleaned up. Andrew thanks for following up on this.
I am having trouble reproducing the same scenario. I want to nail it so we can work with the team to make it work smoother.
If I put my device in real-time mode I don't get an error on connect but I do get one when I try to flash my program.
Here is what I am doing:
I would like to reproduce the error you get on connect. Can you let me know what GEL file your target config is using? I am wondering if it has some code in the OnTargetConnect() function that is triggering the error. You can see the list of loaded GEL files by going to Tools->GEL Files when you are in a debug session. One solution would be to have the GEL check for real-time mode, disable it if needed and then enable it again after the accesses. I can update the GEL file to do that if that is the case.
Maybe I incorrectly stated that the error occurs while connecting. "Connecting to target....." was the last message seen by me before the error popped up, but it might have connected just fine and failed on the start of writing to the target. I always just click the "Debug launch" button and do not individually connect and program the device.
I don't which .gel file I use, and I don't know where to look (still learning my way around CCS), but I'm pretty sure it's the default file for the 28035.
I just realized the error message says "Error connecting to target" so it must be a connection error.
I can confirm that I use the TI delivered "f28035.gel".
Based on the error message I think for you it really is failing on connect. My error message is quite a bit different.
To see which GEL file is being loaded do the following:
If it is a different file it would be great if you could attach it to the thread.
I have a GEL file now that disables realtime before the load/flash and enables again afterwards that seems to work.
Never mind. I missed your last message. I am going to attach my GEL file
Earlier I mentioned I could continue working again with the "Enable Real-time mode" disabled but now I experience the same errors again. I checked and this time real time mode is disabled for sure. I also never get the "Rude Retry" option which, in the previous case, always solved the problem.
- Tried the GEL files posted by John: Same issues.
- Tried TI's example program "Example_28035_Flash": Same Issues.
- Tried moving the ControlCARD from my custom PCB to the TI docking station with the Blackhawk USB2000: Same issues.
- Tried ControlCARD on TI docking station connected via onboard USB (XDS100) to a different computer: Same issues.
I now suspect that my ControlCARD is causing this. Is it possible that the ControlCARD's FLASH memory is corrupted somehow, so that no debugger can connect to it?
The first error I get is :
Error connecting to the target:Error 0x80000200/-1041Fatal Error during: OCS, Device driver: Problem with the Emulation Controller.It is recommended to RESET EMULATOR. This will disconnect each target from the emulator. The targets should then be power cycledor hard reset followed by an emureset and reconnect to each target.
And then after pressing Retry :
Error connecting to the target:Error 0x80000240/-233Fatal Error during: Initialization, OCS,
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.