Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: trashing 2148 bootloader

2006-02-22 by Jayasooriah

Brendan,

The Errata sheet for 2292 (please read the full text in the original document):

"Due to a timing problem in the interface between the Flash block and the 
digital logic ... in up to 10% of the devices the Flash memory interface, 
at some point during an IAP programming or erase operation, may never 
return from the IAP call"

I have looked at the code before and after boot loader update to address 
this problem. I formed my opinion on the significance of this mode of 
failure after considering the update, and based on looking at parts that 
failed.

Perhaps you should do something similar before you refute my observations 
with substance.

Kind regards,

Jaya

PS:  If you have something to say, I ask that say it here rather than 
advocate or solicit by way of private emails.  Thank you.


>Message: 6
>    Date: Wed, 22 Feb 2006 14:30:50 -0000
>    From: "brendanmurphy37" <brendan.murphy@...>
>Subject: Re: trashed 2148 bootloader
>
>I think you're wasting your time here (as I've been). I'd suggest
>making no further contributions to this thread (I certainly won't be
>making any). From what I've seen it's the same as the CRP thread: vague
>suggestions of how there might be a problem somewhere; no specific
>failure mode that's actually been observed described; criticism of a
>design by someone not familiar with all of the requirements that led to
>it (as noone outside Philips can have); etc. etc.
>
>As ever, if there is some failure mode or problem that's been observed
>in practice, then let's hear about it. If not, then I think it's better
>to keep our opinions of the parts design to ourselves: it just
>generates heat rather than light.
>
>Brendan

Send instant messages to your online friends http://au.messenger.yahoo.com

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.