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

CCS/AM5718: BARE METAL CODE FOR I2C FROM EXAMPLE CODES

Anonymous
Anonymous
Guru 17045 points
Part Number: AM5718

Tool/software: Code Composer Studio

Can i able to collect bare metal code from the project file(I2C_BasicExample_idkAM571x_armTestProject) TI provided??. I just removed USE_BIOS  symbol from the symbols defined list.but it shows some error.

  • 0
    TI__Guru** 114410 points
    No, the unit tests that are packaged with I2C driver are not meant to be built for bare-metal for the device you are using. The bare-metal example is only supported for TI Keystone II product as described in the ReadME.txt file:
    pdk_am57xx_1_0_13\packages\ti\drv\i2c\test\baremetal\ReadMe.tx

    The unit tests for AM57xx are only TI RTOS based examples. For AM57xx I2C LLD based bare-metal examples, you can refer to the I2C examples in Board diagnostics. These are however meant to be built using makefile and not CCS projects:
    software-dl.ti.com/.../index_board.html

    Regards,
    Rahul
  • Anonymous
    0 Anonymous in reply to Rahul Prabhu
    Guru 17045 points

    can i able to derive baremetal code from the project file(I2C_BasicExample_idkAM571x_armTestProject) TI provided??.(by removing bios related potions from code)

  • 0 in reply to Anonymous
    TI__Guru** 114410 points
    Muhammad,

    You can remove BIOS related portions of code and fix the project to build in bare-metal code however if you are not familiar with TI RTOS and XDC build this will be a non-trivial effort to eliminate BIOS related source code, exclude .cfg from the project and replace that with linker command file and linker options to link to the component libraries and link to no-OS version of OS abstraction layer.

    Is there some reason that you don`t want to use the makefile approach which build bare-metal I2C diagnsotic tests. If CCS project is required then please echo the build options from the I2C EEPROM diagnostic test and add the same build settings(Compiler and linker options) to the CCS project.

    Regards,
    Rahul