This is the mail archive of the ecos-discuss@sources.redhat.com 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] |
Hi,
I am relatively new to eCos and its tools.
My question is, in order to use cross-gdb to connect to a remote target that runs redboot, does the redboot has to be built as a ROM monitor?
My set up:
target: IDT79eb438, ecos 2.0 from cvs repository, HAL package from IDT for the board. cross gdb built from GDB5.3.
I built Redboot with RAM startup type( currently I don't have flash programming capability in my lab), which disabled CYGSEM_HAL_ROM_MONITOR, I do include ' include GDB stubs in HAL' and 'include GDB external break support for stubs' though. Then I run Redboot on target's RAM, and on the host side I run the cross gdb Here is what I did and got,
Jifl -- eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts --[ "You can complain because roses have thorns, or you ]-- --[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
-- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |