Difference between revisions of "Using Guiliani 2.0 RZ/A with TES eGML SDK with e2Studio"
From Guiliani
(→Prerequisites) |
|||
| Line 1: | Line 1: | ||
| − | + | == Assumed knowledge == | |
| − | |||
| − | |||
| − | |||
* C++ | * C++ | ||
* General Handling of e² studio or eclipse | * General Handling of e² studio or eclipse | ||
| − | + | == Prerequisites == | |
* Installed [https://www.guiliani.de/mediawiki/downloads/SDK/Guiliani_2.0_SDK_GSE_RenesasRZ-A.zip Guiliani 2.0 SDK for Renesas RZ/A] | * Installed [https://www.guiliani.de/mediawiki/downloads/SDK/Guiliani_2.0_SDK_GSE_RenesasRZ-A.zip Guiliani 2.0 SDK for Renesas RZ/A] | ||
* Installed [https://www.renesas.com/en-eu/products/software-tools/tools/ide/e2studio.html e² studio V5] | * Installed [https://www.renesas.com/en-eu/products/software-tools/tools/ide/e2studio.html e² studio V5] | ||
| − | + | == e² studio workspace == | |
Select this directory as project workspace (relative to SDK directory): | Select this directory as project workspace (relative to SDK directory): | ||
| Line 22: | Line 19: | ||
| − | + | === QSPI bootloader === | |
The QSPI bootloader configures the QSPI FLASH to execute the application code at maximum speed. It can be configured for Single or Dual QSPI interfaces depending on your Hardware setup. | The QSPI bootloader configures the QSPI FLASH to execute the application code at maximum speed. It can be configured for Single or Dual QSPI interfaces depending on your Hardware setup. | ||
| − | + | ==== bin folder ==== | |
Includes binaries for both Dual QSPI and Single QSPI flashes. | Includes binaries for both Dual QSPI and Single QSPI flashes. | ||
| − | + | ==== inc folder ==== | |
Holds includes. | Holds includes. | ||
| − | + | ==== linker_script ==== | |
Holds linker script. | Holds linker script. | ||
| − | + | ==== src folder ==== | |
C sources | C sources | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 58: | Line 55: | ||
| − | + | ==== startup folder ==== | |
low-level startup code | low-level startup code | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 75: | Line 72: | ||
| − | + | ==== Boot-up sequence ==== | |
[[File:QSPI Bootloader.png|QSPI Bootloader]] | [[File:QSPI Bootloader.png|QSPI Bootloader]] | ||
| − | + | ==== Possible Adaptions ==== | |
* The application entry point can be defined by setting APPLICATION_VECTOR_TABLE. | * The application entry point can be defined by setting APPLICATION_VECTOR_TABLE. | ||
* You can choose between dual or single QSPI by choosing the Build configuration | * You can choose between dual or single QSPI by choosing the Build configuration | ||
| − | + | === Board support package === | |
{| class="wikitable" | {| class="wikitable" | ||
!|Directory | !|Directory | ||
| Line 109: | Line 106: | ||
| − | + | ==== Driver ==== | |
{| class="wikitable" | {| class="wikitable" | ||
!|Directory | !|Directory | ||
| Line 131: | Line 128: | ||
| − | + | ==== Possible Adaptions ==== | |
* Heap menagement of FreeRTOS | * Heap menagement of FreeRTOS | ||
Revision as of 10:32, 25 January 2017
Contents
Assumed knowledge
- C++
- General Handling of e² studio or eclipse
Prerequisites
- Installed Guiliani 2.0 SDK for Renesas RZ/A
- Installed e² studio V5
e² studio workspace
Select this directory as project workspace (relative to SDK directory):
SR_ShowRoom\projects\e2Studio
The opened workspace includes three projects :
- BSP: Renesas Board support package files
- RZ_A1H_QSPI_LOADER: Loader for QSPI flash files
- SR_ShowRoom: The ShowRoom demo
QSPI bootloader
The QSPI bootloader configures the QSPI FLASH to execute the application code at maximum speed. It can be configured for Single or Dual QSPI interfaces depending on your Hardware setup.
bin folder
Includes binaries for both Dual QSPI and Single QSPI flashes.
inc folder
Holds includes.
linker_script
Holds linker script.
src folder
C sources
| File/directory | Description |
|---|---|
| qspi_controller_driver | General driver for QSPI controller |
| main.c | Program entry |
| qspi_change_config.c | QSPI configuration |
| rza_io_regrw.c | Register I/O |
startup folder
low-level startup code
| File | Description |
|---|---|
| low_level_init_gcc.c | C/C++ Inititlization; call to main function |
| reset_handler.S | low-level Program entry |
| start.S | Interrupt handler |
Boot-up sequence
Possible Adaptions
- The application entry point can be defined by setting APPLICATION_VECTOR_TABLE.
- You can choose between dual or single QSPI by choosing the Build configuration
Board support package
| Directory | Description |
|---|---|
| Architecture_support | Common ARM drivers (i.e. caches) |
| Chip_support | Special RZ/A drivers |
| Driver | RZ/A peripherial drivers |
| Board_settings | Set-up for Display-It board |
| FreeRTOS | FreeRTOS Operating System |
| startup | startup files for application |
Driver
| Directory | Description |
|---|---|
| INTC | Interrupt controller |
| OSTM | Operating System Timer |
| RIIC | I²C interface |
| SCIF_UART | UART with Serial Communication Interface |
| VDC5 | Video display controller |
Possible Adaptions
- Heap menagement of FreeRTOS