15: Target error from Commit Flash write: Ef(34): Timed-out initializing flash

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

15: Target error from Commit Flash write: Ef(34): Timed-out initializing flash

3,719 Views
rnb
Contributor II

Running LPCXpresso 8.1.4 on W10-1607.

Same above error appear on 2 developpment boards when I tried to download a new project to implement IAP

I used NXP AN11071 application note as a start base of developpment.

I had control on the boards before  (LPCXpresso) with the previous project but error appeared after the first download of IAP project. First download went well but issue start with the second download. I then realized I omit to change the CPU type in the IAP project.

I've tried both ISP and Vector catch method without success.

Anything else i can try ?

Labels (1)
Tags (1)
0 Kudos
Reply
6 Replies

2,169 Views
lpcxpresso_supp
NXP Employee
NXP Employee

So it certainly looks like the code already loaded into flash is causing a fault before the debugger can take control. Try booting into ISP mode again - and make sure that you follow the process correctly ...

  1. GND the ISP pin
  2. With ISP still pulled to GND, assert RST and release RST
  3. Now remove the GND to ISP pin, and start your debug session

It would also be worth trying a more recently version of LPCXpresso IDE. v8.2.x does contain some improvements that can help in this sort of situation. You can have both your current and the latest versions of the IDE installed at the same time.

Regards,

LPCXpresso Support

0 Kudos
Reply

2,169 Views
rnb
Contributor II

Ok, Thanks for your help.

Regards

René

0 Kudos
Reply

2,169 Views
lpcxpresso_supp
NXP Employee
NXP Employee

It does sound like you need to be booting into ISP mode: Regaining debug access to target MCU. What exactly did you do to try to do this on your board?

And what is your board and your target MCU? And can you clarify what you mean by "omit to change the CPU type"?

Also what debug probe are you using? And can you post the whole debug log? The Debug Log 

Finally, if you are using IAP, make sure you reserve RAM for it in your project - Reserving RAM for IAP Flash Programming 

Regards,

LPCXpresso Support

2,169 Views
rnb
Contributor II

It does sound like you need to be booting into ISP mode: Regaining debug access to target MCU. What exactly did you do to try to do this on your board?

R: in order to regian vontral I tried first ISP mode (as described in Regaining debug access to target MCU) and i alsi tried to set vector catch

 

And what is your board and your target MCU? And can you clarify what you mean by "omit to change the CPU type"?

R: the board is a production version board (custom) with LPC1768. When I said I omit to change MCU (not CPU...sorry) I meant I did the first image download with the wrong definition of MCU settings ( in Project properties>C/C++ build). That is most likely the reason why I loss control on the board

 

Also what debug probe are you using? And can you post the whole debug log? The Debug Log

R: probe is LPC-LINK2

LPCXpresso RedlinkMulti Driver v8.1 (Mar 11 2016 13:34:34 - crt_emu_cm_redlink build 672)
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.147 (NXP Semiconductors)
Serial Number:  IWFWFTKW
VID:PID:  1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#7&26e0e6fd&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Emu(0): Connected&Reset. DpID: 2BA01477. CpuID: 410FC230. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
inspected v.2 On-chip Flash Memory C:\nxp\LPCXpresso_8.1.4_606\lpcxpresso\bin\Flash\LPC175x_6x_512.cfx
image 'LPC175x_6x (512K) Feb 16 2016 09:18:52'
NXP: LPC1769  Part ID: 0x00000000
Connected: was_reset=false. was_stopped=true
LPCXpresso Free License - Download limit is 256K
AFTER driver startup timeout
Driver Register State
R0:     10002620
R1:     00000000
R2:     00000000
R3:     00000000
R4:     00000000
R5:     00000000
R6:     00000000
R7:     00000000
R8:     00000000
R9:     00000000
R10:    00000000
R11:    00000000
R12:    00000000
SP:     10000600
LR:     FFFFFFF9 (exception from main thread)
PC:     00000028
xPSR:   00000003
MSP:    10000600
PSP:    10000620
CFBP:   00000001
Exception information:
1000061C:  xPSR:   00000000
10000618:  VECTPC: 10000034
10000614:  LR:     10000035
10000610:  R12:    00000000
1000060C:  R3:     00000000
10000608:  R2:     00000000
10000604:  R1:     00000000
10000600:  R0:     10002620
E000ED04:  ICSR:   00000803 (VECTPEND=0, RETTOBASE, VECTACTIVE=3)
E000ED38:  BFAR:   E000EDF8
E000ED28:  CFSR:   00020000
E000ED2C:  HFSR:   40000000 ()
E000ED30:  DFSR:   00000000
E000ED3C:  AFSR:   00000000
E000ED24:  SHCSR:  00000000
Flash Driver V.2 startup failed - rc Ef(34): Timed-out initializing flash.
(100) Writing Flash ended with an error.
Target error from Commit Flash write: Ef(34): Timed-out initializing flash.
(crt_emu_cm_redlink) terminating on communication loss: Pipe has been closed by GDB. 

Finally, if you are using IAP, make sure you reserve RAM for it in your project - Reserving RAM for IAP Flash Programming 

R: Yes, I will check that point. Can that be the cause of control loss ?

Thanks:

0 Kudos
Reply

2,169 Views
rnb
Contributor II

Hello,

Any news on the topic ?

Thanks,

René

0 Kudos
Reply

2,169 Views
rnb
Contributor II

No clue anyone ?

Maybe I was not clear, but I guess the boards were somehow affected by the wrong MCU setting. Having set the correct MCU doesn't help to regain control.

Don't know what to do

Thanks, René

0 Kudos
Reply