This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: using GDB without ROM Monitor


On 01/12/2011 07:08 AM, Christian Kraus wrote:
Hallo,

We want to use the GDB Stub together with our application, we do not want to use the GDB/Redboot ROM Monitor
and we want to debug only one thread. While we debugging this thread, the others threads should not suspended or stopped.
The debugging should be done by GDB and Eclipse.
We do not exactly know if this is posible with ecos with the GDB.

Sorry, no. Once you are interacting via GDB, all else stops, interrupts, threads, etc.


We are still using ecos 2.0 release. We using the STR912 microcontroller. We have porting the ecos to this Controller by ourselves.


We have now include the GDB Stub support into the target. There was no error durring compilation.
After flashing the binary the target printed out some chars on the serial debug port.

That's the application telling you that it's ready to talk via the GDB protocol. Most likely, something like $O1234#99 which is an output string.

Then we start to connect to the target with GDB. First it seems that it works, but we get SIGTRAP error, after that
the Programm counter goes to 0 and after that nothing works any more.

More details are required to help much more.


--
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]