Hash of the received firmware image does not match the hash in the init packet

RE: Hash of the received firmware image does not match the hash in the init packet

Einar Thorsrud — Tue, 23 Jun 2020 09:30:27 GMT

Hi Navin,

Good to hear. Thank you for letting us know!

Einar

RE: Hash of the received firmware image does not match the hash in the init packet

Navin — Tue, 23 Jun 2020 07:59:40 GMT

Hi Einar,

The issue here was related to the flash alignment. Since we removed the SLIP encoding, which took care of the memory alignment, we had to fix this by offsetting the start address by certain value (3). It now works fine.

Thank you!

RE: Hash of the received firmware image does not match the hash in the init packet

Einar Thorsrud — Fri, 17 Apr 2020 15:20:20 GMT

Hi Navin,

I don't have an explanation for this, but it is interesting that you only see the issue with debug builds. Can you upload the complete project here so that I can have a look? You can also upload it in a private case and refer to this thread if you prefer that.

RE: Hash of the received firmware image does not match the hash in the init packet

Navin — Wed, 15 Apr 2020 11:47:06 GMT

Hello Einar,

I reduced the FLASH_PH_SIZE by 0x2000, but that doesn't work too. The same code works in non-debug example, but fails at the CRC validation after receiving first block(4096 bytes).

Please see the image above about the error reported.

What can be done about this?

Please let me know!

Best regards,

Navin

RE: Hash of the received firmware image does not match the hash in the init packet

Einar Thorsrud — Mon, 23 Mar 2020 11:23:54 GMT

Hi,

You need to edit the section placement macros of the project, which you find from Project -> Options..., then as shown in this screenshot:

First of all, you could reduce FLASH_PH_SIZE by 0x2000 to see if you get a linker error (and keep it reduced regardless). If you do, then this is (at least part) of the problem. Then you fix it by moving down the bootloader start address (FLASH_START) by 0x2000.

RE: Hash of the received firmware image does not match the hash in the init packet

Navin — Mon, 23 Mar 2020 10:16:49 GMT

Hi Einar,

Can you direct me regarding bootloader start address? Where can I find this in the settings (SES). By how much would you suggest me to change it?

The bootloader in DEBUG mode worked fine a few times, after I removed redundant for-loop-print statements. But now, again, the same problem is occuring.

RE: Hash of the received firmware image does not match the hash in the init packet

Navin — Wed, 11 Mar 2020 15:35:50 GMT

Hi Einar,

I will give it a try and update you on this.

RE: Hash of the received firmware image does not match the hash in the init packet

Einar Thorsrud — Wed, 11 Mar 2020 14:47:41 GMT

I have not checked in detail, but from the log, it looks like the transferred data is identical. If that is the case, then it should work, as you write.

There is one typical issue when modifying the bootloader, which we should rule out. If you are using SES, the bootloader project in the SDK is misconfigured, and will not generate a build error if the image is up to two pages (8 kB) too large, overwriting MBR params and bootloader settings. In this case, you would see undefined behavior. Can you try to move the bootloader start address down with two pages and see if this changes anything? This is a long shot, but it is worth ruling out.

RE: Hash of the received firmware image does not match the hash in the init packet

Navin — Wed, 11 Mar 2020 08:48:34 GMT

The solution of increasing the STACK size didn't help as suggested in this LINK.