• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 83 subscribers
  • Views 1225 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.

Problems Running Code on the HV DMC + PFC Kit

Jedcon
Prodigy 110 points

Other Parts Discussed in Thread: CONTROLSUITE

I have just received and started using the CCS4 & HV DMC + PFC Kit for FOC Sensorless DMC development. When I try to connect to the DSP to load code in a debug session, I get an error most of the time. There are a couple of different error messages that come up. The one here is by far the most common.

 

   Error connecting to the target:

   Error 0x80000200/-1142

   Fatal Error during: OCS,

   Processor blocked debug accesses.

 

I have gone thru the accompanying setup docs, several times, I have deleted, re-installed, and updated, both CCS4 and ControlSuite a couple of times. If  I walk away for some period of time (10 min to over an hour), and try again it will usually work once or twice.

 

Examples loaded from the \ControlSUITE\device_support\f2803x\v121\ DSP2803x_examples_ccsv4\ directory work first time, every time. Because the example code always works (no hardware changes) I believe I must have a setting wrong somewhere in CCS4. I have tried many configurations. Has anyone encountered this before? I am open for suggestions.

 

Thanks in advance,

 

Jedcon

  • 0
    TI__Guru** 119680 points

     Is this fresh out of the box?  Does the GUI work?

    I was thinking this may be that the controlCARD SW2 or main board SW1 are set for the GUI mode...but I don't think you would get sporadic operation.

     

  • 0 in reply to ChrisClearman
    Prodigy 110 points

    Hi Chris,

    Sorry it took so long to get back to you. I have had issues updating CCS4. The anti-virus program was interfering.

    To anwser your question, I don't know if it worked out of the box. I connected and displayed the correct DC bus voltage (50Vdc). The motor didn't spin. I assumed that was due to the low voltage.

    I have tried every (8) combination of sw1 and sw2 on control card. The one that works the best is the original sw1 - off and sw2 both on. I can not find an sw1 on the main section, the only sw1 on the DMC-HV board is the 15v dc power on/off switch.

    The configuration that I am using is :
    1) Digital power from supplied 15 Vdc wall wort.
    2) Motor Drive power from AC input via a varac. (monitor with scope using gnd buster)
    3) Conrtol card (see above)
    4) M4 settings - all jumpers open (J4 shorted for GUI operation)

    I don't think any of the other settings impact the jtag interface.
    The project is configured for Ram per instructions in Sensorless FOC for PMSM doc supplied with kit. Some how phase 2 build has gotten flashed and this code starts running as soon as I connect the usb cable after cycling power, I know this is the boot from flash setting, but it is the only one that works (some of the time). If I get the right combination of cycling power, resetting emulator and loading code things will work. It may be more timing related than sequence related. I don't have a repeatable process that works every time.

    The one thing that does work every time with this configuration are the example projects located under the device_support dir. They work first time, every time. (i.e. cpu_timer, gpio_toggle, and timed_led_blink)

    Any thoughts on this.

    jedcon

  • 0 in reply to Jedcon
    TI__Mastermind 43730 points

    To answer your first question of the error that keeps on popping up, this can arise if you fail to disable the real time debugger option before reloading the code,

    I apologize for the inconvenience, The correct sequence for terminating the debug should have one more step..

    Step 25, HVMotorCtrl+PFCKit_HowToRunGuidev1.2, located at controlSUITE\development_kits\HVMotorCtrl+PfcKit_v1.2\~Docs

    25. Once complete, reset the processor (Target->Reset->Reset CPU), Go to generic Debugger Options and un-check the "Enable Real Time mode " and "Enable polite real time mode", then terminate the debug session by clicking (Target->Terminate All). This will halt the program and disconnect Code Composer from the MCU.

    The other examples work, because they do not use real time mode, if you enable real time mode and disconnect in that workspace you may face the same problem,

    Other thing is to try out launching CCSv4 with a clean option... i would post soon how to do that..

    Hope this helps in the meanwhile,

    Manish Bhardwaj