• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 758 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.

CCS/TMS320F28069M: BLDC Motor is not Running, When the code is flashes TMS320F28069M and interfaced with DRV8301.

Chandrasekar P
Prodigy 60 points
Part Number: TMS320F28069M
Other Parts Discussed in Thread: DRV8301, , MOTORWARE

Tool/software: Code Composer Studio

Hello All, 

I'm new to thisEnviroment, kindly help me out for the below mentioned scenario.

For implementing the [boostxldrv8301_revB\f28x\f2806xM\projects\ccs5\proj_lab05d] for DRV8301 startup process. Imported and build the project successfully. 

After that, I have followed [Target Configuration settings] for flashing into target TMS320F28069M.

1) Connection-Texas Instruments XDS100v2 USB Debug Probe

2) Device- TMS320F28069M

In that, Test Connection TMS320F28069M Without connecting to DRV8301 the JTAG DR & IR Testing was succeeded, whereas when we connect the DRV8301 with TMS320F28069M JTAG DR & IR Testing was get failed. Can you please help to solve this issue? 

 


This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 83.3 percent.

The JTAG IR Integrity scan-test has failed.

-----[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.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 83.3 percent.

The JTAG DR Integrity scan-test has failed.

[End: Texas Instruments XDS100v2 USB Debug Probe_0]

3) How to get -Texas Instruments XDS100v2 USB Emulator Probe/C28xx instead of Texas Instruments XDS100v2 USB Debug Probe, is there any Emulator package support for this?, This Emulation package 6.0.504.4 is has been already installed, Even when we connect the target it's always shown below-mentioned error. How to Rectify this error?

Error connecting to the target:
(Error -1135 @ 0x0)
The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation.
(Emulation package 6.0.504.4)

Even though, when we use debug option, it\s entered into Debug mode, but the values in the expressions have been loaded with errors. 

Sometimes, values are also loaded, But from the DRV8301 signals are not gone through to BLDC motor and motor is not running, Don't know what is happening??

Thanks in advance, If you help for this it would very much indeed and thankful,

Regards,

Chandrasekar P

  • 0
    TI__Guru** 115440 points
    You don't need to change anything for JTAG connection if you are using lunchPAD with on-board emulator, and Texas Instruments XDS100v2 USB Debug Probe is the right configuration. Please check the DRV8301 and LunchPAD power are OK, and confirm the USB driver is OK also.
    Please refer to Lab user guide, to run lab05d, the motor inertia value should been identified and populated in user.h, this process can be completed in Lab 5c - InstaSPIN-MOTION Inertia Identification.
  • 0 in reply to Yanming Luo
    Prodigy 60 points
    Dear Yanming,

    We have checked the Power source and checked with another one. It got worked and some misconnections are also made rectified, then the motor has spinned.

    Can you please tell me!! What are all the parameters that we can change for Motorware driver in DRV8301 user.h.

    How to change the PWM signals and Load parameters in user.h.