Ccs can initialize target cpu

A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question. Ask a new question Ask a new question Cancel. Tags More Cancel. Share More Cancel. Similar topics. This thread has been locked. Prodigy points. Thanks in advance. Gautam Iyer over 7 years ago. Guru points. The last line of output indicating ' scan-test has succeeded' indicates that we have a complete and functioning JTAG scan path, but may not necessarily mean that everything is correct.

We will explore this condition in a future article. One possible problem is the an input or output signal shorted to ground like in the output below:. We can troubleshoot this problem with the help of a scope and a new command. Tracing the TDI signal will allow us to locate the point of failure.

This will wrap up this article, and we will address more advanced troubleshooting issues in the next article. To post reply to a comment, click on the 'reply' button attached to each comment. To post a new comment not a reply to a comment check out the 'Write a Comment' tab at the top of the comments. Registering will allow you to participate to the forums on ALL the related sites and give you access to all pdf downloads.

Mike has over 30 years of direct involement with embedded systems like communication controllers, mainframe and minicomputer peripheral controllers, custom minicomputers, microcontrollers and DSPs. His role in these systems has included hardware, microcode, firmware, and software for companies ranging in size from startups to Fortune Mike also enjoys sharing his knowledge and experience with others.

Blogs Mike Dunn. Configuration The previous article discussed CCS configuration. The ccBrd0. Step 2 - Read the Output!

If the target does not have power, the out put looks like: [Print the reset-command software log-file] This utility has selected an XDS class product.

If I accidentally used the standard TI XDS configuration, my output would look like: [Print the reset-command software log-file] This utility has selected an XDS class product. Selecting an invalid address gives an expected error message.

It would be more accurate if it said something like: The standard emulators use ports 0x0, 0x1, 0x2 and 0x3. One possible problem is the an input or output signal shorted to ground like in the output below: [Print the controller-open software log-file] This utility has selected an XDS class product. The details of the first eight errors have been provided. The utility will now report only the count of failed tests.

Scan tests: 1, skipped: 0, failed: 1 Do a test using 0x Scan tests: 6, skipped: 0, failed: 5 Some of the values were corrupted - Comments Write a Comment Select to add a comment [ - ]. But there seems to be something else, too. Thank you very much for very useful post.

I've read it and solve some of my problem. This utility will load the adapter 'XDSU2. The emulator adapter is named 'XDSU2. The emulator adapter is titled 'Custom block-mode adapter for use with an TDS '. The emulator adapter is using 'Block-Mode'. This utility will attempt to reset the controller. This utility has successfully reset the controller.

The scan-path link-delay has been set to exactly '0' 0x The explanation is: The length of the scan is too large for the emulators controller. That's all for now, mikedunn p. Part 2 is here. Comments Write a Comment Select to add a comment [ - ]. Thanks for this. In the past, I have spent over days setting the tools up before I have written a single line of code.

Very frustrating! This will definately help. What is so different about all these emulators? Thanx for the comment vakilp.

I plan to do a more detailed article on emulators in the future. You add a unique piece of hardware in the middle [a vendor's emulator] and some amount of unique software [a vendor's software]. After you do this, you must communicate with CCS how to access the vendor software and target.

It all sounds so simple - but then you throw in the real life situations. Once you consider the total universe - different versions of CCS, different vendor's emulators, and different types of targets the task of configuration can become difficult at times. Very nice writeup Mike. Do not hesitate to announce this document to the c6x group. I am sure many people will benefit from it.

Thanx and regards linda. Linda, your problem may originate as a software bug. The error message portion "Target CPU: Invalid Source port address" which is shown as "0xffffffcf" [a definite bad address]. The code that you are running could be written for a different C family member than you are using causing the invalid address.

Mike, I am taking the advantage of asking you for help. I love digital signal processing and i have theoretical experience on it. But as i do not have any experience programming DSP, I do not know and like to know how to configure different peripherals around the dsp core and it's associated GPIO pins. I just wanted to hear from someone like you if it is true. Please drop a note for me. Any sample code that configures a target would be great help.

If you have CCS installed, there are probably example or tutorial projects for the 55x installed. You may have to modify the addresses for the OMAP. You can also search ti. I hope this helps. Thanks a lot mike.