EmbeddedRelated.com
Forums
The 2024 Embedded Online Conference

ICP problems with LPC921

Started by orenhayman February 1, 2006
Hello people.

I've written an ICP programmer for use with our philips-based 
products, for use in our mass-production environment.

I've based it on both the ISP to ICP bridge v1.6 and the ICP 
Specifications PDF.

It manages to erase the chip, write the program data, write the 
configuration bytes and security bytes, and verifies the CRC (and the 
CRC matches the original data).

The only problem is that the chip doesn't work...

In order for a chip to work, i need to program it once with a philips 
programmer, after that is done, i can program it with my programmer, 
and the chip works. 

At first i thought maybe my programmer doesn't really do anything... 
but when i erase a chip, it doesn't work, and when i program it with 
a different program, it works with the new program.. so that's not it.

I believe i've missed something, but i can't find it in the ICP 
specifications PDF...

Any ideas?

Thanks,
  Oren Hayman
	
Clear the BSB bit.

  Eric

> -----Oorspronkelijk bericht-----
> Van: orenhayman [mailto:orenhayman@oren...]
> Verzonden: woensdag 1 februari 2006 11:09
> Aan: lpc900_users@lpc9...
> Onderwerp: [lpc900_users] ICP problems with LPC921
> 
> 
> Hello people.
> 
> I've written an ICP programmer for use with our philips-based 
> products, for use in our mass-production environment.
> 
> I've based it on both the ISP to ICP bridge v1.6 and the ICP 
> Specifications PDF.
> 
> It manages to erase the chip, write the program data, write the 
> configuration bytes and security bytes, and verifies the CRC (and the 
> CRC matches the original data).
> 
> The only problem is that the chip doesn't work...
> 
> In order for a chip to work, i need to program it once with a philips 
> programmer, after that is done, i can program it with my programmer, 
> and the chip works. 
> 
> At first i thought maybe my programmer doesn't really do anything... 
> but when i erase a chip, it doesn't work, and when i program it with 
> a different program, it works with the new program.. so that's not it.
> 
> I believe i've missed something, but i can't find it in the ICP 
> specifications PDF...
> 
> Any ideas?
> 
> Thanks,
>   Oren Hayman
> 
> 
> 
> 
> 
>  
> Yahoo! Groups Links
> 
> 
> 
>  
> 
> 

I've checked in the ICP PDF, and I've figured it's the
configuration 
byte at 0x03 ("Status Byte").

I'm already programming it to 0x00.

Either that's not the byte or that's not the problem..

--- In lpc900_users@lpc9..., Eric Rullens <gorilla@...> wrote:
>
> Clear the BSB bit.
> 
>   Eric
> 
> > -----Oorspronkelijk bericht-----
> > Van: orenhayman [mailto:orenhayman@...]
> > Verzonden: woensdag 1 februari 2006 11:09
> > Aan: lpc900_users@lpc9...
> > Onderwerp: [lpc900_users] ICP problems with LPC921
> > 
> > 
> > Hello people.
> > 
> > I've written an ICP programmer for use with our philips-based 
> > products, for use in our mass-production environment.
> > 
> > I've based it on both the ISP to ICP bridge v1.6 and the ICP 
> > Specifications PDF.
> > 
> > It manages to erase the chip, write the program data, write the 
> > configuration bytes and security bytes, and verifies the CRC (and 
the 
> > CRC matches the original data).
> > 
> > The only problem is that the chip doesn't work...
> > 
> > In order for a chip to work, i need to program it once with a 
philips 
> > programmer, after that is done, i can program
it with my 
programmer, 
> > and the chip works. 
> > 
> > At first i thought maybe my programmer doesn't really do 
anything... 
> > but when i erase a chip, it doesn't
work, and when i program it 
with 
> > a different program, it works with the new
program.. so that's 
not it.
> > 
> > I believe i've missed something, but i can't find it in the
ICP 
> > specifications PDF...
> > 
> > Any ideas?
> > 
> > Thanks,
> >   Oren Hayman
	
Hi Oren,

Are the config bytes written correctly? If you read them back, do they have
the correct value? They are NOT included in the CRC, and you'll have to
issue a CCP command before programming them.

If you can't find anything, I'd read back all the config bytes from a
device
programmed with the Philips programmer, using your own programmer. That is
the only area where the chip can be different if the CRC matches.

  Eric
 
