CodeWarrior Development Tools中的主题 Re: MK20DX256VLH7 locked/problems mass erasing

MK20DX256VLH7 locked/problems mass erasing

mariogongora — Fri, 20 Nov 2015 18:53:31 GMT

Hi everybody, I am developing my own k20 board specifically with mk20dx256vlh7, my problem is that I have already mass erased 2 chips ( first to do before debug and program), but I must have erase (and program) 4 more, I am doing same process as 2 I have already erased but without good results with 4 chips.

By reading posts and documentation I know that maybe it's a registers issue, but cartainly this is a new issue for me.

I am using PE micro multilink universal, SWD/JTAG configurations, IDE Code Warrior.

I have:

Reset_b: 10K pull up

Ez_port: 10K pull up

DIO: 10K pull up

CLK: 10K pull down + capacitor 1000pF pull down

I followed above circuit recommendations from other posts and datasheets from freescale.

I attach some print screens of my process:

I am really concerned about this, cause I can't explain how it's possible that I have succes with 2 chips (both configurations SWD and JTAG) but no with other.

I hope you can help me with this.

Thanks so much.

Re: MK20DX256VLH7 locked/problems mass erasing

trytohelp — Tue, 24 Nov 2015 15:22:33 GMT

Hi Mario,

May be it's another problem.

I think you're using CW for MCU v10.6.

We released several patches (updates) for this version which are:

- Update 1.0

- Update 2.0

- Update 3.0

We've a problem with the Update 3.0 and Muliltink interface.

In May the MCU V10.6.4 was released.

This is not a patch but a new release and must be installed in new folder.

Please can you have a look to the link:

Problem with Multilink Rev C - not running after MCU V10.6 Update3 installed & CW for MCF V7.2

Have a great day,
Pascal
Freescale Technical Support
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: MK20DX256VLH7 locked/problems mass erasing

mariogongora — Tue, 24 Nov 2015 16:32:04 GMT

Hi Pascal, Thanks for your response.

I am using CW for MCU v10.6.4, Multilink universal Rev C, and it works perfect to mass erase and program 2 of my k20 chips. The problem is when I try to do the same with other 4, It appears that "The Debugger can not connect to the P&E Device"

I already have installed the P&E micro update and stills working with my 2 erased chips, but no with other.

Thanks for the supporting!

Re: MK20DX256VLH7 locked/problems mass erasing

trytohelp — Wed, 25 Nov 2015 10:50:35 GMT

Mario,

Using the same tools and hardware configuration you can flash the project on 2 devices without problem but not on other devices.

It seems you tried the Flash File to Target and launching a debug session.

In both case you can not load the application on board.

As it's working with other device the Multilink Universal interface is working fine (driver installed correctly).

Is there a difference between the working and not working device ?

Do you use the same board and just change the chip ?

Or is it 2 boards (I mean 1 for each chip) ?

- same devices are used for boards ?

- same mk20dx256vlh7 chip ? Check the mask

Can you try with a generic example created with the wizard (File + NEW) ?

Can you load the sample code on board ?

Can you try to keep the Multilink plugged on your PC but not connected on the board ?

is it same error message ?

Re: MK20DX256VLH7 locked/problems mass erasing

mariogongora — Wed, 25 Nov 2015 18:39:34 GMT

Pascal,

I have differents boards for each chip(6 in total), first one is a pcb hand made by myself, all others were donde by machine (exactly the same), but unfortunately just 1 works, so I can deduce circuit is ok.

I have tried creating a New+File+ new bareboard project (no code just in blank), but stills failing.

executing flash file to target I obtain the following

Error executing task K20DX256M7.

Error: Connect Failed.

Can't connect. The Debugger can not connect to the P&E device(ARM GDI Protocol Adapter)

Error: Connect Failed.

Trying to load program to the board I obtain:

Error launching prueba_2_FLASH_PnE U-MultiLink

ARM GDI Protocol Adapter : Can't connect. The Debugger can not connect to the P&E device

