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.

TMS320F28062: Flashing/debugging F28062 using LAUNCHXL_F2800137 XDS110 on board programmer

Part Number: TMS320F28062


Hi all,

At our company, we have two generations of motorcontrollers. The "old" using the F28062. We're currently using an Spectrum Digital XDS200 with a conversion board to program it.

For the "new" motorcontroller, we're using the F2800137. We've developed the code initially on the LAUNCHXL_F2800137, with of course using the onboard debugger.

Now, we've created a conversion print from the LAUNCH board to the actual hardware design of the F2800137 motorcontroller. Using a 12 pin jtag header.

The old controller uses a 10 pin jtag header. The conversion print from the LAUNCHXL is a direct connection from the 14 pin jtag header to a 10 pin, and 12 pin header.

Now here is the issue. Programming, debugging, reading memory, etc, works wonderfully and reliably on the F2800137 hardware design (the "new" motorcontroller).

However, it does not work with the F28062 board. All using direct JTAG connections.

What are we missing here? The JTAG connections can be direct right? Since that's how it was using the Spectrum digital probe, and the F2800137 probe.

Sometimes we get a 'SC_ERR_PATH_BROKEN', sometimes a reset error, and sometimes no connection at all. There is no real correlation. The F2800137 always works.

We're trying to resolve this since we want to use a single debugging probe for both devices. The LAUNCHXL board will also be used as a functional tester for the software department. So the DUI will be programmed using the on board XDS110, and tested using the actual F2800137 processor on the LAUNCHXL board.

Thanks in advance!

  • Hi,

    At our company, we have two generations of motorcontrollers. The "old" using the F28062. We're currently using an Spectrum Digital XDS200 with a conversion board to program it.

    Is the old conversion board from 14 pin JTAG to 10 pin for your header? 

    The old controller uses a 10 pin jtag header. The conversion print from the LAUNCHXL is a direct connection from the 14 pin jtag header to a 10 pin, and 12 pin header.

    Are you using the same 14-pin to 10-pin conversion board? 

    From the error message, I am thinking that there is some problem with the JTAG pin connections. I would make sure that TCK, TMS, TRST, TDI, TDO, GND are all properly connected between your JTAG debug probe and your target board.

    Best Regards,

    Ben Collier

  • The old conversion board is a TI board i think. Called PWB 510401 REV A. This goes to a connector we made to the 10-pin on our hardware. This connection to the Spectrum Digital XDS200 works fine.

    We are not using the same conversion board on the new motorcontroller.

    The error message keeps popping up, even if we make a direct connection from the JTAG pins on the LAUNCHXL board to the JTAG pins on the TMS320F28062. These connections have been verified.

  • Could you please post a screenshot of the advanced tab of your target configuration? 

    Please click on the debug probe so you can see the settings like this:

     

  • Here you go:

    This is the debug configuration for the LAUNCHXL_F2800137 as debug probe connecting to the F28062 over JTAG.

  • Hi Christian,

    I just noticed this:

    The error message keeps popping up, even if we make a direct connection from the JTAG pins on the LAUNCHXL board to the JTAG pins on the TMS320F28062.

    The F28062 needs more JTAG signals than the F280013x. For example, it needs TRST and possibly EMU0 and EMU1.

    The F280013x launchpad does not pinout TRST, so I wonder if this is the source of your problem. You may need the standalone XDS110 if you want to use the XDS110.

    Best Regards,

    Ben Collier