CCS/BOOSTXL-DRV8320RS: DRV8320RS MotorControl SDK lab with TMS320F280049C

Akila,

Can you open the target configuration, and run "Test Connections" and send the log?

[Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\ASADHA~1\AppData\Local\TEXASI~1\
CCS\ccs1000\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'May 7 2020'.
The library build time was '21:10:18'.
The library package version is '9.2.0.00002'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

[End: Texas Instruments XDS110 USB Debug Probe_0]

Akila,

Can you run any C2000ware DriverLib simple example, without the DRV8320 kit and check if you can connect and run successfully? Just wanted to narrow it down if Launchpad itself is still working fine.

I ran the adc example fine. 

 When I try to run epwm_ex2_updown_aq, I am getting this error.

Error connecting to the target:
(Error -716 @ 0x0)
Required dynamic library jscserdes could not be located.
The library isn't on the search path.
(Emulation package 9.2.0.00002)

Akila,

When do you encounter this error? during loading the program?

yes

Akila,

Is this using F280049C controlCARD or Launchpad?

Launchpad

I even tried adding predefined symbol, _LAUNCHXL_F280049C to the project properties. Still getting the same error.

"When I try to run epwm_ex2_updown_aq, I am getting this error."

Is this C2000ware DriverLib example or you have modified anything? The stock C2000ware DriverLib example should work fine.

Can you create a new workspace (different location on your computer) and re-import the DriverLib project and check if it works. I am suspecting your workspace somehow got corrupted.

I also tried CLA background nesting task driver library example and got the same error.

 When I tried CLA background nesting task driver library example with a new workspace, I did not got the error. But, no LEDs blinking. I expected 2 new LEDs to blink. Also, I cannot locate the LED2. Please help.

Akila,

You should be able to set the break point and debug from there?

ok. I take it back. It worked one time. I try to do the same thing again with another new workspace. It throws me the same error.

These are TI provided example projects. Should I not expect them to work without having to debug? 

Got the same error even when imported in new workspace.

Akila,

In the new workspace it works, so it must be something after you add your changes. We should review that.

Can you list what are steps you are doing after that? Or if you have any simplified workspace, I can try over here.

Like I said earlier,it works sometimes and not most of the time. Got the same error even when imported in new workspace. I am not making any changes to the workspace.

Let me loop in the control control expert to comment on it. I have Launchpad and I tested few examples, it works fine all the time.

or can you run DriverLib example on standalone Launchpad (disconnect Boostxl) and see if it works consistently. Use Launchpad user's guide to get started.

C2000 Piccolo F28004x Series LaunchPad Development Kit (Rev. B)

I am running DriverLib example on standalone Launchpad without Boostxl using the guidance from Launchpad user's guide.

Are you running Launchpad configuration of the project?

Right-click on project, Build Configuration -> Set Active -> CPU1_LAUNCHXL_RAM

yes

Akila,

The DriverLib examples with Launchpad configurations are tested on Launchpad, and I have also tested it.

Are you seeing connection issue or the example functionality does not work?

I am seeing connection issue during loading.

I went back to running with booster board. I tried running lab 6 of Insta spin FOC lab.In this case, error occurs predictably every time I set the flagEnableSys to 1. Immediately, I tried running test connection in target configuration. I get the below error.This happens predictable every time.

[Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\ASADHA~1\AppData\Local\TEXASI~1\
CCS\ccs1000\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'May 7 2020'.
The library build time was '21:10:18'.
The library package version is '9.2.0.00002'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.

An error occurred while hard opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-261' (0xfffffefb).
The title is 'SC_ERR_XDS110_FAIL'.

The explanation is:
Invalid response was received from the XDS110.

[End: Texas Instruments XDS110 USB Debug Probe_0]

Akila,

I want to make sure.

You tried Standalone Launchpad. It works fine with all the examples if you use CPU1_LAUNCHXL_RAM configuration.

Then you went back to BOOSTXL, and now you are seeing the same connection issue during loading, is that correct?

I tried Standalone Launchpad. It also gives me error when loading sometimes even with CPU1_LAUNCHXL_RAM configuration.
Then I went back to BOOSTXL, to see if I am still seeing the same connection issue during loading, I still see the same error.

That is where I am.

Let's try to fix with standalone first. It it fails in standalone mode, then there is no point in adding the BOOSTXL.

Which example it is failing to load? What is the boot switch you are using? Can you send picture of board when it is in standalone mode and failing to connect.

CLA background nesting task

Wen I try to load, I get below error.

The picture did not came through. Please post it again.

SCREEN2.pptx

Something is not right.

Are you using onboard XDS110 emulator or external XDS100 v2?

Please take full screen-shot. I want to see your project window 

SCREEN3.pptx

I think I am using onboard XDS110 emulator. How can I tell for sure?

I just tested same example on my hardware and it works fine. Can you try following steps?

1) Open Target Configuration Window  (CCS menu, View -> Target Configuration)

2) Expand Projects. go to cla3_background_nesting_task -> targetConfigs -> TMS320F280049C_Launchpad.ccxml

