• Locked Locked
  • Replies 4 replies
  • Subscribers 119 subscribers
  • Views 5639 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Keil RTX and bootloading

Johan Moraal
Note: This was originally posted on 25th January 2011 at http://forums.arm.com

Hi all.

I've recently written a secondary bootloader for NXP LPC17xx devices. The design is relatively simple: All our products have embedded serial flash connected with an SPI bus to the micro. The user application is responsible to load a binary image onto the serial flash. When the bootloader starts, it checks the serial flash for a binary image. If one is not found, it jumps to the user application. If one is found, it verifies the integrity of the image by doing a CRC check. If the check passes it begins to update the LPC's flash from the binary image on the serial flash.

I've confirmed that the bootloader application is working properly. Firstly I checked the LPC's flash with a ULINK Pro and made sure the bootloader is not accidentally overridden. Then I uploaded a small application that reads and verifies a large chunk of flash and blinks a led. All these tests succeeded and I'm confident my bootloader works properly.

The problem arises when I try to upload an application which uses the Keil RL-ARM real time OS. When I upload this type of application, nothing happens. I traced the problem with a ULINK and I found that the trace stops at SVC_Handler in startup_LPC17xx.s.

All our RL-ARM based applications run in privileged mode. I know the RTOS uses SVC to access hardware etc in privileged mode.

Is there something I should do in the bootloader in order to support RL apps?
Parents
  • Note: This was originally posted on 21st August 2011 at http://forums.arm.com

    Johan

    I have a booloader running on 0x00000000 and another application starting 0x00002000, where the first read the external
    flash and copy the firmware upgrade to 0x00002000 and jump the pc for it.

    So What do I need modify on

    startup_lpc17xx.s
    core_cm3.h
    system_lpc17xx.c
    lpc17xx.h

    In order to :

    - Use the 0x00002000 application on normal and debug mode, avoiding undesired writes on bootloader region.
    - Remap all vector address to run the application normally.

    Should you explain, what the correct order of code execution before the PC go to the main ?

    Regards.

    Jean Fernandes
Reply
  • Note: This was originally posted on 21st August 2011 at http://forums.arm.com

    Johan

    I have a booloader running on 0x00000000 and another application starting 0x00002000, where the first read the external
    flash and copy the firmware upgrade to 0x00002000 and jump the pc for it.

    So What do I need modify on

    startup_lpc17xx.s
    core_cm3.h
    system_lpc17xx.c
    lpc17xx.h

    In order to :

    - Use the 0x00002000 application on normal and debug mode, avoiding undesired writes on bootloader region.
    - Remap all vector address to run the application normally.

    Should you explain, what the correct order of code execution before the PC go to the main ?

    Regards.

    Jean Fernandes
Children
No data