Help with DFU

[AudioBoy]

Hello,
I need some help with burning firmware. Can anybody check if I'm doing all correctly?

I'm doing the tests with the original Audio 2.0 Reference Design (2ioxxx), compile it with XComposer 13.1.0

At 1st I make secured factory bin file:
xflash --factory device_a.xe -o device_a.bin --key device_a.key

then I burn it with XTAG-2:
1)
xflash --target-file device_a.xn --write-all device_a.bin
xburn --target-file device_a.xn --lock device_a.key --enable-jtag --disable-master-lock

After this I check the functionality, and in a future I will secure the chip:
2)
xburn --target-file device_a.xn --disable-jtag --enable-master-lock.
But now I'm doing the last stage.

Also I prepare the upgrade image with another revision number:
3)
xflash --factory-version 13 --upgrade 1 device_a_up.xe -o device_a_ud_1.bin --key device_a.key

Next:
after I made 1), check that device is working, and play with dfucons:
dfucons.exe revertfactory

dfucons makes his job and device is working.

Then I make an upgrade, using TUSBAudioDfu.exe with device_a_ud_1.bin, device still working, FW revision changed.

If after this I try to use "dfucons revertfactory" again - I've expected to return back to the 1st, factory firmware and to see it's revision number, bit - get a "brick".
Device is not working, PC does not see it and I must to burn the factory firmware again with XTAG-2.

Using "dfucons revertfactory -d0" - the same.

What I'm doing wrong?

Thank you.

[Ross]

What do you mean by "brick", where is the code stuck?

[AudioBoy]

What do you mean by "brick", where is the code stuck?

"Brick" I mean - device is not working, PC does not see it. For user - it is like a brick, or peace of plastic (FR4) with some electronic components on it.

[AudioBoy]

Nobody can help me?

[infiniteimprobability]

Sorry - not an expert on the xburn stuff, but I wonder if the procedure works without burning keys into the OTP? It would make sense to try to debug the DFU and revert flow without the security first to narrow down the issue to DFU/flashing or a security issue.

Also, could you do an xrun --dump-state to find out where things are stuck when bricked.. some more info here:

http://www.xcore.com/questions/3233/wha ... debug-boot