LPC Bootloader - Revision history

Preet: /* The Basics */

2014-02-04T17:54:37Z

‎The Basics

Preet at 17:50, 4 February 2014

2014-02-04T17:50:56Z

Preet at 15:53, 7 June 2012

2012-06-07T15:53:28Z

New page

== The Basics ==
* The Development Board used in SJSU courses contain Hyperload Bootloader pre-loaded, and a non-erasable Manufacturer Bootloader also exists.
* The term Hyperload refers to Windows '''Hyerpload''' program, and also a corresponding '''Hyperload Bootloader''' on the chip.
* If using Hyperload, your project's loader file (*.ld) tells the compile to compile a program with offset of 4K because the first 4K is where Hyperload bootloader lives.

== Bootloader ==
'''What is Bootloader exactly ?'''
<br/>
Bootloader is a program in a microcontroller that can communicate with your PC to load a program. So yes, it is a program that helps you program. NXP LPC processors contain factory bootloader that works over UART0 and by utilizing RESET and NMI hard wires, it can be executed to load a program onto your processor without expensive JTAG hardware programmers.

This article attempts to explain the NXP's LPC microcontroller bootloaders, and why/how Hyperload extends this functionality.

== NXP Bootloader & FlashMagic ==
NXP loads a special program that resides in their processors that helps you program over UART. FlashMagic is a Windows program that communicates with this factory bootloader to help you load a HEX file in the NXP microcontroller.

== Hyperload ==
Hyperload is a Windows based program that is suited for programming any microcontroller, not just NXP LPC microcontrollers. The reason why it is used with the SJSU Development package is because it helps you program 10-20 times faster than NXP bootloader with FlashMagic. Here is an outline of the steps to use Hyperload:
# Use FlashMagic to load a Hyperload bootloader (Secondary Bootloader)
# Compile future programs with Flash Offset of 4K
# Load all future programs with Hyperload

=== LPC Boot Process ===
# If the NMI pin is LOW and RESET is toggled, LPC processors start from the top of memory, where the LPC factory bootloader lives.
#: This factory bootloader communicates with '''FlashMagic''' Windows program to load a program to the controller.
# Upon a normal RESET without NMI being LOW, the LPC starts from Address 0x0000.0000
# This is where Hyperload lives, and it communicates with Windows Hyperload program to load a program starting from address 4K
# Once Hyperload is finished executing, or it cannot communicate with Windows Hyperload program, it starts your program that lives at starting address 4K

<br/>
[[File:TutorialImage_BootloaderMemoryMap.png‎|left|frame|Bootloader Memory Map]]

@@ Line 2: / Line 2: @@
 *  The Development Board used in SJSU courses contain Hyperload Bootloader pre-loaded, and a non-erasable Manufacturer Bootloader also exists.
 *  The term Hyperload refers to Windows '''Hyerpload''' program, and also a corresponding '''Hyperload Bootloader''' on the chip.
-*  If using Hyperload, your project's loader file (*.ld) tells the compile to compile a program with offset of 64K because the first 64K is where Hyperload bootloader lives.
+*  If using Hyperload, your project's loader file (*.ld) tells the compiler to compile a program with offset of 64K because the first 64K is where Hyperload bootloader lives.  A large portion of this 64K is just spare memory because actual code-size of hyperload on the chip is only about 6K.  The motivation was to reserve all 4K sectors leaving 32K sectors for your program.
 == Bootloader ==

@@ Line 2: / Line 2: @@
 *  The Development Board used in SJSU courses contain Hyperload Bootloader pre-loaded, and a non-erasable Manufacturer Bootloader also exists.
 *  The term Hyperload refers to Windows '''Hyerpload''' program, and also a corresponding '''Hyperload Bootloader''' on the chip.
-*  If using Hyperload, your project's loader file (*.ld) tells the compile to compile a program with offset of 4K because the first 4K is where Hyperload bootloader lives.
+*  If using Hyperload, your project's loader file (*.ld) tells the compile to compile a program with offset of 64K because the first 64K is where Hyperload bootloader lives.
 == Bootloader ==
@@ Line 17: / Line 17: @@
 Hyperload is a Windows based program that is suited for programming any microcontroller, not just NXP LPC microcontrollers.  The reason why it is used with the SJSU Development package is because it helps you program 10-20 times faster than NXP bootloader with FlashMagic.  Here is an outline of the steps to use Hyperload:
 #  Use FlashMagic to load a Hyperload bootloader (Secondary Bootloader)
-#  Compile future programs with Flash Offset of 4K
+#  Compile future programs with Flash Offset of 64K
 #  Load all future programs with Hyperload
@@ Line 24: / Line 24: @@
 #:  This factory bootloader communicates with '''FlashMagic''' Windows program to load a program to the controller.
 #  Upon a normal RESET without NMI being LOW, the LPC starts from Address 0x0000.0000
-#  This is where Hyperload lives, and it communicates with Windows Hyperload program to load a program starting from address 4K
+#  This is where Hyperload lives, and it communicates with Windows Hyperload program to load a program starting from address 64K
-#  Once Hyperload is finished executing, or it cannot communicate with Windows Hyperload program, it starts your program that lives at starting address 4K
+#  Once Hyperload is finished executing, or it cannot communicate with Windows Hyperload program, it starts your program that lives at starting address 64K
 <br/>
 [[File:TutorialImage_BootloaderMemoryMap.png‎|left|frame|Bootloader Memory Map]]