CCS/TMS320F28027: TMS320F28027 HVPSFB development kit cannot debug

user5277039

Intellectual 640 points

Part Number: TMS320F28027
Other Parts Discussed in Thread: CONTROLSUITE, UNIFLASH

Tool/software: Code Composer Studio

Dear Ti community

I'm developing PCMC on HVPSFB.

And I want to operate HVPSFB development_kits.

I supply 12V at TP1 at base board, remove R6 resister and J1 at controller card.

Then connect the USD cable attached the kit.

In CCS,create target configuration file and debug default HVPSFB_PCMC Project.

The debug success.

After that,I want to change the program.

I debug same process,but the error occuer.

the error is

C28xx:error connecting to the target:(Error - 1135 @ 0x0)

the emulator reported an error.Confirm emulator configuration and connection,

reset the emulator,and retry the operation.

(Emulation package 5.1.507.0)

I tried R6,J1 populate,but same error occuer.

What is the cause?

over 6 years ago

0 Chen Jiang ti over 6 years ago

TI__Genius 15935 points

Hi user5277039，

When you say "After that,I want to change the program. I debug same process,but the error occuer."

So this problem happens once you change the source code or not? Does this happen after the experiment with power on?
Can you go back to use the original code and hardware settings to try again?

Regards,
Chen

0 user5277039 over 6 years ago in reply to Chen Jiang ti

Intellectual 640 points

When I wrote first time,the code is not changed.

But I want to Incremental Builds pattern 1,change from INCR_BUILD = 2to INCR_BUILD = 1

I never power on DC 400V.Bias 12V is input every time.

I tried go back original code.

About hardware,I tried J1,R6 are removed and populated.

0 user5277039 over 6 years ago in reply to user5277039

Intellectual 640 points

Sorry,I had a mistake.
I removed and populated diferent R6 in same board.
Is there a possibility that this will be a problem?
The place I removed by mistake was following picture.

And when I removed and populated corrent R6 and J1,
It wasn't improved.
When J1,R6 are removed,It occuers above error.
When J1,R6 are populated It occuers following error.

Error connecting to the target:(Error -1015 @0x0)
Device is not responding to the request.Device may be locked,or the emulator connection may be unreliable.
Unlock the device if possible(e.g. use wait in reset mode,and power-cycle the board).
If error persists,comfirm configuration and/or try more reliable JTAG settings(e.g. lower TCLK).
(Emulation package 5.1.507.0)

0 user5277039 over 6 years ago in reply to user5277039

Intellectual 640 points

And There is a more infomation.
At TargetConfiguration,
I selected「Texas Instruments XDS100v1 USB Debug Probe」,「TMS320F28027」,
and tried 「Test Connection」.
The result is same when R6,J1 is removed or populated.
The message is

[Start: Texas Instruments XDS100v2 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\11E9B6~1\AppData\Local\TEXASI~1\
CCS\TI\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusb.dll'.
The library build date was 'Nov 21 2018'.
The library build time was '00:08:45'.
The library package version is '8.0.903.2'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '4' (0x00000004).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the FTDI FT2232 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for FTDI FT2232 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[The log-file for the JTAG TCLK output generated from the PLL]----------

There is no hardware for programming the JTAG TCLK frequency.

-----[Measure the source and frequency of the final JTAG TCLKR input]--------

There is no hardware for measuring the JTAG TCLK frequency.

-----[Perform the standard path-length test on the JTAG IR and DR]-----------

This path-length test uses blocks of 64 32-bit words.

The test for the JTAG IR instruction path-length failed.
The JTAG IR instruction scan-path is stuck-at-ones.

The test for the JTAG DR bypass path-length failed.
The JTAG DR bypass scan-path is stuck-at-ones.

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

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 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 XDS100v1 USB Debug Probe_0]

And I cannot understand when J1,R6 are removed or populated.
I read 「HVPSFB_User's Guide」 but It is difficult to image.
So, please tell me for example following case
1.When write code.
2.When debug.
3.When operate continually.

