ON Semiconductor RSL10 CPU Support Package
This package contains project templates and system files for the ON Semiconductor RSL10.
CrossWorks Version 4 Installation Instructions
- To install this support package
-
- Click the Tools > Package Manager menu option to open the package manager window.
- Right click on the ON Semiconductor RSL10 CPU Support Package entry and select Install Selected Packages.
- Click Next to take you to the summary page.
- Click Next to install the package.
- Click Finish to close the package manager window.
- Click the Tools > Show Installed Packages.
- Click on the ON Semiconductor RSL10 CPU Support Package link to view the package and its contents.
- To manually install this support package
-
- If you have not done so already, follow the CMSIS 5 CMSIS-Core(M) Support Package and CrossWorks Tasking Library Package installation instructions.
- Download the file RSL10.hzq using your web browser.
- Click the Tools > Manually Install Packages menu option.
- Select the file you have just downloaded to install the package.
- Click the Tools > Show Installed Packages.
- Click on the ON Semiconductor RSL10 CPU Support Package link to view the package and its contents.
Release Notes
4.0
- Initial Release.
Documentation
Creating RSL10 Projects
To create a new RSL10 project
- Select the File > New > New Project menu item.
- Select the appropriate Generic RSL10 from the Categories list.
- Select the required project template type from the Templates list.
- Set the required project name and location directory.
- Click OK.
To build and debug an application the runs in Flash memory
- Select the project to work on by using the Project > Set Active Project menu option.
- Select the configuration you require by using the Build > Set Active Build Configuration menu option.
- Right click on the project node in the project explorer and select the Flash placement property.
- Build the project by using the Build > Build Project menu option.
- Connect to the appropriate target in the target window.
- Download and start debugging the current project by using Debug > Start Debugging.
To make the application startup from reset
- Right click on the project node in the project explorer and select Properties...
- In the properties window scroll down to the Preprocessor Options section.
- Type STARTUP_FROM_RESET into the Preprocessor Definitions property editor.
RSL10 Project Specifics
Target Processor
Once a project has been created you can select different target processors by right clicking on the project node in the project explorer and selecting the Target Processor entry.
Selecting the target processor will specify the memory map that is used for the build and debug. You can view the selected memory map by right clicking on the project node in the project explorer and selecting Edit Memory Map.
Section Placement
CrossStudio for ARM supports RSL10 projects running applications in a number of different memory configurations. You can select the memory configuration you require by setting the Section Placement property.
For RSL10 projects the set of placements are:
- Flash application runs in internal Flash memory.
- RAM application runs in RAM memory.
Stack and Heap Sizes
The default stack and heap sizes are set to be 1024 and 1024 bytes by default when a project is created.
Target Startup Code
The startup code startup_RSL10.s is common to all RSL10 processors. There are a set of preprocessor defines that configure the startup code and are documented in the startup file itself. The startup code calls out to a weak symbol SystemInit with the stack pointer set to the top of of SRAM. The SystemInit function can be used to set the CPU clock or configure any external memories prior to the C initialisation code as such it cannot access initialised static data. Note that the SystemInit() function is called with the stackpointer pointing to the end of the SRAM.
The startup code declares symbolic names (and weak implementations) for each interrupt service routine, for example the RTC_SEC_IRQHandler function will be called when the RTC second match interrupt occurs. The names of the interrupt service routines match those in the CMSIS header file. If you are porting code that has application specific interrupt service routines then you can use preprocessor definitions to rename the declared symbolic name for example RTC_SEC_IRQHandler=RTC_SEC_DriverIRQHandler.
Target Reset Script
The reset script RSL10_Target.js is used by the debugger to reset the target board.