Known Problems

The supported symbols are:

    CYGNUM_HAL_STACK_SIZE_MINIMUM
and
    CYGNUM_HAL_STACK_SIZE_TYPICAL

which are recommended for a thread which does almost nothing, such as the idle thread and for one which makes substantial use of system calls, a more typical thread, respectively. If your threads have stack variables of any size, you should add their size (in bytes) to these symbols when defining your stacks.

If you enable asserts (CYGPKG_INFRA_DEBUG, CYGDBG_USE_ASSERTS), then threads with stack size smaller than CYGNUM_HAL_STACK_SIZE_MINIMUM will not be allowed to start; an assert will fire, halting the system.

These symbols are typically made up of others which may be defined depending on architecture; an example is CYGNUM_HAL_STACK_FRAME_SIZE which represents the stack space needed to make a function call. See your cyg/hal/hal_arch.h file for details, or others that it includes, for the stack requirements may vary with the number of simultaneously active interrupt sources, for example.

In future releases, these sizes may change depending on configuration. Specifically, some target architectures are undergoing HAL improvements for future releases that will enable all interrupt processing code, including DSRs, to execute on a single separate dedicated stack; this will mean that normal thread stacks do not all need to have enough space for fielding all possible simultaneous interrupts, but instead just enough space to enter the interrupt system once. This may reduce memory requirements considerably, depending on target, and so the values of these symbols will reduce to match in versions where this feature is supported.

The supported symbols are:

    CYGNUM_HAL_STACK_SIZE_MINIMUM
and
    CYGNUM_HAL_STACK_SIZE_TYPICAL

which are recommended for a thread which does almost nothing, such as the idle thread and for one which makes substantial use of system calls, a more typical thread, respectively. If your threads have stack variables of any size, you should add their size (in bytes) to these symbols when defining your stacks.

If you enable asserts (CYGPKG_INFRA_DEBUG, CYGDBG_USE_ASSERTS), then threads with stack size smaller than CYGNUM_HAL_STACK_SIZE_MINIMUM will not be allowed to start; an assert will fire, halting the system.

These symbols are typically made up of others which may be defined depending on architecture; an example is CYGNUM_HAL_STACK_FRAME_SIZE which represents the stack space needed to make a function call. See your cyg/hal/hal_arch.h file for details, or others that it includes, for the stack requirements may vary with the number of simultaneously active interrupt sources, for example.

In future releases, these sizes may change depending on configuration. Specifically, some target architectures are undergoing HAL improvements for future releases that will enable all interrupt processing code, including DSRs, to execute on a single separate dedicated stack; this will mean that normal thread stacks do not all need to have enough space for fielding all possible simultaneous interrupts, but instead just enough space to enter the interrupt system once. This may reduce memory requirements considerably, depending on target, and so the values of these symbols will reduce to match in versions where this feature is supported.

    mips-tx39-elf-run --board=jmr3904 --memory-region 0xffff8000,0x900 --memory-region 0xffffe000,0x4 --memory-region 0xb2100000,0x4 --sockser-addr=localhost:XXXX cygmon50.rom

    #XCC = arm-elf-gcc -mcpu=arm7di

*** ecosSWtools-arm-990321.orig/src/bfd/elf32-arm.h
--- ecosSWtools-arm-990321/src/bfd/elf32-arm.h
***************
*** 913,917 ****
                + input_section->output_offset + 8);
        value -= offset;
!       value = value >> howto->rightshift;
  
        value &= 0xffffff;
--- 913,920 ----
                + input_section->output_offset + 8);
        value -= offset;
!       value = (bfd_signed_vma)value >> howto->rightshift;
!       if ((bfd_signed_vma) value > 0x7fffff ||
!         (bfd_signed_vma) value < -0x800000)
!       return bfd_reloc_overflow;
  
        value &= 0xffffff;