AnsweredAssumed Answered

FRDM complaints about memory inconsistency

Question asked by Kai Liu on Oct 18, 2013
Latest reply on Oct 23, 2013 by Kai Liu

I use IAR and FRDM-KL25Z for my work. I found FRDM-KL25Z always complaints about memory inconsistency at address 0x00000000. The code execution is normal. But it is annoying.

 

I tried to erase all memory. But it doens't help at all. And I have two boards, they have same issues. Here is my log file. Please comment if you have any ideas about it.

 

================ IAR Debug Log ==================

 

Sat Oct 19, 2013 12:18:38: Loaded macro file: C:\Program Files\IAR Systems\Embedded Workbench 6.5\arm\config\flashloader\Freescale\FlashKLxx.mac

Sat Oct 19, 2013 12:18:39: Windows NT detected.

Sat Oct 19, 2013 12:18:43: OpenSDA detected - Flash Version 1.02

Sat Oct 19, 2013 12:18:44: Device is KINETIS.

Sat Oct 19, 2013 12:18:44: Mode is In-Circuit Debug.

Sat Oct 19, 2013 12:18:44: CPU reset by debugger.

Sat Oct 19, 2013 12:18:44: 

Sat Oct 19, 2013 12:18:44: Software reset was performed

Sat Oct 19, 2013 12:18:44: ----- Prepare hardware for Flashloader -----

Sat Oct 19, 2013 12:18:45: 768 bytes downloaded and verified (1.02 Kbytes/sec)

Sat Oct 19, 2013 12:18:45: Loaded debugee: C:\Program Files\IAR Systems\Embedded Workbench 6.5\arm\config\flashloader\Freescale\FlashKLxx16K.out

Sat Oct 19, 2013 12:18:45: Target reset

Sat Oct 19, 2013 12:18:48: Downloaded D:\Freescale FRDM KL25Z\an4379sw_msd_bootloader\Source\Device\app\msd_bootloader\iar_ew\kinetis_l2k\Debug\

Exe\USB_MSD_Bootloader.out to flash memory.

Sat Oct 19, 2013 12:18:51: 22368 bytes downloaded into FLASH and verified (3.77 Kbytes/sec)

Sat Oct 19, 2013 12:18:51: Warning: Target inconsistency detected at Memory address 0x00000000

Sat Oct 19, 2013 12:18:53: Warning: There were warnings during download, see Log Window

Sat Oct 19, 2013 12:18:53: Loaded debugee: D:\Freescale FRDM KL25Z\an4379sw_msd_bootloader\Source\Device\app\msd_bootloader\iar_ew\kinetis_l2k\

Debug\Exe\USB_MSD_Bootloader.out

Sat Oct 19, 2013 12:18:53: CPU reset by debugger.

Sat Oct 19, 2013 12:18:53: 

Sat Oct 19, 2013 12:18:53: Software reset was performed

Sat Oct 19, 2013 12:18:53: Target reset

Sat Oct 19, 2013 12:18:56: There was 1 warning during the initialization of the debugging session.

Sat Oct 19, 2013 12:18:56: Preset breakpoint encountered.

Sat Oct 19, 2013 12:18:56: 

Outcomes