Thu Apr 10 19:07:00 GMT 2003
Being a rather experienced developer using the eCos + Lauterbach
combination, I haven't either found any good way of using T32-Win
together with code compiled under Cygwin due to the problems You are
Luckily, this problem can easily be solved by switching to a Linux build
and debugging host instead - The T32 is very well working under Linux
(provided You are using the Ethernet-based HW-interface variant), and
the eCos build environment is generally better working in native Linux
If You peek around a little in Your T32 installation CD (check e.g the
t32\demo\powerpc\kernel\eCos directory), You will even find that there
is a T32 plugin providing eCos kernel awareness and some eCos menu
extensions avaliable for the T32 :-)
Happy T32-eCos debugging!
Kjell Svensson Embedded Technology Manager
Techtribe Solutions AB Tel: +46 (0)31 706 06 00
FlÃ¶jelbergsgatan 12 GSM: +46 (0)70 270 76 66
SE-431 37 MÃLNDAL Mail: email@example.com
Adolfo Lucha wrote:
> i am not sure if this the right discussion forum for my question. Sorry if it is not.
> I am developing a system with eCos on a own ppc HW. I am using T32 debugger from http://www.Lauterbach.de company. It will show me my private project files in a rigth manner but the eCos files will not be showed. The problem is that the debugger will not found the files because the path is prefixed with "/ecos-c/...". T32 is a Win32 application and can not expand such text to a drive letter. Therefore I am not able to step through the eCos code.
> I fell that there is a compiler or linker flag to say: do not use the cygwin path ("/ecos-c/"), and use the windows drive letter instead. Is not it? I did not find it :-(
> Or need I any settings in the cygwin environment? Mount flags? ECos configuration settings?
> Any Idea?
> thanks and regards,
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
More information about the Ecos-discuss