Keeping Multilink plugged to PC and disconnecting board I get same errors showed above.

What else can I do?

Thank you very much for your supporting.

Re: MK20DX256VLH7 locked/problems mass erasing

mariogongora — Wed, 25 Nov 2015 22:17:12 GMT

Just to be more clear, hand made pcb works great, the others (machine manufcturing) just 1 works.

Thank you!!

Mario.

Re: MK20DX256VLH7 locked/problems mass erasing

trytohelp — Thu, 26 Nov 2015 13:54:32 GMT

Hi Mario,

Difficult to say what is the problem.

The first, and most easy answer will be there is a problem with boards.

If same PC, application, interface is working on some board and not on other boards, it will have sens to say the problem is on boards side.

The Flash Programmer and the Debugger are not using the same "flash application".

I don't think there is a problem linked to the Flash features else I would expect 1 working solution.

As the problem appears on both features I think you should search the cause of the problem in another direction.

In both case the same interface configuration is used.

Please can you enable to log generation for P&E interface ?

Now can you try to launch debug session when the working board is plugged and when not working board is plugged.

On my side with the TWR-K20D72M board I see:

+++++++++++++++++++++++++++++++++

GDI: DiExecStop()

GDI: => DI_OK

GDI: DiMeeDisconnect(exec_env_id = 1)

GDI: => DI_OK

GDI: DiGdiClose()

GDI: => DI_OK

=== CodeWarrior GDI protocol log ===

GDI DLL: E:\Freescale\CW MCU v10.6.4\MCU\bin\Plugins\Debugger\protocols\..\..\support\arm\gdi\arm_pne_gdi.dll

CPU: K20DX256M7

GDI: DiGdiOpen()

GDI: => DI_OK

GDI: DiGdiGetFeatures()

GDI: => DI_OK

GDI: Identification: ARM Cortex M4 P&E to GDI wrapper, Version: 1.0.1, MeeAvailable: true, NrCpusAvailable: 1

GDI: DiGdiAddCallBack(cb_type = 0x4000)

GDI: => DI_OK

....

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : CPUTARGETTYPENAME, Value : , R) => DI_ERR_NONFATAL

INF: P&E Interface detected - Flash Version 6.15

INF: Device is K20DX256M7.

INF: Mode is In-Circuit Debug.

GDI: => DI_OK

GDI: DiMeeConnect(exec_env_id = 1)

GDI: => DI_OK

GDI: DiExecResetChild()

INF: CPU reset by debugger.

GDI: => DI_OK

....

+++++++++++++++++++++++++++++++++

Re: MK20DX256VLH7 locked/problems mass erasing

mariogongora — Sat, 28 Nov 2015 17:54:16 GMT

Hi Pascal,

Yes, I know this is difficult and really weird, I can't find explanation about this.

I have tried what you comment, enabling logging, but I get same error, The debugger cannto connect to the P&E device, The problem doesn't allow even to connect with target. As you, I'm beginning to think that there is a problem with the board.

Do you have any recommendation to add, replace or remove to my circuit?

I have:

All VDD-3.3 V

All GND-GND

Reset_b: 10K pull up

Ez_port: 10K pull up

DIO: 10K pull up

CLK: 10K pull down + capacitor 1000pF pull down

I'm not using crystal.

Thanks for your support.

Mario

Re: MK20DX256VLH7 locked/problems mass erasing

trytohelp — Mon, 30 Nov 2015 10:32:07 GMT

Hi Mario,

I'm not Hardware expert so I can not give you recommendation for your board.

Now this morning I've just performed another test with my demo board.

As explained in my previous post I can flash the code on board without problem.

Now I tried to flash (launch debug) it when the board power is down.

I got similar dialog saying:

Extract of Multilink Console Dialog:

+++++++++++++++++++++++++

=== CodeWarrior GDI protocol log ===

GDI DLL: E:\Freescale\CW MCU v10.6.4\MCU\bin\Plugins\Debugger\protocols\..\..\support\arm\gdi\arm_pne_gdi.dll

