TM4C129ENCPDT: TM4C129ENCPDT

Hey Charles,

Thank you for the reply.

I found boot_demo1 from the example. It has the Jump to Bootloader function, which I can work with on my application. One issue I faced during building is 

ROM_SysTickIntDisable();
ROM_SysTickDisable();

These 2 functions can't be accessed from my source file. It shows as an implicit declaration of the function.

1. Do you know which header file I should include to resolve the error?

I can see that  (*((void (*)(void))(*(uint32_t *)FlashAddress)))(); is called in order to jump to the specified FlashAddress. But I found that it is to call the SVP handler to the application in the FlashAddress. 

2. Is it not necessary to change the Program Counter to the address and main stack pointer address also? or will it work only with this?

Hey Charles,

One more update. I got the SysTickIntDisable(), and SysTickDisable(); and my errors are resolved. But I could not perform the jump to the application.

Do you have any idea about that?

Hi,

Rahul Santhosh said:

One more update. I got the SysTickIntDisable(), and SysTickDisable(); and my errors are resolved.

Glad you that revolve the compile issue. 

Rahul Santhosh said:

But I could not perform the jump to the application.

You would need to program the bootloader to the flash to 0x0 through JTAG. After this is done, the only thing you have in the flash is the bootloader. There is no application yet. The bootloader will not jump to the application since the application is not there yet. The bootloader will still be in the bootload mode waiting for you to provide the application code (e.g. boot_demo1). If you are using the LaunchPad which I will strongly suggest you do to get it working before you move on to your own custom board, you can just use LM flash program to provide the boot_demo1.bin. The application will then be downloaded to the flash through the UART interface. Once the application is downloaded, the next time the device is started, the bootloader will find a valid application at 0x4000 and it will then jump to the application. 

- See below to use LM flash program to select serial interface for download. You need to provide your own COM port.

- Next provide the boot_demo1.bin and hit 'Program'.

Hi Charles,

Thanks for the reply.

But I have already flashed the application's hex file to the specified location, which is 0x10010. And my bootloader lies at 0x00000000.

I have individually tested the application code and it is working fine. Below are the code portions of the bootloader to jump to the application.

This is the function for GoToApplication().

void GoToApplication(uint32_t FlashAddress)
{
        IntMasterDisable();

        // We must make sure we turn off SysTick and its interrupt before entering
        // the boot loader!
        SysTickIntDisable();
        SysTickDisable();

        //
        // Disable all processor interrupts.  Instead of disabling them
        // one at a time, 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;

        //
        // Return control to the application.  This is a call to the SVC handler in the application.

        (*((void (*)(void))(*(uint32_t *)FlashAddress)))();
}

But Application 1 is not executing.

In  my reply I already said the application image must align to 1024bytes. Is your application image starting at 0x10010? This is not aligned to 1k boundary. Why don't you try the stock example first (both the serial bootloader and the boot_demo1) and get to to work before you make any modification. 

For your kind information, my application is aligned to 1024 bytes. The application image is starting at 0x10010. but I have provided the length to be 384 KB, so it is aligned to 1024 bytes.

I'm adding the snapshot below.

anyway, I'll try with the example in the meantime. 

Hello Charles,

Thank you for your support.

This solved my issue.