ID |
CVS fix |
Problem |
Workaround
|
eCos 1.3.1 documentation |
19739 |
|
The need to specify the architecture-specific version of GDB
while following the tutorial text in
'Getting Started with eCos' is not clear. |
The user should substitute the appropriate architecture-
specific version of GDB (eg 'sparclite-elf-gdb') wherever 'gdb'
is encountered in the documentation. |
19871 |
|
HAL stack size symbols are not documented. |
HALs now define some symbols to make it easier to create stacks
of a suitable size for the system in question, if writing code
for many different eCos targets. This is target-dependent
because of the varying memory needs for stack frames and for
interrupt handling.
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. |
19935 |
|
The configuration option
CYGVAR_KERNEL_INSTRUMENT_EXTERNAL_BUFFER is documented but
is no longer accessible from the eCos Configuration Tool. |
Do not use CYGVAR_KERNEL_INSTRUMENT_EXTERNAL_BUFFER. |
20024 |
|
The eCos serial filter tool (ser_filter) is not documented. |
Refer to the file ser_filter.txt located in the tools/bin
directory under the base of the eCos installation for details
of this tool. |
100880 |
|
The prebuilt test, thread_gdb, does not contain the
GDB stubs, which means that C-c does not work as
described in the Running Applications on the Target
chapter on ARM, SH and PowerPC architectures. |
Set breakpoint on cyg_test_exit before starting the test. |
eCos 1.3.1 |
17814 |
|
During installation under Windows, InstallShield incorrectly calculates the amount of disk
free-space. It calculates available space on a character, not
disk allocation unit basis. As the eCos distribution contains
many small files, this can lead to installation being allowed
to proceed when there is insufficient disk space available. |
Please manually check that enough disk space exists after
consulting the installation requirements in the documentation. |
19787 |
|
Under certain circumstances, the eCos Configuration Tool may
output a linker script fragment which has a forward reference.
This results in a linker error of the form "LOADADDR forward
reference ..." when attempting to build the eCos tests. |
When modifying memory layouts, ensure that the order of memory
sections is preserved during any section relocation. |
19822 |
|
When using the GDB 'thread' command to switch context to
another thread, any register values changed by the user are not
preserved. |
There is no known workaround. |
19922 |
|
eCos will not build correctly on a file system which has been
mounted using the Cygwin binary mode. |
Do not attempt to mount eCos-related file systems in binary
mode. |
20020 |
|
Certain eCos tests do not start the scheduler and so interrupts
are disabled. When run on hardware, these tests cannot be
interrupted using Ctrl-C. |
There is no workaround. |
100885 |
|
PowerPC QUICC Serial driver cannot reliably change
baud rate on the fly as is required in the serial4
test. |
There is no workaround. |
101058 |
|
Control-C only interrupts a running program when the
program prints output using the HAL diagnostic output,
when device drivers are enabled.
The problem is that device drivers install their own
serial ISR which replaces the one used normally to
process Ctrl-C. |
Disable device driver support, or force the program to use
the diagnostic output when required. |
101059 |
|
Kernel exceptions fail to be delivered when GDB stubs
are included. This causes the except1 and kexcept1
tests to fail. |
Do not enable the 'Include GDB stubs' option if the
program uses kernel exceptions. |
101393 |
|
Libc malloc does not use all available memory on
target. |
Manually set malloc memory pool as large as required
(CYGNUM_LIBC_MALLOC_MEMPOOL_SIZE). |
901428 |
|
CMA230, EBSA285, EDB7xxx: k/except1 and signal2
tests do not succeed in
generating bad alignment exceptions. |
There is no known workaround. |
902157 |
|
Changing compiler flags with either the eCos Configuration
Tool or by editing the ecos.ecc save file does not result in
automatic rebuild of all affected files. |
Delete all object files with 'make clean'. |
902158 |
|
Deleting object files in the build tree does not cause
them to be rebuilt. |
Delete the dependency file (.d) to force a rebuild. |
902226 |
|
CygMon on ARM does not handle breakpoints after the
application starts to execute. |
Use eCos GDB stubs instead of CygMon in the ROM/FLASH,
or include GDB stubs support when configuring eCos for
the application. |
902232 |
|
Problems may be encountered when using the eCos Configuration
Tool to save eCos build trees with very long paths. |
Limit the length of build tree paths if this problem is
encountered. |
902250 |
|
Enabling the CPU cache on the AEB rev C causes random failures. |
As a temporary measure, the CPU cache is not enabled by
default for the AEB Rev C. |
902255 |
|
eCos Config and Package Admin Tools may not have the correct
installation path if you re-install eCos in a different
location. The paths to the Build and User tools may also be
incorrect in the Config Tool. |
On startup, the eCos Config tool will prompt you for the
path to the packages directory within eCos (e.g.
D:\Red Hat\eCos\packages) and the Package Admin Tool will
prompt you for the ecos.db file (e.g.
D:\Red Hat\eCos\packages\ecos.db).
To correct the paths for the Build tools, in the Config Tool
select 'Tools->Paths->Build Tools' and enter the correct
path (e.g.
D:\Red Hat\eCos\ecos-99r1-991015\H-i686-cygwin32\bin) and
for the User tools select 'Tools->Paths->User Tools' and
enter the correct path (e.g.
D:\cygnus\gnupro\i686-cygwin32\
i686-cygwin32\unsupported-990805\H-i686-cygwin32\bin). |
902263 |
|
Some targets use the same architecture or platform HAL, but
with different options. Prebuilts are only provided
for the target's default configuration. |
You will have to build tests for the target yourself
in order to verify that GDB communicates properly with
the target. |
902538 |
|
Enabling GDB break support on PID in Thumb mode
causes the kernel to fail with random memory
corruption. |
Do not enable GDB BREAK support in this release.
The next CVS snapshot will contain a fix for this problem. |
902540 |
|
Viewing [headers] with 'associated viewer' in the
Configation Tool does not work. |
Specify the viewer as 'use this viewer'. Problems have
been observed using WordPad to view headers. Notepad
seems reliable. |
Tools for eCos 1.3.1 |
17574 |
|
The Insight target settings dialog can display the
selected serial communication speed incorrectly when a
radix other than 10 has been selected. |
Avoid use of the 'set radix' command. |
17614 |
|
Mixing some operations between the Insight GUI and
console window can cause problems. |
Avoid use of the Insight console window where possible. |
18007 |
|
GDB cannot cope with executables whose absolute pathnames are
longer than 128 characters. This is only a problem when gdb is
used with hardware. The built in simulators are OK. The failure
mode is that the application will download correctly, but then
GDB terminates with an error. |
Only attempt to run applications located in a path consisting
of less than 128 characters. |
18585 |
|
GDB does not allow the value of variables of type 'bool' to be
changed. |
There is no known workaround. |
18615 |
|
GDB and GDBTk do not list/display inline functions correctly
for object files which have been created without the gcc -O2
flag. |
Use the -O2 flag of gcc to create object files which call
inline functions. |
18694 |
|
GDB shows the code associated with a weak symbol when an
alternative symbol definition has been provided. |
The developer may comment out the weak definitions. |
19388 19968 19970 19981 101030 |
|
Certain entries in a GDB backtrace may be incorrect and the
backtrace may be incomplete. The nature of these errors
is target-dependent. |
There is no known workaround. |
19978 |
|
Sometimes the download progress dialog is not opened
when starting a download in Insight. |
Download progress is shown in the main window's
status bar. |
19980 |
|
The dots identifying breakpoints sometimes change
color from pink (thread-breakpoint) to red (global
breakpoint). |
The tooltip displayed when the pointer is moved over
a breakpoint dot shows if the breakpoint is
thread-specific or global. |
20402 |
|
PowerPC Simulator fails with 'events.c:165: assertion failed -
(events->time_from_event >= 0) == (events->queue !=
NULL)' |
There is no known workaround. |
100877 |
|
PowerPC: The list of threads presented in Insight when setting a
thread-specific breakpoint may contain garbage
ASCII strings from the GDB protocol. |
This does not happen when using the 'info thread' or
Thread List window. Use these to find the thread
number and use the GDB CLI console to set the
thread-specific breakpoints. |
100881 |
|
Insight's Download Progress window doesn't
reset the progress bars if it is left open after an
earlier download. |
Close the Download Progress window before starting a new
download. |
100886 |
|
Insight has bad performance when doing many operations
on threads. This is because the complete thread state of all
threads is transferred from the target every time the target
stops. |
Close unnecessary windows in Insight so that Insight
does not need to update as much information when the target
stops. |
100914 |
|
Insight reports "DOWNLOAD CANCELLED" even after a
successful download. |
Ignore this message. |
101035 |
|
Ctrl-C fails to work as expected inside a 'bash'
shell. If GDB is used in command-line mode, sometimes
both it and the bash shell will receive the Ctrl-C. In
other cases, if programs are run in the background in
a bash shell, and Ctrl-C is pressed, then those
programs will be terminated as well. |
Use GDB in graphical mode (Insight) and use the
'console' window to control GDB. Alternatively start
GDB from within a normal 'Command Prompt' window,
setting the path up in the same way as the develop.bat
file in the eCos installation directory. For other
programs, there is no known workaround. |
101036 |
|
GDB can lose track of what breakpoints are installed
when per-thread breakpoints are used with eCos. It
reports hitting a 'SIGTRAP Trace/Breakpoint trap',
instead of just reporting a breakpoint.
This problem only appears rarely. |
Ignore the extra traps and just continue anyway. |
101293 |
|
If asked to show the thread list after hitting a
breakpoint in a function with varargs/string inputs
which are long, Insight may hang. |
If you experience this problem, use the CLI 'info
threads' command instead of the thread list window. |
902240 |
|
On Windows Control-C used in GDB CLI mode also affects bash,
causing further input to randomly be read by either
GDB or bash. |
The problem does not occur when launching GDB from a
DOS command prompt. |
902267 |
|
When running an application which produces large amounts
of output, selecting 'q <return>' when presented with
the prompt:
---Type <return> to continue, or q <return> to quit---
gdb will hang if you select 'q <return>' and then try to
exit gdb, reattach to the target, or other various gdb
operations. |
Do not select 'q <return>'. Instead select '<return>'
and press ^C to halt the application. Alternatively, remove
the prompts with the GDB command 'set height 0'. |
eCos 1.2.1 documentation |
17569 |
|
The appearance of asterisks against configuration items in the
eCos Configuration Tool is not mentioned in the documentation. |
Users should note that an asterisk appears against
configuration items which have changed since the configuration
was last saved. |
19731 |
|
With a SPARClite target, kernel exceptions may not work as
expected when support for CygMon is enabled. This is the
default configuration when building for the SPARClite
evaluation board with RAM startup. This problem occurs
because certain hardware exception vectors are handled
directly by CygMon, rather than eCos. As a result, registering
an exception handler for those exceptions will not have any
effect. This problem is exhibited in the kernel tests except1
and kexcept1. |
For the exceptions to be handled correctly the option
CYG_HAL_USE_ROM_MONITOR_CYGMON must be disabled in
. However, it will no longer be possible to
interactively debug the target. |
19737 |
|
Use of the BASE_DIR expression within Chapter 12 of
'Getting Started with eCos' is not clear. |
The user should substitute the location of the eCos repository
wherever BASE_DIR is encountered (eg /usr/local/ecos-1.2.1).
Note also that pkgconf.tcl is located at
BASE_DIR/packages/pkgconf.tcl and not as otherwise specified in
this chapter. |
19739 |
|
The need to specify the architecture-specific version of GDB
while following the tutorial text in Chapter 13 of
'Getting Started with eCos' is not clear. |
The user should substitute the appropriate architecture-
specific version of GDB (eg 'sparclite-elf-gdb') wherever 'gdb'
is encountered in the documentation. |
19871 |
|
HAL stack size symbols are not documented. |
HALs now define some symbols to make it easier to create stacks
of a suitable size for the system in question, if writing code
for many different eCos targets. This is target-dependent
because of the varying memory needs for stack frames and for
interrupt handling.
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. |
19935 |
|
The configuration option
CYGVAR_KERNEL_INSTRUMENT_EXTERNAL_BUFFER is documented but
is no longer accessible from the eCos Configuration Tool. |
Do not use CYGVAR_KERNEL_INSTRUMENT_EXTERNAL_BUFFER. |
19954 |
|
The format of output generated by the eCos Configuration Tool
while running tests is not documented. |
Developers should note that each line of output is prefixed by
which indicates the time at which the line was
output.
tt.t is the time from the start of test execution
aa.a is the time since the output of the previous line
Both quantities are measured in CPU seconds in the case of
execution in simulators and in elapsed seconds in the case of
execution on hardware. |
19987 |
|
The command necessary to run CygMon in the simulator is
incorrect in the GNUPro Reference for eCos (Toshiba TX39)
document. |
The correct command line is as follows:
mips-tx39-elf-run --board=jmr3904 --memory-region 0xffff8000,0x900 --memory-region 0xffffe000,0x4 --memory-region 0xb2100000,0x4 --sockser-addr=localhost:XXXX cygmon50.rom |
20017 |
|
In chapter 2 of 'Getting Started with eCos', the section 'ROM
monitor image' does not mention the need to enable GDB stub
support when debugging capabilities are required for the ARM
evaluation boards. |
Enable all the options grouped under 'Source-level debugging'
in the eCos Configuration Tool. |
20024 |
|
The eCos serial filter tool (ser_filter) is not documented. |
Refer to the file ser_filter.txt located in the tools/bin
directory under the base of the eCos installation for details
of this tool. |
20025 |
|
In the examples Makefile, the XCC line is incorrect for the
ARM AEB-1 evaluation board. The line for the ARM PID board
is correct. |
Modify the line by removing an 'm' character such that the
line reads:
#XCC = arm-elf-gcc -mcpu=arm7di |
eCos 1.2.1 |
17485 19988 |
|
In certain situations, pkgconf does not remove old header
files when packages are added/removed from an existing
build tree. |
When packages are added/removed, the developer is recommended
to save the revised configuration to a new build tree. |
17814 |
|
During installation under Windows, InstallShield incorrectly calculates the amount of disk
free-space. It calculates available space on a character, not
disk allocation unit basis. As the eCos distribution contains
many small files, this can lead to installation being allowed
to proceed when there is insufficient disk space available. |
Please manually check that enough disk space exists after
consulting the installation requirements in the documentation. |
18848 |
|
The Linux getitimer returns [period, period] rather than
[period, period-elapsed]. This causes HAL_CLOCK_READ to fail.
The Linux synthetic target support is an alpha release. |
There is no known workaround. |
18956 |
|
An additional linker output section is required when linking
eCos tests compiled for the i386-linux synthetic target with
CYGIMP_LIBC_MALLOC_CXX_DELETE_CALLS_FREE enabled. The Linux
synthetic target support is an alpha release. |
Add a .rel.got linker-defined memory section to the memory
layout when building eCos under these conditions. |
19234 |
|
When using the eCos based GDB stub with the MN10300 target,
the downloaded program cannot be executed. |
Only use provided CygMon ROM monitor with the MN10300. |
19235 |
|
When using the eCos based GDB stub with the TX39 target,
the GDB 'info threads' command lists one thread only. |
Use provided CygMon ROM monitor with the TX39. |
19676 |
|
When running under Windows 95, the eCos Configuration Tool
does not always display any errors detected during the
loading of an eCos repository. |
There is no known workaround. |
19695 |
|
The cache locking macros (HAL_DCACHE_LOCK(),
HAL_DCACHE_UNLOCK(), HAL_ICACHE_LOCK(), HAL_ICACHE_UNLOCK())
for the TX39 may not lock the intended memory region. |
The developer may implement alternative code to lock the
cache if this functionality is required. |
19732 |
|
Under certain conditions, it is possible for the eCos
Configuration Tool to enter a state where it will ignore user
requests to exit. |
Exit the Configuration Tool using the Task Manager. |
19742 |
|
Under Windows 95, the eCos Configuration Tool may cause an
exception in USER.EXE while disabling an eCos package.
Windows 95 support is currently Beta. |
There is no known workaround. |
19787 |
|
Under certain circumstances, the eCos Configuration Tool may
output a linker script fragment which has a forward reference.
This results in a linker error of the form "LOADADDR forward
reference ..." when attempting to build the eCos tests. |
When modifying memory layouts, ensure that the order of memory
sections is preserved during any section relocation. |
19799 |
|
Linker-defined memory sections which are defined to follow
a user-defined memory section may not be displayed or output
correctly by the eCos Configuration Tool. |
Avoid specifying memory layouts where a linker-defined section
follows a user-defined section. |
19822 |
|
When using the GDB 'thread' command to switch context to
another thread, any register values changed by the user are not
preserved. |
There is no known workaround. |
19823 |
|
The eCos serial4 test may report an error when running
ser_filter under Sun Solaris. This is because serial ports on
the Sun cannot be configured to use two stop bits. |
There is no known workaround. |
19908 |
|
Use of the 'Find' dialog box within the eCos Configuration
Tool under the Japanese version of Windows NT 4.0 may generate
an exception. |
Avoid use of the 'Find' dialog if this problem is encountered.
|
19912 |
|
If compiler optimization level is set to -O0, then in very
rare circumstances the MN10300 HAL cache macros can cause
lockups. |
Do not disable optimization when using the HAL cache macros. |
19919 |
|
The eCos Configuration Tool may generate an exception if a
build is stopped while the configuration header files are being
written. |
Avoid stopping the build during this phase of the build
process. |
19921 |
|
Problems may be encountered when using the eCos Configuration
Tool to save eCos build trees with very long paths. |
Limit the length of build tree paths if this problem is
encountered. |
19922 |
|
eCos will not build correctly on a file system which has been
mounted using the Cygwin binary mode. |
Do not attempt to mount eCos-related file systems in binary
mode. |
19942 19947 |
|
The protocol used for negotiating a new serial configuration
in the eCos serial tests is not reliable when the host machine
has a high load. |
There is no known workaround. A new implementation is planned. |
19961 |
|
The eCos Configuration Tool may generate an exception if the
user cancels the message box "Press OK when the target is reset
ready for test download" when running tests. |
Always respond 'OK' to this message box. |
19976 |
|
If the user halts the execution of a series of tests from the
eCos Configuration Tool, the tool may be left in a state where
it is unable to restart test execution. |
Exit and restart the configuration tool. |
19991 |
|
There is an race condition in the eCos stress_threads test
which can cause failures to be erroneously reported if the
bitmap scheduler has been configured. |
There is no known workaround. |
20020 |
|
Certain eCos tests do not start the scheduler and so interrupts
are disabled. When run on hardware, these tests cannot be
interrupted using Ctrl-C. |
There is no workaround. |
GNU tools for eCos 1.2.1 and CygMon |
18007 |
|
GDB cannot cope with executables whose absolute pathnames are
longer than 128 characters. This is only a problem when gdb is
used with hardware. The built in simulators are OK. The failure
mode is that the application will download correctly, but then
GDB terminates with an error. |
Only attempt to run applications located in a path consisting
of less than 128 characters. |
18034 |
|
The Windows hosted compiler must be provided with file
extension when using the "-o" flag. If no extension is provided
the compilation fails with an unrelated and misleading error. |
Always specify an extension when using "-o" |
18585 |
|
GDB does not allow the value of variables of type 'bool' to be
changed. |
There is no known workaround. |
18615 |
|
GDB and GDBTk do not list/display inline functions correctly
for object files which have been created without the gcc -O2
flag. |
Use the -O2 flag of gcc to create object files which call
inline functions. |
18694 |
|
GDB shows the code associated with a weak symbol when an
alternative symbol definition has been provided. |
The developer may comment out the weak definitions. |
19388 19968 19970 19981 |
|
Certain entries in a GDB backtrace may be incorrect and the
backtrace may be incomplete. The nature of these errors
is target-dependent. |
There is no known workaround. |
19885 |
|
Setting $pc at the TX39 '(gdb)' prompt can cause GDB to core
dump. |
There is no known workaround. |
19945 19946 |
|
The PowerPC simulator does not correctly communicate certain
exception conditions to GDB. This causes the eCos kexcept1,
signal2 and except1 tests to fail. |
There is no known workaround. |
|
|
When linking code with PC REL24 branches, the ARM
bfd linker does not complain nor modify the branch
instruction when the offset overflows, it just
generates code that branch anywhere. The attached patch
should fix this problem.
Reported by Robin Farine <advanc@dial.eunet.ch>
|
*** 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;
|
|
|
ARM linker problem: the '--gc-sections' linker
flag can cause the linker to discard C++ virtual functions.
Reported by Robin Farine <advanc@dial.eunet.ch>
|
Patch supplied by Catherine Moore
(clm@redhat.com)
|
|
|
The GDB in ecosSWtools-990319-src.tar.gz gets
enumerated bitfields wrong for the synthetic Linux
target. Reported by Andrew Lunn <andrew.lunn@ascom.ch>
|
Upgrade to the latest net release of GDB.
|
eCos 1.1 |
17814 |
|
Windows only problem. InstallShield incorrectly calculates the
amount of disk free-space. It calculates available space on a
character, not disk allocation unit basis. As the eCos
distribution contains many small files, this can lead to
installation being allowed to proceed when there is
insufficient disk space available. |
Please manually check that enough disk space exists after
consulting the installation requirements in the documentation. |
18003 |
|
The Windows based eCos Configuration Tool does not support
early versions of Internet Explorer - version 2 or earlier.
When accessing help in the Configuration Tool, the browser
may display errors regarding the URL that it was invoked
with. This is due to an inability to handle URL fragments. |
Install Internet Explorer version 3 or later, or Netscape.
Note that Netscape cannot however provide an integrated
browser pane within the Configuration Tool. |
GNU tools for eCos 1.1 and CygMon |
16573 |
|
On the TX39 and MN10300, the CygMon command line "load"
command does not function correctly. |
Use gdb to load binaries into the target system using the GDB
support built into CygMon. Optionally, on the TX39 we provide a
simple srecord downloader "loaders/tx39-jmr3904/sload.bin"
that can be used for this purpose. |
17046 |
|
Only applicable to the MN103002 evaluation board hardware.
Breakpoints do not function after a watchdog exception fires. |
No known workaround. |
17831 18000 |
|
The TX39 simulator does not support simulation of the external
interrupt configuration register (located at 0xffffe000). This
correctly leads to the "intr0" and "kintr0" eCos testcases
failing when run under the simulator. |
Do not access this register in the simulator. |
17974 |
|
The MN103002 simulator does not support simulation of the
on-chip watchdog timer. This correctly leads to the "watchdog"
eCos testcase failing. |
Do not access the watchdog device in the simulator. |
18007 |
|
GDB cannot cope with executables whose absolute pathnames are
longer than 128 characters. This is only a problem when gdb is
used with hardware. The built in simulators are OK. The failure
mode is that the application will download correctly, but then
GDB terminates with an error. |
Only attempt to run applications located in a path consisting
of less than 128 characters. |
18034 |
|
The Windows hosted compiler must be provided with file
extension when using the "-o" flag. If no extension is provided
the compilation fails with an unrelated and misleading error. |
Always specify an extension when using "-o" |
18036 |
|
When using the PowerPC simulator built in to GDB, GDB only
displays the top stack frame, and it is not possible to select
any other stack frame. |
None. |
18056 |
|
GDB can occasionally run out of memory when repeatedly loading
applications into the simulator. |
If you experience this problem, simply exit GDB and restart. |
18085 18001 |
|
TX39 (net release only) problem connecting to simulated
CygMon. Following the instructions in the documentation will
not result in successful connection to a standalone simulator
running a simulated CygMon. |
To connect to a simulated CygMon it is necessary to run GDB
first, setting "target remote localhost:xxxx", and then
immediately start the standalone simulator from a different
shell. |
18086 |
|
TX39 GDB deletion of assembler breakpoints within interrupt
handlers can cause problems. This problem does not occur in the
TX39 simulator. |
Only ever disable interrupt handler assembler breakpoints, do
not delete them. |
18110 |
|
TX39 "si" and "ni" commands can cause problems in a
multi-threaded environment. In certain circumstances GDB can
get confused by a thread context switch when single stepping.
This is a rare occurrence, but results in control of the target
being lost. |
If this occurs, hit ^C to regain control of the target. |
18122 |
|
PowerPC GDB stub BREAK support is only partial implemented in
this release. When a user interrupts execution, GDB doesn't
display the context of the running thread. |
Use the "thread" command to select the context of any other
thread you wish to view. |