F28M35H52C: Burn an error

Neal,

Do you have any update on this?

Is this resolved now?

Thanks and regards,
Vamsi

Neal,

I am closing this post since I did not hear from you.

If you have further questions in the future, you can open a new post.

Thanks and regards,

Vamsi

Hi

Newly bought XDS200, but still burning error report,Please help to analyze, thanks!

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)

Thanks,Vamsi

Recently, I have done many experiences. I bought XDS200 from TI store. With CCS 10.5, there are also errors.

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.

Eric,

I saw you opened a new post a few minutes ago.  We can discuss your issue there.  Let me use this thread to work with Neal Zhu.

Thanks and regards,

Vamsi

Neal,

Thank you for the details.

Are you trying to program an already programmed device?  If yes, did you program any DCSM settings in the previous iteration?

Are you using CCS or Uniflash?  What is the version you are using?  Did you check for updates and install if any for the emulator?  If not, please check and install.

How are the boot mode pins configured?  Could you confirm whether you are using the WIR mode or not?  Please see section 1.4 WIR Mode in TRM (https://www.ti.com/lit/pdf/spruh22) for details on how to use this mode.

Also, please take a look at http://www.ti.com/lit/spracf0 

Thanks and regards,

Vamsi

I have tried to program an already programmed device with XDS200. It's OK.

The CCS(10.5) and Uniflash(6.0.1) are both used.

Vamsi,

I'm not familiar with DCSM settings.

And verified by experiments，The error is closely related to the F28M35H52C and nothing to do with the PCB substrate.

Now there are 200pcs defective products, the matter is very urgent.

Thanks.

Eric,

I don't think it is a device issue.  Can you answer my previous question copied below?

Could you confirm whether you are using the WIR mode or not?  Please see section 1.4 WIR Mode in TRM (https://www.ti.com/lit/pdf/spruh22) for details on how to use this mode.  

Thanks and regards,
Vamsi

I have confirmed the usage of WIR mode.The software has not operated on this part and performs the default operation.

Could you provide source code about this?

Thanks.

Eric,

Are you saying that you are using WIR mode?

What source code are you asking for?  Please clarify.

Here is the info about using EMU0 and EMU1 pins from datasheet:

Thanks and regards,

Vamsi

Hi, Vamsi

I mean the software that i'm using doesn't use WIR mode.

With hardware circuits, the pin of EMU0 and EMU1 are both  pulled up.

I want some source codes including WIR mode to verify your point.

Thanks

Eric,

WIR mode needs EMU0 to be low and EMU1 to be high.

Thanks and regards,

Vamsi

Eric,

When you say you need source code, which method are you planning to implement given the below choices to enter the WIR mode?  Please confirm.  I am suggesting method #1.  

I asked our system control expert to help you further on WIR mode as needed.

Thanks and regards,
Vamsi

Eric,

          Reading through the thread, I am not clear exactly what the issue is. Are you having a problem connecting to the device via CCS? Or are you having a problem programming the flash memory?

Thanks,Hareesh

I have done that via CCS, the error above is reported by CCS.

And there is no problem when programming the flash memory.

So what exactly is the problem you are facing with the device now?

The problem is that M3 can be brushed in, C28 is all wrong.

The error is shown at above picture.

Sorry, I don't understand what you mean by "M3 can be brushed in". Are you saying M3 can be programmed? As Vamsi stated early on, this is unlikely to be a device issue. Something likely changed in your programming setup or the programming method. If the issue persists, you may want to send a few units to TI for analysis. I hope there is a TI FAE that you are working with.

Thank you for contacting us offline on this.

As mentioned previously, WIR mode needs EMU0 to be low and EMU1 to be high.  If not, device will boot to flash and start executing invalid opcodes (as nothing is programmed yet).  This can cause ITRAP and continuous resets ->  Device will not be in a clean state for the flash programmer to do flash erase/program operations.

Reason why you may not see an issue with every device is:  It depends on the instant when the target connection is made.  If the connection is made before the ITRAP occurrence or just after a reset, connection will be stable.  If not, it is not possible to make a stable good connection with the device to do flash operations. WIR mode prevents the CPU from executing invalid opcodes in flash.

If not WIR mode, can you configure boot mode pins to something other than flash boot?  For example, SCI/UART boot – this way the CPU won’t boot to flash and start executing garbage.  

As per the errors, this is not a flash programming issue.

Please note:  We prefer to work on E2E directly instead of the email.  It would be tough to track and close via emails. 

Thanks and regards,
Vamsi

You updated us offline that M3 boot mode is changed to UART boot and still the issue is present.

WIR mode is not required for M3 if UART boot is chosen.  However, C28x does not look for any boot mode GPIOs in this device.  At the end of the boot, if WIR mode is not enabled for C28x, it will enter idle mode.  Our system control expert can help you further on this.

Thanks and regards,
Vamsi

Hi Hareesh,

As we discussed, my customer has understand why there is a burn issue on C28x core. Now he has tried change the boot mode to UART in circuit, but hasn't change any code, and the error stays the same.

Since my customer has limited software knowledge on this chip, can you provide the most simple way to solve the issue?

Sirui,

    Is it possible to ship some devices for failure analysis?

Quality process is needed if do FA, I'll contact local quality colleague.

Since it will take a long time, and my customer is in urgent situation, could you please provide some instruction (code would be better) of using WIR in the burning process?

WIR is entered by tying EMU0/1 low/high. Are you able to share the schematics privately with me?

Hi,Hareesh

Our firmware engineer want to know the time node of entering the WIR mode.

That's to say,when to enter the WIR mode and when to exit the WIR mode?

Would you provide some support? Thanks.

WIR mode should be entered upon power-up. This is to ensure that the device is in a stable/known state when the tool (could be CCS or Uniflash) attempts to connect to it. Could you please try WIR mode on a failing device and see if it fixes the issue? After programming the flash, you could change the EMU0/EMU1 connections.

Hi,Hareesh

Our firmware engineer have tested the WIR mode.There is no change.The error  still exists.

I suggested WIR mode through hardware, not software. Please try WIR through H/W.

Hi,Hareesh

Through hardware,we have also tried.There are also no change.

Can you please clarify what H/W modification you did on your board to put the device in WIR upon power-up?

Befor power the board,put the EMU0 to GND.Then power the board,after a few seconds,put EMU0 to the pull-up state.After performing the above steps,start burning.

Our FAE is in the process of setting up a call. Let us continue the conversation there.

Hi，Hareesh

As the meeting said, we tried three methods.

1、WIR mode

Before power the board, put the EMU0 to GND and not connect the JTAG.

Then power the board,keep EMU0 with 0 and EMU1 with high level.

And give a low pluse to  XRST. Next, burning the MCU, failed again.

2、Blinky routine 

When use CCS to burning Blinky to RAM, error happened.

Please work with Sirui to return 3 devices to TI for analysis.

For #1, could you please list out the exact procedure step-by-step that you followed?