Part Number: C2000WARE-MOTORCONTROL-SDK Other Parts Discussed in Thread: C2000WARE Tool/software: I am trying to debug a startup issue with a *newly-created* project, and I am running into issues with driverlib. I have driverlib linked to the version at C2000Ware_MotorControl_SDK_5_03_00_00\c2000ware\driverlib\f2837xd\driverlib\ccs\Debug If I step into Device_Init(), and then into SysCtl_setClock(DEVICE_SETCLOCK_CFG) I get an error Can't find a source file at "/home/ubnuser/ti/repos/c2000ware/repos/f2837xd/release_pkg/driverlib/f2837xd/driverlib/sysctl.c" I guess this is the build directory of the user at TI that built driverlib? If I use the "Locate File" option to point to C2000Ware_MotorControl_SDK_5_03_00_00\c2000ware\driverlib\f2837xd\driverlib, it opens the copy of sysctl.c in that directory. However, if I step through this sysctl.c, the source code does not line up with the stepping. The PC stops on a comment, etc. I guess, maybe this is because driverlib.lib was built with optimization and the link between PC and line of code was lost. Or is the other possibility that the version of sysctl.h does not match the driverlib.lib binary? And stepping through sysctl.c, it seems to crash at SysCtl_selectOscSource(config & SYSCTL_OSCSRC_M); This is with the LaunchPad-28379D, with _LAUNCHXL_F28379D defined, so that DEVICE_SETCLOCK_CFG is set to the LaunchPad options in device.h A few questions: 1) Is the missing link to the source file sysctl.c a bug in the SDK? 2) Is it likely that the sysctl.c in driverlib a match for the binary in Debug? 3) Any suggestions on what the issue may be with the call to SysCtl_selectOscSource? Thanks!
↧