Table of Contents
Advertisement
Each time the unit is powered on or reset, the BBL will look to see if an application is already installed, and if so,
control is passed to the ABL which then launches the application. If no application is found, the BBL will search for the
necessary files on an SD Card or USB drive, and if found, installs the ABL before passing control to it so the application
may be installed and booted. If no application and no SD card/USB drive are found, the user is prompted to install an
SD card/USB drive with the appropriate files.
The demo kit comes with an SD card on which are several demos for the user to try out. Out of box, the uEZGUI
comes preinstalled with a unique 'bootloader application' that allows the user to select one of these demos to install.
The uEZ bootloader can be configured using the file named INSTALL.INI located in one of the demo applications'
folders. When "rename=true", and after an application is installed, the file INSTALL.INI in the root of the SD card is
renamed to INSTALL.FIN, which when viewed by the uEZ bootloader, will indicate that the application installation is
final. At this point, every time the uEZGUI is powered on or reset, the bootloader will boot to the installed
application.
This can be undone by renaming the INSTALL.FIN file back to INSTALL.INI. Doing so will allow the uEZ bootloader to
boot back to the demo selection screen and permit the user to install a different application.
12. µEZ Project Maker
FDI has provided a project maker to help create new projects for EZ GUI hardware. It is available for download at
https://sourceforge.net/projects/uez/.
To create a new project, run the executable file included with uEZ, and follow the onscreen instructions. It will create
a demo project using an emWin example GUI that will provide basic peripheral functionality. The project maker
speeds up the development process for new applications. Example projects are ready to be compiled and
programmed onto EZ GUI hardware using the included J-Link debugger, with no extra project configuration
necessary.
For this uEZGUI the Crossworks project option will generate a second project for the secondary M0 core. Both
projects should be opened and built in Crossworks. Then the primary project (for the M4 core) will automatically
program the secondary project's application. Using the secondary project, the J-Link can be connected to the second
core.
Note: The M0 core project now has full FreeRTOS, SEGGER RTT/SystemView, and uEZ API support.
Note: When connected to the M0 core, the J-Link cannot program the LPC4357's flash banks. This is why the M4
project automatically programs the M0 project's output. The option "Additional Load File[0]" enables this
programming and can be easily removed if the M0 core is not used.
Note: The second core must be enabled in the shared Config_Build.h file, otherwise it will not be started.
Note: The Crossworks projects use variables to subtract RAM or Flash from the M4 core to assign to the M0 core. By
default, the last 64KB of each 512KB Flash bank (128KB total), the entirety of SRAM2, and the last 512KB of SDRAM is
assigned. See the following "Memory Map Macros" for typical application configuration: SDRAM_CM0_SIZE,
FLASHA_CM0_SIZE, FLASHB_CM0_SIZE, SPIFI_CM0_SIZE. When changing a macro size, make sure to use the same
size in both *.hzp project files to prevent overlap. If SRAM banks were swapped between cores, assembly startup
code will need to be modified. uEZ_Platform_Start_Additonal_Cores() needs to be updated to match the starting
flash address if changed.
13. Software
3/27/2024
µ E Z G U I U s e r ' s M a n u a l
Copyright ©2024, Future Designs, Inc.
P a g e
| 8
Revision 1.4
Advertisement
Table of Contents
