This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
It is possible to run code on a Stellaris device that causes the device to lose JTAG communication. The two most common causes are:
If you accidentally do either of these things, you can restore communication with your target device by running the Debug Port Unlock utility in LMFlash Programmer as shown below. Select the appropriate product class for your device. If you don't know the class for your device, you can find it by reading the Device Identification 0 (DID0) register at address 0x400F.E000. Then click on the "Unlock" button.
On Tempest- and Firestorm-class devices, the MAC address is erased by the Debug Port Unlock utility, so be sure to write down the number before running the utility.
For further advice on bringing up a board with JTAG, see this post from cb1.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
I use a XDS 100v2 JATG emulator to connect the board. The emulator is made by Blackhawk. It has a cTI 20-pin header.
I ues a 20e_cTi-20t_ARM pin converter to connect it to a MDL-ADA210-pin to 20-pin JTAG adapter module, and then connect to Board.
The configuration is shown as below:
In reply to alex yu:
You cannot use the XDS100 with LMFlash programmer. You need to use another Stellaris evaluation board to do a debug port unlock sequence.
In reply to Sue Cozart:
Could you recommend me what kind of Evakuation board that is duitable for that application ?
Any one will work, except for the EK-LM4F232 board. The EK-LM3S811 is the cheapest at around $50.
Is it suitable for febuging and programming LM3s9B92 based applications?
Yes it is, Alex.
I have the EKS-LM3S811. And I tried to unlock the board, but it shows an error: unable to initialize target -1! as shown below:
Could you please tell me what cause the problem. and how to solve it?
I'm sorry for the delay in responding - I was on vacation. What is your configuration on the front tab? You have to configure for the target (use EK-LM3S9B92), not the emulator.
Yes, I used LM3SB92 Evaluation Board as the target in confiuration.
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.