• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 903 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC1310 Custom Board TI Stack Crashes during RF Commands

Gregor Ponert
Prodigy 70 points
Other Parts Discussed in Thread: CC1310

Hi,

I have a strange problem with my own designed Board based on the CC1310.

As a basis for my design  I used the cc1310 Launchpad schematic and combined it with a compact pcb antenna from another TI reference design.

For testing, I modified the packet error rate application so that I have one stand alone Transmitter and one Stand alone Receiver. With two cc1310 Launchpad everything works as expected and fully stable.

When I program the Test Firmware into my own pcb (using the CC1310 Launchpad as programmer), the Software in principle runs normally. However, when trying to transmit a packet calling the RF_runCmd or a RF_postCmd followed by a RF_pendCmd, the TI Stack does not transmit anything, but instead crashes and never returns from the RC command Calls.

The Receiver Firmware behaves very similarly: when calling the RF Command on my board:

    /* Set the frequency */
    RF_cmdFs.frequency = config_frequencyTable[config->frequency].frequency;
    RF_cmdFs.fractFreq = config_frequencyTable[config->frequency].fractFreq;
    RF_runCmd(rfHandle, (RF_Op*)&RF_cmdFs, RF_PriorityNormal, NULL, 0);

the TI Stack never returns from the RFrunCmd Call. On the CC1310 Launchpad it works as expected.

After some research in this forum, my suspect was either the DCDC converter or the LF ext Oscillator. So I systematically switched to the RC LF Oscillator and disabled the DCDC converter and cross checked that the resulting Firmware still worked on the Launchpad after each step. On my custom boards (I tried several of them) still the Software crashes when calling the RF commands !

Now I do not have any other idea what to check or what to try...

Is there any magic initialization that needs to be done with a factory fresh CC1310 ? Do I need a "real" debugger for programming the CC1310 custom board ?

Any other Ideas or hints ?


Thank you,

Gregor

  • 0
    TI__Mastermind 36375 points

    Gregor,

    No, there is no magic that needs to happen first, but have you tried SmartRF studio and successfully transmit packets and receiver packets? If not, then you need to look at basic stuff like power supplies, XTAL oscillator, JTAG etc.

    For TISTACK

    Are you using the same device package size as the reference design?

    Regards,
    /TA

  • 0 in reply to TA12012
    Prodigy 70 points

    Hi TA12012,

    ad Package size: yes, same package size.


    what difference will it make to use SmartRF Studio ? (besides even less control over what´s happening)


    As I wrote, the microprocessor is running. So obviously JTAG is working, otherwise I would not be able to download Firmware and run the Firmware. Debugging also works (e.g. Breakpoints) up to the point where RF Commands are being called.

    Whaz sould I check regarding power supplies and XTAL oscillators ? Are there Register Flags that can be checked ?


    Best Regards,

    Gregor

  • 0 in reply to TA12012
    Prodigy 70 points
    OK, I tried SmartRF Studio.

    With a pair of Launchpads, everything is working fine.

    Then I tried to use my own board as Transmitter. It does not transmit anything. In the command view, I see that the Status: 0x0 IDLE is displayed for each command. I can only guess what this means. So I am stuck again and have no clue what to do next.

    Best Regards,
    Gregor
  • 0 in reply to Gregor Ponert
    Prodigy 70 points

    Last thing I checked was the XOSC HF and found out that the crystal I used did not match the package. After a quick and dirty fix by rotating the Package by 90 degrees the thing works like a charm ...

    Sorry for bothering you but this stupid mistake might still be helpful for somebody.

    by the way, the XOSC can be checked by:

        if ( OSCClockSourceGet( OSC_SRC_CLK_HF ) == OSC_XOSC_HF )
           {
              //  XOSC is working       
           }

     

    I fully agree that this was a stupid mistake. On the other hand it reveals a serious bug in the TI Stack: If for any reason at any time the XOSC HF would fail to work correctly, the Stack completely crashes. I propose that an TI Software engineer should take a look at this behavior (just remove the XOSC HF crystal and see what´s happening).

    Best Regards,

    Gregor