Epson S5U1C17001C, Руководство пользователя

Страница: 32 / 742

3-2
EPSOn
S5U1C17001C ManUal
(C COMPilEr PaCkagE fOr S1C17 faMily) (Ver. 1.5.0)
3 SOfTWarE DEVElOPMEnT PrOCEDUrES
As shown above, the tools included with this package handle all software processing required after creating a
source program. All basic operations except debugging are performed in the
GNU17 IDE (hereafter the IDE ).
The development flow is outlined below.
(1) Creating a project
Use the IDE to create a new project. The system will set up the project file needed to collectively manage the
software resources of the application to be developed and a workspace directory in which those resources are
stored.
(2) Creating a source program
Use the IDE editor or a general-purpose editor to create a source file and add it to the project.
(3) Building a program
Start by using the IDE to set startup options for the tools from the C compiler to the linker and linker scripts.
Then execute a build process from the IDE . The system will execute make.exe using the makefile (generated
according to the set content), generating object files in debuggable ‘elf’ format and ROM data files (psa files),
which are created by converting object files into S-record format.
The necessary processing is automatically executed sequentially in the following operations according to the
makefile.
• Compile (for C sources)
The source files are compiled by the
xgcc
C compiler, generating the object files (.o) are to be input to the
ld
linker.
• Assemble (assembler sources)
The assembler source files are assembled by the as assembler to generate the object files (.o) to be input to
the ld linker.
If the source files include preprocessor instructions, use xgcc to perform preprocessing and assembly. When
the necessary options are specified, xgcc will execute the cpp preprocessor and the as assembler.
• Link
The compilation and assembly operations described above will prepare one or multiple object files required
for subsequent processing. The
ld
linker then generates an executable object file capable of being loaded and
executed in the target ROM, namely ‘elf’ format object files that include information required for debugging,
etc.
• S-record conversion
Launches objcopy/moto2ff/sconv32 and outputs S-record-format ROM data files (psa files) from ‘elf’ format
object files.
Use the objcopy object file format conversion utility to create HEX files for writing programs to external
ROM or internal ROM from ‘elf’ format object files generated by the ld linker .
Then convert the HEX file for the internal ROM into a Motorola S2 file in which the unused area is filled
with 0xff by moto2ff and sconv32 .
Using the ROM data file created above, perform final verification of program operation on the actual target
board.
(4) Debugging
Use ‘elf’ format object files generated by the ld linker and S-record format ROM data file (psa file) to perform
verification and debugging with the gdb debugger. Although an ICD can be used to debug hardware as well as
software operation, the gdb has simulator mode that allows the PC to emulate device operations as the S1C17
Core and memory models.
Debugger setting and startup can be performed from the IDE .