gdb and jtag

[Grant Edwards]

Hi Bill,

> The BDI2000 implements the "remote" protocol directly:
> 
> (gdb) target remote 192.168.2.5:2001

Excellent.  I think that's what EPI should have done also, but
they were worried that customers would have to upgrade firmware
when GDB changed.

> You can also telnet to the box and drive it manually from a CLI:
> 
> $ telnet 192.168.2.5
> BDI2000> load 0xa0200000 zImage binary
> Loading zImage, please wait...
> Loading program file passed
> BDI2000> bi 0x8029abfc
> BDI2000> go 0xa0200000
> - TARGET: target has entered debug mode
> BDI2000> ti  /* step one instruction */

That's cool.  Don't know that I'd want to do a lot of debuggin
that way, but it's nice to have a fallback position.

Thanks!

-- 
Grant Edwards
grante@visi.com

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com