0 Mark Labbato over 6 years ago in reply to user5277039

Guru 30330 points

Hi,

Please follow the procedures outlined in the "Procedure" section of the HVPSFB_User's Guide.pdf document.

Ensure that J1 is populated on the controller card, also make sure that Jumpers J8 and J6 are populated on the base board.
I think Steps 1-5, and then Steps 11 - 15 are all that are needed.

It also looks like you are using an XDS100 v1 debug probe? The connection should use the XDS100 v2.

Please let me know the results of Step 15 when you get there.

If you are still unable to connect, please check out the JTAG connection debug guide - http://www.ti.com/lit/spracf0

Thanks,
Mark

0 Mark Labbato over 6 years ago in reply to Mark Labbato

Guru 30330 points

One extra comment,

It seems like there is just a bit of confusion in the documentation here. You need to populate R6 on the PiccoloA macro, not the R6 from the Controller_Card board you highlighted. The Macro is located here: "C:\ti\controlSUITE\development_kits\HVPSFB_v1.1\~HVPSFB-HWdevPkg\CC_F2802x_Controller card\Macros\PiccoloA-48LQFP[R2]schem.pdf"

The R6 in this macro is the pulldown on the GPIO37/TDO boot mode pin. J1 Connects TRSTn to the debug probe, which is pulled high. enabling emuboot.

Regards,
Mark

0 user5277039 over 6 years ago in reply to Mark Labbato

Intellectual 640 points

I retried following procedure.

1.          I make sure that jumpers J8 and J6 on the base board are populated.
2.         I make sure that jumpers J1 and R6 on Piccolo Macro of the controller card are populated.
             Power up the bias supply between TP1 and TP2 with around 11V DC.
             Not turn on 400V DC
3-5        I import 「HVPSFB_PCMC」
6-12     I don't change the code. I make sure the code.
             Rebulid Project」 is successed.
13-14    I make target configuration file check 「Use shared location」.
             select 「Texas Instruments XDS100v2 USB Emulator」,「TMS320F28027」
15        Debug the project

But the same error occuer

0 user5277039 over 6 years ago in reply to user5277039

Intellectual 640 points

I check out JTAG connection debug guide .
I have a few problems.
1.When I populate the R6, the LD1 on controller card macro don't light.
2.check my device manager, there are not 「TI XDS100 Channel A」,「TI XDS100 Channel B」
3.check TRSTn signal,when connect CCS, the signal isn't high.

And I cann't understand 「Reprogram Emulation Controller」,
Please tell me the procedure in detail.

And to reinstall the XDS100 driver, I remove the driver.
But after that,I cann't reinstall driver .
So I want to install the driver manually.
Please send me the driver file

0 user5277039 over 6 years ago in reply to user5277039

Intellectual 640 points

I found out that a microcontroller is damaged.
2 pin and GND is short.

0 MatthewPate over 6 years ago in reply to user5277039

TI__Guru* 80270 points

Pin 2 is TRSTn, which is connected only to the isolated emulator and the C2000 MCU. My point being that the HV network should never see this net to damage it, so this might have occured through ESD/handling which is rare for a PCB even if not handled in a ESD safe manner.

Note there is a 2k PD on this pin to keep the emulation logic in reset. If this is removed do you still see a hard short to VSS?

Just to confirm, the USB serial/emulation connection does not provide power to the C2000. Per the QSG ~11V needs to be applied to the Bias net that exists between TP1 and TP2 on the main board. This is the voltage that will power both the UCC device as well as the 3.3V LDO that will power the C2000 MCU. Can you confirm that the 11V is present and this issue still exists(assuming that TRSTn is not damaged).

Best,
Matthew

0 user5277039 over 6 years ago in reply to MatthewPate

Intellectual 640 points

There are 2 resistance R1,R7 connect with Pin 2.

I remove 2 resistance and check Pin 2 .

