Flash driver not ready

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

Flash driver not ready

1,108 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by Marco72 on Thu Nov 24 23:04:25 MST 2011
Ciao

I have a problem with my LPCXpresso LPC1769 and I hope someone can gently help me:

The unit worked for a month without problems, and was working the day before this problem appear. I had my problem at the beginning of a develop session and not after a modification of system.

When I launch debug, after build and some other connecting message I had an error window with this message:
15: Target error from Commit Flash write: Et: Flash driver not ready.

On console window some message flows but unfortunately they are cleared at the end when the error appear.

These are the steps that I made to try to recover
enlarging timeout editing scripts in debugger config
power cycle everything

I made also an attempt to just program the flash and this end to an error window:
05: File 'my_prog.axf' load failure: Et: Flash driver not ready

Enabling log i have this messages:
Pc: (  0) Reading remote configuration
Ni: LPCXpresso Debug Driver v4.0 (Jun 21 2011 23:10:14)
Nc: Looked for chip XML file in C:/nxp/LPCXpresso_4.0.5_123/lpcxpresso/bin/LPC1769.xml

Nc: Looked for vendor directory XML file in C:/nxp/LPCXpresso_4.0.5_123/lpcxpresso/bin/nxp_directory.xml

Nc: Found generic directory XML file in C:/nxp/LPCXpresso_4.0.5_123/lpcxpresso/bin/crt_directory.xml

Pc: (  5) Remote configuration complete
Pc: ( 30) Emulator Connected
Pc: ( 40) Debug Halt
Pc: ( 50) CPU ID
Nc: Emu(0): Conn&Reset. DpID: 2BA01477. Info: T1S6RGRIA
Nc: SWD Frequency: 250 KHz. RTCK: False. Vector catch: False.
Nc: Packet delay: 0  Poll delay: 0.
Nc: NXP: LPC1769  Part ID: 0x00000000
Pc: ( 65) Chip Setup Complete
Nt: Connected: was_reset=false. was_stopped=true
Cr:v Registered license, download limit of 128K
Pc: ( 70) License Check Complete
Nt: Loading ELF file 'my_prog.axf' at location 00000000
Nt: Writing 34616 bytes to 0000 in Flash (assumed clock: 4.0MHz)
Pb: 1 of 2 (  0) Writing pages 0-7 at 0x00000000 with 32768 bytes
Pb: (100) Writing Flash ended with an error.
Ed:05: File 'my_prog.axf' load failure: Et: Flash driver not ready.

Pc: (100) Target Connection Failed


When all is working I remember a message in console or status bar about the assumed clock was 100.0MHz now I see 4.0MHz is here the problem ? Where this option can be changed ?

Thank you in advance

Marco
0 Kudos
Reply
4 Replies

1,084 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by Marco72 on Sat Nov 26 04:11:36 MST 2011
As suggested I enabled vector catch and regained flash programming, after this I disabled vector catch and micro remain working.

I didn't made any further steps suggested because this first worked for me.
I will keep these other suggestion saved for the future.

Wonderful! I am again on the road.

Thank you everybody.
0 Kudos
Reply

1,084 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by SteveClevenger on Fri Nov 25 01:20:38 MST 2011
As a first step, try starting the debug session with vector catch enabled in the Debug Configuration. From the console display, it appears the flash program succeeded, but a reset issue is preventing LPCXpresso from running your code.
0 Kudos
Reply

1,084 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by mhjerde on Fri Nov 25 00:13:55 MST 2011
Hi
I've had the same problem for a while.
I'm using a probe, not the LPC link. What I do is turn off power to the board, wait until it tries to flash the device (it shows "set timeout 6000") and then turn power back on.

If I start a debugging session when the board hangs on a breakpoint, reflashing is never a problem.

Figuring out this has been on my todo list for a while, but so has a ton of actual coding :-)

Do you have anything connected to the ISP pin?
0 Kudos
Reply

1,084 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by Ex-Zero on Thu Nov 24 23:53:21 MST 2011
First of all I would always suggest to switch vector catch on and switch in ISP mode :)

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

It's not unusual that a board refuses to work, but in general switching to ISP solves this problem.

If that fails, there's also a description about this error in:

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