??? 03/17/06 07:52 Read: times |
#112364 - Too many variables Responding to: ???'s previous message |
If I understand correctly, you've tested the release by using the HEX file, Flash Magic, and some test target hardware;
Your customer is using the BIN file, a different programmer, and their own hardware. You have too many variables here! For a start, can you program a device from your HEX file, test it in your test setup, and send it to the customer to test in their target hardware? If that fails, then you know there's a fundamental problem with your test setup that doesn't fully correspond to the customer's real target hardware. You need to know that your test setup is fully representative of the real application! If this works, send the customer the HEX file, and have them program a device with their programmer from the HEX file. If that fails, then you know there's a problem with your hex-to-bin conversion, or with the way you transfer the bin file to the customer. |
Topic | Author | Date |
.bin image when burnt does not function | 01/01/70 00:00 | |
why not... | 01/01/70 00:00 | |
Too many variables | 01/01/70 00:00 | |
Hex file tested works fine | 01/01/70 00:00 | |
so why | 01/01/70 00:00 | |
hex works but not the bin | 01/01/70 00:00 | |
Their problem? | 01/01/70 00:00 | |
could it be | 01/01/70 00:00 | |
A Note on HEX files | 01/01/70 00:00 | |
The reason for Intel Hex | 01/01/70 00:00 | |
Bin file compare | 01/01/70 00:00 | |
You need the customer to do it | 01/01/70 00:00 | |
Why not hex | 01/01/70 00:00 | |
my very first suggestion in parallel pos![]() | 01/01/70 00:00 |