Bad ACK returned from status - wire error

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

Bad ACK returned from status - wire error

2,512 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by signumx on Thu Mar 22 10:49:00 MST 2012
Greetings,
Sorry to start another thread on a previously discussed subject but I tried everything I read so far without success.

I tried the proposed sequence found here http://support.code-red-tech.com/CodeRedWiki/DebugAccessChip but without success.  So my first question would be: is there a way to know for sure that we entered ISP mode?

FYI, I'm using boards based on an LPC11C22 that we designed in-house and trying to program it through an LPC-Link.  I tried different boards with the same result.  Of course I checked the connections and the power and it all seems good.  PIO0_1 is left floating and there's a 10K pull-up on the reset line.

Is there something special to do with a blank chip that has never been programmed?

Any help would be appreciated.

Thanks,
JF
0 Kudos
Reply
4 Replies

2,503 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by jdurand on Wed Nov 20 09:32:24 MST 2013
I had tried that yesterday and it didn't work, now it looks like it's working.  I loaded code into the part after blanking it with FlashMagic and was able to exit the debugger and reenter it.  I can now step through my changes to see how they locked out the debugger, this is an update to code I have out in the field.

Maybe it wanted to be powered off for the night???  I do wish the debugger was a bit more stable on these parts, but I guess I can't have everything.
0 Kudos
Reply

2,503 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Wed Nov 20 01:25:35 MST 2013
It sounds like your code is putting the core into a non-debuggable state. I suggest you use flash magic to erase the flash and then use the debugger to download your code and step through to find where you code is causing the problem.

Please read:
http://www.lpcware.com/content/faq/lpcxpresso/regaining-debug-access

The first paragraph gives some hints about what you code may be doing to stop debug.
0 Kudos
Reply

2,503 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by jdurand on Tue Nov 19 16:49:59 MST 2013
I'm getting this on my debug board now.  If I boot with the ISP pin low I can load new code in with FlashMagic and verify that CRP is disabled, but I still can't connect with the debugger.

This board has been working fine for a while now, it just started this today

Error:
see attached images

Part:  LPC1113FBD48/302
LPCXpresso v6.0.4 [Build 159] [2013-10-09]
Red Probe +

ISP pin is pulled up.
0 Kudos
Reply

2,503 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by Ex-Zero on Thu Mar 22 11:08:06 MST 2012

Quote: signumx
So my first question would be: is there a way to know for sure that we entered ISP mode?JF



No :mad:


Quote: signumx
PIO0_1 is left floating...

:eek: Then it's time to pull it up.


Quote: signumx
Is there something special to do with a blank chip that has never been programmed?



No, never had any problems with new chips :)

To check a board you should use ISP (via UART or CAN).  That's more reliable than SWD. And don't forget PIO0_3 to switch between UART and CAN :)
0 Kudos
Reply