• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 83 subscribers
  • Views 186 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.

F28M35H52C: Debugging C28 doesnt perform correctly

Peter Berger
Prodigy 110 points

Part Number: F28M35H52C

I am debugging the C28 DSP and it seems that if i have any enabled breakpoints in my code i cannot perform step by step operation? it skips around the code.

Please assist with why this is the case?

using CCS 9.0.1.00004 

Compiler options:

-v28 -ml -mt --float_support=fpu32 --vcu_support=vcu0 -g --include_path="C:/ti/ccs901/ccs/tools/compiler/c2000 ver 6.0.2/include" --include_path="../../../../inc" --include_path="../../../inc" --include_path="../../inc" --include_path="../../inc_l" --include_path="C:/ti/mcusdk_1_00_00_68/products/MWare_v140x/F28M35x_common/include" --include_path="C:/ti/mcusdk_1_00_00_68/products/MWare_v140x/F28M35x_headers/include" --define=_FLASH --define=xxxDESKTOP --define=xxxCHILLER_PASSIVE --define=CONCERTO_EV_OPERATE_1 --diag_warning=225 --display_error_number

XDC Tools Options:

--xdcpath="C:/ti/mcusdk_1_00_00_68/packages;C:/ti/mcusdk_1_00_00_68/products/bios_6_33_04_39/packages;C:/ti/mcusdk_1_00_00_68/products/ipc_1_24_02_27/packages;C:/ti/mcusdk_1_00_00_68/products/ndk_2_21_01_38/packages;C:/ti/mcusdk_1_00_00_68/products/uia_1_01_01_14/packages;C:/ti/mcusdk_1_00_00_68/products/xdctools_3_23_04_60/packages;C:/ti/ccs901/ccs/ccs_base;" xdc.tools.configuro -o configPkg -t ti.targets.C28_float -p ti.platforms.concertoC28:F28M35H52C1 -r debug -c "C:/ti/ccs901/ccs/tools/compiler/c2000 ver 6.0.2" --compileOptions "-g --optimize_with_debug"

Thanks,

Berger Peter

  • 0
    TI__Guru 50611 points

    Hi,

    The subject matter expert is out of office due to holiday break. Please expect response by 1st week of January. Sincere apology for inconvenience.

    Regards, Santosh

  • 0
    TI__Guru 54675 points

    Seeing the debugger skip around in the code can sometimes be caused by optimization. I don't see optimization turned on in your compiler options, but it's possible you're using a library that was build with it turned on? Does it only happen in certain functions or the whole application?

    Whitney