LPSTK-CC1352R: Analog Signal Chain Studio tutorial failed to work on a LPSTK-CC1352R CCS project

Hi Tim,

We switcher our drivers from "master/slave" to "central/peripheral" terminology a while back. Not sure if all components have made this change. Looks like you need to rename your "slaveAddress" to "targetAddress".

https://dev.ti.com/tirex/explore/content/simplelink_cc13xx_cc26xx_sdk_7_40_00_77/docs/drivers/doxygen/html/struct_i2_c___transaction.html

Cheers,

Marie H

SysConfig does not allow me to change its generated codes!  It restores its codes once I press "Compile"!

My temporary solution is to edit i2c.h so that targetAddress becomes slaveAddress.  This works for this project.

Please provide a permanent solution.  I am testing many sensor projects and integrating into Wi-SUN nodes.

Hi Tim,

Do you know which part of the project this outdated name comes from?

Alternatively you can disable SysConfig from generating ti_drivers_config. 

https://dev.ti.com/tirex/explore/content/simplelink_cc13xx_cc26xx_sdk_7_40_00_77/docs/proprietary-rf/proprietary-rf-users-guide/sysconfig/sysconfig-disable.html#first-method-excluding-generated-files-from-building

Cheers,

Marie H

Hello, It is file mcu.c.  Sysconfig does not allow me to edit it.

Hello Marie,

I recall that we can edit project spec so that some SDK files can be copied to that project`s directory.

Do you know how to do this in my project?

Hi Tim,

Those SysConfig-generated source files are created from templates inside the ascstudio product, which as you're finding, hasn't been updated to the more 'inclusive' names used in newer SimpleLink SDKs.  If you need to use the newer SimpleLink SDKs(?), you may be able to modify the ascstudio templates to accommodate for this compatibility break.

For example, the problematic mcu_i2cTransfer() function in your screenshot is generated from the source/ti/drivers/sensors/mcu_tidrivers.c.xdt file in ascstudio.  If you modify that file to use 'targetAddress' (and restart SysConfig... and maybe even restart CCS(?) to so the modified file is rescanned), your generated file should use the new field name.

No idea what you'll stumble on next(!), but this may help you get over this particular issue.

Hello Chris,
Your suggestion is not satisfactory.  I still need an untouched ASC Studio to open older SDK and example projects such as those included in

• SimpleLink Sensor and Actuator Plugin
• SimpleLink SDK LVGL Plugin

The best temporary solution for me is:

• Edit project spec so that SDK file i2c.h can be copied over to that project`s directory.  Do you know how to do this in my project?
• Then, I can distribute my project sources while keeping each developer`s SDK and ASC Studio untouched.

Hello Marie,

I added these lines to the related example projectspec file:

<file path="${COM_TI_SIMPLELINK_CC13XX_CC26XX_SDK_INSTALL_DIR}/source/ti/drivers/I2C.h" openOnCreation="false" excludeFromBuild="false" action="copy">
</file>

It successfully copied over i2c.h to the project`s root.

However, when I built the project, it still referred to the SDK`s i2c.h and failed.

How do I correct it?

Hi Tim,

It sounds like the compiler is finding the drivers/i2s.c file before your project application/i2s.c file.

If you open the Properties for the project in CCs, then go to Build -> Arm Compiler -> Include Options you will find a list of include search paths. This list is prioritized, i.e. the compiler will start looking in the top folder.

Can you put the folder with "your" i2s.c file at the top of this list and retry?

Cheers,

Marie H