• State TI Thinks Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 81 subscribers
  • Views 294 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.

Original question:

F28M35H52C: F28M35H52C burning error

F28M35H52C: Burn error and WIR mode

Jimmy Huang
Expert 2195 points
Part Number: F28M35H52C
Other Parts Discussed in Thread: UNIFLASH, C2000WARE

Hello：

My client has a problem that during the production of substrate, there was an error in C28 program burning (200 pieces in 2000 pieces)

1、XDS100 has been used for mass production program burning,and burning through uniflash

Error in burning C28

2. Later, My client bought xds200 from Ti mall and used CCS 10.3 to burn C28, but still an error is reported

The error is as follows:

 

C28xx_0: 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.3.0.00042)
C28xx_0: Error: (Error -1135 @ 0x3FFEAD) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.3.0.00042)

C28xx_0: Unable to determine target status after 20 attempts
C28xx_0: 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

Can't Run Target CPU:
(Error -1156 @ 0x8050)
Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device.
(Emulation package 9.3.0.00042)


C28xx_0: Breakpoint Manager: Unable to remove requested AET job
C28xx_0: 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
C28xx_0: Error occurred during flash operation: Could not write 0x00000064@Data: target is not connected

C28xx_0: Error occurred during flash operation: Could not read 0x00004402@Data: target is not connected
C28xx_0: Error occurred during flash operation: Could not read 0x00004406@Data: target is not connected
C28xx_0: Error occurred during flash operation: Could not write 0x00000@Program: target is not connected
C28xx_0: Error occurred during flash operation: Cannot enable while the target is disconnected

C28xx_0: Error occurred during flash operation: Could not read 0x00000064@Data: target is not connected
C28xx_0: Error occurred during flash operation: Could not write 0x00000064@Data: target is not connected
C28xx_0: Error occurred during flash operation: Failed to run target while trying to execute pwrite_dis.alg
C28xx_0: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.

The JTAG circuit is as follows:

3、In E2E forum posts, TI AE suggests that it can be operated into WIR mode. My client  don't know how to do that, Can you give operation guide and related source code for us？Thank you

  • 0
    TI__Mastermind 38275 points

    Hi Jimmy,

    Not certain if this is related to the errors, but something you can try is removing pull-up resistor R5. It is not needed based on the graphic from the datasheet below:

    I'd recommend trying to fix the issue in CCS before going to Uniflash / command line programming. Please take a look at the 'C2000 MCU JTAG Connectivity Debug' application report linked below for steps and things to check.

    https://www.ti.com/lit/spracf0

    Best,

    Kevin

  • 0 in reply to Kevin Allen18
    Expert 2195 points

    Hi Kevin：

    My client has just tried to remove the pull-up resistor R5 and use CCS to burn. The fault phenomenon is the same as before，So please Check if there are any other problems that cause this error.

    Before, AE on E2E forum suggested to try WIR mode，Is it necessary do that？If yes，Would you please give operation guide and related source code for us？Thank you


  • 0 in reply to Jimmy Huang
    TI__Mastermind 38275 points

    Hi Jimmy,

    Did you try the different things mentioned in the previously mentioned app note? Does the Test Connection of the target config file in CCS complete successfully? I think checking all of the documented things would be a good initial step.

    BOOT ROM symbols are provided within C2000WARE directory below. I'm not certain about the WIR mode, but the referenced e2E seemed to be a HW issue.

    C:\ti\c2000\C2000Ware_3_04_00_00\libraries\boot_rom\f28m35x\rev0

    Best,

    Kevin

  • 0 in reply to Kevin Allen18
    Intellectual 470 points

    Dear Kevin,

    This PM from Arrow Asia,could you help mail to me to involve this case? My key customer has pending for a few days because of this problem. Thank you.

    Derek.zhong@arrow.com

    best regards

    Derek

  • 0 in reply to Derek Zhong
    TI__Mastermind 25311 points

    Hi Jimmy (and Derek),

    Jimmy Huang said:
    In E2E forum posts, TI AE suggests that it can be operated into WIR mode. My client  don't know how to do that, Can you give operation guide and related source code for us？

    Just to be clear, the referenced forum post states that in that case the device was not reaching the ROM code or booting from flash due to the device being stuck in WIR mode. The WIR mode was triggered because EMU0 in the customer board was stuck at "0". This was due to customer hardware/handling problem which is not further described.

    For your case, EMU0 and EMU1 are pulled high. For WIR mode EMU0=0 and EMU=1. The symptoms of the problem do not seem to point to a boot issue, they point to a JTAG issue. Do you believe the device is stuck in WIR mode? Even if the device is stuck in WIR mode, the JTAG access should not be blocked.

    In the app note referenced by Kevin, there is a description of the "Test Connection" feature in CCS when running the target configuration file. It would be very useful if the customer could run that and provide the log. That may give some clues as to the source of the problem.

  • 0 in reply to Gus Martinez
    Expert 2195 points

    Hi Gus：

    My client has read the app note and Indicates that there is no Test Connection. But when it is burned, there are some problems. The main problem is that C28 is not burned well, and M3 is OK

    M3 burning OK

     

    C28 burning wrong

  • 0 in reply to Jimmy Huang
    TI__Guru 55700 points

    Jimmy,

    Do you have CCS? Test connection is available when you open the .ccxml for the device family you are using in CCS.

    It not clear from your description whether you were able to connect to the device before and you started having problem once you programmed something in C28x (or) you were never successful in connecting to C28x.

    Please clarify.

    Regards,

    Manoj

  • 0 in reply to Manoj Santha Mohan
    Expert 2195 points

    Hi  ：

    My client feedback is that test connection It's always OK，He makes sure that the connection is OK. Then he starts programming something in C28x. When doing C28 burning, it failed

  • 0 in reply to Jimmy Huang
    TI__Guru 55700 points

    Jimmy,

    Let me try summarizing the problem you're facing...

    (1) You are able to successfully connect to both M3 and C28x device. Correct?

    (2) You are able to successfully program M3 but not C28x. Correct?

    Is your device secured? Are you trying to program C28x without unlocking the device? Did you try programming C28x in CCS?

    Regards,

    Manoj

  • 0 in reply to Manoj Santha Mohan
    Expert 2195 points

    Hi Manoj：

    (1) You are able to successfully connect to both M3 and C28x device. Correct? Yes

    (2) You are able to successfully program M3 but not C28x. Correct? Yes

    My client don‘t know device is locked or unlocked. He has tried  programming C28x in CCS. The fault code is posted in the previous description. Thanks

  • 0 in reply to Jimmy Huang
    TI__Guru 55700 points

    Error message seems to indicate that device might be locked. If the customer doesn't have the password, then the only option is to replace the part.