TM4C1290NCPDT: TM4C1290NCPDT

Hi Charles,

thanks so much for the hint. This resolved my issue on the hex file.

I'm still experiencing the warnings on the .elf creation:

warning: section BIC1100SP18TD3BL2220vectoritaly.elf(.text) was padded by 2 to a size of 198400 to satisfy the specified memory width of 4
warning: section BIC1100SP18TD3BL2220vectoritaly.elf($fill000) at 030906h overlaps BIC1100SP18TD3BL2220vectoritaly.elf(.text) (BIC1100SP18TD3BL2220vectoritaly.elf($fill000) incomplete or skipped)

Have you any idea about it?

Thanks.

Best regards.

Diego Greco

Hi,

 I think the warning is that the toolchain (the linker) is trying to align the text section to a 32-bit address and therefore adding whatever number of padding it sees fit. I'm not an linker expert and I will forward your question to our toolchain experts for further clarification. 

Despite the warnings, I think the hex file will work.  Does it?

Please attach the linker command file to your next post.  So it will be accepted, please add the file extension .txt.  

Thanks and regards,

-George

Hi George,

yes, the .hex file is correct now. 
I would like to solve also the remaining warning in order to avoid any malfunctions.

/******************************************************************************
 *
 * Default Linker Command file for the Texas Instruments TM4C1290NCPDT
 *
 * This is derived from revision 15071 of the TivaWare Library.
 *
 *****************************************************************************/

--retain=g_pfnVectors


MEMORY
{
    FLASH (RX) : origin = 0x00000000, length = 0x000eff00, fill = 0xFFFFFFFF
    SOFT (RX)  : origin = 0x000eff00, length = 0x000000f8, fill = 0xFFFFFFFF
    CRC  (R)   : origin = 0x000efff8, length = 0x00000008, fill = 0xFFFFFFFF
	TEXT (R)   : origin = 0x000fc000, length = 0x00002000

    SRAM (RWX) : origin = 0x20000000, length = 0x0003ef00
    TRAM (RWX) : origin = 0x2003ef00, length = 0x00001000
    CRAM (RWX) : origin = 0x2003ff00, length = 0x00000100
}


//}

/* The following command line options are set as part of the CCS project.    */
/* If you are building using the command line, or for some reason want to    */
/* define them here, you can uncomment and modify these lines as needed.     */
/* If you are using CCS for building, it is probably better to make any such */
/* modifications in your CCS project and leave this file alone.              */
/*                                                                           */
/* --heap_size=0                                                             */
/* --stack_size=256                                                          */
/* --library=rtsv7M4_T_le_eabi.lib                                           */

/* Section allocation in memory */

SECTIONS
{
    .intvecs:   > 0x00000000
    .text   :   > FLASH
    .const  :   > FLASH palign 4
    .cinit  :   > FLASH
    .pinit  :   > FLASH
    .init_array : > FLASH
	.softstart: > SOFT
	.result	:	> CRC
	.partext:   > TEXT

    .stack  :   > 0x20000000
    .vtable :   > SRAM
    .data   :   > SRAM
    .bss    :   > SRAM
    .sysmem :   > SRAM
    .stack  :   > SRAM

	.sentram : > TRAM
	.memcheck : > CRAM
}

__STACK_TOP = __stack;

Thanks for the support.

Best regards.

Diego Greco

Hi George,

I'm sorry, I have to retract my answer.
I noted that the .hex file is correct on the block number side (and the relative addresses), but it is not correct on the endiannes:

Hex file:

It differs from the .bin file:

And if I flash the .hex file it doesn't work. If I flash the .bin it works properly.

I didn't find any option in the Arm Hex Utility in order to change the byte order. I searched for it also in the SPNU118U document.

These are my flags set:

Do you have any suggestion about that?

Thanks and regards.

Diego Greco

I'd appreciate if you would try a different utility.  The command armobjcopy is located in same \bin directory as the compiler armcl.  From the command line, please run a command similar to ...

armobjcopy -O ihex project_name.out project_name.hex

Because I can't test it, I cannot be certain this suggestion works.  But I'm confident enough to ask you to try it.

Thanks and regards,

-George