Quantcast
Channel: Forums - Recent Threads
Viewing all articles
Browse latest Browse all 262198

CC1352P: CPU going to unknown state while calling RF_scheduleCmd in the rfpacketTx example

$
0
0

Part Number:CC1352P

In our custom board we are using CC1352P.

We have tried both the recommended crystals(48MHz ) but the board was not working when the RF is invoked.

Same situation with Smart RF Studio & in IAR project. We tried with different cap delta values , but still it was not working.

Later when we connected an external 48MHz clock from a function generator,it started working and transmitting and receiving packet both from

Smart Rf Studio and from IAR project.

Then we connected an external TCXO output to the same point. It was working in the AC coupled mode with smart RF studio with a cap delta value of -16.

Same is not working with the IAR project.

Then we edited the ccfg.c for enabling the cap delta and added the delta value(0xf0).

But the project is stucking when we call the RF_scheduleCmd which was working previously in the function generator case

To see the effect of the cap delta value in the ccfg file, we read back the register using the following code:

ccfg_ModeConfReg = HWREG( CCFG_BASE + CCFG_O_MODE_CONF );

Value read in the ccfg_ModeConfReg variable showed that the cap delta is enabled with the given value.

We have the following questions:

1. Why the board is not up with any of the recommended crystals(AVX & NXP)?

2. Why the board is behaving differently with  function generator output clock and TCXO clcok output ? (TCXO case requires cap tuning)

3. Why the board is not working with IAR project while working with Smart RF studio when a TCXO is connected?

   What additional we need to do in the IAR project to work similar to the smart RF studio in the TCXO case?


Viewing all articles
Browse latest Browse all 262198

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>