I'm currently trying to perform an EFU firmware update using the 1722.1 protocol and am running into some issues. We are using a custom board with a custom .xn file.
I have 3 .bin files I'm working with. I will name them one.bin, two.bin, three.bin.
one.bin and two.bin were created using xflash 14.3.2, the three.bin I'm unsure which xflash was used to create it (was created by someone else in our research group that I haven't been able to contact).
I've created one.bin and two.bin using the following command :
Code: Select all
xflash <binary>.xe -o <one/two>.bin
I have xtag flashed one.bin onto the board using the correct .xn file. I believe this means that it is saved to the bootloader as the factory image and is hardware-protected.
From here I'm able to perform EFU using the three.bin file, and the one.bin file, but when I try perform EFU with the two.bin file, it defaults back to the one.bin file. Similarly, if I xtag flash the two.bin file, I'm able to perform EFU using the two.bin and three.bin but when I try with the one.bin, it defaults back to the two.bin file.
when I try xtag flash the three.bin file, the board does not work correctly and I'm not able to see it on my AVB network. This seems to me the three.bin file is not being saved as a factory image, or it wasn't created as a factory image.
What I've tried:
1. I've tried to create upgradeable binaries one.bin and two.bin using the command:
Code: Select all
xflash --factory-version 14.3 --upgrade 1 <binary >.xe -o <one/two>.bin
2. I've tried xtag flashing these same upgradeable binaries and the board also does not work, so cannot do further testing.
Does anyone have any ideas as to why this behaviour occurs? I have a feeling I'm just not using the --upgrade command correctly, but am unsure where I'm going wrong
Thanks in advance!