Yahoo Groups archive
Thread
2004-11-09 by edsonghidini
Hello, I would like to know if the device identification returned by IDCODE instruction is unique. I need to get one key to encrypt one password that can't be decrypted in another LPCxxxx. How could I do that? Thanks
2004-11-09 by Charles Manning
The device Id is fixed per-device type according to "part_id-table.pdf" in the files section. If you want a small, very low cost, unique per-unit id, I'd consider the Dallas DS24011-wire silicon serial number. http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2903 -- CHarles
On Wednesday 10 November 2004 01:40, you wrote: > Hello, > > I would like to know if the device identification returned by IDCODE > instruction is unique. I need to get one key to encrypt one password > that can't be decrypted in another LPCxxxx. How could I do that? > Thanks > > > > > > > > Yahoo! Groups Links > > >
2004-11-12 by ggindele
Wouldn't be a flash stored unique key would be safer for the password encryption? There's a little inconvenience making every flash image randomized and the flash read protected, but can be done and cost could be lower than the DS2401 for volume. And the LPC-DS2401 boundary is not protected in any way, the number can be sniffed, duplicated and so on. --- In lpc2000@yahoogroups.com, Charles Manning <manningc2@a...> wrote: > The device Id is fixed per-device type according to "part_id-table.pdf" in > the files section. > > If you want a small, very low cost, unique per-unit id, I'd consider the
> Dallas DS24011-wire silicon serial number. > http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2903 > > -- CHarles > > > > On Wednesday 10 November 2004 01:40, you wrote: > > Hello, > > > > I would like to know if the device identification returned by IDCODE > > instruction is unique. I need to get one key to encrypt one password > > that can't be decrypted in another LPCxxxx. How could I do that? > > Thanks > > > > > > > > > > > > > > > > Yahoo! Groups Links > > > > > >
2004-11-12 by edsonghidini
It will really be better. Do you have some suggestion of which flash to use? --- In lpc2000@yahoogroups.com, "ggindele" <ggindele@y...> wrote: > > Wouldn't be a flash stored unique key would be safer for the password > encryption? There's a little inconvenience making every flash image > randomized and the flash read protected, but can be done and cost > could be lower than the DS2401 for volume. And the LPC-DS2401 boundary > is not protected in any way, the number can be sniffed, duplicated and > so on. > > --- In lpc2000@yahoogroups.com, Charles Manning <manningc2@a...> wrote: > > The device Id is fixed per-device type according to > "part_id-table.pdf" in > > the files section. > > > > If you want a small, very low cost, unique per-unit id, I'd consider > the > > Dallas DS24011-wire silicon serial number. > > http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2903 > > > > -- CHarles > > > > > > > > On Wednesday 10 November 2004 01:40, you wrote: > > > Hello, > > > > > > I would like to know if the device identification returned by IDCODE > > > instruction is unique. I need to get one key to encrypt one password > > > that can't be decrypted in another LPCxxxx. How could I do that?
> > > Thanks > > > > > > > > > > > > > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > >
2004-11-12 by Curt Powell
I put our serial number in the startup assembler file at a fixed address (soon after the interrupt table). That way we can easily modify the hex file with the new serial number before we flash a part.
-----Original Message----- From: edsonghidini [mailto:edson@...] Sent: Friday, November 12, 2004 9:57 AM To: lpc2000@yahoogroups.com Subject: [lpc2000] Re: Unique ID It will really be better. Do you have some suggestion of which flash to use? --- In lpc2000@yahoogroups.com, "ggindele" <ggindele@y...> wrote: > > Wouldn't be a flash stored unique key would be safer for the password > encryption? There's a little inconvenience making every flash image > randomized and the flash read protected, but can be done and cost > could be lower than the DS2401 for volume. And the LPC-DS2401 boundary > is not protected in any way, the number can be sniffed, duplicated and > so on. > > --- In lpc2000@yahoogroups.com, Charles Manning <manningc2@a...> wrote: > > The device Id is fixed per-device type according to > "part_id-table.pdf" in > > the files section. > > > > If you want a small, very low cost, unique per-unit id, I'd consider > the > > Dallas DS24011-wire silicon serial number. > > http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2903 > > > > -- CHarles > > > > > > > > On Wednesday 10 November 2004 01:40, you wrote: > > > Hello, > > > > > > I would like to know if the device identification returned by IDCODE > > > instruction is unique. I need to get one key to encrypt one password > > > that can't be decrypted in another LPCxxxx. How could I do that? > > > Thanks > > > > > > > > > > > > > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > > ------------------------ Yahoo! Groups Sponsor --------------------~--> Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar. Now with Pop-Up Blocker. Get it for free! http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/dN_tlB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links