This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Tue, 5 Nov 2002, Grant Edwards wrote: > > 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. This is the strongest reason to have formal remote protocol specification however, it is completely lost on our GDB gurus. > > > 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 > Thanks, Aleksey ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |