Daniel Peppicelli
07/12/2011 9:28 AM
post87274
|
Hi,
We are creating an embedded system (hardware + software) for motion
control. Our project is on QNX. We would like to let the users of our
product sending a new firmware in order to upgrade it (so we can keep
our jobs ;)). The firmware is an IFS file.
For the moment, we are able to
1. Let the user send the new firmware through a web page
2. Get the firmware (ifs file) on the board.
3. Copy it to a raw flash partition
4. Restart the product on the new firmware.
Our current issue is that we would like to be able to check, on the
product, that the user did send a valid ifs image. We notice that there
are two checksum embedded in the ifs image. One for the startup code and
one for the image itself.
What we do not know (and maybe you can help us on this) is:
- What is the internal structure of the ifs file (in order to
parse it) ? Is there some header files describing the data ?
- Is there (we did not find it) an API to recalculate the
checksum and compare them with the embedded checksum ?
- Has someone already done such kind of code and is there some
example, documentation somewhere ?
Regards,
Daniel Peppicelli
Kollmorgen
Please be advised that this email may contain confidential
information. If you are not the intended recipient, please notify us
by email by replying to the sender and delete this message. The
sender disclaims that the content of this email constitutes an offer
to enter into, or the acceptance of, any agreement; provided that the
foregoing does not invalidate the binding effect of any digital or
other electronic reproduction of a manual signature that is included
in any attachment.
|
|
|