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.

CCS/AWR1642: How to step debugging if the driver is modified by a customer.

Part Number: AWR1642

Tool/software: Code Composer Studio

Hi Experts,

Could you please let me know how I do step debugging the modified driver which is called TI library.
I believe that Step debugging is impossible for SDK provides TI library.

Thank you very much for your teaching me the method.
Best regards,

Hitoshi

  • HI,

    It is possible to debug the driver. In order to set breakpoints in the driver one just needs to re-compile it without optimization.

    The mmwave UG provides instructions on how to re-build the driver code.

    thank you
    Cesar
  • Hi Cesar,

    I could re-build the driver but I don't know about the optimization.
    Some of the break points can be set but there are still other points can't be set.
    If this caused by optimization, would you mind providing how to re-build the driver without optimization?
    I couldn't find any optimization info in the user guide.

    Best Regards,
    -Kevin
  • Hi Kevin,

    To rebuild a driver:

    1) Edit packages/ti/common/mmwave_sdk.mak to modify the optimization flags.  Look for R4F_CFLAGS (for MSS) or C674_CFLAGS (for DSS).  IMPORTANT: If your editor converts tabs to spaces or removes end-of-line spaces, TURN THIS FEATURE OFF!  makefiles do not work if tabs are removed.

    2) Start a DOS Command window and run packages\ti\scripts\windows\setenv.bat after verifying that MMWAVE_SDK_DEVICE is set correctly for your AWR device.

    3) In the DOS Command window, cd to packages\ti\drivers\uart (or whatever driver you want to rebuild), and either delete or backup the files in the \lib directory, or type: gmake clean.

    4) Type: gmake all, or gmake drv.  Look in the \lib folder for the new files.

    5) Rebuild your application.

      -dave