LPC3250 Using the NAND Flash Secondary Bootloader

Follow

Bob Destremps

• September 17, 2010 00:51

CrossStudio Release 2.07 with LPC3250 Phytec Board Support Package Ver 2.1

I anticipated having to program the Secondary Bootloader into the NAND flash at Block 0. And separately programming an application (simple LED example) into NAND beginning at Block 2. After studying for sometime I'm at a loss as to how to achieve that.

My goal is to see the system boot from NAND flash. Pulling first the Secondary Bootloader from NAND. Then that in turn pulls the LED application from NAND and runs it. No such luck yet.

I've somewhat studied the source for the NAND Loader. It seem to write the Secondary Boot Loader to Block 0 and then I think somehow write the app to Block 2? But I'm not sure.

Is there a document describing the needed steps in detail? What is the role of each of the loaders provided? How do we control where in the NAND flash the applications are loading? Does the <right click><Program NAND> write the app beginning at block 2? Following the <right click><Program NAND> should one be able to pull the JTAG, cycle power, and see the app run?

Any guidance appreciated.

Bob

 

0

• 

  Michael Johnson

  • September 17, 2010 10:34

  There are some words on this buried in the package system

  Tools | Show Installed Packages

  Click on the "Creating Phytec LPC3250 Project"

  Look at the section "To load and debug an SDRAM application application into the NAND flash".

  You'll need to set the STARTUP_FROM_RESET #define to allow the program to startup.

  0

  Comment actions Permalink
• 

  Bob Destremps

  • September 17, 2010 21:11

  Okay. I see now. In the top of the LPC3200_Startup.s file there is a description of that define. And I will define that in the Preprocessor Definitions at the project level. Though I suppose you could do it at the startup file level just as well.

  I have a question though. Should I do this for the ARM Debug or ARM Release configuration? Or it doesn't matter. Could you give a brief summary of the differences between the two? It's hard to identify the differences going back and forth between the property settings. Maybe there is an easy way to compare?

  Thanks

  Bob

  0

  Comment actions Permalink
• 

  Michael Johnson

  • September 17, 2010 21:46

  You can define at either of these levels or "Common" if you wish it to apply to all configurations.

  I use the project explorer to see what is set at what level and in which configuration - use the V drop down on the toolbar to select the properties to be shown in folders.

  Regards

  Michael

  0

  Comment actions Permalink
• 

  Bob Destremps

  • September 17, 2010 22:01

  Michael, Could you please provide some detail about the typical differences in settings made between the debug and release configurations. Using the project explorer I've been going back and forth for a while and am having trouble finding the differences.

  Bob

   

  0

  Comment actions Permalink
• 

  Bob Destremps

  • September 17, 2010 22:07

  Oh and defining STARTUP_FROM_RESET did the trick. Thanks very much for that. You might note that the package notes you directed me to don't talk about the STARTUP_FROM_RESET define. I have version 2.1.

  Bob

  0

  Comment actions Permalink
• 

  Michael Johnson

  • September 18, 2010 07:30

  Debug configuration #defines DEBUG, sets optimisation to None and enables full debug info

  Release configuration #defines NDEBUG, set optimisation to Level 1 and sets a complier option to enable backtracing out of functions.

  The Debug and Release configurations are specified at the solution node level.

  I'll update the documentation with STARTUP_FROM_RESET on the next release.

   

  Regards

  Michael

  0

  Comment actions Permalink

Please sign in to leave a comment.