Pin 2 short GND.

I confirm that vias 11VDC is powered and 3.3V.

0 MatthewPate over 6 years ago in reply to user5277039

TI__Guru* 80270 points

I think at this point, you have confirmed that some damage has occurred to the F28027 module. Given that we do not sell the PCBs of this kit individually it may make more sense to sample a TMS320F28027PTT device and replace the MCU.

Best,
Matthew

0 user5277039 over 6 years ago in reply to MatthewPate

Intellectual 640 points

I get new control card and,I can debug first.
But, after I try any time,
same point break.(2pin short GND)

I think there are any problems of my environment and my procedure.

When I debug,
DC 400V is not input.
Bias 11V is input.
Jamper 1 is populated.
Resister R6 removed.
Then , I connect USB cable and debug.

And I ran the code without DC 400V .
And I boot the code without DC 400V .

What is the problem?

0 MatthewPate over 6 years ago in reply to user5277039

TI__Guru* 80270 points

Just to confirm, you got a new controller card as shown below? This is not the same as the F28027CNCD that we normally refer to as the "control CARD" in our documentation. If you don't connect the controller card to the HVPSFB kit does it connect/function OK? This board should be able to be independently powered by the USB connection alone.

0 user5277039 over 6 years ago in reply to MatthewPate

Intellectual 640 points

The kit and controller card I have are this.

My microcomputer is broken already.

I comfirm that it can connect GUI and it generate PWM pulse

0 MatthewPate over 6 years ago in reply to user5277039

TI__Guru* 80270 points

If the card is OK on its own(not plugged to the base board) I would suspect there is some issue/damage to the power board itself. I need to look at the schematic some more to suggest how to debug this issue.

Matt

0 MatthewPate over 6 years ago in reply to MatthewPate

TI__Guru* 80270 points

Looking at the schematic, is it possble for you to probe the OUTx nodes when the 400V is on/off? TP9/TP8 as well?

0 user5277039 over 6 years ago in reply to MatthewPate

Intellectual 640 points

I got new TMS320F28027 and changed.

But other problem occur.

When I write to MCN.

Following error and dialog are happen .(J1 and R6 are populated)

C28xx:Flash Programmer:Error encounterd when writing to flash memory.

C28xx:GEL:File:C:\・・・\HVPSFB_PCMC\F2802x_FLASH\HVPSFB_PCMC.out: Load failed.

build is OK.

Test connection is OK.

But can't write

And,

It seems that following LED don't light.

if my memory is correct,this LED light.

0 MatthewPate over 6 years ago in reply to user5277039

TI__Guru* 80270 points

In Code Composer, can you try to right click on the target .ccxml and select "Launch Selected Configuration". Assuming that works, right click on the C28x CPU and click "Connect". Please let me know if this works.

In terms of the LED, I agree it should light, can you measure cap C1 with a DMM and report the voltage you see?

Matt

0 user5277039 over 6 years ago in reply to MatthewPate

Intellectual 640 points

I try to "Connect Target".

