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.

Configuring .cfg file for CC1310 in IAR



Hi. everybody and hotline!

We have a problem with understanding of .cfg file structure.

 In CCS it is edited automatically in graphical mode but we have to use IAR and to edit the .cfg file manually.

 There are many docs describing this process especially for Code Composer (we've already seen it) but there is no information about how to write this file manually (description of it’s sections, examples in IAR).

Hope for your help!

 

  • Hi Anastacia,

    As you said, there is no means to graphically/automatically change the .cfg file in IAR.  However, in recent releases we have updated our example .cfg files to have the most commonly used modules & options available.  To select options you need only un/comment what is desired.  I have attached the config file for the uartecho example (from the 2.18.00.03 release) for reference.

    1325.uartecho.cfg

    If you are interested in full config details, all of the kernel modules (and options) are documented in cdoc which can be accessed through the product release notes: release_notes.html -> select bios_6_4x_xx_xx (in Products included section) -> select "SYS/BIOS APIs (cdoc)... ".  If you really require a graphical means to change the .cfg file, you could always use CCS to make the changes & copy over the file to your IAR project.  

    Regards,

    -- Emmanuel

  • Hi, Emmanuel!

    Thank's a lot for your reply. I'll inspect your example...

    Could you please also explain how could we use RF nonblocking (or blocking) mode? I mean files 

    RF.h
    RFCC26XX_singleMode.c
    RFCC26XX_multiMode.c

    For example it is quiet clear for UART:

    typedef enum UART_Mode {

    UART_MODE_BLOCKING,

    UART_MODE_CALLBACK

    } UART_Mode;

    typedef struct UART_Params {

    UART_Mode readMode; /*!< Mode for all read calls */

    UART_Mode writeMode; /*!< Mode for all write calls */

    unsigned int readTimeout; /*!< Timeout for read semaphore */

    unsigned int writeTimeout; /*!< Timeout for write semaphore */

    UART_Callback readCallback; /*!< Pointer to read callback */

    UART_Callback writeCallback; /*!< Pointer to write callback */

    UART_ReturnMode readReturnMode; /*!< Receive return mode */

    UART_DataMode readDataMode; /*!< Type of data being read */

    UART_DataMode writeDataMode; /*!< Type of data being written */

    UART_Echo readEcho; /*!< Echo received data back */

    uint32_t baudRate; /*!< Baud rate for UART */

    UART_LEN dataLength; /*!< Data length for UART */

    UART_STOP stopBits; /*!< Stop bits for UART */

    UART_PAR parityType; /*!< Parity bit type for UART */

    uintptr_t custom; /*!< Custom argument used by driver

    implementation */

    } UART_Params;ms;


    typedef enum UART_Mode {

    /*!

    * Uses a semaphore to block while data is being sent. Context of the call

    * must be a Task.

    */

    UART_MODE_BLOCKING,

    /*!

    * Non-blocking and will return immediately. When UART_write() or

    * UART_read() has finished, the callback function is called from either

    * the caller's context or from an interrupt context.

    */

    UART_MODE_CALLBACK

    } UART_Mode;

    But I've found only this about RF modes:

    The RF driver allows clients (applications or other drivers) to control the radio of the device. The radio interface can either be blocking or non-blocking.

    Best regards, Anastasia

  • Hi Anastasia,

    Unfortunately, I don't have expertise with the RF driver. Can you create a new post in the CC13XX device forum? They have more knowledge of the RF driver & can better support your RF questions.

    Regards,
    -- Emmanuel
  • Hello, Emmanuel!

    Thank you for your reply. I'll try your advise a little bit later.

    BR,

    Anastasia