xburn --serial-number

Technical questions regarding the XTC tools and programming with XMOS.
User avatar
armands117
Member
Posts: 11
Joined: Fri Dec 28, 2012 1:39 am

xburn --serial-number

Post by armands117 »

Hi,

Any idea, why xburn with --serial-number option crashes?

xburn --make-exec ua-1_otp_loader.xe --target-file src\ua-1.xn --lock ua-1_keys.txt --serial-number 127
Assertion failed: options.boardInfo.empty(), file C:\buildbot\slave\windows_xp_32bit_nightly\build\sb\tools_xburn\xburn\
main.cpp, line 1284


Regards,
Armands


richard
Respected Member
Posts: 318
Joined: Tue Dec 15, 2009 12:46 am

Post by richard »

What tools version are you using? From what I can remember this was a known issue with 11.11.0 that was fixed in 11.11.1
User avatar
armands117
Member
Posts: 11
Joined: Fri Dec 28, 2012 1:39 am

Post by armands117 »

richard wrote:What tools version are you using? From what I can remember this was a known issue with 11.11.0 that was fixed in 11.11.1
I tried with 11.11.0, 11.11.1 and 12.0.0 - the same result.
richard
Respected Member
Posts: 318
Joined: Tue Dec 15, 2009 12:46 am

Post by richard »

I've managed to reproduce this. It looks like there is a bug which means it is not possible to write board information at the same time as locking the device - this is something we'll definitely try and fix in future releases. In the meantime you can workaround this by writing the device in two stages. First write the board information (or create an executable to write the board information) and then once this has been written run xburn again to lock the device. For example:

Code: Select all

xburn --make-exec ua-1_otp_loader_1.xe --target-file src\ua-1.xn --serial-number 127
xburn --make-exec ua-1_otp_loader_2.xe --target-file src\ua-1.xn --lock ua-1_keys.txt
You would then need to run ua-1_otp_loader_1.xe and ua-1_otp_loader_2.xe in sequence.
User avatar
armands117
Member
Posts: 11
Joined: Fri Dec 28, 2012 1:39 am

Post by armands117 »

Great! This works.

Thanks,
Armands