EmbeddedRelated.com
Forums

Another problem with flash utility v2.2.3

Started by mahbub1833 April 19, 2006
Hi,
Today I downloaded flash utility v2.2.3 from philips website for
lpc2148. after successful installation when i ran that program i
couldn't change device. All other buttons works except the device
selection.

Another interesting thing is - when I change device from my prior
installation (v2.2.0) and then run v2.2.3 again then the chaged device
is shown in that.

I tried by uninstalling all prior versions and fresh installation, but
didn't work.

Did I miss anything? Or the utility have that error? How would I slove
this problem?

Thanks.

An Engineer's Guide to the LPC2100 Series

Hi,

> Today I downloaded flash utility v2.2.3 from philips website for
> lpc2148. after successful installation when i ran that program i
> couldn't change device. All other buttons works except the device
> selection.

Click the "Read Device ID" button and it will show up.

> Another interesting thing is - when I change device from my prior
> installation (v2.2.0) and then run v2.2.3 again then the chaged device
> is shown in that.

The device type is stored in the registry. Ver. 2.2.3 will probably read
it there if the registry entry has not been removed.

> I tried by uninstalling all prior versions and fresh installation, but
> didn't work.

When you uninstall the registry entry probably _will_ be removed.

Kell
--- In l..., "mahbub1833" wrote:
>
> Hi,
> Today I downloaded flash utility v2.2.3 from philips website for
> lpc2148. after successful installation when i ran that program i
> couldn't change device. All other buttons works except the device
> selection.
>
> Another interesting thing is - when I change device from my prior
> installation (v2.2.0) and then run v2.2.3 again then the chaged device
> is shown in that.
>
> I tried by uninstalling all prior versions and fresh installation, but
> didn't work.
>
> Did I miss anything? Or the utility have that error? How would I slove
> this problem?
>
> Thanks.
>

This is not a bug but a feature.

2.2.3 automatically senses the device. I use 2.2.3 all the time and it
works pretty well.