• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 79 subscribers
  • Views 1329 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Bootloader and Vector Remapping for MSP430F6779

Piyush Chande
Prodigy 35 points
Other Parts Discussed in Thread: MSP430F67791

Hello.

I am working on MSP430F67791 (512KB). We need to develop a bootloader for this microcontroller which shall have the provision to receive the file for the main application over UART and save it in the External Flash Memory. After receiving the complete file and verifying the validity through checksum check, it shall load the received file in the Main Flash memory of the microcontroller. To begin with, I have allocated memory range 0x00C000 to 0x2BFFF for the Bootloader and 0x02C000 to 0x08BFFF for the application code.

I am facing some issues as described below:

Bootloader as well as Application require to use the interrupts. But in case of MSP430, the Interrupt Vector table is hardcoded to the memory range 0xFF80 to 0xFFFF, with Reset Vector at 0xFFFE. Since bootloader is supposed to be executed first, I understand that the hardcoded interrupt vector table should be available with the bootloader.

I have gone through many of the threads in the TI Forum for finding the solution.

One of the solution is using Proxy Interrupt Vector table. But this too requires the address of ISR to be 16-bit only, i.e. between 0xC000 and 0xFF7F. This is not possible for us as we have divided the Flash memory into to parts, Bootloader - residing at start of the flash memory and Application - residing at the upper section of flash memory (0x2C000 to 0x8BFFF)

Another solution is using Interrupt Vector Table remapping to RAM. I tried the remapping of interrupt vector table to RAM in a small application without using any bootloader. The code got executed, but the interrupts did not work.

My bootloader code cannot fit into 4 KBytes (i.e. 0xC000 to 0xFF7F) to allow a starting address of 16 bits for the application.

Can anyone guide me to allow bootloader as well as application code to use the interrupts?

Is it actually possible to remap the interrupt vector table to RAM for the application code. If yes, how?

How do I avoid the reset vector to be at 0xFFFE for the application code.

In case I am unclear in explaining my requirements and issues, do let me know.

Looking forward to a helpful reply soon.

Thanks in Advance.

Piyush Chande

  • 0
    Guru 34773 points
    My CDC BSL working without interrupts just fine. And it fits to 2 KByte BSL memory area.

    If max application code is < 256 KBytes then there is no need for extra external flash. BSL can store updated code to free 256 KBytes, because flashing rate (200 KByte/s) is faster than UART.
  • 0 in reply to zrno soli
    Prodigy 35 points

    Thanks for the prompt reply Zrno Soli.

    Our application code will be more than 256 KB. Hence we are using external Flash for storing the image file before programming the internal flash memory of the microcontroller.

    However, I am trying to fit my bootloader code in to 2KB BSL memory area.

    Can anyone please let me know if we can debug the BSL code through JTAG.

    I loaded the BSL code into controller through JTAG but unable to debug it.

    Regards,

    Piyush Chande

  • 0 in reply to Piyush Chande
    Guru 34773 points

    Piyush Chande said:

    However, I am trying to fit my bootloader code in to 2KB BSL memory area.

    Can anyone please let me know if we can debug the BSL code through JTAG.

    I loaded the BSL code into controller through JTAG but unable to debug it.

    At startup my BSL is copied to RAM and executed from there. Development was done in main flash area with full (UART / Mailbox) logging, because inlined logs can't fit to 2 KByte. At the end, code without logs was relocated to 2 KByte BSL area.

**Attention** This is a public forum