CC1352R: rfEasyLinkTx_CC1352 example crashes custom board

Martin Helie

Expert 2555 points

Part Number: CC1352R
Other Parts Discussed in Thread: CC1310

Hello,

I have a CC1352 custom board which seems to work correctly in SmartRF Studio, which I can program correctly, etc.

But on running the SimpleLink example "rfEasyLinkTx_CC1352R1_LAUNCHXL_tirtos_ccs",

I get

Cortex_M4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.0.803.0)

Cortex_M4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.0.803.0)

soon after it attempts transmission.

I have attempted slowing down XDS110 to a crawl, but still no dice.

Any help appreciated.

over 6 years ago

0 Severin Suveren over 6 years ago

TI__Mastermind 23730 points

Are you able to start a debugging session and halt in main?

0 Martin Helie over 6 years ago in reply to Severin Suveren

Expert 2555 points

Hi,

yes, I can step through the code.

Crash occurs in RF_postCmd() in RFCC26X2_multiMode.c, as soon as hardware interrupts are re-enabled at the end of the function,

0 Severin Suveren over 6 years ago in reply to Martin Helie

TI__Mastermind 23730 points

Which SDK version are you using?

0 Martin Helie over 6 years ago in reply to Severin Suveren

Expert 2555 points

Hi Edvard,

simplelink_cc13x2_sdk_2_20_00_71 & xdctools_3_50_07_20_core

0 Severin Suveren over 6 years ago in reply to Martin Helie

TI__Mastermind 23730 points

Do you have a LAUNCHXL-CC1352R1 to test with as well?

0 Martin Helie over 6 years ago in reply to Severin Suveren

Expert 2555 points

Hello Edvard, yes I do, and that actually works.

0 TER over 6 years ago in reply to Martin Helie

TI__Guru**** 317180 points

If the code runs on the LP and ont on your custom board it could indicate that the 24 MHz xtal osc is not running as needed. Is it possible to post the xtal portion of your schematic?

0 Martin Helie over 6 years ago in reply to TER

Expert 2555 points

Hi TER, pretty straightforward (48MHz for the CC1352, right? - disregard mislabeled pins on schematic). Note that transmissions work with SmartRF Studio. Could a capacitance offset for the Xtal explain this problem? (I am pretty sure I imported the RF config from RF Studio, but I may have made a mistake, and the target's 5pF difference may not have made it into the CCS project).

For ref:

0 TER over 6 years ago in reply to Martin Helie

TI__Guru**** 317180 points

You are right, if it was a issue with the 48 MHz xtal (I thought of CC1310 when I wrote 24 MHz) it should not have worked with Studio.

What is the 5 pF you mentioned? If you have tuned the internal xtal array you can set this in the CCFG as described in processors.wiki.ti.com/.../CC13xx_CC26xx_Crystal_Tuning

What is the delta/ differences between your board and the launchpad since the later work?

If you just flash your board and run the code on it without the debugger connected, does it send packets?

0 Martin Helie over 6 years ago in reply to TER

Expert 2555 points

Hi TER,
sorry - 5pF was wrong; I erroneously thought the offset was in pF to the xtal. Basically, there is a 0x05 offset in the cap array in SmartRF Studio form my board, that's all.

Differences: mostly, my board only breaks out a few GPIO pins (no LEDS, buttons, etc), and the flash memory is on different pins (properly set up in my board file). The biggest difference is that there are two antennas and I am using baluns.

I tried just flashing, and it looks like it's working for a bit, then I get the same error (though printed only once), and the process ends.

Other projects flash correctly (for example, the rfPacketRX counterpart flashes OK).

0 Martin Helie over 6 years ago in reply to Martin Helie

Expert 2555 points

...and I now confirm it doesn't appear to be transmitting. As though the code weren't flashed properly or at all. Or something else :-)

0 Martin Helie over 6 years ago in reply to Martin Helie

Expert 2555 points

@TER, I lowered the transmission power and it no longer causes the problem. Any idea what might be wrong on my board, that being the case?

0 TER over 6 years ago in reply to Martin Helie

TI__Guru**** 317180 points

Interesting. Do you have a spectrum analyzer so you are able to check the spectrum of the sent signal? It could sound like you have a feedback from the RF to something else that impact how things works.

I can do a schematic/ layout review if you like (send me a friend request if you want to send it to me directly) to see if anything sticks out.

Sub-1 GHz

Sub-1 GHz forum

CC1352R: rfEasyLinkTx_CC1352 example crashes custom board