3) Select it and right-click, and launch the configuration ("Launch Selected Configuration") as shown below.

4) Connect C28xx_CPU1

5) Load the program using CCS menu Run -> Load -> Load Program and then browse the out file.

If I do it the way you have mentioned, it works. 

If I click the debug icon, it throws the below error.

Error connecting to the target:
(Error -2131 @ 0x0)
Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 9.2.0.00002)

Akila Sadhasivan said:

f I click the debug icon, it throws the below error.

Error connecting to the target:
(Error -2131 @ 0x0)
Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 9.2.0.00002)

Looks like it is picking wrong target configuration when you debug.

Can you check the debug configuration?

Right click the project, Debug as -> Debug configuration, and then make sure it has correct configuration, something like below.

It has this in debug target configuration.

C:\ti\C2000Ware_MotorControl_SDK_3_00_01_00\c2000ware\device_support\f28004x\common\targetConfigs\TMS320F280049C_LaunchPad.ccxml

I expect this instead.

${target_config_active_default:cla_ex3_background_nesting_task}

Can you replace this and try again?

Still getting 

Error connecting to the target:
(Error -2131 @ 0x0)
Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 9.2.0.00002)

SCREEN4.pptx

When I right click TMS320F280049C_LaunchPad.ccxml, under target configuration in project explorer shown in previous attached picture, and set as active target configuration, then run it, it works. This still does not resolve my booster driver lab 6 issue.

I am glad it is working fine as standalone Launchpad project with configuration making as active.

With Booter, are you seeing same error? Can you try manually launching it as I mentioned earlier?

No with booster, I am not seeing the same error.

I get error only when I set the variable flagEnableSys in the expression window with lab6.

What is the error?

Can you attach the screenshot?

This issue started with that. Copying again.

I have been going through the various TI instaspin motor control tutorials . I was able to run lab5 multiple times. Suddenly, I get the following error when I try to re-run lab5. Lab6 errors out consistently every time when I change the variable value to 1.

C28xx_CPU1: Trouble Reading Register RPC: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.2.0.00002)
C28xx_CPU1: Trouble Halting Target CPU: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.2.0.00002)
C28xx_CPU1: Error: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.2.0.00002)
C28xx_CPU1: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

When I tried again after an emulation reset, I get the following error.

IcePick_C_0: Error: (Error -261 @ 0xFFFFFEFB) Invalid response was received from the XDS110. (Emulation package 9.2.0.00002)
C28xx_CPU1: JTAG Communication Error: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.2.0.00002)
C28xx_CPU1: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

Akila,

Assigning to motor control expert to help as it is working in standalone mode and you are seeing issue only with Instaspin.

SCREEN5.pptx

Lab7 screen shot after turning on the motor control.lab7.pptx

You might take a  look at the InstaSPIN lab's guide in the folder of MotorControlSDK, make sure that the right motor parameters are set in the file of the user.h if you want to run the lab06 and the subsequent labs. And recommend that you might start from the "is01_intro_hal" lab if you didn't implement instaSPIN-FOC before.

MotorControl SDK InstaSPIN Lab Guide.pdf, C:\ti\c2000\C2000Ware_MotorControl_SDK_<version>\solutions\common\sensorless_foc\docs\labs

For a new motor, you must use the "is05_motor_id" lab to identify the motor parameters and set them in the file of the use.h.

You should click the "CPU reset" button and then click "Restart" if you want to reset the loading program and re-run it.

Otherwise, you only need to set the "motorVars.flagRunIdentAndOnLine" variable to "0" or "1" to stop or run the motor. Before doing that, make sure that you install the boosterPal board to launchPad correctly and connect the right power supply to the booster board, all of the labs must be run with the boosterPack on the right side of the LaunchPad. 

Please have a detailed description of the operation steps you did if you still had any issues running these labs. I can't repeat any issues you mentioned above.