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: GDB stub support


Hi Bernd

On 17/12/12 17:24, Bernd Schuster wrote:

> unfortunately I couldn`t get GDB working as expected. 
> 
> At the moment, I`m able to run Redboot at my target system - mips32
> 24kc processor as ROMRAM version. When redboot starts, I`m able to
> see all messages from the redboot bootloader by my serial port ttyS0
> (configurated with 115200 baud). After that redboot starts my
> application which is located at the addr 0x800400BC by a short boot
> script. 
> 
> Now, I`m trying to add GDB support by using the same serial interface
> ttyS0. I`m not totally sure if that could be already the problem,
> because my application also puts some messages to this serial interface. 
> 
> When I enable GDB with the following commands I can see that cutecom -
> terminal programm - will go from the open to the close state. That`s
> seems a correct behaviour to me. Furthermore I got a very small message
> on the serial terminal - something like that: 
> 
> RedBoot> 
> RedBoot>+$#00

You have two host-side applications competing for incoming characters
arriving on a single serial port. In the above example, your terminal
emulator has received characters intended for GDB. You must close your
terminal program before attempting to connect to RedBoot's GDB stub.

It is perfectly feasible to use a single channel for both debug and
diagnostics as you suggest. You should configure eCos (for your
application build) with CYG_HAL_STARTUP == "RAM" and with
CYGSEM_HAL_USE_ROM_MONITOR enabled. You should then find that (by
default) diagnostic/trace messages from your application are routed via
the GDB stub and appear within your GDB session on the host.

For avoidance of doubt, you can use the GDB "load" command to download
your application to RAM when debugging an application configured for RAM
startup. It is not necessary to load it at the "RedBoot>" prompt.

I hope this helps...

John Dallaway
eCos maintainer
http://www.dallaway.org.uk/john

-- 
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]