Prev: New Era Hats ( www.nike-black.com )
Next: Documentation shortcomings
From: Enrico on 9 Jul 2010 12:09
Hi,

> I do that sort of thing using the boot loader.  What boot loader are
> you using?  Since you mention a .elf, I assume you have a boot loader.

I'm working on a LPC2388 CPU.

The toolchain is WinIdea/GCC and the programmer is made by ISystem.

Enrico
From: Chris Maryan on 9 Jul 2010 12:25
On Jul 9, 8:03 am, Enrico <zig...(a)libero.it> wrote:
> Hi,
>
>  I'm designing a board with an ARM controller and I need to store a
> unique ID (32 bit integer) in the application.
>
>  Are there any ways to do it?
>
> They told me that some flashers are able to modify the .s19/.elf
> executable file just before programming the flash.
> Is that true?
>
> Ciao,
> Enrico

Do you have an environment variable space in your flash? If not, I
highly recommend it. Assuming your board can upgrade itself, then it
must already have some routines for writing to the flash. Modify those
to create an area that's not blown away between upgrades. Write the
serial number into this space. This is common practice, we do it with
MAC addresses, product descriptions, serial numbers, configuration
strings, etc.

Chris
From: Walter Banks on 9 Jul 2010 13:22


Enrico wrote:
>
> Hi,
>
> I'm designing a board with an ARM controller and I need to store a
> unique ID (32 bit integer) in the application.
>
> Are there any ways to do it?
>
> They told me that some flashers are able to modify the .s19/.elf
> executable file just before programming the flash.
> Is that true?

We created a tool that modifies the programming binary by looking for
a pattern and modifying it. The reason we are looking for a pattern
is to allow code motion over various releases. Alternatively we have
set aside specific ROM or EEPROM for system information typically
checked with a polynomial type checksum.

Regards,


w..
--
Walter Banks
Byte Craft Limited
http://www.bytecraft.com

--- news://freenews.netfront.net/ - complaints: news(a)netfront.net ---
From: Enrico on 12 Jul 2010 15:46
Hi,

that's an interesting.
Could you post here the name of that tool?

ciao,
Enrico

> We created a tool that modifies the programming binary by looking for
> a pattern and modifying it. The reason we are looking for a pattern
> is to allow code motion over various releases. Alternatively we have
> set aside specific ROM or EEPROM for system information typically
> checked with a polynomial type checksum.
>
> Regards,
>
> w..
> --
> Walter Banks
> Byte Craft Limitedhttp://www.bytecraft.com
>
> --- news://freenews.netfront.net/ - complaints: n...(a)netfront.net ---

From: Walter Banks on 12 Jul 2010 16:23


Enrico wrote:
>
> Hi,
>
> that's an interesting.
> Could you post here the name of that tool?
>
> ciao,
> Enrico
>
> > We created a tool that modifies the programming binary by looking for
> > a pattern and modifying it. The reason we are looking for a pattern
> > is to allow code motion over various releases. Alternatively we have
> > set aside specific ROM or EEPROM for system information typically
> > checked with a polynomial type checksum.

It was a little application that we wrote for internal use. It
depends on the choices that we made for the production of our
distribution disks.

The description above is just about all that there is to it. In
serial number assignment there was a small ini file that records
the current serial number for each product and which encoding to
use.

That was about it. In our case product masters are a binary image.
It would be probably be just as easy to re-create it for your specific
requirements.


Regards,


w..
--
Walter Banks
Byte Craft Limited
http://www.bytecraft.com

--- news://freenews.netfront.net/ - complaints: news(a)netfront.net ---
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: New Era Hats ( www.nike-black.com )
Next: Documentation shortcomings