topic Re: DFUSec programming not work as expected in LPC Microcontrollers

DFUSec programming not work as expected

lpcware — Wed, 15 Jun 2016 18:12:44 GMT

Content originally posted in LPCWare by brightcloud on Fri Sep 26 02:37:22 MST 2014
We faced some in using DFUSec tool.
Maybe someone could help us.
1.Error in programming algorithm, like in the attachment DFUError_InBankB.jpg.
BankB is start from 0x1B000000, with size 0x7ffff.
Why there got this error?

2.Why there has read data upload failure? Like in the attachment FWDownloadError_ReadData.PNG.

3.What's the program cycle complete used for? It seems that Reset, Jump to address have no difference with Do nothing.
Can we have a way that after finish SW loading, let the SW start automatically?

Re: DFUSec programming not work as expected

lpcware — Wed, 15 Jun 2016 18:12:44 GMT

Content originally posted in LPCWare by bavarian on Mon Sep 29 05:22:15 MST 2014
The size of the flash banks is 0x80000. If you think about programming a loop you would maybe set the parameter running from 0 ... 0x7FFFF, but here you need to provide the pure size, and this is 0x80000.

Second problem: for me it's running fine in principle (see attached picture). Can you maybe see more details where it's going wrong in the "Program log" ?

If you generated the binary for the flash bank #A with Keil, then you have maybe already added the CRC checksum over the first words of the image. This is the indication for the bootloader that it is a valid executable code and it will start with it. If you didn't do it with Keil (or any other method in other tools), then you need to do it here with "Compute/Insert checksum in image before programming".

Regards,
NXP Support Team.

Re: DFUSec programming not work as expected

lpcware — Wed, 15 Jun 2016 18:12:45 GMT

Content originally posted in LPCWare by brightcloud on Mon Sep 29 19:43:33 MST 2014
Hi Bavarian,

Thanks for the answer.
The first question's picture could not be seen, add it again.
It's strange that the problem happened only one of our colleagues's laptop. Not on others

The second question's log files are in the attachment.

About 3rd question, we're using IAR not keil.
We found that neither reset nor jump to the SW start address could not make the MCU restart.