• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 51 subscribers
  • Views 1102 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

RTOS/CC2640R2F: Simple Peripheral: Debugging with ROV not working

Andre Vaas
Intellectual 570 points
Part Number: CC2640R2F
Other Parts Discussed in Thread: SYSBIOS

Tool/software: TI-RTOS

Hello,

we build our project up on the Ti base project "Simple_Peripheral". My code is now a little bit larger and the sensor controller is involved. The main CPU hangs a second after changing from connetable to nonconnectable advertising. I don't know why this is happening. I already tested the code without changing the advertising. There the code runs fine. Also I tested changing advertising state without usage of the additional code handling the sensor controller. This runs, too. So it could be (?), there is a buffer overflow anywhere relating to my bigger firmware. Now I wanted to debug the RTOS and look at the ROV-Task "stackPeak" value. But I cannot get to this window. I get the error: "Received exception from ROV server: Target memory read failed at address: ...".

So I opened a blank new Simple_Peripheral Project and tried to debugging it. There ROV also failed with the same error. I also tried to halt the program in the SimpleBLEPeripheral_taskFxn before the main loop. Also not working.

ROV is working fine with the "hello" Project, as described in the tutorials. So I think my CCS should run OK.

Question: Do you have some ideas, what I can do to get ROV working properly with the Simple_Peripheral project?

Thanks!

Regards
Andre

  • 0
    TI__Guru* 77991 points
    Hi Andre,

    Which CCS version are you using? Have you seen there is a workaround here for ROV for certain CCS versions (see the "warning" section): dev.ti.com/.../rtos_object_view.html

    Regards,
    Katie
  • 0 in reply to Katie Pier
    Intellectual 570 points

    Hi Katie,

    I use the newest CCS version 8.0.0.00016.

    I now used the ROV2 and I can see that after running my programm until the system or core M3 freezes, there is no overflow or to high stackPeak size happening. I wanted to scan for errors in the BIOS module. But getting the data from the development board opens a window with the message: "The update request for ti.sysbios.BIOS Scan for errors... has timed out." I am not able to get the data. Also with the standard simple_peripheral project.

    Do you have a solution for that?

    Thanks
    Andre

  • 0 in reply to Katie Pier
    Intellectual 570 points
    Katie, could you push this case to high priority? Our FAE is not in office this week and we need a solution as close as possible. Thank you!
  • 0 in reply to Andre Vaas
    TI__Guru* 77991 points
    Hi Andre,

    Due to your latest error message, I've been working to loop in someone from our TI-RTOS/SYSBIOS team. I will ping them again to escalate. Thanks for your patience.

    Regards,
    Katie
  • 0 in reply to Katie Pier
    TI__Guru* 77991 points

    Hi Andre,

    I consulted with the team that creates these tools.

    The scan for errors function is the function most likely to trigger a timeout warning simply because the command is one that causes ROV2 server to check all modules in the system for an error condition, so it's the longest running command. It is possible to increase the timeout period by using the "Data retrieval settings" menu item.

    If increasing the timeout doesn't help, then you should be able to manually open the individual views, e.g:
    Task: Detailed – look for Task stack overflow
    Task: Callstacks – look for unexpected function calls
    HWI: Exception – look for any exceptions
    HWI: Module – to get the ISR stack
    HeapMem: Detailed – look for heap issues
    :

    If any of these manual views results in a timeout warning, it would give us a clue as to what is causing the problem - please let us know.

    Do you still get the "Received exception from ROV server: Target memory read failed at address: ..." from your original post? If so, what's the address mentioned?

    Regards,
    Katie

  • 0 in reply to Katie Pier
    Intellectual 570 points

    Hi Katie,

    I will get back to you as soon as I can get my CCS back to working condition. Today it did not find my installed simple link SDK and some projects can not be opened due to missing cfg files.

  • 0 in reply to Katie Pier
    Intellectual 570 points
    Hi Katie,

    I stretched the timout period as you mentioned and this worked.

    Also thank you for the listing of the single items which are important in ROV2.

    The "Receive exception from ROV server" I was getting is from ROV classic. As you mentioned before, I shall use ROV2 instead as a workaround. It is sufficient.

    Thank you.
    Regards
    Andre
  • 0 in reply to Andre Vaas
    TI__Guru* 77991 points
    Great - so glad to hear you got everything working! :-)
    -Katie