Multiple hardware platforms

[Richard]

Our SBC hit EOL and we had to select another SBC. I really did not want
unique images for each SBC as it would be difficult in the field servicing
the systems.

A quick description of our system. We do not use unique clonining. All
systems use the same exact settings for computer name and IP and such. They
are not on a network and only connect to a field laptop via crossover cable
so the network settings remain the same from system to system. Next, Post
FBA, we do a few small manual settings, like a few ADVANTECH drivers which
are almost impossible to componentize. We then take the final image, delete
some uneeded log files, setup files and such from it, and we make a sector
copy of it so we can duplicate it perfectly.

Back to my slx, Since I normally make a selector prototype component for
each SBC from the TAP import. I decided I would try to keep my original
build, and just add the new component for the new hardware so either would
work.

This seems to work when each image runs thru FBA on it's specific target.
Now, what about a Post FBA Ready to go Golden Image. I tried it for grins
and it mostly works. The Bootlog shows where the proper drivers are indeed
loaded for each platform.

The only thing that did not seem to work, is the Display resolution is not
set. Both video drivers are present in the build and both are set to 1024,
768, 32 bit, 60 hz.

My questions are, will XPe pickup all the new hardware devices and
automatically install them? I guess it does to some extent if all the
drivers are there.

On a post FBA image, can FBA be kicked off again, and should it?

 

[Ralph A. Schmid, dk5ras]

The only thing that did not seem to work, is the Display resolution is not
set. Both video drivers are present in the build and both are set to 1024,
768, 32 bit, 60 hz.

My questions are, will XPe pickup all the new hardware devices and
automatically install them? I guess it does to some extent if all the
drivers are there.

Usually it does.

I managed to produce an image that works on three kinds of hardware,
Intel 855GM, 945GM and 945GME chipsets. The basic problem was the
graphics driver, but with Intels IEGD it was easy to build one that
supports all three chipsets. I have to boot the image on each platform
once to manually set the video settings, and to allow PnP finish all
driver installations (chipset, audio, network), then the image works
at once an all platforms, without changing anything else.


-ras

--

Ralph A. Schmid

http://www.dk5ras.de/ http://www.db0fue.de/
http://www.bclog.de/

 

[Richard]

Thanks Ralph, BTW, what is Intels IEGD?

Usually it does.

I managed to produce an image that works on three kinds of hardware,
Intel 855GM, 945GM and 945GME chipsets. The basic problem was the
graphics driver, but with Intels IEGD it was easy to build one that
supports all three chipsets. I have to boot the image on each platform
once to manually set the video settings, and to allow PnP finish all
driver installations (chipset, audio, network), then the image works
at once an all platforms, without changing anything else.


-ras

--

Ralph A. Schmid

http://www.dk5ras.de/ http://www.db0fue.de/
http://www.bclog.de/

 

[Ralph A. Schmid, dk5ras]

Thanks Ralph, BTW, what is Intels IEGD?

It is a kit the allows to build your own gfx drivers for your systems;
it can be downloaded without registration or costs from their website.
It was the only way for us to include different chipsets into one
driver, and to ensure that LVDS is used and also VGA is active all the
time, even when no monitor is connected during boot.


-ras

--

Ralph A. Schmid

http://www.dk5ras.de/ http://www.db0fue.de/
http://www.bclog.de/