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.
I debug the LAUNCHXL-F28379D with the BOOSTXL-3PhGaNInv , It is all TI hardware. and I use the program from E:\ccs\C2000Ware_MotorControl_SDK_3_01_00_00\solutions\boostxl_3phganinv\f2837x\ccs\sensored_foc.
Everytime I terminated the program and have a new debug, It face a problem just like below. It makes me can not begin to debug and run.I just followed the file SPRACO3 step by step. It seems that second time I start to debug It runs into the AUTO RUN mode.
and my antorun setup is like below
But everytime I delete the project and newly import the project of dual_axis_servo_drive_fcl_qep_f2837x , It can debug and run. watch window can work well, but no Graph on the graph window. I also removed the R20 on the BOSTXL-3PhGaNInv, it still no correct graph.
just like below.
How are your "Program/Memory Load Options" configured? If the "Reset the target on a program load or restart" option is checked, can you uncheck it and see if that makes any difference?
Whitney
Hi Whitney,
Thank you for your reply. may you all fine.
As I have set the option of "Reset the target on a program load or restart" unchecked, now it works well. But I am still confused about this, What's the function of this option? Do TI has further DOCs?
Further more, I still did not solve the problem of no graph on the graph window as I am debuging, I found that because the variable in the expression window named motorVars[0].runMotor is always MOTOR_STOP. It makes all output variable are zero when it is in the level 1.
As I setup the motorVars[0].runMotor to MOTOR_RUN, then the motorVars[0].isrTicker do not change ......
so how to setup this?
Scaler
The doc for these settings is here, although in the case of this particular option I don't think it adds much detail. In general, when you load the program or do a restart, you probably want it to go to the start of main() anyway, so it doesn't make much sense to do a reset. Plus, doing the reset just sends it into boot ROM where it seems to be getting stuck, probably for lack of a configured emulator boot mode selection.
Can you see the application going to the start of main() you do a reset and a restart? From there, if you run for a little bit and then halt, what code is it executing?
Whitney
Now, it works well. when I halt the application, now it is executing main().