LPCXpresso Debugger

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

LPCXpresso Debugger

893 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by MikeSimmonds on Mon Sep 17 01:12:25 MST 2012
[SIZE=2][FONT=Tahoma]When debugging (with LPCXpresso 4.3.2) does it always burn to flash (assuming load = true) when internal flash is the target address even if the source code is unchanged?

This obviously wastes erase cycles and takes longer to get going. :(

Or is the debugger smart enough to compare current contents with the potential download image (constructed from the axf/elf file) and skip the pointless step.

What if one wants to flash regardless (I can't think why, but some -- perverse -- individual may want so to do).

Obviously, one can flip 'Load' on and off by hand, but this is a pain (in the ;)) and errors are just waiting to happen if you forget when the image [I]has[/I] changed.

Perhaps the 'load' configuration item should have an 'if changed' setting along with true/false.

Regards, Mike[/FONT][/SIZE]
0 Kudos
Reply
4 Replies

882 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by micrio on Mon Sep 17 06:06:07 MST 2012
Actually the flash "endurance" spec is 10K minumum.   The "typical" is 100K.
0 Kudos
Reply

882 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by MikeSimmonds on Mon Sep 17 04:33:36 MST 2012
[FONT=Tahoma][SIZE=2]
Quote: TheFallGuy
I don't think the number of erase cycles is a problem - these devices are validated to something like 100k cycles. Assuming the lower limit, that would allow for 1 reflash every minute for 70 days (assuming you  do this every minute for 24 hours a day. 7 days a week etc)). In practice, I don't think you are likely to reach the limit...



So I'd have to buy a new board after two months and a bit?:eek:
At least I'd get some sleep waiting for it to arrive.:cool:

[/SIZE][/FONT]
0 Kudos
Reply

882 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by TheFallGuy on Mon Sep 17 03:11:19 MST 2012
I don't think the number of erase cycles is a problem - these devices are validated to something like 100k cycles. Assuming the lower limit, that would allow for 1 reflash every minute for 70 days (assuming you  do this every minute for 24 hours a day. 7 days a week etc)). In practice, I don't think you are likely to reach the limit...
0 Kudos
Reply

882 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by ex-kayoda on Mon Sep 17 02:59:44 MST 2012

Quote: MikeSimmonds
[SIZE=2][FONT=Tahoma]When debugging (with LPCXpresso 4.3.2) does it always burn to flash (assuming load = true) when internal flash is the target address even if the source code is unchanged?[/FONT][/SIZE]



See #6 of http://knowledgebase.nxp.com/showthread.php?t=2422


Quote:

...if the image you're trying to program is already in flash, the programming operation does nothing...

0 Kudos
Reply