[ECOS] Self extracting target installer

[ECOS] Self extracting target installer

[Doyle, Patrick]

Before I go and reinvent the wheel, I thought I would ask if anybody else
had already solved this problem.

We have a product that includes RedBoot, two executable binary images, and
17 data files that all need to be installed in the Flash Image System
managed by RedBoot.  The heads up I've gotten from Manufacturing is that
they are going to throw a fit if we ask them to:

 1)  run Hyperterm
 2)  type in "fis load -m ymodem"
 2a) sometimes, you need to type in "fis load -r -b -m ymodem"
 3)  Use Hyperterm to select the next file to download
 4)  type in "fis create filename"
(By the way -- it's very important that you spell the filename correctly
here -- if you don't then the product won't work, so make sure that the
filename matches the one you downloaded)
 5)  later, rinse, repeat for each of 17 files
(By the way -- it's very important that you download all 17 of the files and
install them in flash.  If you take a break for lunch and come back and you
start off where you ended before, but you forgot one of the files, then the
product won't work).

You get the idea :-)

So I am going to write a single (ROM-monitor-less, so we could even use it
to update the RedBoot stored in FLASH if we needed to), application that
contains as data, the 19 or 20 files that need to be installed in FLASH.
I'll probably even go so far as to compress the data so it doesn't take as
long to download it.  Then I can revision control a single image, which I
give to manufacturing, and they can download and run a single program in
order to load everything on the device that needs to be loaded.

This sounds a lot like a self-extracting archive that we use in the
non-embedded land (does anybody remember "shar" files from Unix anymore?).

Any thoughts?

Patrick Doyle
DSP Design Engineer
(603) 546-2179

 

This communication is from DTC Communications, Inc. and is intended to be
confidential and solely for the use of the persons or entities addressed
above.  If you are not an intended recipient, be aware that the information
contained herein may be protected from unauthorized use by privilege or law,
and any copying, distribution, disclosure, or other use of this information
is prohibited.  If you have received this communication in error, please
contact the sender by return e-mail or telephone the above number
immediately and delete or destroy all copies.  Thank you for your
cooperation.

 


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

AW: [ECOS] Self extracting target installer

[Volker Kamp]

> Von: ecos-discuss-owner@ecos.sourceware.org
> [mailto:ecos-discuss-owner@ecos.sourceware.org]Im Auftrag von Doyle,
> Patrick
> Gesendet: Freitag, 9. Juli 2004 16:51
> An: ecos-discuss@sources.redhat.com
> Betreff: [ECOS] Self extracting target installer
>
>
> Before I go and reinvent the wheel, I thought I would ask if anybody else
> had already solved this problem.
>
> We have a product that includes RedBoot, two executable binary images, and
> 17 data files that all need to be installed in the Flash Image System
> managed by RedBoot.  The heads up I've gotten from Manufacturing is that
> they are going to throw a fit if we ask them to:
>
>  1)  run Hyperterm
>  2)  type in "fis load -m ymodem"
>  2a) sometimes, you need to type in "fis load -r -b -m ymodem"
>  3)  Use Hyperterm to select the next file to download
>  4)  type in "fis create filename"
> (By the way -- it's very important that you spell the filename correctly
> here -- if you don't then the product won't work, so make sure that the
> filename matches the one you downloaded)
>  5)  later, rinse, repeat for each of 17 files
> (By the way -- it's very important that you download all 17 of
> the files and
> install them in flash.  If you take a break for lunch and come
> back and you
> start off where you ended before, but you forgot one of the
> files, then the
> product won't work).
>
> You get the idea :-)

What about using a scriptable terminal program like ZOC? You can control all
the action within a script: typing, downloading, checking replys etc. It
would save a lot of work.
Or use "expect" on linux.
Regards,
Volker

>
> So I am going to write a single (ROM-monitor-less, so we could even use it
> to update the RedBoot stored in FLASH if we needed to), application that
> contains as data, the 19 or 20 files that need to be installed in FLASH.
> I'll probably even go so far as to compress the data so it doesn't take as
> long to download it.  Then I can revision control a single image, which I
> give to manufacturing, and they can download and run a single program in
> order to load everything on the device that needs to be loaded.
>
> This sounds a lot like a self-extracting archive that we use in the
> non-embedded land (does anybody remember "shar" files from Unix anymore?).
>
> Any thoughts?
>
> Patrick Doyle
> DSP Design Engineer
> (603) 546-2179
>
>
>
> This communication is from DTC Communications, Inc. and is intended to be
> confidential and solely for the use of the persons or entities addressed
> above.  If you are not an intended recipient, be aware that the
> information
> contained herein may be protected from unauthorized use by
> privilege or law,
> and any copying, distribution, disclosure, or other use of this
> information
> is prohibited.  If you have received this communication in error, please
> contact the sender by return e-mail or telephone the above number
> immediately and delete or destroy all copies.  Thank you for your
> cooperation.
>
>
>
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] Self extracting target installer

[Andrew Lunn]

On Fri, Jul 09, 2004 at 10:50:56AM -0400, Doyle, Patrick wrote:
> Before I go and reinvent the wheel, I thought I would ask if anybody else
> had already solved this problem.
> 
> We have a product that includes RedBoot, two executable binary images, and
> 17 data files that all need to be installed in the Flash Image System
> managed by RedBoot.  The heads up I've gotten from Manufacturing is that
> they are going to throw a fit if we ask them to:
> 
>  1)  run Hyperterm
>  2)  type in "fis load -m ymodem"
>  2a) sometimes, you need to type in "fis load -r -b -m ymodem"
>  3)  Use Hyperterm to select the next file to download
>  4)  type in "fis create filename"
> (By the way -- it's very important that you spell the filename correctly
> here -- if you don't then the product won't work, so make sure that the
> filename matches the one you downloaded)
>  5)  later, rinse, repeat for each of 17 files
> (By the way -- it's very important that you download all 17 of the files and
> install them in flash.  If you take a break for lunch and come back and you
> start off where you ended before, but you forgot one of the files, then the
> product won't work).
> 
> You get the idea :-)

A couple of completely different solution, with the same theme. 

For flashes that are not yet actually soldered to the board use a bulk
programmer.  You just need to supply Manufacturing with one file they
blast into the flash before mounting on boards.

Does your device have JTAG. Industrial JTAG programmer will be faster
than serial port, or JTAG parallel port dongles.  Again you just
supply them with one image for them to download into the flash.

I've found that manufacturing understand these sorts of things because
its nearly all automatic, no brainer. Plug in a cable, hit a button,
wait till the light goes green.  Having to use a keyboard they don't
like.

        Andrew



-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss