• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 1135 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.

RTOS/EK-TM4C129EXL: How to configure TI drivers for new BIOS project using GUI

Naveen Kumar29
Intellectual 735 points

Part Number: EK-TM4C129EXL

Tool/software: TI-RTOS

I have opened a new Empty BIOS project in CCS 8.0.0. After that I have opened .cfg file in XGCONF. CCS had opened a GUI In which I had configured all Middle-wares and stacks necessary for my application. when I tried to configure Drivers, the GUI doesn't show any Options in the GUI windows. Hence how to configure TI Drivers in GUI windows??

Another question what is use of having board.c and board.h file, when user has option to configure the Stacks and middle-wares through GUI??? 

  • 0
    TI__Guru* 96960 points
    Hi Naveen,

    What version of TI-RTOS are you using? In tirtos_tivac_2_16_01_14, we removed the GUI configuration for the drivers. The only thing that was really configurable was instrumented vs non-instrumented for the drivers.

    The "Board" files contain the static configuration for the drivers. For example, what pins are used for UART, etc.

    Note: we default the .cfg to open as a text file now in CCS (this change happened in 7.?). You can still open it graphically by right-clicking and selecting Open With XGCONF.

    Todd
  • 0 in reply to ToddMullanix
    Intellectual 735 points
    I am using tirtos_tivac_2_16_00_08 version only and still not able to configure drivers.We haven't confirmed to use UART yet in our Application. But still assume that we will be using UART'S on pin PA0,PA1.
    Also is it possible in TM4C129EXL Evaluation kit to use DMA along SPI??
  • 0 in reply to Naveen Kumar29
    TI__Guru* 96960 points
    Sorry. I missed that we had an earlier 2.16 release. GUI config of the drivers are removed from that version also.

    If you include UART_init() and supply UART_config, the UART driver code is brought in. The UART_config supplies the configuration.

    The TI-RTOS SPI driver for TivaC uses DMA.

    Todd
  • 0 in reply to ToddMullanix
    Intellectual 735 points
    So which version of TI-RTOS supports Configuring driver capability, so that I can install that version.


    With regards,
    Naveen
  • 0 in reply to Naveen Kumar29
    TI__Guru* 96960 points

    The TI-RTOS 2.14.xx.yy releases had support for "configuring" the drivers in the .cfg. Please note, by "configuring" I mean only the following can be done in the .cfg
    1. Select whether to use the instrumented or non-instrumented driver.
    2. Added the driver libraries to the link.

    In the 2.16.xx.yy release, we removed the ability to have instrumented vs non-instrumented by driver (e.g. before you could have had an instrumented UART driver and non-instrumented SPI). In the 2.16.xx.yy release, you can select instrumented or non-instrumented, but it applies to all the drivers.

    The driver library is now brought in via the "var driversConfig = xdc.useModule('ti.drivers.Config');" line.

    Note: instrumented libraries have Log and Assert calls enabled.

    The "real" configuration of the drivers are done in the "Board" files (e.g. EK_TM4C129EXL.c) for all releases. I would not recommend moving back a release to simply get the two items I listed above.

    Todd

  • 0 in reply to ToddMullanix
    Intellectual 735 points
    Based on your reply I have understood that It is recommended o configure the drivers by means of using Board.c and Board.h files. If certain peripherals I don't need in the application like I2C's I have to unlink them.

    If that is the case how to un-link the unused driver peripherals from board.c file???



    With regards,
    Naveen kumar E.S.
  • 0 in reply to Naveen Kumar29
    TI__Guru* 96960 points
    The unused code should not be pulled in via the compiler options. For example, look at an I2C example in the product. It is not pulling in the EMAC or SPI driver code (since the application is not directly calling SPI_init or any other SPI APIs)

    Todd