Potential bug in mcuXpresso

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Potential bug in mcuXpresso

481 Views
tamir_michael
Contributor IV

Hello,

Using MIMXRT1062, if you perform a post build step 

arm-none-eabi-objcopy -v -O binary "${BuildArtifactFileName}" "${BuildArtifactFileBaseName}.bin"

checksum -p ${TargetChip} -d "${program}.bin"

you get to see something like

Written checksum 0x67b5b5b9 at offset 0x1c in file program.bin

in the console. But offset 0x1c is deep inside structure _FlexSPIConfig, and it's mapped to

uint8_t configCmdEnable; //!< [0x01c-0x01c] Configure command Enable Flag, 1 - Enable, 0 - Disable
uint8_t configModeType[3]; //!< [0x01d-0x01f] Configure Mode Type, similar as deviceModeTpe

I don't think this is a good idea - I guess the intention was to write the value into the vector table of the Cortex M7 (offset 0x1c is reserved).

Labels (1)
Tags (1)
0 Kudos
1 Reply

437 Views
jingpan
NXP TechSupport
NXP TechSupport

Hi Tamir,

Yes, you are right. Checksum.exe is for Kinetis device only. It is not designed for i.mxRT product. But customer may not know this. I'll escalate it to IDE team.

Thanks,

Jing

0 Kudos