I show the picture after "Connect Taget".(I can't judge success or failed)

After "Connect Target", I checked "Memory Browser" at SectionA～D.

It seems that Section A isn't erased.

About LED , I mesured C1 voltage when 12V bias ON/OFF(2V/div).

0 MatthewPate over 6 years ago in reply to user5277039

TI__Guru* 80270 points

This is very good news, that you are able to connect and then view the memory. It looks like when you attempted to program the device, some areas did get data.

Can you try and erase the flash using the tools inside CCS Tools->On Chip Flash->Erase Flash? Does this succeed?

If so, go ahead and try and re-load your program under Run -> Load ->Load Program and note if this works as well.

In terms of the voltage on C1, the above is good so I'm not sure why the LED would not be lit. Perhaps it had some damage from the earlier event.

Matt

0 user5277039 over 6 years ago in reply to MatthewPate

Intellectual 640 points

I tried Erase Flash ,but failed.
Console message is
C28xx : Flash Programmer : Error eraseing flash memory.
Flash operation timed out waiting for the algorithm to complete.Operation cancelled.

I turned off/on supply voltage and retry.
Then success.

After that I tried load program,but failed.
The error is same as the one written in first.

I check Section A memory after erase success.
It seems not to be erased.
The contents of the memory are like a picture I attached last time.

0 user5277039 over 6 years ago in reply to user5277039

Intellectual 640 points

I want an answer as soon as
possible or would like to hear
progress.

0 MatthewPate over 6 years ago in reply to user5277039

TI__Guru* 80270 points

I want to go back a few posts, is the control card still unplugged from the base board, and only powered from the USB connection? I just want to eliminate the power board as a potential problem here.

Best,
Matthew

0 user5277039 over 6 years ago in reply to MatthewPate

Intellectual 640 points

When I try connection test or write the code,

I set control card to base board and supply about 11V.

Of course USB connection too.

0 MatthewPate over 6 years ago in reply to user5277039

TI__Guru* 80270 points

Can you put a scope probe on the VDDIO pin and observe the pin voltage normally, as well as when you attempt to erase/program the flash? It is important to make sure that this pin does not droop during erase/program time. You can also verify cap C2 is measuring correctly(2.2uF).

Best,
Matthew

0 user5277039 over 6 years ago in reply to MatthewPate

Intellectual 640 points

I checked C2 voltage.

When normal,constantly 3.3V below picture.(1V/div)

When erase the flash,constantly 3.3V too.

0 user5277039 over 6 years ago in reply to user5277039

Intellectual 640 points

Dear Ti community

When can I have the next answer?

Please tell me only a schedule.

0 MatthewPate over 6 years ago in reply to user5277039

TI__Guru* 80270 points

Let's check some of the CSM status registers to determine the state of the security module.

Power up and connect the device, then look at the contents of memory locatin 0x0AEF:

If you see a "1" in the Secure bit, open up a different memory window to memory address: 0x3F7FF8-0x3F7FFF, and refresh the memory window. Are the contents 0x0000 or 0xFFFF. If 0x0000 then the device is secure/locked with some password. Will wait for your reply to see where we go from there.

Best,

Matthew

0 user5277039 over 6 years ago in reply to MatthewPate

Intellectual 640 points

I check CSM_CCSMSCR at address 0x0AEF.

the memory is 0x0070 so first bit is 0.

And I check 0x3F7FF8-0x3F7FFF.

Then ,all memorys are 0xFFFF.

0 MatthewPate over 6 years ago in reply to user5277039

TI__Guru* 80270 points

Thank you for confirming this, we now know that the flash should be able to be accessed, erased and programmed. Can you use the CCS flash tools to do a blank check to see if the flash is entirely erased?

If it is not erased, let's attempt to do that proceedure again and see if we can get it to pass.

Looking at the map file for the project it looks like on Sector A is used by this project, if that is programmed the PCMC code should work correctly:

MEMORY CONFIGURATION

         name            origin    length      used     unused   attr    fill
----------------------  --------  ---------  --------  --------  ----  --------
PAGE 0:
  BOOT_RSVD             00000000   00000050  00000000  00000050  RWIX
  progRAM               00008000   00000300  0000022e  000000d2  RWIX
  OTP                   003d7800   00000400  00000000  00000400  RWIX
  FLASHD                003f0000   00002000  00000000  00002000  RWIX
  FLASHC                003f2000   00002000  00000000  00002000  RWIX
  FLASHA                003f6000   00001f80  0000150a  00000a76  RWIX
  CSM_RSVD              003f7f80   00000076  00000000  00000076  RWIX
  BEGIN                 003f7ff6   00000002  00000002  00000000  RWIX
  CSM_PWL               003f7ff8   00000008  00000000  00000008  RWIX
  IQTABLES              003fe000   00000b50  00000000  00000b50  RWIX
  IQTABLES2             003feb50   0000008c  00000000  0000008c  RWIX
  IQTABLES3             003febdc   000000aa  00000000  000000aa  RWIX
  BOOTROM               003ff27c   00000d44  00000000  00000d44  RWIX
  RESET                 003fffc0   00000002  00000000  00000002  RWIX
  VECTORS               003fffc2   0000003e  00000000  0000003e  RWIX

PAGE 1:
  RAMM0                 00000050   000003b0  00000000  000003b0  RWIX
  RAMM1                 00000400   00000400  00000380  00000080  RWIX
  DEV_EMU               00000880   00000105  00000004  00000101  RWIX
  SYS_PWR_CTL           00000985   00000003  00000003  00000000  RWIX
  FLASH_REGS            00000a80   00000060  00000008  00000058  RWIX
  CSM                   00000ae0   00000010  00000010  00000000  RWIX
  ADC_RESULT            00000b00   00000020  00000020  00000000  RWIX
  CPU_TIMER0            00000c00   00000008  00000008  00000000  RWIX
  CPU_TIMER1            00000c08   00000008  00000008  00000000  RWIX
  CPU_TIMER2            00000c10   00000008  00000008  00000000  RWIX
  PIE_CTRL              00000ce0   00000020  0000001a  00000006  RWIX
  PIE_VECT              00000d00   00000100  00000100  00000000  RWIX
  COMP1                 00006400   00000020  00000014  0000000c  RWIX
  COMP2                 00006420   00000020  00000014  0000000c  RWIX
  EPWM1                 00006800   00000040  00000040  00000000  RWIX
  EPWM2                 00006840   00000040  00000040  00000000  RWIX
  EPWM3                 00006880   00000040  00000040  00000000  RWIX
  EPWM4                 000068c0   00000040  00000040  00000000  RWIX
  ECAP1                 00006a00   00000020  00000020  00000000  RWIX
  GPIOCTRL              00006f80   00000040  00000040  00000000  RWIX
  GPIODAT               00006fc0   00000020  00000020  00000000  RWIX
  GPIOINT               00006fe0   00000020  0000000a  00000016  RWIX
  SYSTEM                00007010   00000020  0000001f  00000001  RWIX
  SPIA                  00007040   00000010  00000010  00000000  RWIX
  SCIA                  00007050   00000010  00000010  00000000  RWIX
  NMIINTRUPT            00007060   00000010  00000010  00000000  RWIX
  XINTRUPT              00007070   00000010  00000010  00000000  RWIX
  ADC                   00007100   00000080  00000051  0000002f  RWIX
  I2CA                  00007900   00000040  00000022  0000001e  RWIX
  dataRAM               00008300   00000d00  0000029e  00000a62  RWIX
  PARTID                003d7fff   00000001  00000001  00000000  RWIX
  FLASHB                003f4000   00002000  00000000  00002000  RWIX
  CSM_PWL               003f7ff8   00000008  00000008  00000000  RWIX

0 user5277039 over 6 years ago in reply to MatthewPate

Intellectual 640 points

What is CCS flash?
I can use Uniflash.
I erase SectorA～D by using Uniflah.
But Sector A is all 0x0000

I show the map file below.
It looks like that FLASHA is deffrent.

MEMORY CONFIGURATION

         name            origin    length      used     unused   attr    fill
----------------------  --------  ---------  --------  --------  ----  --------
PAGE 0:
  BOOT_RSVD             00000000   00000050  00000000  00000050  RWIX
  progRAM               00008000   00000300  0000022e  000000d2  RWIX
  OTP                   003d7800   00000400  00000000  00000400  RWIX
  FLASHD                003f0000   00002000  00000000  00002000  RWIX
  FLASHC                003f2000   00002000  00000000  00002000  RWIX
  FLASHA                003f6000   00001f80  00001514  00000a6c  RWIX
  CSM_RSVD              003f7f80   00000076  00000000  00000076  RWIX
  BEGIN                 003f7ff6   00000002  00000002  00000000  RWIX
  CSM_PWL               003f7ff8   00000008  00000000  00000008  RWIX
  IQTABLES              003fe000   00000b50  00000000  00000b50  RWIX
  IQTABLES2             003feb50   0000008c  00000000  0000008c  RWIX
  IQTABLES3             003febdc   000000aa  00000000  000000aa  RWIX
  BOOTROM               003ff27c   00000d44  00000000  00000d44  RWIX
  RESET                 003fffc0   00000002  00000000  00000002  RWIX
  VECTORS               003fffc2   0000003e  00000000  0000003e  RWIX

PAGE 1:
  RAMM0                 00000050   000003b0  00000000  000003b0  RWIX
  RAMM1                 00000400   00000400  00000380  00000080  RWIX
  DEV_EMU               00000880   00000105  00000004  00000101  RWIX
  SYS_PWR_CTL           00000985   00000003  00000003  00000000  RWIX
  FLASH_REGS            00000a80   00000060  00000008  00000058  RWIX
  CSM                   00000ae0   00000010  00000010  00000000  RWIX
  ADC_RESULT            00000b00   00000020  00000020  00000000  RWIX
  CPU_TIMER0            00000c00   00000008  00000008  00000000  RWIX
  CPU_TIMER1            00000c08   00000008  00000008  00000000  RWIX
  CPU_TIMER2            00000c10   00000008  00000008  00000000  RWIX
  PIE_CTRL              00000ce0   00000020  0000001a  00000006  RWIX
  PIE_VECT              00000d00   00000100  00000100  00000000  RWIX
  COMP1                 00006400   00000020  00000011  0000000f  RWIX
  COMP2                 00006420   00000020  00000011  0000000f  RWIX
  EPWM1                 00006800   00000040  00000040  00000000  RWIX
  EPWM2                 00006840   00000040  00000040  00000000  RWIX
  EPWM3                 00006880   00000040  00000040  00000000  RWIX
  EPWM4                 000068c0   00000040  00000040  00000000  RWIX
  ECAP1                 00006a00   00000020  00000020  00000000  RWIX
  GPIOCTRL              00006f80   00000040  00000040  00000000  RWIX
  GPIODAT               00006fc0   00000020  00000020  00000000  RWIX
  GPIOINT               00006fe0   00000020  0000000a  00000016  RWIX
  SYSTEM                00007010   00000020  0000001f  00000001  RWIX
  SPIA                  00007040   00000010  00000010  00000000  RWIX
  SCIA                  00007050   00000010  00000010  00000000  RWIX
  NMIINTRUPT            00007060   00000010  00000010  00000000  RWIX
  XINTRUPT              00007070   00000010  00000010  00000000  RWIX
  ADC                   00007100   00000080  00000051  0000002f  RWIX
  I2CA                  00007900   00000040  00000022  0000001e  RWIX
  dataRAM               00008300   00000d00  0000029e  00000a62  RWIX
  PARTID                003d7fff   00000001  00000001  00000000  RWIX
  FLASHB                003f4000   00002000  00000000  00002000  RWIX
  CSM_PWL               003f7ff8   00000008  00000008  00000000  RWIX

0 MatthewPate over 6 years ago in reply to user5277039

TI__Guru* 80270 points

This is OK, there could be a slightly different compilation on your side either from a additional seciton or just a difference in compiler.

At any rate the flash is showing erased with Uniflash, so it is unlocked. Can you show the same Uniflash screen after you try and program the .out file for the HVPSB kit?

Best,
Matthew

0 user5277039 over 6 years ago in reply to MatthewPate

Intellectual 640 points

I try load and verify using Uniflash.

When load

When verify

memory mop around 0x3F73CE

0 MatthewPate over 6 years ago in reply to user5277039

TI__Guru* 80270 points

I would like to try depletion recovery to see if that is an issue. Go ahead and re-erase the flash, and then run depletion recovery(should be a button for that if you scroll down in the UniFlash window) and try to program the device again and see if there is any difference.

Can you confirm the Clock Configuration settings in Uniflash as well?

Finally, I know we have checked the decoupling caps near the device for correct values; given that the board had a over-voltage event do you see any physical signs of stress to any of those caps(on the 3.3V and 1.8V supplies of the MCU), burn marks or otherwise.

Best,
Matthew

0 user5277039 over 6 years ago in reply to MatthewPate

Intellectual 640 points

It occur problem.

Suddenly,I can't erase flash by uniflash and CCS.

0 user5277039 over 6 years ago in reply to user5277039

Intellectual 640 points

Sorry

I can erase flash and depletion recovery.

But when I try load and verify program after depletion recovery,

same error occur.

Clock Configuration settings is below

I checked C1,C2,C3,C4,C5 caps.

All of then no problem.

0 MatthewPate over 6 years ago in reply to user5277039

TI__Guru* 80270 points

I don't have a good explanation why the device is not reliably writing and intermittantly erasing its flash. I would suspect some inconsistencies in either the flash power on the chip, but we don't see any evidence of that occuring.

I'd like to try and re-compile the project and change the location the linker file is allocating for the program code.

I've attached a modified .cmd moving the program to sector C, if this doesn't work you can try sector D as well.

At this point if we can get the code to load the and run, you can continue to evaluate the kit.

Please replace the exisiting .cmd with the one attached and let's see if the flash will load properly.

Best,

Matthewhttps://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/171/F28027_5F00_FLASH_5F00_HVPSFB_5F00_FC.CMD

0 user5277039 over 6 years ago in reply to MatthewPate

Intellectual 640 points

I tried attached CMD file but can't load.

error is same.

I change attached CMD file to sector D but failded.

0 MatthewPate over 6 years ago in reply to user5277039

TI__Guru* 80270 points

At this point we should try and replace the MCU again. I can't explain why the device would function/connect but the flash will not program correctly, other than the device has been damaged. If you need more samples I can assist with that as well.

Best,

Matthew

0 MatthewPate over 6 years ago in reply to MatthewPate

TI__Guru* 80270 points

Checking back in to see if you were able to get device samples to replace the MCU on the PCB.

Best regards,
Matthew

0 MatthewPate over 6 years ago in reply to MatthewPate

TI__Guru* 80270 points

After researching internally quite a bit, I think your new problem of not being able to program the flash may be related to a known issue with the conroller card design, vs any damage that was done.

If you look near the F2802x MCU there are 2 inductors, L1 and L2, inline with the 3.3V power rail. Based on some previous design notes I think these may be limting the current draw of the MCU, and flash programming operation is usually the peak current need for this device.

Can you place a 0 Ohm resistor on top(in parallel) with each inductor and see if we can get the device to program.

Thanks for your patience in debugging this kit, hopefully this may resolve the issue.

Best,
Matthew

0 user5277039 over 6 years ago in reply to MatthewPate

Intellectual 640 points

Thank you for your long time support.

When I place 0 Orm resistor with L1 inductor,

I can program.

There are several questions.

・What is the cause of this breakdown?

・Isn't there a problem in operation even while placing this 0 Orm resistor?

0 MatthewPate over 6 years ago in reply to user5277039

TI__Guru* 80270 points

I'm glad the device now programs with this change.

The inductors are there as a best practice to limit noise from the system coming into the device via the power rails.

I beleive the issue is that the inductors chosen for this PCB have too much series resistance and limit the current into the device from the LDO. Most/all operations are OK with this reduced current, but flash programming is not due to its current/power needs during the program function only.

As this is best practice there should be no issue in operation of the kit with the 0 ohm in series.

Best,

Matthew

C2000™︎ microcontrollers

C2000 microcontrollers forum

CCS/TMS320F28027: TMS320F28027 HVPSFB development kit cannot debug