topic 4370 USB boot DFU header question in LPC Microcontrollers https://community.nxp.com/t5/LPC-Microcontrollers/4370-USB-boot-DFU-header-question/m-p/552648#M14428 <HTML><HEAD></HEAD><BODY><STRONG>Content originally posted in LPCWare by MikeSimmonds on Thu Sep 18 15:36:40 MST 2014</STRONG><BR /><SPAN>I am just starting with the 4370 (LPC-Link2 board) and I have a question about the 16 byte header that has to be</SPAN><BR /><SPAN>prefixed to the DFU download image.</SPAN><BR /><BR /><SPAN>Does the image size field (i.e the 512-byte block count) have to include the DFU header itself.</SPAN><BR /><SPAN>With the rounding going on, in most cases it will not matter if the header is included or not,</SPAN><BR /><SPAN>but imagine this ...</SPAN><BR /><BR /><SPAN>The actual code image is EXACTLY 512 bytes and (by definition) the DFU header is 16 bytes.</SPAN><BR /><SPAN>Would the 'HASH_SIZE' be 1 (= 512) or 2 (512+16 round up to 1024)?</SPAN><BR /><BR /><SPAN>Secondly, I suppose that the code image will start with a vector table (with initial SP and reset address etc.)</SPAN><BR /><SPAN>Can you confirm this and indicate if the code image should be based a zero (and rely on the Boot ROM setting</SPAN><BR /><SPAN>the M4MEMMAP to hex 10000000) or base the image at absolute hex 10000000?</SPAN><BR /><BR /><SPAN>The 4370 is not an AES capable device, and the 'HASH_VALUE' will be zero.</SPAN><BR /><BR /><SPAN>Regards, Mike</SPAN><BR /></BODY></HTML> Wed, 15 Jun 2016 18:37:42 GMT lpcware 2016-06-15T18:37:42Z 4370 USB boot DFU header question https://community.nxp.com/t5/LPC-Microcontrollers/4370-USB-boot-DFU-header-question/m-p/552648#M14428 <HTML><HEAD></HEAD><BODY><STRONG>Content originally posted in LPCWare by MikeSimmonds on Thu Sep 18 15:36:40 MST 2014</STRONG><BR /><SPAN>I am just starting with the 4370 (LPC-Link2 board) and I have a question about the 16 byte header that has to be</SPAN><BR /><SPAN>prefixed to the DFU download image.</SPAN><BR /><BR /><SPAN>Does the image size field (i.e the 512-byte block count) have to include the DFU header itself.</SPAN><BR /><SPAN>With the rounding going on, in most cases it will not matter if the header is included or not,</SPAN><BR /><SPAN>but imagine this ...</SPAN><BR /><BR /><SPAN>The actual code image is EXACTLY 512 bytes and (by definition) the DFU header is 16 bytes.</SPAN><BR /><SPAN>Would the 'HASH_SIZE' be 1 (= 512) or 2 (512+16 round up to 1024)?</SPAN><BR /><BR /><SPAN>Secondly, I suppose that the code image will start with a vector table (with initial SP and reset address etc.)</SPAN><BR /><SPAN>Can you confirm this and indicate if the code image should be based a zero (and rely on the Boot ROM setting</SPAN><BR /><SPAN>the M4MEMMAP to hex 10000000) or base the image at absolute hex 10000000?</SPAN><BR /><BR /><SPAN>The 4370 is not an AES capable device, and the 'HASH_VALUE' will be zero.</SPAN><BR /><BR /><SPAN>Regards, Mike</SPAN><BR /></BODY></HTML> Wed, 15 Jun 2016 18:37:42 GMT https://community.nxp.com/t5/LPC-Microcontrollers/4370-USB-boot-DFU-header-question/m-p/552648#M14428 lpcware 2016-06-15T18:37:42Z