Getting "Debug Port error occurred" when trying to launch CCS debugger

Hello David

It seems that the CPU is accessing the address location 0xb1064965 and a disassembly or memory window is open in the same address space.

There must have been some change otherwise the CAN Bus activity would have been there if the code was working as expected.

Hello Amit,

Thank you for your reply and your completely useless answer. Apparently the .metadata file in the active workspace was corrupted somehow. I deleted this file, re-imported the project into CCS and now it works fine.

Hello David,

Considering the information presented the response to your post was the most appropriate as I had no clue that you had somehow managed to corrupt the .metadata file. Investigation of an issue has to start with eliminating the obvious and that is what I had started with.

Hello Amit,

Your initial response did not start by eliminating anything ---- your two line comment, the first of which says:

"It seems that the CPU is accessing the address location 0xb1064965 and a disassembly or memory window is open in the same address space"

Has nothing to do with solving the problem I was reporting, but simply stating the problem through the use of jargon that is appropriate to a level lower down in the inner workings of the debugger.

Your second comment:

"There must have been some change otherwise the CAN Bus activity would have been there if the code was working as expected"

Is priceless. Something has changed? Thank you, Captain Obvious........

Now that you have, as you say, "eliminated the obvious", I guess its okay for you to actually spend some time thinking about the reported problem and rummaging through your solution database to actually provide me with some assistance.

In closing ---- I did not corrupt the .metadata file ---- I didn't even touch it. The debugger corrupted the .metadata file.

Keep up the good work!

David

I'm no apologist for this vendor - differ w/many of their methods/madness.

That said - your personal "attack" upon Mr. Ashara was completely uncalled for - and w/out redeeming value.   Surely you're frustrated - yet what could be gained by resorting to such harshness?   (you've effectively (properly) turned the entire forum against you!)

I doubt that this is your normal, "Modus Operandi" - and you're (likely) having a bad day.   But such attack is inexcusable - really an apology is very much in order!

Know that Mr. Ashara has hundreds (perhaps thousands) of "Tech fans" here - and his record is w/out equal.

His strength of character & commitment is such that I'm confident he will continue to answer your (future) pleas - in spite of such unwarranted attack.   And most others (surely) and deservedly would not!

I stand by my previous comments -- as I stated to Mr. Ashara, his initial reply to me was absolutely useless, and quite frankly, an insult to my intelligence. I am sure that Mr. Ashara is quite knowledgeable in his field, however replying to my request for help with a statement that offers absolutely no insight to the problem at hand (and I am CERTAIN that this problem has been reported before) smacks of intellectual and professional laziness. I find it hard to believe that Mr. Ashara does not have at the ready (or at least with several clicks of the mouse) an entire laundry list of potential causes for the problem that I reported, as well as a list of potential solutions. Upon receiving his initial response, it was necessary for me to undertake my own web search to find other individuals who have experienced the problem that I reported, and fortunately I was able to find a solution in a corner of the web completely separate from Texas Instruments.

As an electrical engineer with over 30 years of experience in both digital and analog electronics, I have been using Texas Instruments components in my designs for decades. Unfortunately, in the past five years or so, I have seen the company's customer support and field applications engineering staff degrade steadily, and it is now getting so bad that I oftentimes need to wait over a week to get technical support. Many engineers with whom I work share this frustration, and some of us are actually turning to other semiconductor vendors because of the poor state of Texas Instruments customer support.

I am well aware that the problems that TI has in this area do not fall solely upon Mr. Ashara's shoulders, however, when an engineer contacts technical support, the person who assists them, whether they like it or not, is the FACE of the company for whom they work. As a professional myself who deals with customers all the time, when people come to me with technical problems, I do not answer them with statements like, "Well, something must have changed, because otherwise the system would still be working." Surely you agree that such a statement says nothing, means nothing, and accomplishes nothing.

David

Hello David,

I believe in your frustration at the issue, you have not read my post. It was "eliminating" and not "eliminated" that I had mentioned.

If as an experienced engineer, you cannot seem to eliminate the "inner workings of the debugger" as a probable cause for something "all of a sudden two days ago", I can surely understand the insult you may have felt (for which I am truly sorry).