TM4C123GH6PGE: Bootloader corrupted. Not working properly after the device power down when flashing.

Would you please clarify if you are using the ROM based bootloader or a flash based bootloader?

It is rom based Bootloader. I did not know if there is a flash based bootloader.

Actually , i can write flag into memory. But i do not know how can i check when bootloader start up. 

Another option to consider is to use a flash based bootloader like the one in TivaWare: C:\ti\TivaWare_C_Series-2.2.0.295\boot_loader

In the configuration fjile bl_config.h, you can require the bootloader to check the CRC value of an application before leaving the bootloader. The details are described in the comments of bl_config.h which I have included below:

//*****************************************************************************
//
// Enables runtime and download CRC32 checking of the main firmware image.
// If this is defined, the boot loader will scan the main firmware image for
// an image information header (stored immediately above the vector table and
// marked by the words 0xFF01FF02 and 0xFF03FF04).  If the header is found and
// the CRC32 value it contains matches that calculated for the image, the
// firmware is run.  If the CRC32 does not match or the image information
// is not found, the boot loader retains control and waits for a new download.
// To aid debugging, if this option is used without ENFORCE_CRC being set, the
// image will also be booted if the header is present but the length field is
// set to 0xFFFFFFFF, typically indicating that the firmware file has not been
// run through the post-processing tool which inserts the length and CRC values.
//
// Note that firmware images intended for use with CRC checking must have been
// built with an 8 word image header appended to the top of the vector table
// and the binary must have been processed by a tool such as tools/binpack.exe
// to ensure that the required length (3rd word) and CRC32 (4th word) fields
// are populated in the header.
//
// Depends on: ENFORCE_CRC
// Exclusive of: None
// Requires: None
//
//*****************************************************************************
//#define CHECK_CRC

//*****************************************************************************
//
// This definition may be used alongside CHECK_CRC to remove the debug behavior
// which will allow an image with an uninitialized header to be run.  With
// ENFORCE_CRC defined firmware images will only be booted if they contain a
// valid image information header and if the embedded CRC32 in that header
// matches the calculated value.
//
// Depends on: None
// Exclusive of: None
// Requires: CHECK_CRC
//
//*****************************************************************************
//#define ENFORCE_CRC

Hi Bob, 

Thank you for your valuable information.I noticed the source is flash based bootloader, not rom based. I could not distinguish at first.

Bob Crosby said:

Program the rest of the code first, then program the first 8 bytes last.

It is acceptable.

#define APP_START_ADDRESS       0x2800

I tried to program the rest of the code first , then program first page including 1024 bytes that is first page.

But not success  after power down when loading program.

So , I did program at starting at APP_START_ADDRESS + 1024, last program APP_START_ADDRESS. Is it right ? 

Also, i did not used CRC part. I think needs "binpack tool" which inserts the length and CRC values into the header.

There is a method CheckForceUpdate in bl_check.c.

I did program rest of the code, but not first page. First page Filled with 0xFF.

If i debug this method return 1 as expected, if the first page is filled 0xFF. 

I think this part not working correctly when power down, or bootloader program area is damaged. How can it be ?

    //
    // See if the first location is 0xfffffffff or something that does not
    // look like a stack pointer, or if the second location is 0xffffffff or
    // something that does not look like a reset vector.
    //
    pui32App = (uint32_t *)APP_START_ADDRESS;
    if((pui32App[0] == 0xffffffff) ||
       ((pui32App[0] & 0xfff00000) != 0x20000000) ||
       (pui32App[1] == 0xffffffff) ||
       ((pui32App[1] & 0xfff00001) != 0x00000001))
    {
        return(1);
    }

There is uniflash memory browser image after power down device.

I used several interface. Ethernet, Serial & CAN.

i think "program the rest of the code, then last first bytes " is not the only solution.

I think the problem is about reset vector .

I did not understand that,

Bob Crosby said:

I programed the stack pointer and reset vector starting at address 0.

I did start to program starting at APP_START_ADDRESS. 

Could you write details ?

I will work in the following day and give you feedback.

Thank you.