|Non-Confidential||PDF version||ARM 100897_0000_00_en|
|Home > Typical customizations > Migrating from Cortex-M3 DesignStart Eval to Cortex-M3 DesignStart Pro|
ARM recommends that you perform this migration as early as possible in your development process.
The Cortex®-M3 DesignStart™ Eval product is
packaged to provide a working FPGA targeted system out of the box. Although it is
closely based on the SSE-050 Subsystem,
which is included as part of the Cortex-M3 DesignStart Evalproduct, the
Cortex-M3 DesignStart Pro deliverables offer more flexibility, and do not specifically
target the MPS2+ FPGA platform. This results in a smaller set of peripherals
integrated in the ‘platform-specific’ group. In
Cortex-M3 DesignStart Pro, the example
integration uses a more simplified AHB peripheral subsystem connected to the TARGEXP1 master port. This
mps2_peripherals_wrapper, which includes
all the FPGA peripherals provided with the Cortex-M3 DesignStart Eval system.
When you develop a system, you may initially choose to retain some peripherals specific to the MPS2+ FPGA platform. To do this, you need to plan to partition your extensions to the system so that they can be easily integrated into the final and simpler platform-specific extension peripheral subset. You can then branch from your Cortex-M3 DesignStart Eval system by using the working Cortex-M3 DesignStart Pro Execution Testbench and modifying that example system.
If you plan to build an FPGA view of your system developed from
Cortex-M3 DesignStart Pro instead, then you
should replace every module instantiated within the
m3ds_user_partition with the equivalent modules from
Cortex-M3 DesignStart Pro. When you do this,
the closely coupled peripherals and the platform-specific extension peripherals are
imported as two separate modules. You will need to rewire all the peripheral I/O to suit
your new design.
When you do the migration, ARM recommends the following: