• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 56 subscribers
  • Views 874 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.

CC1352P: Unable to debug CC1352P based custom board

Bibin Varghese
Intellectual 815 points

Part Number: CC1352P

We made a new card with CC1352P. (CC1352P P1F3 C, no. written on top of the IC). We are using CX2016DB-48MHz Crystal across the pins P46 & P47. We made a ribbon cable to connect the JTAG lines of our board to the XDS110 JTAG pins of the CC1352P-2 launchexl board after removing its jumpers. When we are trying to debug, from IAR, its failing. We have connected only pins 1 & 3 of the crystal. Other pins(p2 & p4) are floating. We are not seeing the 48MHz clock across the crystal pins(P1 & p3). We are seeing a 48MHz clock across the corresponding pins on the laucnhexl board. we havnt wired the shunt caps at the xtal pins.

We have measured a voltage of 1.67 at the DCDC_SW(P33) when the VDDR & DCDC_SW are shorted via inductor and a voltage of 1.8V when these pins made open.

In both cases we are not seeing the 48MHz and not able to debug.We have wired two cards and both having the same issue.

How can we solve this issue?

  • 0
    TI__Guru**** 317180 points
    - Have you tried to connect using SmartRF Studio or Flash Programmer 2?
    - Do you have a picture on how you have connected the board?
    - Could you share the schematic for the board? (If you don't want the schematic public, please send me a friend request)
  • 0 in reply to TER
    Intellectual 815 points

    We will try it with Smart RF studio.

    We have tried only with IAR. But its working with launchpad when we short the jumpers btw onboard JTAG debugger and CC1352P on the launchpad.

    Why we are not getting the 48MHz clock on the crystal pins. We are able to see the same in the launchpad in mV range.

    How can i add u as friend to share the schematic?

  • 0 in reply to Bibin Varghese
    Intellectual 815 points

    Interconnection btw the boards is shown in the schematic below:

  • 0 in reply to Bibin Varghese
    TI__Guru**** 317180 points
    I assume that the last two posts are missing a picture?
  • 0 in reply to TER
    Intellectual 815 points
    Schematic is sent in private mode. Pls verify the same.
  • 0 in reply to Bibin Varghese
    TI__Guru**** 317180 points
    Still waiting for the pictures that are missing in the posts.
  • 0 in reply to TER
    Intellectual 815 points

    There was a connection mistake in the JTAG interface btw the launchpad and our custom card. It is now resolved.

    Now we are able to transmit packets from both Smar RF studio and from our easylink Tx example project running in IAR.

    But we are still working with external clock(48MHz) from a function generator.(connected to pin 47)

    When we connect a crystal across the 46 & 47 pins, we are unable to debug in IAR or send a paket in IAR or smart RF studio.We are not seeing any clock across these pins.

    As shown in the reference design, we havn't connected the shunt caps in these pins. Is it required.

    We havnt connected pins 2 & 4 of the crystal to GND. Is it required?

    We have used the same family of crystal mentioned in the ref design(CX2016DB48000D0).It is having a load cap spec of 8pf than that of the one used in ref design(7pf). Is it an issue.

    How can we solve the clock issue?

    Another observation is, when we used a laptop to power the launch pad and when we connected the adapter to charge it while testing and when we connected the GND pin of the launchpad with a DSO, a spark occurred and the CC1352P got damaged.(not detecting in smart RF and no voltage at VDDR). Why its happening so?

  • 0 in reply to Bibin Varghese
    TI__Guru**** 317180 points
    - Note that TCXO is not official supported for CC1352P at the moment. It's ongoing work that will be finished later this year.

    - For ground connection of the xtal: Please check the datasheet for the xtal and follow what is stated in this.

    - With regards to shunt caps for the xtal, see chapter 6 in www.ti.com/.../swra640a.pdf . If the xtal require a different load than default, you have to adjust the cap array.

    - Spark: Sounds like the ground potential on what you have connected to the board is different.