SIMPLELINK-CC13XX-CC26XX-SDK: BIOS Scan for Error Issue in ROV and ROV2 (ROV Classic)

Hi Shiv,

Please refer to the TI-RTOS Basics SimpleLink Academy Lab, BLE5-Stack Debugging Guide, and Runtime Object View User's Guide for more information.  Here are some other E2E resources you might be interested in:

https://e2e.ti.com/f/1/t/953527 
https://e2e.ti.com/f/1/t/840835 
https://e2e.ti.com/search?q=structuredecoder.xs&category=forum&group=330_336_341 

Regards,
Ryan

Hi Ryan,

Thanks for the links. I have gone through all of them but didn't find anything that is resolving my issue. 
In some of the links, it was mention to observe the Task Peak exceed, Stack Overflow and other things for issue resolution but I have verify the application code and everything is fine.

In the BLE5 Stack Debugging Guide (https://dev.ti.com/tirex/explore/content/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/docs/ble5stack/ble_user_guide/html/ble-stack-5.x-guide/debugging-index.html#rov-in-ccs ), I have found the patch for INVALID ADDRESS READ issue and I also tried that but it didn't work out. I am still facing the same issue.
Can you please help me to figure out what might be going wrong? Or is there any issue in the application code?

Regards and Thanks,
Shiv

Is the project hanging or entering an assertation?  Are you using an auto-size or static-size heap (from the *.cfg file)?  What is your compiler optimization setting?    You can enable heap monitoring to ensure that your memory is intact.  The addresses listed are not realistic for SimpleLink devices, and if your application is still operating as expected then this could be an issue with the ROV tool.

Regards,
Ryan

No, Project is not hanging or entering an assertion.
Yes, we are using the auto-size heap and I tried the work around which was mention in the BLE5 Stack Debugging Guide. That also didn't help.
To see detailed value of ROV's data, we have disabled the optimization i.e. OFF.
Yeah, we are monitoring our heap consumption as well as its size, it is as expected.

Our application is working as expected, we didn't see any undefined behavior other than ROV's BIOS Scan for Error's Tab showing.

Can you please confirm, if this is ROV tool issue and suggest some work around? so that we can move forward with our Project release.

Regards,
Shiv

Please confirm whether or not you are observing any similar ROV issues with the default Simple Peripheral example.  I also recommend that you evaluate a static heap configuration to evaluate whether the issue persists with this setting.  There have been known issues between the XDCTools and the BLE5-Stack auto heap mechanism which produces ROV errors similar to what you are experiencing:

https://e2e.ti.com/f/1/t/738873 
https://e2e.ti.com/f/1/t/808315 
https://e2e.ti.com/f/1/t/831737 
https://e2e.ti.com/f/1/t/923126 
https://dev.ti.com/tirex/content/simplelink_cc13x2_26x2_sdk_3_20_00_68/docs/ble5stack/ble_user_guide/html/ble-stack-5.x-guide/debugging-index.html#workaround-for-rov 

Although it is typically considered benign and can be ignored, there are workarounds involving modifications to the package.xs file which can be considered as well.

Regards,
Ryan

Ryan Brown1 said:

Please confirm whether or not you are observing any similar ROV issues with the default Simple Peripheral example

I was able to reproduce the issue on Simple Peripheral example code (see below)

Classic ROV:

ROV :

Ryan Brown1 said:

I also recommend that you evaluate a static heap configuration to evaluate whether the issue persists with this setting

As you suggested, I have modified the setting to "Static Heap Configuration"(see below, .cfg file screenshot) and still facing the same issue.

Ryan Brown1 said:

there are workarounds involving modifications to the package.xs file which can be considered as well.

I have also tried out modifying the "function init()" in the package.xs file as suggested in the https://dev.ti.com/tirex/content/simplelink_cc13x2_26x2_sdk_3_20_00_68/docs/ble5stack/ble_user_guide/html/ble-stack-5.x-guide/debugging-index.html#workaround-for-rov (see below, modified package.xs screenshot)

I am still facing the issue after trying out all the workaround but still facing the same issue. And my firmware is working as expected without any issue(i.e. without any assertion or any undefined behavior ). 
As you mention it can be ROV tool issue and can be ignore. Should I consider the same or do I need to analysis anything in my implementation?

Regards,
Shiv

Hi Shiv,

I launched simple_peripheral in the 5.40 SDK and opened ROV. I used CCS 11.1 I did not come across the same error. This is the ROV output I got while running simple_peripheral in debug mode:

Can you try verifying if you are able to run into the same issue when using an unmodified simple_peripheral project on CCS11.1?

Best Regards,

Jan

Hi Jan,

As I mention earlier, I am using  TI SDK v5.10 with CCS IDE v10.3.0 and have developed my application on it. It will be hard for us to update the SDK to latest as we are near to releasing the firmware.

Shiv Pratap Singh said:

I was able to reproduce the issue on Simple Peripheral example code

Earlier when I test Simple Peripheral example code for this issue, it was unmodified version (i.e. out of box example code) from TI SDK 5.10 with CCS IDE v10.3.0

Can you help me out with this as mention it is not possible for us to update the SDK?

Regards,
Shiv

Hi Shiv,

You mentioned that the you are observing the ROV error in an unmodified simple_peripheral as well as your project custom project. This makes me think that maybe there may be a problem either with the CCS install or the SDK install. I would suggest re-installing both to see if the issue still remains. However, since this seems to point to an issue with the SDK install or the CCS install, then I believe it is likely that your project is properly configured and the issue may just be on the ROV tool side of things.

Best Regards,

Jan

Jan said:

You mentioned that the you are observing the ROV error in an unmodified simple_peripheral as well as your project custom project. This makes me think that maybe there may be a problem either with the CCS install or the SDK install. I would suggest re-installing both to see if the issue still remains

We have multiple setup (i.e. multiple user having different system) for our custom application which have TI SDK 5.10 installed with CCS IDE v10.3.0 and all of them have same issue with ROV for BIOS' Scan for error.

For unmodified simple_peripheral example code, I had installed the TI SDK 5.10 with CCS IDE v10.3.0 on new setup and still faced the same issue.

Jan said:

However, since this seems to point to an issue with the SDK install or the CCS install, then I believe it is likely that your project is properly configured and the issue may just be on the ROV tool side of things.

As mentioned, I will be considering this as ROV tool issue not an application issue.

Regards,
Shiv

Hi Shiv,

Got it. This may be an issue with the SDK/CCS combination that has already been resolved. However, I believe this is on the ROV tool side of things as well. I believe you should be okay to proceed with your development. As a quick test, you could try to download and install CCS 11.1 and SDK 5.40 and afterwards attempt to open ROV with simple_peripheral. I would expect ROV to work properly there, but as I mentioned in this message I think your project should be okay to proceed.

Best Regards,

Jan

Jan,

I tried to reproduce this issue with TI SDK v6.10 and CCS IDE 11.2 but I wasn't able to do so. As default simple peripheral example was throwing different issue when I tried to open ROV i.e. it was not able to connect to debugger. But when I tried with SDK v5.10 I was able to do so. 
Project configuration is similar for both project (i.e. example project from older sdk and newer one) and hardware is also just fine as I am able to open ROV with SDK v5.10 example code.
Can you let me know, what could be the cause of issue?

Regards,
Shiv

Hi Shiv,

To confirm, you installed the 6.10 SDK as well as CCS11.2 and you saw a different issue when opening ROV than the one you were seeing earlier? Can you share some details with regards to the new issue? Are you able to successfully build and flash projects on the 6.10 SDK? Can you verify if there are any spaces in your workspace name?

Best Regards,

Jan