TM4C1294NCPDT: Ethernet Firmware Update

Muhammad Sobeh said:

I've tried to build MQTT client when i try to burn it usig bootloader it burns from address 0x4000

Which bootloader is this? Is this the flash-based  bootloader? If you are using the flash-based bootloader then it will program your firmware to 0x4000 if APP_START_ADDRESS is 0x4000 as defined in the bl_config.h file.  See below snippet.

//*****************************************************************************
//
// The starting address of the application. This must be a multiple of 1024
// bytes (making it aligned to a page boundary). A vector table is expected at
// this location, and the perceived validity of the vector table (stack located
// in SRAM, reset vector located in flash) is used as an indication of the
// validity of the application image.
//
// The flash image of the boot loader must not be larger than this value.
//
// Depends on: None
// Exclusive of: None
// Requires: None
//
//*****************************************************************************
#define APP_START_ADDRESS 0x00004000

//*****************************************************************************
//
// The address at which the application locates its exception vector table.
// This must be a multiple of 1024 bytes (making it aligned to a page
// boundary). Typically, an application will start with its vector table and
// this value should be set to APP_START_ADDRESS. This option is provided to
// cater for applications which run from external memory which may not be
// accessible by the NVIC (the vector table offset register is only 30 bits
// long).
//
// Depends on: None
// Exclusive of: None
// Requires: None
//
//*****************************************************************************
#define VTABLE_START_ADDRESS 0x00004000

//*****************************************************************************
//
// The size of a single, erasable page in the flash. This must be a power
// of 2.
//
// Depends on: None
// Exclusive of: None
// Requires: None
//
//*****************************************************************************
#define FLASH_PAGE_SIZE 0x4000

Muhammad Sobeh said:

then i've added the Software Update which pass the control to the bootloader to burn the updated firmware but it burns the code starts from address 0x000

Jumping from the application to the bootloader is not different than starting the bootloader to download the firmware the first time. It should update the firmware  at 0x4000 unless you call the ROM bootloader instead of the flash bootloader. See below SoftwareUpdateBegin when you call it in your application. The ROM-based bootloader will always program the firmware at 0x0. 

//*****************************************************************************
void
SoftwareUpdateBegin(uint32_t ui32SysClock)
{
//
// Disable all processor interrupts. Instead of disabling them
// one at a time (and possibly missing an interrupt if new sources
// are added), a direct write to NVIC is done to disable all
// peripheral interrupts.
//
HWREG(NVIC_DIS0) = 0xffffffff;
HWREG(NVIC_DIS1) = 0xffffffff;
HWREG(NVIC_DIS2) = 0xffffffff;
HWREG(NVIC_DIS3) = 0xffffffff;
HWREG(NVIC_DIS4) = 0xffffffff;

//
// Also disable the SysTick interrupt.
//
SysTickIntDisable();
SysTickDisable();

//
// Return control to the boot loader. This is a call to the SVC
// handler in the flashed-based boot loader, or to the ROM if configured.
//
#if ((defined ROM_UpdateEMAC) && !(defined USE_FLASH_BOOT_LOADER))
ROM_UpdateEMAC(ui32SysClock);
#else
(*((void (*)(void))(*(uint32_t *)0x2c)))();
#endif
}