15: Target error from Commit Flash write: Et: Flash driver not ready.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by maxmel on Fri Jun 10 03:02:32 MST 2011
hello,

i have for thr first time the following message on my board LPC1768
15: Target error from Commit Flash write: Et: Flash driver not ready.
i have use an external power but i have always the same problem

please could you help me ?

thank you

lpcware · ‎06-15-2016

Content originally posted in LPCWare by alexism on Sun Feb 09 13:23:36 MST 2014
For me worked to connect ISP pin (P0.1) to GND, next enter debug mode and so float ISP pin.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by magicdim on Thu Jan 17 05:03:45 MST 2013

Quote: CodeRedSupport
Unless you fix the problem in Example4, then it will happen every time

Even reprogramming with another and safe image???
So from the moment it happens we won't be able to avoid it anymore, why?

Example1,2,3,4 are examples given in the FreeRTOS learning package, they print out a string to the console whether Task1 or Task2 is processing, according to their priority.
The only difference is that Example4 uses "vTaskDelay( 250 / portTICK_RATE_MS )" which allow the tasks to be in a "blocked" state instead of a crude delay loop.

Otherwise, as the trouble can come from USB power supply, I tried a lot of port configuration with my external USB hard disk, but apparently the problem is fixed with LPCXpresso v5.0.14 Build 1109, so I hope this problem will never come again.

The only trouble I have been able to remark is that sometimes the image is not correctly downloaded to the Flash, so the previously downloaded program hasn't been replaced by the new one and is still running...pointing to the main.c file of the new program!:confused:
Anyway, this small inconvenience can be fixed launching debug/reprogramming a second time!

Hope all this helps!

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Thu Jan 17 03:13:04 MST 2013
Unless you fix the problem in Example4, then it will happen every time. We would be interested to know what Example4 is doing to prevent 'normal' debug connection.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by magicdim on Wed Jan 16 11:01:19 MST 2013
OK, thanks for the explanation!

This occured when I downloaded a project (let's call it Example4) to the Flash, whereas everything was alright with Example1,2,3, so I think I was in the "The image contains code that sets the MCU clocks up "incorrectly"" case.

I tried to enable Vector Catch then disable it which fixed the problem, but I had to do it again after each USB cable disconnection, or after each PC reboot even reprogramming with Example1,2 or 3
==>[U] Is it normal or Can this case cause problem such as [I]"the part ID being incorrectly read[/I]" ??? [/U]

I thought that enabling then disabling Vector Catch only once could fix the problem forever, but apparently not?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Wed Jan 16 10:31:07 MST 2013
Vector Catch modifies the way that the debugger connects to the MCU and can have different behavior depending on the target MCU, as each has different recovery methods.

We normally only recommend using Vector Catch when having connection issues. It is not 'dangerous' in any way, but we do not recommend leaving it switched on.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by magicdim on Wed Jan 16 04:02:59 MST 2013
Hi everybody!

I have few questions to CodeRedSupport...

I am using LPCXpresso1769 borad alone (without baseboard), with LPCXpresso v5.0.14 Build 1109 under windows7 on my laptop.

Now I upgraded to LPCXpresso v5.0.14 Build 1109 it works fine, but...

When I used the LPCXpresso v5.0.12 Build 1083 I got, as for most LPCXpresso users, that "15: Target error from Commit Flash write: Et: Flash driver not ready." error.

I had to to "cheat" with ISP or Catch Vector [B]EVERYTIME [/B]I disconnected the USB LPC-Link, even reprogramming the Flash with a program which was debugging normally before
So, I can remark that once a program which turns wrong the debug system is put in the Flash, it will turn it wrong [B]FOREVER[/B], [U]by which way can you explain that?[/U]

Also, at http://support.code-red-tech.com/CodeRedWiki/DebugAccessChip, you warn us that "[I]once you have recovered debug access to your MCU, then in most cases you should then modify your Debug Configuration to turn vector catch off again[/I]"

[U]OK, so is it also "dangerous" if I do it everytime I disconnect the USB LPC-Link, but turn it off after the problem fixed?[/U]

I hope I'm clear enough, and I just ask these questions as I am affraid it does it again with LPCXpresso v5.0.14 Build 1109!

Thanks in advance for your answers!

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Tue Jun 14 03:28:01 MST 2011

Quote: maxmel

what is the meaning of "vector catch " because it's working very well now

Vector catch is some logic within the debug hardware of the Cortex-M3, which can be used to stop execution when a vector event takes places - in this case reset. Normally the debugger can gain control of an LPC17 system without needing to use this logic. But in this case, that appears not to have been the case.

Regards,
CodeRedSupport

lpcware · ‎06-15-2016

Content originally posted in LPCWare by maxmel on Tue Jun 14 01:05:55 MST 2011
hi,

what is the meaning of "vector catch " because it's working very well now

thank you

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Ex-Zero on Sun Jun 12 13:13:35 MST 2011
'PIO0_1' label is just too boring :mad:

And now you know that this pin can be used as GPIO or USB_FTOGGLE :)

lpcware · ‎06-15-2016

