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.

CCSTUDIO: View ramVectorTable in CCS Theia

Part Number: CCSTUDIO
Other Parts Discussed in Thread: CC3551

Tool/software:

I would like view what the vector table is pointing to in the CC3551.

In the SDK in source/ti/device/cc35xx/driverlib/interrupt.c, VTOR is set with SCB->VTOR = (uint32_t)ramVectorTable;

ramVectorTable is "not available in the watch. The table seems to be a address zero based on the register view of VTOR

I can see individual vectors by setting "((int*)0x0)[1]" in the watch window. Is it possible to view the complete table at once?

More generally, the ability to cast an arbitrary address as an array of any type would solve my problem and probably others.

I am using CCS Version: 20.1.1.8__1.7.1

  • Hello,

    I can answer this question:

    I can see individual vectors by setting "((int*)0x0)[1]" in the watch window. Is it possible to view the complete table at once?

    More generally, the ability to cast an arbitrary address as an array of any type would solve my problem and probably others.

    Support for this is planned in a future release:

    https://sir.ext.ti.com/jira/browse/EXT_EP-12658

    For you other questions I will bring this thread to the attention of the device experts.

    Thanks

    ki

  • Ki,

    After further investigation,I believe I should monitor HwiP_dispatchTable[] instead of ramVectorTable[]

    The events vectors seem to be set to HwiP_dispatch(). This common function will then call a function stored in HwiP_dispatchTable[]

    The generic challenge remains. HwiP_dispatchTable[] is not visible in the watch. Casting its address as an array would allow me to see the what the callback functions are assigned. The planned feature would help.

    More simply, I would like to add HwiP_dispatchTable[] to the watch, but I vaguely understand there are multiple complex reasons why an IDE cannot interpret a variable. Casting the address to an array would ignore the complications.

    Thank you,

    Peter B