Difference between revisions of "Using Guiliani 2.0 RZ/A with TES eGML SDK with e2Studio"
From Guiliani
m (Marco moved page RZA e2Studio to RZA e² studio without leaving a redirect) |
|||
| Line 1: | Line 1: | ||
== Guiliani 2.0 developing on e² studio == | == Guiliani 2.0 developing on e² studio == | ||
| + | |||
| + | |||
=== Assumed knowledge === | === Assumed knowledge === | ||
* C++ | * C++ | ||
* General Handling of e² studio or eclipse | * General Handling of e² studio or eclipse | ||
| + | |||
=== Prerequisites === | === Prerequisites === | ||
| Line 8: | Line 11: | ||
* Installed e² studio V5 | * Installed e² studio V5 | ||
* Installed Segger JLink drivers | * Installed Segger JLink drivers | ||
| + | |||
=== e² studio workspace === | === e² studio workspace === | ||
| Line 18: | Line 22: | ||
* RZ_A1H_QSPI_LOADER: Loader for QSPI flash files | * RZ_A1H_QSPI_LOADER: Loader for QSPI flash files | ||
* SR_ShowRoom: The ShowRoom demo | * SR_ShowRoom: The ShowRoom demo | ||
| + | |||
==== QSPI bootloader ==== | ==== 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 ===== | ===== bin folder ===== | ||
Includes binaries for both Dual QSPI and Single QSPI flashes. | Includes binaries for both Dual QSPI and Single QSPI flashes. | ||
| + | |||
| + | |||
===== inc folder ===== | ===== inc folder ===== | ||
Holds includes. | Holds includes. | ||
| + | |||
| + | |||
===== linker_script ===== | ===== linker_script ===== | ||
Holds linker script. | Holds linker script. | ||
| + | |||
| + | |||
===== src folder ===== | ===== src folder ===== | ||
C sources | C sources | ||
| Line 45: | Line 58: | ||
|Register I/O | |Register I/O | ||
|} | |} | ||
| + | |||
| + | |||
===== startup folder ===== | ===== startup folder ===== | ||
low-level startup code | low-level startup code | ||
| Line 60: | Line 75: | ||
|Interrupt handler | |Interrupt handler | ||
|} | |} | ||
| + | |||
| + | |||
===== Boot-up sequence ===== | ===== Boot-up sequence ===== | ||
[[File:QSPI Bootloader.png|QSPI Bootloader]] | [[File:QSPI Bootloader.png|QSPI Bootloader]] | ||
| + | |||
| + | |||
===== Possible Adaptions ===== | ===== 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 ==== | ==== Board support package ==== | ||
| Line 89: | Line 109: | ||
|startup files for application | |startup files for application | ||
|} | |} | ||
| + | |||
| + | |||
===== Driver ===== | ===== Driver ===== | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 109: | Line 131: | ||
|Video display controller | |Video display controller | ||
|} | |} | ||
| + | |||
| + | |||
===== Possible Adaptions ===== | ===== Possible Adaptions ===== | ||
* Heap menagement of FreeRTOS | * Heap menagement of FreeRTOS | ||
Revision as of 12:34, 23 January 2017
Contents
Guiliani 2.0 developing on e² studio
Assumed knowledge
- C++
- General Handling of e² studio or eclipse
Prerequisites
- Installed Guiliani 2.0 SDK for Renesas RZ/A
- Installed e² studio V5
- Installed Segger JLink drivers
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