• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 32 subscribers
  • Views 556 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.

MSPM0G3507: Include MSPM0L11XX_L13XX TI-Driver Library I2C APIs

Felix Debus
Intellectual 1620 points

Part Number: MSPM0G3507
Other Parts Discussed in Thread: SYSCONFIG

Dear e2e team,

currently I am developing a demo application on a MSPM0 G3507 device. For this I want to communicate via an I2C interface. This demo is build in an empty mspm0g3507_nortos_ticlang example file.

First I added the according I2C interface with Sysconfig. Afterwards I looked into the provided I2C.h file located at <mspm0_sdk_1_20_00_05 source direction>\source\ti\drivers.

In the description is an example initialization of this module. I included the I2C.h file acoording to the description. During the building process I get the linker "error #10234-D: unresolved symbols remain" of each function I used from I2C.h. I already looked in the ARM linker>File search path and added the location of the file. This lead to the same error. 

Can you please tell me which prerequisite is missing? 

Best regards

Felix

  • 0
    Guru 44045 points

    You might want to start with the empty driverlib project.

  • 0 in reply to Keith Barkley
    TI__Intellectual 1620 points

    Hi Keith,

    thank you for your answer! I tried that too but I get the same error message. 

  • 0 in reply to Felix Debus
    TI__Mastermind 29065 points

    Hi Felix,

    If you started by importing the empty example project into CCS it typically includes all the project settings you need. Are you using Sysconfig? How did you import this and did the empty project build okay right after you imported it? 

    Can you capture an image of your project settings under CCS Build -> Arm Linker -> File Search Path?

    Best Regards,
    Brandon Fisher

  • 0 in reply to Brandon Fisher94
    TI__Intellectual 1620 points

    Hi Brandon,

    yes I am using Sysconfig. I imported the empty project by right clicking in the Project Explorer. From there I press Import>CCS Projects. The I browse to the empty project by the Select search-directory configuration. Directly after importing the project I can build it.

    Attached is a capture of the Arm Linker file path search configuration.

    Best regards

    Felix

  • +1 in reply to Felix Debus
    TI__Mastermind 29065 points

    Hi Felix,

    That looks okay, you shouldn't need the absolute path to the MSPM0 SDK, so I'd probably remove it. Also within project properties, can you check CCS General-> Products tab, and verify that MSPM0SDK version 1.20.0.5 is shown correctly?

    I didn't notice initially, but you are trying to call TI Drivers functions, and the empty example is for DriverLib (driverlib provides lower level APIs). 

    TI Drivers for MSPM0 are still under development, so the only example we have that uses the I2C TI Drivers is the FreeRtos enabled one located at C:\ti\mspm0_sdk_1_20_00_05\examples\rtos\LP_MSPM0G3507\drivers\i2c_tmp\freertos\ticlang

    You could try importing and building that if you want to use TI Drivers, or you could use the functions available in driverlib (dl_i2c.c/h).

    Best Regards,
    Brandon Fisher

  • 0 in reply to Brandon Fisher94
    TI__Intellectual 1620 points

    Hi Brandon,

    yes  the MSPM0SDK version 1.20.0.5 is taken.

    Ok thank you for your help! This FreeRtos example works. I will try to import the necessary modules.

    Best regards

    Felix