CCS/CC2640R2F: Right way to tell TI device driver being executed is ROM code or source code with user modification

peiqing xia

Part Number: CC2640R2F

Tool/software: Code Composer Studio

My goal is to use different GPIO IOC setting. In a quick test hack, source code simplelink_cc2640r2_sdk_2_30_00_28\source\ti\drivers\i2c\I2CCC26XX.c, I hard coded i2cPinTable value. From the disassembly and variable watch, the new value doesn't show up, it seems ROM code is being executed instead of my hacked source code.

What would be the best way to determine a function is ROM code or compiled code? Is there some flag in CCS TiRTOS tool we can watch?

To modify the IOC property of GPIO pin, for example here in the I2C pins, I want to adjust the IO mA capability, other than hacking the driver code, what would be the recommended approach?

Thanks a lot.

over 6 years ago

0 TER over 6 years ago

TI__Guru**** 317180 points

- It's not clear to me why you need to hack the driver. Please elaborate some.
- If you want to use I2CCC26XX.c directly you have to add this file in your CCS project

0 peiqing xia over 6 years ago in reply to TER

Intellectual 320 points

Hi, TER, it is a quick hacking to experiment different IO capability. Thank you very much for your accurate guidance.

Bluetooth®︎

Bluetooth forum

CCS/CC2640R2F: Right way to tell TI device driver being executed is ROM code or source code with user modification