• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 81 subscribers
  • Views 429 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.

TMS320F28075: Can NOT connect to TMS320F28075 with XDS200

Eddie Hsieh
Intellectual 290 points

Part Number: TMS320F28075
Other Parts Discussed in Thread: UNIFLASH

Dear Sir,

We had several cases that can NOT connect to TMS320F28075 with XDS200.

Case1: Unstable Hardwarw1 

Sometime we get the following message from CCS. Sometime it works properly.

== CCS Output======

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 8.4.0.00006)

==================

Case2: Flash Issue Hardwarw2

We can connect to hardware2 by uniflash or CCS through XDS200. But, we can NOT write the program into TMS320F28075

Here is the message

===== CCS Message 1=========


Memory Map Initialization Complete
C28xx_CPU1: Warning: Failed unlocking device (zone 1) after reset.
C28xx_CPU1: Warning: Failed unlocking device (zone 2) after reset.
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc0eb: (Error -1066 @ 0xC0EB) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.4.0.00006)
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
C28xx_CPU1: Error executing PLL configuration algorithm. Operation cancelled. (0x0)
C28xx_CPU1: File Loader: Memory write failed: Unknown error
C28xx_CPU1: GEL: File: C:\Users\HAL\workspace_v9\HSENC_Engine1_B003_2022\CPU1_FLASH\HSENC_Engine1_B003_2022.out: Load failed.
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc056: (Error -1066 @ 0xC056) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.4.0.00006)
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc056: (Error -1066 @ 0xC056) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.4.0.00006)
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint

===============================

======= CCS Message 2===========

Memory Map Initialization Complete
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc0eb: (Error -1066 @ 0xC0EB) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.4.0.00006)
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint
C28xx_CPU1: Error writing the PLL values. (Flash algorithm returned error code). Operation cancelled.
C28xx_CPU1: File Loader: Memory write failed: Unknown error
C28xx_CPU1: GEL: File: C:\Users\HAL\workspace_v9\HSENC_Engine1_B003_2022\CPU1_FLASH\HSENC_Engine1_B003_2022.out: Load failed.
C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc056: (Error -1066 @ 0xC056) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.4.0.00006)
C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint

===============================

======= CCS Message 3 ===========

IcePick_C_0: Warning: A firmware update is recommended for the XDS200 debug probe. Click the "Update" button to update the firmware. Click the "Continue" button to continue without updating. (Emulation package 8.4.0.00006)
C28xx_CPU1: GEL Output:
Memory Map Initialization Complete
C28xx_CPU1: Error initializing flash programming: Interface returned from dll, but flash is not available on this device.

===============================

Eddie

  • 0
    TI__Mastermind 30461 points

    Are you testing/using custom board for the F28075? Or is this a TI EVM? If it is custom board, do you have a TI EVM handy you can test with the XDS200 to see if the issue is the XDS200 or the board? Do you see this issue on multiple boards or just these two? 

  • 0 in reply to Gus Martinez
    Intellectual 290 points

    We design the hardware boards. It happens on some boards. They are good at beginning. It seems the issues happens in JTAG or on-board flash. Is there alternative to fix  or bypass the issues?

    Eddie 

  • 0 in reply to Eddie Hsieh
    TI__Mastermind 30461 points
    Eddie Hsieh said:
    Is there alternative to fix  or bypass the issues?

    Impossible for me to tell at this point. There could be many different reasons for these types of failures: poor JTAG connection, brown-out on DSP power supplies, firmware bug, etc.

    Eddie Hsieh said:
    We design the hardware boards. It happens on some boards. They are good at beginning.

    If it only happens on some boards, then there could be some hardware marginal issue, i.e. a pull-up resistor which is a percentage point too strong or maybe a power supply that is dipping lower compared to other boards. Again, it is difficult to tell.

    I would suggest the following:

    - Use CCS to run a JTAG test connection (see step 9 in section 5.2. of this app note: https://www.ti.com/lit/an/spracf0b/spracf0b.pdf 

    - Share the schematics for your board, you only need to share the JTAG connection portion.

    - Monitor the power supplies to the DSP using a scope, verify that these stay within operating conditions.

  • 0 in reply to Gus Martinez
    Intellectual 290 points

    We modify the JTAG to 5MHz from 10MHz. Use the 5MHz setting to program the flash. It works well. Then, we change back to 10MHz. Everything is ok too.

    Does the MCU save the setting? I don't understand.

    I attach the JTAG setting and schmatic.

  • +1 in reply to Eddie Hsieh
    TI__Mastermind 30461 points

    If JTAG speed is making a difference, then perhaps there is a signal integrity issue on your board with the JTAG pins. It's only happening on some boards, so it could be marginal. Are you using a particularly long cable between the debug probe and your board? 

  • 0 in reply to Gus Martinez
    Intellectual 290 points

    On PCB side, maximum trace length from JTAG connector to MCU is 0.8”(about 2 cm),

    The cable of XDS200 is about 15cm.

    If the root casue is cable length, it will have problem when we change the speed back to 10MHz.

    Now, those boards, have issues, now all work wrll at 10MHz.

    Eddie