Why flash image file include sram address data?

guohuoping — Fri, 12 Dec 2014 12:33:17 GMT

Hi, ladies and gentleman.

Today, I use J-Flash (J-Link tool) to program the project flash image file .hex to the chip MK10DX256VLH7. Unfortunately, J-Flash push the error message as follows:

I check the .hex file, surely there existing data on the address 0x1fff8000-0x1fff82A3.

I don't know why KDS make the flash data on this range of address 0x1fff8000-0x1fff82A3.

But on the page 137 of K10 Sub-Family Reference Manual.pdf , it describes this address range belongs to sram, as follows:

I guess, maybe I missed setting some options on the KDS when build this project.

For this, I spent much time to check. Now, I still have no idea to shoot this trouble yet.

I sincerely wait for your help.

Re: Why flash image file include sram address data?

ZhangJennie — Mon, 15 Dec 2014 09:41:55 GMT

Hello huoping.

I wonder you select build configuration as "RAM " ? please make sure you select build configuration as "Flash" instead of "RAM"

make sure your project use correct ld file(allocate code/data in proper memory ).

Best Regards,

Zhang Jun

=====================================

this answer is for you. if it helps, please click on "Correct Answer", thanks!

================================================

Re: Why flash image file include sram address data?

guohuoping — Tue, 16 Dec 2014 00:45:17 GMT

Hi, Mr. Zhang,

I think your advice is good. But I don't know how to select build configuration as "RAM" in KDS IDE. I am confused where to get the good reference manual of KDS IDE. Can you give me advice further more?

Thank you sincerely!

Best Regards,

Guo Huoping

Re: Why flash image file include sram address data?

ZhangJennie — Tue, 16 Dec 2014 02:30:02 GMT

Hello guohuoping@126.com.

in linker setting, we can see which *.ld file is used in your current project.

then you search out this ld file under your project folder, see how the memory management inside. see if all the code is allocated in flash.

Best Regards,

Zhang Jun

=====================================

this answer is for you. if it helps, please click on "Correct Answer", thanks!

================================================

Re: Why flash image file include sram address data?

guohuoping — Tue, 16 Dec 2014 11:23:34 GMT

Hi, Mr. Zhang,

The following code is the linker file. This file was created by PE of KDS IDE automatically. Forgive me please, I don't know how to change it to fulfil my project and kill the above problem. So, can you check and change it?

/* ################################################################### */

/*##

/*## This component module is generated by Processor Expert. Do not modify it. */

/*## */

/*## Filename : ProcessorExpert.ld */

/*## */

/*## Project : tuft_project_new20141202 */

/*## */

/*## Processor : MK10DX256VLH7 */

/*## */

/*## Compiler : GNU C Compiler */

/*## */

/*## Date/Time : 2014-12-03, 12:24, # CodeGen: 0 */

/*## */

/*## Abstract : */

/*## */

/*## This file is used by the linker. It describes files to be linked, */

/*## memory ranges, stack size, etc. For detailed description about linker */

/*## command files see compiler documentation. This file is generated by default. */

/*## You can switch off generation by setting the property "Generate linker file = no" */

/*## in the "Build options" tab of the CPU component and then modify this file as needed. */

/*##

/*## */

/*## ###################################################################*/

/* Entry Point */

ENTRY(__thumb_startup)

/* Highest address of the user mode stack */

_estack = 0x20000000; /* end of m_data */

__SP_INIT = _estack;

/* Generate a link error if heap and stack don't fit into RAM */

__heap_size = 0x00; /* required amount of heap */

__stack_size = 0x0400; /* required amount of stack */

MEMORY {

m_interrupts (RX) : ORIGIN = 0x00000000, LENGTH = 0x000001BC

m_text (RX) : ORIGIN = 0x00000410, LENGTH = 0x0003FBF0

m_data (RW) : ORIGIN = 0x1FFF8000, LENGTH = 0x00008000

m_data_20000000 (RW) : ORIGIN = 0x20000000, LENGTH = 0x00008000

m_cfmprotrom (RX) : ORIGIN = 0x00000400, LENGTH = 0x00000010

}

/* Define output sections */

SECTIONS