CPU: K20DX256M7

GDI: DiGdiOpen()

GDI: => DI_OK

GDI: DiGdiGetFeatures()

GDI: => DI_OK

GDI: Identification: ARM Cortex M4 P&E to GDI wrapper, Version: 1.0.1, MeeAvailable: true, NrCpusAvailable: 1

GDI: DiGdiAddCallBack(cb_type = 0x4000)

GDI: => DI_OK

GDI: DiGdiInitIO()

GDI: Mtwks Callback(MTWKS_CB_SETMEEID, 1) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : DO_DEBUG_OUTPUT, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : DEPENDENCY_CHECK, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : UUID, Value : DefaultProject, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : CWDBG, Entry : Processor, Value : K20DX256M7, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : ERASE_PROGRAM_WITHOUT_ASKING, Value : 0, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : AUTO_SYNC, Value : 1, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : DOTRIM, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : CURRENT_ALGORITHM_INDEX, Value : 0, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : PRESERVE1_START, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : PRESERVE1_END, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : PRESERVE1_ACTIVE, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : PRESERVE2_START, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : PRESERVE2_END, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : PRESERVE2_ACTIVE, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : PRESERVE3_START, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : PRESERVE3_END, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : PRESERVE3_ACTIVE, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : K20DX256M7, Entry : PRESERVE_EEPROM_START, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : K20DX256M7, Entry : PRESERVE_EEPROM_END, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : K20DX256M7, Entry : PRESERVE_EEPROM, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : ALTERNATIVE_ALGORITHM_PATH, Value : , R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : ALTERNATIVE_ALGORITHM_CHECKBOX, Value : 0, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : PARTITION_PARAM, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : DO_PARTITIONING, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : CUSTOM_TRIM, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : K20DX256M7, Entry : TRIM_VALUE, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : NGS_TRIM_OVERRIDE_REFERENCE_FREQUENCY, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : PEDEBUG, Entry : ENABLE_FLASH_PROGRAMMING_DIALOG, Value : 0, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : SCRIPTFILE, Entry : RUN_RESET_SCRIPT_FILE, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : SCRIPTFILE, Entry : RESET_SCRIPT_FILE, Value : E:\Freescale\CW MCU v10.6.4\MCU\bin\Plugins\support\arm\gdi\P&E\resetscript.mac, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : SCRIPTFILE, Entry : RESET_SCRIPT_FILE_RUN_MODE, Value : 1, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : SPECIFY_NETWORKCARD_ENABLED, Value : 0, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : jtag_numbits_pre_ir, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : jtag_tap_num, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : jtag_use_daisy_chain, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : user_specified_daisy_chain, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : IO_DELAY_CNT, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP12, Entry : show_hstep_assembly_details, Value : 0, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : CWDBG, Entry : Connect, Value : 0, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : eclipse_show_connection_assistant, Value : 1, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : FREQ_FX, Value : 4, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : FREQ_NORMAL, Value : 0, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : FREQ_OSJTAG, Value : 0, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : FREQ_CYCLONE, Value : 3, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : FREQ_TRACELINK, Value : 3, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : FREQ_LIGHTNING, Value : 1, R) => DI_ERR_NONFATAL

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : FREQ_OPENSDA, Value : 0, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : RESET_DELAY, Value : 0, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : PORT, Value : 21, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : PORT_NAME_STRING, Value : PE5656229, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : interface_selection, Value : 1, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : USE_CYCLONEPRO_RELAYS, Value : 0, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : CyclonePro_poweroffonexit, Value : 0, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : CyclonePro_currentvoltage, Value : 128, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : CyclonePro_PowerDownDelay, Value : 250, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : CyclonePro_PowerUpDelay, Value : 250, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : Multilink_PowerUpDelay, Value : 1000, R) => DI_OK

GDI: Mtwks Callback(MTWKS_CB_PROJECTACCESS, Section : STARTUP, Entry : Multilink_PowerDownDelay, Value : 250, R) => DI_OK