Warning: #10247-D creating output section "BSLSKEY" without a SECTIONS specification.

If i define in linker file as below,

SECTIONS
{
..
.bslkey : {} > BSLSKEY
..
}

still getting the warning.

For ".text" inside SECTIONS is self explanatory that the code will be routed to FLASH1

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

.text       : {} > FLASH1

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

But where to define ".bslkey"and how does the copiler interpret .bslkey like .text?

I think you are getting confused, in part, because you name everything bslkey, with only minor variations.  While all these things are in different namespaces, and thus can have the same name, it is wise to avoid doing that until you understand all the differences between them.

Here is what you need to do.  I'll name everything bslkey_something, where that something describes what it is.  Note I use all caps for the memory range name, following the unwritten convention for linker command files.

In C code you need to write ...

#pragma RETAIN(bslkey_c_variable)
#pragma DATA_SECTION(bslkey_c_variable, "bslkey_section_name")
const WORD bslkey_c_variable = 0xAA55;

In the linker command file you write ...

MEMORY
{
   ...
   BSLKEY_MEMORY_RANGE : origin = 0xFFDA, length = 0x0002
   ...
}

SECTIONS
{
   ...
   bslkey_section_name > BSLKEY_MEMORY_RANGE
   ...
}

Hope this helps ...

-George

I think you want section splitting.  Note section splitting uses >> syntax, and not > like you do.  You are not using section splitting.  Using only > syntax means the .text output section is not split at all.  If it fits entirely in FLASH1, it is placed there.  Otherwise, all of .text goes in FLASH2.  

Thanks and regards,

-George