• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 41 subscribers
  • Views 883 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.

CCS/CC3220MOD: Boundary Scan and JTAG Interface CC3220MOD

Forrest Erickson
Genius 4125 points
Part Number: CC3220MOD
Other Parts Discussed in Thread: UNIFLASH,

Tool/software: Code Composer Studio

We have build three prototypes of our product which incorporates the CC3220MODA.
We have used a launchpad to program the code in to two of the three prototypes.  We put the target into SOP1 and applied power. We worred the U0 TX and TX from the launce pad to the target. We connected the JTAG interface from the Launchpad to the target.  We Power cycled the target and the launch pad and powerd on the target first.
We used UNIFLASH 4.40 to program the target in Development mode.

With the LAUNCHPAD as programer and debugger, we were able to read the MAC address on two of the three target hardware boards and program the CC3220MODA in Development mode.

We can not get the programmer to read the MAC address. It times out and reports an error:

I have verified proper 3.3Volts to the target. I have inspected the UAR and JTAG connections between the Launcpad and the target and found no errors.

I have no shorts on the JTAG interface.

I tried loading software in the blind (with out reading the MAC) in production mode but again the UNIFLASH times out.

Not sure what to try next.

Has anyone ever developed a boundary scan test for the JTAG interface and the UART0 interface necessary to program this part?  Anything to help us better localize the fault.

  • 0
    Genius 4125 points
    The launchpad we are using is a CC2320MODA
  • 0 in reply to Forrest Erickson
    TI__Mastermind 22935 points
    Hello Lee,

    Just to make sure we are on the same page, are you trying to use a CC3220 LP to program the CC3220MOD on your prototype? Also, are you trying to program the CC3220MOD via UART or JTAG? If you can reference our documents as to what programming method you're trying to use that would help.

    I don't know if this one would be relevant to you.

    www.ti.com/.../swpa230a.pdf

    Jesu
  • 0 in reply to Jesu
    Genius 4125 points

    Hello Jesu,

    I am using a CC3220MOD Launchpad like at this link:

    I am connecting both the JTAG and the UART0 interfaces and have successfully programmed a factory fresh part using UNIFLASH and both the TI OOB and our own code.


    Because the pads on the MOD are under the part where they cannot be inspected I had the idea that perhaps it was time to learn how to do Boundary Scan and shift in and out test patterns on the IO to aid factory test. Thus my question.

    I hope to review the SWPA230A document tomorrow, thanks for the link.

    Regards!

  • 0 in reply to Forrest Erickson
    Genius 4125 points
    Forgot to say I found a backwards diode in three of our five prototypes (We are still wondering how that happened) preventing our programmer from putting the device in reset. Once I cleared the diode problem the prototypes programmed.

    I still want a way to do boundary scan to probe connections in the factory test. I admit I am not sure JTAG BOundary scan would have helped me find this problem but I sure want a way to troubleshoot the JTAG interface too and shifting in a pattern to light an LED comes to mind.
  • 0 in reply to Forrest Erickson
    TI__Mastermind 22935 points
    Hi Lee,

    From what I gathered you can only perform boundary-scan tests through a dedicated port called the test access port (TAP). Unfortunately, according to the TRM for the CC3220, TAPS are reserved for TI production testing.

    Jesu
  • 0 in reply to Jesu
    Genius 4125 points

    So bottom line is that there is no Boundary Scan Definition File available or other ideas for how to qualify a TAP which is not functioning or not functioning as expected?

    Nor, short of loading an application we write, a way to test module connectivity?

    While not the answer for which I hopped I guess this closes out my question.  I will mark as resolved.