{

/* The startup code goes first into INTERNAL_RAM */

.interrupts :

{

__vector_table = .;

. = ALIGN(4);

KEEP(*(.vectortable)) /* Startup code */

. = ALIGN(4);

} > m_interrupts

.cfmprotect :

{

. = ALIGN(4);

KEEP(*(.cfmconfig)) /* Flash Configuration Field (FCF) */

. = ALIGN(4);

} > m_cfmprotrom

/* The program code and other data goes into INTERNAL_RAM */

.text :

{

. = ALIGN(4);

*(.text) /* .text sections (code) */

*(.text*) /* .text* sections (code) */

*(.rodata) /* .rodata sections (constants, strings, etc.) */

*(.rodata*) /* .rodata* sections (constants, strings, etc.) */

*(.glue_7) /* glue arm to thumb code */

*(.glue_7t) /* glue thumb to arm code */

*(.eh_frame)

KEEP (*(.init))

KEEP (*(.fini))

. = ALIGN(4);

_etext = .; /* define a global symbols at end of code */

} > m_text

.ARM.extab : { *(.ARM.extab* .gnu.linkonce.armextab.*) } > m_text

.ARM : {

__exidx_start = .;

*(.ARM.exidx*)

__exidx_end = .;

} > m_text

.ctors :

{

__CTOR_LIST__ = .;

/* gcc uses crtbegin.o to find the start of

the constructors, so we make sure it is

first. Because this is a wildcard, it

doesn't matter if the user does not

actually link against crtbegin.o; the

linker won't look for a file to match a

wildcard. The wildcard also means that it

doesn't matter which directory crtbegin.o

is in. */

KEEP (*crtbegin.o(.ctors))

/* We don't want to include the .ctor section from

from the crtend.o file until after the sorted ctors.

The .ctor section from the crtend file contains the

end of ctors marker and it must be last */

KEEP (*(EXCLUDE_FILE (*crtend.o ) .ctors))

KEEP (*(SORT(.ctors.*)))

KEEP (*(.ctors))

__CTOR_END__ = .;

} > m_text

.dtors :

{

__DTOR_LIST__ = .;

KEEP (*crtbegin.o(.dtors))

KEEP (*(EXCLUDE_FILE (*crtend.o ) .dtors))

KEEP (*(SORT(.dtors.*)))

KEEP (*(.dtors))

__DTOR_END__ = .;

} > m_text

.preinit_array :

{

PROVIDE_HIDDEN (__preinit_array_start = .);

KEEP (*(.preinit_array*))

PROVIDE_HIDDEN (__preinit_array_end = .);

} > m_text

.init_array :

{

PROVIDE_HIDDEN (__init_array_start = .);

KEEP (*(SORT(.init_array.*)))

KEEP (*(.init_array*))

PROVIDE_HIDDEN (__init_array_end = .);

} > m_text

.fini_array :

{

PROVIDE_HIDDEN (__fini_array_start = .);

KEEP (*(SORT(.fini_array.*)))

KEEP (*(.fini_array*))

PROVIDE_HIDDEN (__fini_array_end = .);

___ROM_AT = .;

} > m_text

/* Initialized data sections goes into RAM, load LMA copy after code */

.data :

{

. = ALIGN(4);

_sdata = .; /* create a global symbol at data start */

*(.data) /* .data sections */

*(.data*) /* .data* sections */

. = ALIGN(4);

_edata = .; /* define a global symbol at data end */

} > m_data

___data_size = _edata - _sdata;

___m_data_20000000_ROMStart = ___ROM_AT + SIZEOF(.data);

.m_data_20000000 : AT(___m_data_20000000_ROMStart)

{

. = ALIGN(4);

___m_data_20000000_RAMStart = .;

*(.m_data_20000000) /* This is an User defined section */

___m_data_20000000_RAMEnd = .;

. = ALIGN(4);

} > m_data_20000000

___m_data_20000000_ROMSize = ___m_data_20000000_RAMEnd - ___m_data_20000000_RAMStart;

/* Uninitialized data section */

. = ALIGN(4);

.bss :

{

/* This is used by the startup in order to initialize the .bss section */

__START_BSS = .;

PROVIDE ( __bss_start__ = __START_BSS );

*(.bss)

*(.bss*)

*(COMMON)

. = ALIGN(4);

__END_BSS = .;

PROVIDE ( __bss_end__ = __END_BSS );

} > m_data

__S_romp = 0;

/* User_heap_stack section, used to check that there is enough RAM left */

._user_heap_stack :

{

. = ALIGN(4);

PROVIDE ( end = . );

PROVIDE ( _end = . );

__heap_addr = .;

__HeapBase = .;

. = . + __heap_size;

__HeapLimit = .;

. = . + __stack_size;

. = ALIGN(4);

} > m_data

.ARM.attributes 0 : { *(.ARM.attributes) }

}

Thank you sincerely!

Best Regards!

Guo Huoping

topic Re: Why flash image file include sram address data? in Kinetis Design Studio

Why flash image file include sram address data?

Re: Why flash image file include sram address data?

Re: Why flash image file include sram address data?

Re: Why flash image file include sram address data?

Re: Why flash image file include sram address data?