RTOS/CC2640: CC2640 resetting when the task stack size is modified?

Arun Joe

Expert 1780 points

Part Number: CC2640
Other Parts Discussed in Thread: BLE-STACK,

Tool/software: TI-RTOS

Hi,

I ave modified the SimpleBLE_Peripheral example with a pedometer task that works as a pedometer using an accelerometer.

The memory status is Flash-99% and Flash Last page - 97%.

The increased memory is because of other drivers used to drive display graphics etc..

Issue I face is, CC2640 resets approximately every 1 hour. The stack size of Simple Peripheral Task is 1024 and that of the pedometer task is 644.

If I increase this to, say 2048 and 1024 respectively, the deice is continuously resetting.

why is this happening and how can I solve this?

Regards,

Joe

over 8 years ago

0 Sean2 over 8 years ago

TI__Mastermind 33460 points

Hi Joe,

Have you followed the Debugging Guide within the BLE-Stack User's Guide to determine if you are encountering a lockup or exception?
I would recommend running with the debugger attached and a breakpoint set in the exception handler.

Additionally is this issue reproducible on a TI LaunchPad or is this a custom hardware design?

0 Arun Joe over 8 years ago in reply to Sean2

Expert 1780 points

This is a custom Hardware design; I have used power saver mode and thus the system must goes into sleep, I don't think this will occur when the debugger is attached and hence wont't reproduce the issue(but I will give it a try).

Regards,
Joe

0 Sean2 over 8 years ago in reply to Arun Joe

TI__Mastermind 33460 points

Hi Joe,

An alternative is to blink a LED when you think the issue has occurred, and then attach to a running target after you observe the LED blink.

This way the device will be able to run free from the debugger until the issue is reproduced.

0 Arun Joe over 8 years ago in reply to Sean2

Expert 1780 points

But how would I know if the issue had occurred? Is there anything in the TI-RTOS that resets the system in case of a memory overflow or halt?, and this issue is not occurring while in debug mode.

0 Sean2 over 8 years ago in reply to Arun Joe

TI__Mastermind 33460 points

You could instrument the code to spinlock in the case of an error. Do you have a watchdog running?
It seems strange to me that the device would reset more frequently due to task runtime stack size changes without throwing a memory exception or otherwise.

As a side task, can you verify your clock and power circuits for the chip ( I am assuming this is not reproducible on TI LaunchPad.)
processors.wiki.ti.com/.../CC26xx_HW_Checklist
processors.wiki.ti.com/.../CC26xx_HW_Troubleshooting
processors.wiki.ti.com/.../CC26xx_Crystals
processors.wiki.ti.com/.../CC13xx_CC26xx_Crystal_Tuning

0 Arun Joe over 8 years ago in reply to Sean2

Expert 1780 points

e2e.ti.com/.../229603
I have seen this thread , do you think that this is a similar issue?

How would I know if the watchdog is running or not?

0 Arun Joe over 8 years ago in reply to Arun Joe

Expert 1780 points

Hi Sean2 , YiKai Chen , it seems like the Stack is getting filled up? , How can I device the optimum size of the stack? should I make any changes in the heap size?

Regards,
Joe

0 YiKai Chen over 8 years ago in reply to Arun Joe

Guru 735695 points

I suggest you to use CC2640R2 or CC2650R2.

0 Sean2 over 8 years ago in reply to Arun Joe

TI__Mastermind 33460 points

Hi Joe,

The runtime stack size and heap are generally unrelated except that increasing the runtime stack will pinch the heap smaller (in the case of an autosized heap).

In any case, we recommend increasing the runtime stack as much as possible and then profiling stack useage (i.e. find the high water mark), from there you can trim the stack down to within a threshold of that mark. If you find that you cannot increase the stack size any more, but need to, you can experiment with shrinking the heap (if you are not using all of it).

1. Profile the stack size using TI-RTOS ROV tools (task view)

2. Profile the heap following the BLE Software Developer's Guide Debugging section (HEAPMGR_METRICS)

Note: The CC2640R2F generally speaking will not offer any improvements in runtime stack utilization, but may offer improvements in available flash memory due to more of the BLE-Stack code being in ROM.

0 Arun Joe over 8 years ago in reply to Sean2

Expert 1780 points

Hi Thanks for the reply, can you tell me what I must be doing with the task stack size? increasing the task stack is also leading to continuous reset. Now I have use stack size of 2048 in SimpleBLE_Task, this is causing a reset in 1 hour.
Regards,
Joe

0 Arun Joe over 8 years ago in reply to YiKai Chen

Expert 1780 points

Can I use the same codes and libraries I used in CC2640 in CC2640R2F?

0 YiKai Chen over 8 years ago in reply to Arun Joe

Guru 735695 points

No, you can not use code for CC2640 to run on CC2640R2F directly.

0 Sean2 over 8 years ago in reply to Arun Joe

TI__Mastermind 33460 points

Hi Joe,

Are you sure that you are not running into an issue with memory corruption and changing the run time stack size is just causing it to show?
Generally we have not seen run time task sizes that need to be as large as 2k, but this is dependent on your application.

I recommend attaching to a running target after the crash has happened and attempting to dump some debug information.

0 Arun Joe over 8 years ago in reply to YiKai Chen

Expert 1780 points

Is the pin configurations and the footprints are same?

0 YiKai Chen over 8 years ago in reply to Arun Joe

Guru 735695 points

Yes, pin configurations and the footprints are same.

0 Arun Joe over 8 years ago in reply to YiKai Chen

Expert 1780 points

What I would be changing in the software, is it only the device drivers ? is there any porting related documents available?

0 YiKai Chen over 8 years ago in reply to Arun Joe

Guru 735695 points

Try to refer to dev.ti.com/.../cc2640-to-cc2640r2.html

0 Sean2 over 8 years ago in reply to Sean2

TI__Mastermind 33460 points

Hi Joe,

I would like to mention that switching to CC2640R2F will not offer any increase in available system RAM.
Additionally if there is an issue with memory corruption in your application, it may also be present on CC2640R2F.
It would be best to debug and root cause the issue.

If you are still considering migrating, please see the migration guide of this document.
software-dl.ti.com/.../

0 Arun Joe over 8 years ago in reply to YiKai Chen

Expert 1780 points

Hi,
I tried importing simplePeripheral example form CC2640R2F SDK , but while building Im getting the errors, Seems like I have chosen wrong configuration for the compiler and XDC , can you tell me what has to be chosen.

0 Sean2 over 8 years ago in reply to Arun Joe

TI__Mastermind 33460 points

Hello,

Please refer to the release notes that are packed with the SDK for the recommend tools and compilers.

Bluetooth®︎

Bluetooth forum

RTOS/CC2640: CC2640 resetting when the task stack size is modified?