Reply by Paul E. Bennett●August 24, 20042004-08-24
Kermit wrote:
> Hello all,
>
> I am about to work on my first embedded x86 project. I have four years of
> embedded software experience. However, all of that experience has been
> with ARM, SH, or XScale based hardware. We are doing a custom x86 hardware
> platform, and my group is responsible for developing design verification
> test software as well final functional test software. To be perfectly
> clear, I'll share my definitions of those two terms.
[-----%X-----------Query about hardware testing----------%X------]
Hello all,
I am about to work on my first embedded x86 project. I have four years of
embedded software experience. However, all of that experience has been with
ARM, SH, or XScale based hardware. We are doing a custom x86 hardware
platform, and my group is responsible for developing design verification
test software as well final functional test software. To be perfectly clear,
I'll share my definitions of those two terms.
- Design verification tests are code that we run to verify that the hardware
is put together correctly. This might be some code that simply does reads
and writes to a specific memory area such that we can capture the bus
transactions on a scope and verify timing values, or it might involve
sending and receiving data on a serial port or network connection. This code
gets run after every board spin to see if we need to do another one :)
- Final functional test software is a suite of tests that are run at the end
of the manufacturing line. They are typically designed to run very fast and
verify that the device has been put together properly. For instance, code
that sends and receives data over the serial port. I know I used that as an
example above however, in this case, the goal would be to verify that the
manufacturer actually soldered the connector on correctly. The focus of the
code above would be to subject the hardware to much greater scrutiny.
Anyway I don't want to get into a semantic argument as I imagine that of the
engineers within this group have a pretty good grasp of what I'm talking
about.
I am looking for advice on how to go about performing these tests. I don't
have many resources available to me, so I want to make as much use of
commercial off the shelf (COTS) software as possible. We are having a BIOS
vendor come out and get the BIOS up and running on the hardware. I expect
that simply bringing up the BIOS will shake out a number of hardware bugs
however, I am certain that more test code will have to be written. So, what
is the best way to go about re-using other people's work out there. If I get
DOS running, are there test suites that I can use? Are there test suites
that can run directly on top of the BIOS?
Any advice would be greatly appreciated.
Best regards,
--kermit
--
It wasn't easy being Greazy ....but it was interesting.