All you ever wanted to know about checksum calculations


Oct 15, 2021

It is a well-known and good practice to use checksum calculation for verifying the image integrity in embedded systems. The image could easily be corrupted during the programming or in the transfer process for the remote update for example. You can use a checksum to verify that the image is the same at runtime as when the image’s original checksum was generated.

This process sounds simple and most of the development tools provide plain ways to work with checksum. However there are some choices that you must always consider and there are some choices to make like the memory range (or ranges) that you want to verify, which algorithm and size is most suitable in your case, specify which fill pattern to be used during calculation and finally define an explicit initial value.

Additionally, what kind of breakpoints can you use to avoid that the checksum calculation over a memory range fails and what about the locations where the checksum can be placed?

In our last webinar you will learn to cover all these matters and how to easily generate the checksum from the IDE or even command line and finally how to debug checksum calculations in the best way.

Watch on-demand webinar

Det här innehållet finns tyvärr inte på svenska.

Vår webbplats finns främst på vårt koncernspråk engelska, förutom det innehåll för investerare som vi är lagstadgade att kommunicera på svenska. Vi rekommenderar att du besöker vår globala webbplats på engelska för att få en bättre upplevelse.

Vi stöder inte längre Internet Explorer. För att få bästa möjliga upplevelse av rekommenderar vi att du uppgraderar till en modern webbläsare som Chrome eller Edge.