• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 82 subscribers
  • Views 300 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.

LAUNCHXL-F28379D: Universal_Servo_Drive board Conversion from F28p65 debugger issues

Kylie Auerbach
Prodigy 30 points
Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: SYSCONFIG, C2000WARE

Tool/software:


I am working with the universal_servo_drive from the Motor Control SDK. I used the one click migration to convert the code from the LAUNCHPAD-F28p65 to the LAUNCHPAD-F28379D and adjusted the sysconfig and the linker file to match accordingly. The project builds as expected but when it is being debugged, it gets stuck between line 68 and 70 which are two lines of comments in the sysctl.c file. I will run the debugger, and pause, run again, pause... etc and it consistently bounces between these two lines.

The next line of code is calling the SYSCTL_DELAY assembler, which is described in the screenshot attached. I was worried compiler optimizations were causing the problem here, so they are now set to off, and I am still getting stuck between these two lines.

In the main.c file, the code is able to reach the breakpoint I set at Device_Init(), but does not make it to Board_Init().

.

  • 0
    TI__Mastermind 24000 points

    Hello,

    Please allow another day for me to review this issue.

    Thanks & Regards,

    Allison

  • 0
    TI__Mastermind 24000 points

    Hi Kylie,

    Can you step through/into the project line by line and see where the debugger stops or if you run into issues? Is it still getting stuck in the same spot?

    Can you please double check the code being applied in the device init? This will be different from device to device, so if configurations were not migrated properly then this could cause issues - particularly in the SysCtrl setup.

    Best Regards,

    Allison

  • 0 in reply to Allison Nguyen
    TI__Prodigy 30 points

    Hi Allison, 

    Stepping into and stepping through both produce that same cycle between lines 68 and 70 continuously. 

    I have attached a screenshot of what the SYSCTL page looks like in the sysconfig editor. 

    Using an o-scope I was able to verify that the clock is producing a sin wave when the program is running, out of a concern that there is an issue with the way the clock is configured in SYSCTL. 

    Additionally, to troubleshoot a potential clocking issue, I switched the OSCCLKSRCSEL in CPU1 SYSCLK from INTOSC1 to X1_XTAL, which caused the program to stop even sooner in the code and be stuck at the same blank line even when starting and stopping the debugger and stepping into/stepping through. 

    Do you have advice on where or what specifically I should investigate in the device init? Happy to provide whatever necessary. 

  • 0 in reply to Kylie Auerbach
    TI__Mastermind 24000 points

    Hi Kylie, 

    Can you please attach your project? Perhaps I can take a look to see if I see the same behavior or an obvious issue.

    Best Regards,

    Allison

  • +1 in reply to Kylie Auerbach
    TI__Mastermind 24000 points

    Hi Kylie,

    When I tried to load the project and step through, I was getting stuck in the sysctrl setup which made me think that the project is trying to configure incorrect system control/clocking related settings. Note that this is not relevant to sysconfig, but rather the driverlib source files that are being referenced and used in your project. The path of the sysctrl.c file that I see imported is still pointing to F28P65x for me, not F2837xD. This is what I see:

    C:\ti\c2000\C2000Ware_5_04_00_00\driverlib\f28p65x\driverlib\sysctl.c. If your setup is similar, you may be pulling in F28P65x driverlib source. Can you please double check your project settings/paths?

    Best Regards,

    Allison

  • +1 in reply to Allison Nguyen
    TI__Prodigy 30 points

    Thank you for your help! I had replaced all the other files in src_device, but did not replace the driverlib.lib file. To do so, I needed to go to C:\ti\c2000\C2000Ware_5_04_00_00\driverlib\f2837xd\driverlib\ccs\Release. 

    I confirmed I was using eabi output format by looking here. 

  • 0 in reply to Kylie Auerbach
    TI__Mastermind 24000 points

    Hi Kylie,

    So glad you were able to resolve this! Feel free to create a new thread should other issues arise.

    Best Regards,

    Allison