CCS/CC2642R: Device Not working after some reboot

Rakesh Rajbhar

Intellectual 630 points

Part Number: CC2642R
Other Parts Discussed in Thread: HDC2080

Tool/software: Code Composer Studio

Hi Team,

I am working on a custom board with cc2642, my development setup is as bellow.

SDK - simplelink_cc13x2_26x2_sdk_3_30_00_03

CCS - 9.2.0.00013

Base code - simple_peripheral_oad_onchip (Bim and the persistent app is also flashed together )

In my project, I have HDC2080 connected to i2c. I have set up the timer for 30 seconds, the device will read temperature value from hdc2080 advertise it and

after every 30-second device will go in sleep. we are powering hdc2080 using GPIO through MOSFET. so whenever I need to take the reading from HDC2080 I need to drive gpio.

once read/write operation is finished I turn-off power for hdc2080. I have already provided approx 4ms of delay after power on hdc2080 for any read/write operation.

I am using a display driver for debugging(It is working fine).

It is working fine normally but currently, we are the following issues.

1) After power-up, the device is working fine for around 30-40 mins but after that, it suddenly stops working and we are not able to see any debug print on the screen. most probably it stuck in I2C_Transfer()

Blocking mode.

-> Some times it is working perfectly fine but some times it gives an issue, and once it gets hang and we try to reboot the device but after reboot also we are not able to run it again, we have to flash the device again to work with it.

-> I have some debug prints that are just before the i2c initialization and so after reboot, I should get some debug print which is before any i2c operation. but the device stops working and looks like its dead.

we have to flash the device again to debug it.

over 5 years ago

0 Eirik V over 5 years ago

TI__Guru 56590 points

Hello,

Are you calling blocking I2C from task context only?

Have you checked for any RTOS task stack or CSTACK overflows?

http://dev.ti.com/tirex/explore/content/simplelink_cc13x2_26x2_sdk_3_40_00_02/docs/ble5stack/ble_user_guide/html/ble-stack-5.x-guide/debugging-index.html#viewing-the-state-of-each-task

0 Rakesh Rajbhar over 5 years ago in reply to Eirik V

Intellectual 630 points

Hi Eirik,

Thanks for the prompt response.

Yes, I am calling i2c blocking from the task context only, As my base code is simple_peripheral_oad_onchip(SimplePeripheral_taskFxn). I am calling i2c functions in the simple peripheral task.

Let me explain my problem in detail.

-> Device working fine some times, even for almost one day if I remove the power and I dont use the device.

-> then if I give power to that device it some times starts normally and shows logs also but in the same situation, some times device just gets dead and then I have to flash it again, after flashing it works fine again.

So I have below queries.

1) if a RTOS task stack or CSTACK overflows, after reboot it should work normal again, right? I don't need to flash it again right?

2) I found in main() if "Board_initGeneral()" gets fail device will go in while(1). so if some times "Board_initGeneral()" gets fails and the device gets stucks in while(1) I will not get any debug prints and it will look like the device is dead as my debug prints start after task creation.

-> But after reboot same code gets fail sometimes and if I flash the same code "Board_initGeneral()" gets pass.

My question is if the same code is running after rebooting device and device does not respond, and if I flash the same code it starts working why in both situations execution will start from "main()" only right, so why i need to flash it?

Please let me know if you need any other information.

0 Eirik V over 5 years ago in reply to Rakesh Rajbhar

TI__Guru 56590 points

Hello,

Please profile potential stack overflow. If this occurs all bets are off.

0 Rakesh Rajbhar over 5 years ago in reply to Eirik V

Intellectual 630 points

Hi Eirik,

Thanks for the response.

but I couldn't get your point exactly can you please elaborate a little more.

0 Eirik V over 5 years ago in reply to Rakesh Rajbhar

TI__Guru 56590 points

Please read section Viewing the State of Each Task in the Users Guide:

http://dev.ti.com/tirex/explore/content/simplelink_cc13x2_26x2_sdk_3_40_00_02/docs/ble5stack/ble_user_guide/html/ble-stack-5.x-guide/debugging-index.html#viewing-the-state-of-each-task

Code Composer Studio™︎

Code Composer Studio forum

CCS/CC2642R: Device Not working after some reboot