> I've checked in the ICP PDF, and I've
figured it's the configuration 
> byte at 0x03 ("Status Byte").
> 
> I'm already programming it to 0x00.
> 
> Either that's not the byte or that's not the problem..
> 
> --- In lpc900_users@lpc9..., Eric Rullens <gorilla@...> wrote:
> >
> > Clear the BSB bit.
> > 
> >   Eric
> > 
> > > -----Oorspronkelijk bericht-----
> > > Van: orenhayman [mailto:orenhayman@...]
> > > Verzonden: woensdag 1 februari 2006 11:09
> > > Aan: lpc900_users@lpc9...
> > > Onderwerp: [lpc900_users] ICP problems with LPC921
> > > 
> > > 
> > > Hello people.
> > > 
> > > I've written an ICP programmer for use with our
philips-based 
> > > products, for use in our mass-production environment.
> > > 
> > > I've based it on both the ISP to ICP bridge v1.6 and the ICP

> > > Specifications PDF.
> > > 
> > > It manages to erase the chip, write the program data, write the 
> > > configuration bytes and security bytes, and verifies the CRC (and

> the 
> > > CRC matches the original data).
> > > 
> > > The only problem is that the chip doesn't work...
> > > 
> > > In order for a chip to work, i need to program it once with a 
> philips 
> > > programmer, after that is done, i can program it with my 
> programmer, 
> > > and the chip works. 
> > > 
> > > At first i thought maybe my programmer doesn't really do 
> anything... 
> > > but when i erase a chip, it doesn't work, and when i program
it 
> with 
> > > a different program, it works with the new program.. so
that's 
> not it.
> > > 
> > > I believe i've missed something, but i can't find it in
the ICP 
> > > specifications PDF...
> > > 
> > > Any ideas?
> > > 
> > > Thanks,
> > >   Oren Hayman
> 
> 
> 
> 
> 
> 
> 
>  
> Yahoo! Groups Links
> 
> 
> 

Hello Eric,

Sending the CCP seem to solve it.

Thank you.

--- In lpc900_users@lpc9..., Eric Rullens <gorilla@...> wrote:
>
> Hi Oren,
> 
> Are the config bytes written correctly? If you read them back, do 
they have
> the correct value? They are NOT included in the
CRC, and you'll 
have to
> issue a CCP command before programming them.
> 
> If you can't find anything, I'd read back all the config bytes
from 
a device
> programmed with the Philips programmer, using your
own programmer. 
That is
> the only area where the chip can be different if
the CRC matches.
> 
>   Eric
>  
> > I've checked in the ICP PDF, and I've figured it's the 
configuration 
> > byte at 0x03 ("Status Byte").
> > 
> > I'm already programming it to 0x00.
> > 
> > Either that's not the byte or that's not the problem..
> > 
> > --- In lpc900_users@lpc9..., Eric Rullens <gorilla@> 
wrote:
> > >
> > > Clear the BSB bit.
> > > 
> > >   Eric
> > > 
> > > > -----Oorspronkelijk bericht-----
> > > > Van: orenhayman [mailto:orenhayman@]
> > > > Verzonden: woensdag 1 februari 2006 11:09
> > > > Aan: lpc900_users@lpc9...
> > > > Onderwerp: [lpc900_users] ICP problems with LPC921
> > > > 
> > > > 
> > > > Hello people.
> > > > 
> > > > I've written an ICP programmer for use with our
philips-based 
> > > > products, for use in our mass-production environment.
> > > > 
> > > > I've based it on both the ISP to ICP bridge v1.6 and
the ICP 
> > > > Specifications PDF.
> > > > 
> > > > It manages to erase the chip, write the program data, write 
the 
> > > > configuration bytes and security
bytes, and verifies the CRC 
(and 
> > the 
> > > > CRC matches the original data).
> > > > 
> > > > The only problem is that the chip doesn't work...
> > > > 
> > > > In order for a chip to work, i need to program it once with
a 
> > philips 
> > > > programmer, after that is done, i can program it with my 
> > programmer, 
> > > > and the chip works. 
> > > > 
> > > > At first i thought maybe my programmer doesn't really
do 
> > anything... 
> > > > but when i erase a chip, it doesn't work, and when i
program 
it 
> > with 
> > > > a different program, it works with the new program.. so 
that's 
> > not it.
> > > > 
> > > > I believe i've missed something, but i can't find
it in the 
ICP 
> > > > specifications PDF...
> > > > 
> > > > Any ideas?
> > > > 
> > > > Thanks,
> > > >   Oren Hayman
	

The 2024 Embedded Online Conference