Hi Johns,
you might have a misunderstanding of the role of the SDK?
The 'burning' file is not created by the SDK, but with a tool like objcopy. See https://mcuoneclipse.com/2017/03/29/mcuxpresso-ide-s-record-intel-hex-and-binary-files/
Objcopy is called either directly from the IDE or as part of the build process.
And yes, you can create different file formats, including Intel Hex, see above article.
PS: As a side note: CRC and checksums are different things (and get easily mixed up). Intel Hex is using a checksum, not a CRC. Same for S19 files.
Hi Erich
Does the SDK have any verification mechanism to verify the generated .elf file when creating the burning file?
Also, can the SDK generate other programming files with CRC, such as .hex?
Thank you for your assistance.
Johns
Hi Johns,
you might have a misunderstanding of the role of the SDK?
The 'burning' file is not created by the SDK, but with a tool like objcopy. See https://mcuoneclipse.com/2017/03/29/mcuxpresso-ide-s-record-intel-hex-and-binary-files/
Objcopy is called either directly from the IDE or as part of the build process.
And yes, you can create different file formats, including Intel Hex, see above article.
PS: As a side note: CRC and checksums are different things (and get easily mixed up). Intel Hex is using a checksum, not a CRC. Same for S19 files.
Hi Erich
Thank you for your correction and information.
I will further study and explore.
Thank you.
Hi Johns,
The .elf itself does not have special checksum. If you are asking how to calculate one to be used in your application (e.g. used with a bootloader), see https://mcuoneclipse.com/2015/04/26/crc-checksum-generation-with-srecord-tools-for-gnu-and-eclipse/
I hope this helps,
Erich