• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 98 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

LAUNCHXL-F28069M: Debug Issue with LAUNCHXL-F28069M + BOOSTXL-3PHGANINV

Marco Lasagni
Prodigy 65 points
Part Number: LAUNCHXL-F28069M
Other Parts Discussed in Thread: BOOSTXL-3PHGANINV

Tool/software:

Dear TI Support Team,

I am currently working with the LAUNCHXL-F28069M paired with the BOOSTXL-3PhGanInv module, and I am encountering a recurring issue. Occasionally, during motor identification or when starting the motor, I receive the following error:

C28xx: Error: (Error -1041 @ 0xFFFFFF6A) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 20.0.0.3178) C28xx: Trouble Halting Target CPU: (Error -150 @ 0x0) One of the FTDI driver functions used during configuration returned an invalid status or an error. (Emulation package 20.0.0.3178) C28xx: Unable to determine target status after 20 attempts C28xx: 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.

I have configured the hardware as follows:

  • JP1 and JP2: Tested both open and closed configurations.
  • S1 Switches: Tested with both H H H and L H H configurations.
  • JP7: Closed.
  • JP6: Open.
  • Power Supply: The LAUNCHXL-F28069M is powered by the BOOSTXL-3PhGanInv through J5 (closed on the BOOSTXL).

Additionally, I ran the dbgjtag connection test, and the results confirmed successful communication and JTAG integrity. Here is the relevant report summary:

-----[Perform the Integrity scan-test on the JTAG IR and DR]----- JTAG IR Integrity scan-test: Passed. JTAG DR Integrity scan-test: Passed. All values scanned correctly.

I have followed the hardware and software configuration steps outlined in the SLUUBP1A guide. The issue occurs in both Code Composer Studio (CCS) and the InstaSPIN Universal GUI.

Could you please advise on possible solutions to this problem?

Thank you for your support.

Best regards,
Marco Lasagni