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.

frustrated with TMS320F2809

Other Parts Discussed in Thread: TMS320F2808

Hi all,

I am developing a new control board based on TMS320F2809GGMS. The developing environment is TI CCS 4 and Signum JTAGjet-C2000F emulator. We have been using TMS320F2808 on another board and never run into probelm. But with F2809, I got some frustrating issues. The first thing I noticed is on the new board the emulator can connect with F2809 and pass the JTAG test however when I tried to download firmware into the flash of F2809 (or even just trying to erase the flash) it seemed to take forever until I turn off the power. I replaced the F2808 on the old board with F2809 and repeated the testing and received the JTAG error message 'TDO changes, but TDI pattern doesn't match'. By probing TDO and TDI with Oscilloscope, I did find TDO was not able to follow the pattern of TDI exactly. It appeared that some pulses were lost in TDO's waveform (the signal waveform seemed quite clean as I slowed down the JTAG clock to 10KHz). Again, with F2808, there is never such an issue with JTAG connection.

Anyone can kindly point out what might cause the difference between TMS2808 and F2809?

Thanks in advance,

wl

  •   there is a different emulation driver and flash API / programmer needed for F2809. make sure you are selecting F2809 in both of those set-ups. Make sure you change your memory map for F2809 as well.

     

  • Yes, I believe I have used right configuration files for 2809.

  • Two things I can think of that may be causing the problem:

    1) Check that the target config file (.ccxml file) is set to the right emulator and processor.

    2) It could be a hardware error. You say that this is a different board than the one with the 2808. Does it not work on all your boards or just one? (it could just be a faulty chip) Have you checked to see if the JTAG hardware (or any hardware) design is correct?  (Not saying that it is, its just we all do make mistakes sometimes).

     

    Tim

  • wl,

    I have a possible thought.  We had seen a similar issue with the Signum JTAG Jet and the 2809 eZdsp.  Basically the eZdsp had 5V on the power sense pin of the JTAG header. Spectrum did this so you could theoretically power an XDS510pp from the JTAG header.  I don't think they do this any more.

    Spectrum's emulators will not drive greater than 3.3V on the JTAG pins regardless of the voltage level on the power sense (PD) pin.  The Signum emulator, however, senses the 5V and drives 5V out on the JTAG pins. For some reason the 2808 seems to tolerate this while the 2809 and 28044 do not.  The fix for this issue is to set the JP2 surface-mount jumper located on the backside of the EzDSP to connect 3.3v to XTPD (or Pin5 of the JTAG header) rather than 5v.

    I suggest checking to see if you have 3.3 or 5V on the JTAG power sense pin.

    -Lori

     

  • Hi Chris, Tim and Lori,

    Thanks a lot for your advices. I think I have figured out the cause of my issue. The JTAG pins on my board under development (my user board) is connected with Signum JTAGjet-C2000F emulator's buffer board through a short ribbon cable. It was the length of this cable that caused the trouble. When the user board stuffed with TMS320F2808GGMS, the length of cable for successful communicaiton is about 6 inches long as I actuallly used. While when I stuffed F2809GGMS, the length of cable has to be much shorter, I actually made it about 2 to 3 inches long to make sucessful JTAG link betwee 2809 and emulator. This seemed to indicate the impedance characteristics of JTAG lines on F2808 and F2809 are different.

    Hope these observations can be helpful for anyone seeing similar issues.

     

    Thanks,

    wl

     

  • A complement/clarification to my last post:

    with F2808 stuffed on my board , the connection cable of 2-3 inches (working for F2809) is not working.