S9KEAZN8AMTG not erasing. Time out Failure during flash

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

S9KEAZN8AMTG not erasing. Time out Failure during flash

4,781 Views
Vertex
Contributor I

This is the first time that I have tried using KEA8 controller. Using CW 10.6.4. Trying to flash a simple looping toggle output pin program to test flash. I keep getting the following:

fl::target -lc "KEA8Test_FLASH_PnE U-MultiLink"
fl::target -b 0x1fffff00 0x400
fl::target -v off -l off
cmdwin::fl::device -d "FTMRE_PFlash8RAM1" -o "2kx32x1" -a 0x0 0x1fff
cmdwin::fl::erase all
 Beginning Operation ...   
-------------------------
Performing target initialization ...   
Device FTMRE_PFlash8RAM1   
 Erasing .............
Error:  Erase Command Failed.  Operation timeout.
Device FTMRE_PFlash8RAM1   
Error: Erase Command Failed.Operation timeout.

I am trying to replace a QG8 TSSOP-16 3.3V controller with this S9KEAZN8AMTG TSSOP-16 5V controller. I rearranged programming header to accept SWD. It looks like the controller is found and I can see activity on Reset, DIO and CLK pins but I keep getting the above message. Any further guidance would be appreciated. 

Thank you,

Chad

0 Kudos
Reply
8 Replies

4,544 Views
Vertex
Contributor I

Hi Alice,

  I greatly appreciate your help. I ordered a PT8 controller and installed it over the weekend. It was easy to flash and the application is up and running. It is a custom board application. I tried changing boards, PC and programmer trying to get the KEA8 up and running and just couldn't get it to work. My application is due next week and I just needed to find a solution and move on. Thank you again for your help and support.

BR,

Chad

0 Kudos
Reply

4,544 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hi Chad,

There are some possible cause for this problem.

- The object file, please change to another object file to have a try, if still can't work, please send the file to me.

- The debugger , could you please change to another debugger to test. About the debug log , I recommend you can

also  sent  it to the P&E support :  PEmicro - P&E Microcomputer Systems: Over 30 years as an Industry leader in Embedded Systems Develop...  they can help to analysis whether there is problem on you debugger.

- If not the above two, I think maybe some problem on your board ,  I use the same debugger Multilink Universal Rev C,

Win7 PC, TRK-KEA8 board, it can work well .

BR

Alice

0 Kudos
Reply

4,544 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello Chad,

Does your board is demo board or custom board ? Can you use another board to test ?

If it is a custom board, please refer to the demo board  schematic on NXP to check the hardware, and

also use another IDE to have a try.

And what about the system of your PC , can you change another PC to have try .

BR

Alice

0 Kudos
Reply

4,544 Views
Vertex
Contributor I

Hi Alice,

  I have verified the items that you have highlighted and recommended. They all look like your version except for a detail.

"Port: USB1: Multilink Universal Rev C (PEMA 19540)" the PEMA 19540 is different and no "FAQ #29".

Verified that Target Type is KEAZN8M4. I keep getting the following:

INF: CMD>RE
INF: Initializing.
INF: Target has been RESET and is active.
INF: CMD>CM C:\Freescale\CW MCU v10.6.4\MCU\bin\Plugins\support\arm\gdi\P&E\freescale_keazn8m4_pflash.arp
INF: Initializing.
INF: Initialized.
INF: ;version 1.00, 07/19/2013, Copyright 2013 P&E Microcomputer Systems, Inc. All rights reserved. www.pemicro.com [ke_8k_pflash_m0]
INF: ;device freescale, keazn8m4, pflash
INF: ;begin_cs device=$00000000, length=$00002000, ram=$20000000
INF: Loading programming algorithm ...
INF: WARNING - Selected .ARP file has been modified. CRC16 = $C20A
INF: Done.
INF: CMD>EM
INF: Erasing.
INF: Module has been erased.
INF: Reloading programming algorithm ...
INF: done.
INF: CMD>PM
INF: Programming.
INF: Processing Object File Data ...
INF: Error during programming.
ERR: Error Programming flash of device
ERR: Error occured during Flash programming.

I shortened the programming ribbon cable and soldered the connections to my board. I'm still getting o-scope traces for Reset, DIO and CLK. I also created a new bare board project with simple toggle output code and tried to flash with no success. I also downloaded the current versions of the .arp files from PE and replaced the old

"freescale_keazn8m4_pflash.arp" file with a fresh version with no success (just in case it was corrupt).

I don't think that it should be this difficult? I must be missing something simple? Thank you very much for your assistance and thank you for any further assistance.

BR,

Chad

0 Kudos
Reply

4,544 Views
Vertex
Contributor I

Hi Alice,

   I read the document and I could not find a place where my CW debug setup was different from the recommended setup in the document. It looks almost identical except for the file names and my controller requires the SWD reduced pin protocol. I compared my Flash Task with the default Task for my controller and it was set up the same except for the path to file name. When I press "Debug" from the Debug Configurations dialog box, it fails and reports the following in the Console:

INF: Initialized.
INF: ;version 1.00, 07/19/2013, Copyright P&E Microcomputer Systems, www.pemicro.com [ke_8k_pflash_m0]
INF: ;device freescale, keazn8m4, pflash
INF: ;begin_cs device=$00000000, length=$00002000, ram=$20000000
INF: Loading programming algorithm ...
INF: Done.
INF: CMD>EM
INF: Erasing.
INF: Module has been erased.
INF: Reloading programming algorithm ...
INF: done.
INF: CMD>PM
INF: Programming.
INF: Processing Object File Data ...
INF: Error during programming.
ERR: Error Programming flash of device
ERR: Error occured during Flash programming.

I ran the update firmware function for the PE Multilink Universal (not FX) and it updated. I retried the task and it failed again with same results. I also tried reducing the speed of communications to .1MHz to see if slowing it down helped (unsuccessful). Thank you for any further assistance.

BR,

Chad

0 Kudos
Reply

4,544 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello Chad,

1. On the debug configuration , please check these place:

pastedImage_1.png

pastedImage_2.png

2.

From the log of console , it seems the board and debugger have connected correctly, it has erased:

INF: Module has been erased.

so please change to a new workspace, and create a new simple project, try to debug it .

3. Also check the program algorithm in console view :

pastedImage_4.png

BR

Alice

0 Kudos
Reply

4,544 Views
Vertex
Contributor I

Hi Alice,

  Thank you very much for responding! I really don't know much about the actual debugging mode. I have always been able to simply select "Flash Programmer" in CW to flash the microcontroller used in my application. I forgot to add that I'm using a PE Multilink Universal (blue) as my interface. I will definitely read your attached document for its content and will respond after reading the document and applying things that I can try. Thank you very much!

0 Kudos
Reply

4,540 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello Chad,

Does it can debug ?  Which debug mode do you used ?

About the debug configuration , please refer to "Targeting_Microcontrollers.pdf"-> chapter 4 Working with Debugger.

BR

Alice

0 Kudos
Reply