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.

CCS/TMS320F28027: JTAG issue with TMS320F28027

Part Number: TMS320F28027
Other Parts Discussed in Thread: LAUNCHXL-F28027

Tool/software: Code Composer Studio

We are having FTDI FT2232H device connected with JTAG port of TMS320F28027 MCU as per reference schematics of evaluation card

C2000 Piccolo MCU F28027 LaunchPad™ development kit

. My case is

1. We have the source code (tida01292 reference design) for programming the MCU, which is running on EVAL Card (F28027 launchpad) but, we are unable to dump it to MCU through JTAG on fresh Card.  

2. As JTAG of the MCU is coming from FTDI FT2232H, we want to dump MCU source code through FTDI USB port from PC.

3. The MPSSE JTAG reference C++ code from FTDI  is working through Visual Studio, but after that how can I dump my MCU Source Code through this?

when i m dumping  the source code from CCS onto fresh MCU it displays the following error.

Kindly tell us what application needs to be run or modification that needs to be done for JTAG programming or MCU for it to able to accept my program.

 

  • Hello Rajat,

    Just wanting to clear this up, are you using the LAUNCHXL-F28027? are you using an external Debugger or the on-board Debug probe?

    Please first go through the JTAG Debug guide and let me know if it helps. http://www.ti.com/lit/spracf0

    Regards,
    Mark
  • We have a board on which LAUNCHXL-F28027 schematic is used and we are using an on board debug probe xds100usbprobe2
  • Ok, so essentially you just have the LaunchPad plugged into whatever board you have it on and are using the provided on-board debug probe. I am assuming that there are no modifications to the LaunchPad itself?

    As previously mentioned - work through SPRACF0 and let me know the results.

    -Mark
  • No sir, no modificationswe on the  fresh board, same schematics of lauchpad is implemented on it. On this dumping code through JTAG option isn't working

  •  Hi mark,  

    we followed the document and we were able to configure it to JTAG mode with XDS100v2 , thanks alot for that.

    But during code dumping stage we are getting the following , I presume it is because of low voltage level on XRS pin. We read the probable causes of low XRS, no brown out  as volatage levels are proper.

    Kindly help us out, awaiting your response  

  • Thanks for confirming that.

    Yes, if XRSn is held low, you will not be able to connect. it sounds like you might have other issues going on with your hardware that is unrelated to the debugger link.

    1. If XRSn is held low, look for external drivers on your board. what else is connected to XRSn? can you share the schematic of just this net?
    2. If XRSn is toggling, that may indicate other issues such as incorrect boot mode settings.
    1. Check your Boot pins, what are they set to? refer to the datasheet and TRM for the configurations
    2. See this thread: https://e2e.ti.com/support/microcontrollers/c2000/f/171/t/608448
    3. See this thread: https://e2e.ti.com/support/microcontrollers/c2000/f/171/t/377523

    -Mark

  •  Hi mark ,thanks for the posts, I have gone through the boot mode and e2e posts

    The e2e posts are more focussed towards toggling reset pin, but in my case it is low i.e i m getting a low signal on XRS pin4.

    I m using same boot settings as it was done for launchpad .

    I.e tdo,gpio34 and trst pins mainly.

    I dont know why i m getting low level on XRS, i m using same boot configuration as used for launchpad. Anything else needs to be done, because now the connection (JTAG DR integrity test succeeded) only problem is this reset is enabled.

     I m attaching the schematics for your reference

  • Rajat,

    I believe that You have one issue in your schematic that is likely contributing to your current problem.

    You are connecting 3.3V to Pin43 which is one of the 1.8V pins (VDD). Additionally, you have VREGENz (pin 34) pulled to GND, which enables the internal VREG. So, the MCU is sourcing 1.8V for the core supply, but is seeing 3.3V on one of the 1.8V pins... 

    The MCU explicitly pulls XRSn to 0V when the internal voltage regulator is enabled and an over-voltage condition is present. See the On-chip Power-On Reset (POR) and Brown-Out Reset (BOR) Circuit section in the datasheet (SPRS523).

    It is unclear if you have already permanently damaged the MCU by having this over-voltage condition. You may be able to correct the issue by modifying the board and debug. (cut the trace between C92  and VCC_3V3_flush  to isolate the 3.3 V Supply and VDD2. - you still need that capacitor on the pin. Long-term however, you will need to correct your schematic and release a new version of the board.

    Additionally, the XRSn circuit and decoupling capacitor values on the power pins are not quite what our recommended values are these days. You can refer the datasheet for the proper values and circuits for this device. This LaunchPad was release about 8 years ago, and does not quite follow our latest best practices.

    Regards,

    Mark

  • Thanks Mark, I removed the 3.3V net from pin 43, its working now.