• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 656 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

tms320c6727 trioubles

albertburbea
Intellectual 330 points

Hi

I developed a board with 2 6727 on it.

I succeed connecting the JTAG emulator to the board BUT

1. The two devices are recognized as 6720 by CCS

2. One is Little Endian, the other is Big endian (!!!! there is no 6727 big endian!!!)

3. When I download some sample code, I see a lot of strange data near _c_int00

4. When I try to fill memory, CCS barely succeeds writing 8 DWORDs

5. If I write single DWORDS either in internal or SDRAM memory, it succeeds

6. Very often CCS complains that it is not able to set a breakpoint.

It seems that my JTAG connection is bad. How can I troubleshoot this?

Also, the JTAG connection testing software that comes with the emulator succeeds testing the connection, even at high speed (30 MHz)

Albert

  • 0
    TI__Guru* 84110 points

    Very bad situation. You have done some good debug so far. I would probably cut the speed way down on your emulator until you get this working.

    Make sure that you have the latest:

    • CCS Service Release
    • Emulation drivers for your emulator pod
    • Chip Support Package for the C6727 (some versions of CCS required this)

    Most likely, you have some bad wiring connections on the board or power supply noise problems or clock/reset signal problems.

    Do you have a known good board with one or two C6727's so you can prove that your emulation setup is valid? An EVM or DSK or such would be nice so you can at least eliminate the software installation and emulation as part of the problem. Of course, going from emulation of 1 DSP to 2 DSPs is a big step, with difficult steps sometimes required to get it done right.

    To try to eliminate one DSP or the other, in CCSetup you could replace one DSP with a BYPASS with the correct scan length. Then try CCS again and see if it works any better. Swap to bypassing the other one to see how that changes your results. Also, if you can modify the board's JTAG traces temporarily to physically bypass one DSP, that would help eliminate some of the issues on one chip from affecting the other one.

    Then, start checking every signal looking for noise or poorly shaped signals (slow rise/fall times), check for valid signal levels on everything, but start with clocks, JTAG signals, reset(s), and power supplies.