 RealView Libraries and Floating Point Support Guide | |
| Home Products Events Support | |
On-Line Manuals
RealView Libraries and Floating Point Support Guide
Preface Introduction The C and C++ Libraries About the C and C++ libraries
Features of the C and C++ libraries Namespaces Writing reentrant and thread‑safe code Introduction to reentrancy and thread‑safety Use of static data in the C libraries The __user_libspace static data area Managing locks in multithreaded applications Using the ARM C libraries with a multithreaded app Thread‑safety in the ARM C libraries Thread‑safety in the ARM C++ libraries Building an application with the C library Using the libraries with an application Building an application for a semihosted environme Building an application for a non semihosting envi Building an application without the C library Integer and FP helper functions Bare machine integer C Bare machine C with floating‑point Exploiting the C library The standalone C library functions Tailoring the C library to a new execution environ How C and C++ programs use the library functions __rt_entry Exiting from the program __rt_exit() __rt_lib_init() __rt_lib_shutdown() Tailoring static data access Tailoring locale and CTYPE using assembler macros Selecting locale at link time Selecting locale at runtime Defining a locale block LC_CTYPE data block LC_COLLATE data block LC_MONETARY data block LC_NUMERIC data block LC_TIME data block _get_lconv() localeconv() setlocale() _findlocale() The lconv structure Tailoring locale and CTYPE using C macros Selecting locale at link time Selecting locale at runtime Macros and utility functions _get_lc_ctype() _get_lc_collate() _get_lc_monetary() _get_lc_numeric() _get_lc_time() _get_lconv() localeconv() setlocale() _findlocale() __LC_CTYPE_DEF __LC_COLLATE_DEF __LC_TIME_DEF __LC_NUMERIC_DEF __LC_MONETARY_DEF __LC_INDEX_END The lconv structure Tailoring error signaling, error handling, and pro _sys_exit() errno __rt_errno_addr() __raise() __rt_raise() __default_signal_handler() _ttywrch() __rt_fp_status_addr() Tailoring storage management Avoiding the ARM‑supplied heap and heap‑using Support for malloc Tailoring the runtime memory model The memory models Controlling the runtime memory model Writing your own memory model __user_initial_stackheap() __user_setup_stackheap() __user_heap_extend() __user_heap_extent() __user_stack_cleanup_space() __rt_heap_extend() __rt_stack_postlongjmp() Tailoring the input/output functions Dependencies on low‑level functions Target‑dependent input/output support functions _sys_open() _sys_close() _sys_read() _sys_write() _sys_ensure() _sys_flen() _sys_seek() _sys_istty() _sys_tmpnam() _sys_command_string() #pragma import(_main_redirection) Tailoring other C library functions clock() _clock_init() time() remove() rename() system() getenv() _getenv_init() Selecting real‑time division ISO implementation definition ISO C library implementation definition Standard C++ library implementation definition C library extensions atoll() strtoll() strtoull() printf() snprintf() vsnprintf() lldiv() llabs() wcstombs() alloca() strlcpy() strlcat() _fisatty() __heapstats() __heapvalid() Library naming conventions Placing ARM libraries Helper libraries Identifying library variants The C Micro-library Floating‑point SupportBuilding an application for a semihosted environment
  | |||
  |  | ||
| |||
| Home > The C and C++ Libraries > Building an application with the C library > Building an application for a semihosted environment | |||
If you are developing an application to run in a semihosted environment for debugging, you must have an execution environment that supports ARM or Thumb semihosting, and has sufficient memory.
The execution environment can be provided by either:
using the standard semihosting functionality that is present by default in, for example, RVISS, ISSM, RealView ICE and RealMonitor
implementing your own handler for the semihosting calls. See Appendix A Semihosting in the Compiler User Guide.
See Overview of semihosting dependencies for a list of functions that require semihosting.
It is not necessary to write any new functions or include files if you are using the default semihosting functionality of the library.
RVISS and ISSM support semihosting and have a memory map that enables the use of the library. RVISS and ISSM use memory in the host machine and this is normally adequate for your application.
The ARM debug agents support semihosting but the memory map assumed by the library might require tailoring to match the hardware being debugged. However, it is easy to tailor the memory map assumed by the C library. See Tailoring the runtime memory model.
You can also mix the semihosting functionality with new input/output functions. For example, you can implement fputc() to output directly to hardware such as a UART, in addition to the semihosted implementation. See Building an application for a non semihosting environment for information on how to re‑implement individual functions.
After an application has been developed in a semihosted debugging environment, you can move the application to a non hosted environment by one of the following methods:
Remove all calls to semihosted functions. See Avoiding semihosting.
Re‑implement the lower‑level functions, for example,
fputc(). See Building an application for a non semihosting environment. You do not have to re‑implement all semihosted functions. You must, however, re‑implement the functions that you are using in your application.Implement a handler for all the semihosting calls.
| Copyright © 2007 ARM Limited. All rights reserved. | ARM DUI 0378A |
 PDF version | |
| Home > The C and C++ Libraries > Building an application with the C library > Building an application for a semihosted environment | |
| |
| Contact Site Map Press Privacy | Copyright © 2008 Keil™, An ARM® Company. All rights reserved. |
