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.

TMS320F28035: ADC in TMS320F28035

Part Number: TMS320F28035
Other Parts Discussed in Thread: CONTROLSUITE, , DRV8323, C2000WARE

Hi TI Team,

We are using TMS320F28035 DSP board in one of the projects, so we have a current sensing application which requires ADC. We have implemented it by referring ADC-SOC example from ControlSuite SDK using CCS IDE. The code builds successfully without any errors but when we debug, it directly starts execution without generating any call stacks to perform step by step debug. Could you please address this issue ASAP.

Components Used : TMS320F28035 DSP board, DRV8323

Thanks & Regards,

Nikhila Patil

  • Hi,

    Due to Thanksgiving Holiday, the subject matter expert is out of office. We will get back to you next week.

    Thanks & Regards,
    Santosh

  • Hi Nikhila,

    We have implemented it by referring ADC-SOC example from ControlSuite SDK using CCS IDE

    Would it be possible for you to try the ADC soc example from C2000Ware SDK instead of the ControlSUITE one. C2000Ware is our latest SDK.

    Please let me know if you are experiencing the same issue with the C2000Ware example.

    C:\ti\c2000\C2000Ware_version\device_support\f2803x\examples\c28\adc_soc 

    Best Regards,

    Marlyn

  • Hello Marlyn,

    We have tried the ADC-soc example from ControlSuite and C2000Ware SDK, we are able to debug it. But, when the ADC logic from same code is mapped into our application code, we are facing the issue described above. Do we have any alternative. Kindly check and reply.

    Thanks & Regards,

    Nikhila Patil

  • Nikhila,

      Marlyn is out-of-the office (and so are many other subject-matter-experts). She will be back in the first week of January, at which time you can expect a response. Thank you for your understanding and patience.

  • Hi Nikhila,

    But, when the ADC logic from same code is mapped into our application code, we are facing the issue described above

    To be clear, the issues you face with not getting any call stacks only happen when you insert the code into your own application code and not with the example provided in c2000Ware?

    Best Regards,

    Marlyn

  • Hello Marlyn,

    Yes. We face this issue only when we insert the code into your own application code.

    Thanks & Regards,

    Nikhila P

  • Hello Marlyn,

    Yes. We face this issue only when we insert the code into your own application code.

    Thanks & Regards,

    Nikhila P

  • Hi Nikhila,

    Thank you for the clarification. Let me send this question to someone else on our team who would be able to best assist you. 

    Best Regards,

    Marlyn

  • The same application didn't have this problem before you integrated the ADC code? You're using the same cmd file, same ccxml file, same debugger settings, yes?

    If you halt the application by hitting the suspend button or by placing breakpoints (either using CCS or putting ESTOP0 instructions in code) does it work? Does the code appear to be running normally aside from the fact that it doesn't halt at main() when first loaded or is it getting stuck somewhere?

    Whitney

  • Hi Whitney,

    1. The same application didn't have this problem before you integrated the ADC code? You're using the same cmd file, same ccxml file, same debugger settings, yes?

    Yes, we didn't have this problem before integrating ADC. We are using the same cmd, ccxml files with same debugger settings.

    2. If you halt the application by hitting the suspend button or by placing breakpoints (either using CCS or putting ESTOP0 instructions in code) does it work? Does the code appear to be running normally aside from the fact that it doesn't halt at main() when first loaded or is it getting stuck somewhere?

    Yes, the application halts if we hit the Suspend button. While executing, it gets struck in ITRAP.

  • Is it at your application's ITRAP handler or the boot ROM one or some other code?

    Can you try putting a breakpoint at c_int00 and/or code_start (may need to do it in the Disassembly window)? Then reset the device in the debugger (but don't hit the restart button) and run and see if it hits the breakpoint?

    Whitney