• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 356 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.

CC1352R: CC1352 custom board bring-up

Alex Kalyadin
Prodigy 10 points
Part Number: CC1352R
Other Parts Discussed in Thread: UNIFLASH, TMDSEMU110-U

Hello,

We have a custom board with CC1352 exhibiting very odd behaviour. Pcb has standard JTAG interface and, frankly, very similar to Launchpad's reference design. What it makes especially weird - it is a second revision with minimal changes - there were no problems with rev1.

Now, what is happening - program often(mostly-like 90% of the time) fails to flash from within CCS but flashing works fine in Uniflash or RF Programmer 2. But! Code execution does not start. However, simple examples like LED toggle occasionally work fine? fw image validation from within Uniflash/RF programmer works fine. CRC and image read-back.

More to that - apparently RF Studio tests run just fine. I can see  packets sent from the custom node to Launchpad(s)

Any help much appreciated.

Silicon rev E 2.1

CCS 10.2

XDS110 TMDSEMU110-U

Windows 10 PC

Regards,

Alex

  • +1
    TI__Guru**** 317180 points

    - Please outline the changes between the two revisions.

    - The code (examples) you are trying to run, do they go down in Standby meaning do they use the 32 kHz xtal? 

    The non-RF examples are using the internal HF-RCOSC to execute the code meaning that the code execution is dependent on very few external components. 

    It sounds like your new PCB revision has some fundamental HW issues (something not connected properly or similar) but without knowing anything about the design I'm not able to be more specific.