Adding the Scope plot of the V_DCB Voltage Divider output spike once the system tries to drive the motor....
In your clock change to 8 MHz you must change the FRDIV to divide by 256 which gives you a reference clock of 31.25 KHz input to the FLL. You have reduced the maximum frequency you can run from 75 MHz to 68.65 MHz using a FLL multiplier of 2197. Any faster and you violate the maximum clock of the MCU.
I find the MCUXpresso Config tools very useful in changing clock settings. The clocks tool is very complete and will check all of your changes to the clock.
If you want to verify you clock changes, you can turn on your clockout and select bus clock (all from the clocks tool).
The PWM and ADC assignments are the same so there is no issue with incorrect pin assignment there.
How stable is your 3.3V and 15V power?
If you still have your reference design , FRDM-KV11 and FRDM-MC-LVPMSM try you software on that reference design..
Did you happen to put in the Test Points that were on the FRDM-MC-LVPMSM. If so you can check you VREF div 2, current and voltage levels so make sure they are in range. If you used the same op-amp then all should be ok.
I've done my share of Letting the smoke out of current measurement resistors. It happens more often than we expect for sure. One thing more to check might be the deadtime setting in the application. Without deadtime the shoot through current of the FETs is massive and will burn out a
Are the parameters set in the MCAT default working for you. When you do the measure of electrical parameters does it finish?
You need to verify the phase currents and voltages before trying to spin your motor. This could be done using the parameter measuring tool in MCAT.
You also can go to the MCAT tab "Control Struc" and select scalar control. without driving a set speed you should see your three phases look similar to above figure.
Below - anytime you make a parameter change do and update target and Store Data. And note that until you have recompiled your code will the changes become default.
In the Speed Loop tab you can change the Speed Ramp down from the default 10000 to say 1000 or 3000.
In the current Loop Tab you can change the Loop Parameters. (If you hover over each of the symbols it pops up with a parameter definition and it's range. ) I very often will slow down the loop bandwidth and reduce the value of attenuation from 1 to .8.
Where did you source your project? Was it from the SDK? In the project that is sourced by the KV11 SDK the Mechanical Measurement is not an option. I'll be looking for a version that includes that as an option.
I hope this helps as a start.
Philip
