[ECOS] connecting gdb to target

[ECOS] connecting gdb to target

[Christoph Csebits]

hi

i have an MPC860T based board and 
i have working threads and SCC2 serial
driver (diagnostics).
(mbx based port -> cvs version May 7 2001 )

cat /dev/ttyS1 gets 
+

(Ack in initialize_stub)

when inserting breakpoint() in my main
function it gets:

+$T05thread:00000001;40:00026d78;01:000308c4;#63

so far so good (i guess):
But gdb doesnt connect to the target:

starting gdb like this:

(gdb) set remotebaud 115200
(gdb) target remote /dev/ttyS1
Remote debugging using /dev/ttyS1

waits forever.

Another problem is that my board 
is featured with a hardware watchdog
which must be triggered within a second.

Calling breakpoint() stops my watchdog
triggering thread -> board reset.

Any suggestions how to deal with?

best regards, christoph

Re: [ECOS] connecting gdb to target

[Jonathan Larmour]

Christoph Csebits wrote:
> 
> cat /dev/ttyS1 gets
> +
> 
> (Ack in initialize_stub)
> 
> when inserting breakpoint() in my main
> function it gets:
> 
> +$T05thread:00000001;40:00026d78;01:000308c4;#63
> 
> so far so good (i guess):
> But gdb doesnt connect to the target:
> 
> starting gdb like this:
> 
> (gdb) set remotebaud 115200
> (gdb) target remote /dev/ttyS1
> Remote debugging using /dev/ttyS1
> 
> waits forever.

Are you sure it's really at 115200? Try enabling remote protocol debugging
with "set remotedebug 1"
 
> Another problem is that my board
> is featured with a hardware watchdog
> which must be triggered within a second.
> 
> Calling breakpoint() stops my watchdog
> triggering thread -> board reset.
> 
> Any suggestions how to deal with?

You could something in the loop in
hal/common/VERSION/src/generic-stub.c:getpacket() to reset your watchdog
there.

We should probably add a HAL_STUB_IDLE() callback macro or something.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine