Problem in generating binary for DFU

[Marf]

Hi Andrew, thanks, I contacted Thesycon and asked for a newer version of their dfu tool. But still, I'm wondering about the file sizes. Jus to illustrate: The factory firmware binary is 2.912KB, the update binary is only 72KB(!). Can this be really correct?

[Marf]

Hi,
The main issue is that xobjdump --strip takes out info that might cause errors during flashing. Try a different command to create the binary file without stripping. Also, check that your .xe file is correct and free from code errors. :)

I'm not sure what you mean with the --strip option. I followed exactly the tutorial from XMOS in the AN2019_1_0_0 sample. I genrated two xe files (factory.xe and update.xe) with different -DBCD_DEVICE flags and flashed the first as factory image (xflash --factory bin/factory.xe) to my devide. Then I generated the update binary out of the update.xe using:

xflash --factory-version 15.3 --upgrade 1 bin\update.xe -o bin\update.bin

and this results in a file only 72KB in size. And this seems incorrectly small to me. Can you tell me, if this is really normal? As I understand the documentation, it is not a kind of delta update but a complete firmware version loaded in a different section of the flash memory.

OK, I just generated a binary by using:

xflash bin/factory.xe -o bin/factory.bin

to see, how big the original binary is. And yes this is also quite tiny (80kB), Is the whole code written to the flash memory of the device really that small?

Thanks to all for helping here.

[andrewxcav]

You can have binaries range from a few dozen k to almost a meg depending on what they are doing. The factory.bin should include all program memory, constants, plus a few k of bootloader code, but little else.

[Marf]

OK, after contacting Thesycom, they send me a driver and update tool. It works now...