Embedded Artists / lpc4088_displaymodule_fs_aid

The purpose of this application is to allow easy manipulation of the QSPI file system from a PC (**NOTE**: Application doesn't work with update to mbed OS 5 since USB Device support is currently not available for LPC4088)

Dependencies:   DMBasicGUI DMSupport

The purpose of this application is to allow easy manipulation of the QSPI file system from a PC.

The application makes the LPC4088 Display Module appear as a USB Memory Stick when connected to a PC. The PC will see the current content of the QSPI file system plus an image file of the file system that can be downloaded and (at a later time) be used to restore the file system to it's current state.

To use this application:

1. Download the lpc4088_displaymodule_fs_aid application using drag-n-drop and then reset the board
2. Optionally start a terminal program to read the status messages from the application
3. Connect a USB cable to the mini USB slot on the back of the LPC4088 Display Module, and then to the PC
4. The PC will install drivers if needed and then the USB Memory Stick will be available as a new drive
5. Modify the file system to suit your needs
6. With the USB cable still connected, press the USER/ISP/SW1 button on the LPC4088 Display Module
7. The application will now:
   1. disconnect the USB Memory Stick
   2. write all changes to the QSPI flash memory
   3. create a new image file of the updated QSPI file system and store it in the .current/ folder
   4. connect the USB Memory Stick again
8. Continue from step 5. until satisfied

Note 1: If the QSPI doesn't have a file system on it or to replace the current one with a new, possibly of a different size, file system just add a file with the name format_qspi_X_mb (where X should be replace with the wanted file system size in Mb). For a 10 Mb file system the file name should be format_qspi_10_mb.

Note 2: The file system that is exposed is a copy (in SDRAM) of the QSPI file system. The reason for this is that the USBMSD class requires a FAT file system.

Note 3: The image files created in step 7.3 above will be a *.fsX file (where the 'X' is the size of the file system in MB so *.fs1 for a 1MByte file system). The *.fsX file extensions are recognized by the HDK and can be used to drag-n-drop to the MBED drive in the same way as the *.bin files are. A *.fsX file will not overwrite the program stored in internal flash.

/*
 *  Copyright 2014 Embedded Artists AB
 *
 *  Licensed under the Apache License, Version 2.0 (the "License");
 *  you may not use this file except in compliance with the License.
 *  You may obtain a copy of the License at
 *
 *    http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software
 *  distributed under the License is distributed on an "AS IS" BASIS,
 *  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 *  See the License for the specific language governing permissions and
 *  limitations under the License.
 */

#ifndef DM_BOARD_CONFIG_H
#define DM_BOARD_CONFIG_H

// Template to use for the project-specific settings. Copy this file to your project,
// rename it to dm_board_config.h and uncomment the wanted features below:

#define DM_BOARD_USE_USB_DEVICE
// #define DM_BOARD_USE_USB_HOST
// #define DM_BOARD_USE_MCI_FS
#define DM_BOARD_USE_QSPI_FS
// #define DM_BOARD_USE_QSPI
#define DM_BOARD_USE_DISPLAY
// #define DM_BOARD_USE_TOUCH
// #define DM_BOARD_USE_ETHERNET
#define DM_BOARD_USE_FAST_UART
// #define DM_BOARD_USE_USBSERIAL_IN_RTOSLOG
// #define DM_BOARD_DISABLE_STANDARD_PRINTF
// #define DM_BOARD_ENABLE_MEASSURING_PINS
// #define DM_BOARD_USE_REGISTRY

#endif