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.

Recommendations on Expanding Flash Memory For LWIP

I am using a F28M35 processor and LWIP for serving web pages and wanted some recommendations on accommodating larger websites.  All the example LWIP projects have small webpages that fit into internal flash.  A utility called makefsfile.exe creates a flat file system that outputs to lmi-fsdata.h. The generated header file is a dead simple way to get a website running on the Concerto platform.  However, this method is limited to internal flash.

I was hoping to gets some recommendations/discussion on the best ways of expanding the flash to accommodate larger websites.  Ideally, I wish I could install a large external flash chip, boot from it, and program it using JTAG, just like I was doing with the internal flash.  I could not find promising/detailed threads on the topic.  I have some alternative ideas below, but wanted to run it by the community before I waste tons of time on an inferior implementation.

  • Serial Communication: I would need to create a new utility for creating a flat files system and a utility for adding the pages to the FLASH.  On startup a lookup table to all the pages is loaded into ram and whenever a page is requested they are loaded over SPI. Seems like a lot of work and degraded performance.
  • EPI: No clue how this works -- seems like it is mostly used for external RAM.  Have people used this with flash?  Is there going to be any performance advantage over SPI?

  • I guess another concern is how quickly LWIP can send files. The website contained on the MCU is filled with javascript libraries.  I had wanted the website site self contained so that customers could run the device disconnected from the internet.  Do you think sending a couple megabytes files is going to completely impractical?  I have not tested it for myself yet.