Content originally posted in LPCWare by LRF on Sun Jun 12 12:59:22 MST 2011

Quote:
marked on the board itself as "FT/GPIO"

Thanks Zero, however you would have thought NXP would have labeled it as such.
By the way any idea what "FT/GPIO" actually stands for?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Ex-Zero on Sun Jun 12 11:22:37 MST 2011
Yes, it's PIO0_1 :)

See:
http://support.code-red-tech.com/CodeRedWiki/DebugAccessChip

lpcware · ‎06-15-2016

Content originally posted in LPCWare by LRF on Sun Jun 12 11:18:21 MST 2011

Quote:
Have you tried booting into ISP before connecting

Please confirm that the ISP pin of the LPC1343 is pin #4 and that this pin on the LPCXpresso board is pin #J6-38 which is actually marked on the board itself as "FT/GPIO"?
If I am not correct then which pin is the ISP pin?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by maxmel on Fri Jun 10 06:17:56 MST 2011
i have tried with the vector catch and it s working

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Fri Jun 10 06:13:53 MST 2011

Quote: maxmel
[FONT=Georgia][/FONT][FONT=Georgia]
- Have you been able to connect to your board successfully in the past via LPCXpresso? If so, what has changed since you were able to - source code, hardware, computer OS, version of LPCXpresso IDE, etc ??

yes it's the MC1700 of keil I have 2 boards with the same problem

So have you ever been able to connect to these board successfully using LPCXpresso ????????????

Quote:

- Have you tried booting into ISP before connecting, or connecting with vector catch set, as mentioned by Zero, and described at:

[COLOR=#5174a3]http://support.code-red-tech.com/Cod...ebugAccessChip[/COLOR]

ii have tried with µVision and it's working well
[/FONT]

It is nice to know that it works with uVision. But that doesn't answer the question.
Have you tried using the ISP and vector catch mechanisms with LPCXpresso ????? Do either of these allow successful LPCXpresso connections?????

Regards,
CodeRedSupport

lpcware · ‎06-15-2016

Content originally posted in LPCWare by maxmel on Fri Jun 10 05:40:19 MST 2011
[FONT=Georgia]As stated in the FAQ...

[COLOR=#5174a3]http://support.code-red-tech.com/Cod...mmitFlashWrite[/COLOR]

power is the "normal" cause of seeing this problem. But it is possible for it to be provoked by other things.

If you want any real help, then you really need to provide more information.

- What version of LPCXpresso are you using? If you are using a version earlier than 3.6.3 (Windows) or 3.8.3 (Linux), I would suggest downloading the latest version.
i have the 3.6.3 (Windows) [/FONT]
[FONT=Georgia]
- Have you been able to connect to your board successfully in the past via LPCXpresso? If so, what has changed since you were able to - source code, hardware, computer OS, version of LPCXpresso IDE, etc ??

yes it's the MC1700 of keil I have 2 boards with the same problem

- Have you tried booting into ISP before connecting, or connecting with vector catch set, as mentioned by Zero, and described at:

[COLOR=#5174a3]http://support.code-red-tech.com/Cod...ebugAccessChip[/COLOR]

ii have tried with µVision and it's working well

- Check your hardware, in particular power, reset and debug circuitry.
i have use an external or via usb

thank you for your help
[/FONT][FONT=Courier][SIZE=2][FONT=Courier][SIZE=2][/SIZE][/FONT][/SIZE][/FONT]

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Fri Jun 10 05:13:15 MST 2011
As stated in the FAQ...

http://support.code-red-tech.com/CodeRedWiki/CommitFlashWrite

power is the "normal" cause of seeing this problem. But it is possible for it to be provoked by other things.

If you want any real help, then you really need to provide more information.

- What version of LPCXpresso are you using? If you are using a version earlier than 3.6.3 (Windows) or 3.8.3 (Linux), I would suggest downloading the latest version.

- Have you been able to connect to your board successfully in the past via LPCXpresso? If so, what has changed since you were able to - source code, hardware, computer OS, version of LPCXpresso IDE, etc ??

- Have you tried booting into ISP before connecting, or connecting with vector catch set, as mentioned by Zero, and described at:

http://support.code-red-tech.com/CodeRedWiki/DebugAccessChip

- Check your hardware, in particular power, reset and debug circuitry.

It might also be worth you going through some of the previous threads that mention this error....

http://lmgtfy.com/?q=%2215%3A+Target+error+from+Commit+Flash%22+site%3Aknowledgebase.nxp.com

Regards,
CodeRedSupport.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by maxmel on Fri Jun 10 04:50:55 MST 2011
i did a flash reset with keil and the ulink2 its working better.
but somes times i found agiain the error

lpcware · ‎06-15-2016

Content originally posted in LPCWare by maxmel on Fri Jun 10 03:12:52 MST 2011
it s working with keil but not with lpcxpresso

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Ex-Zero on Fri Jun 10 03:07:05 MST 2011
Did you try ISP and Vector catch ON?

http://support.code-red-tech.com/CodeRedWiki/DebugAccessChip