This is the mail archive of the
ecos-discuss@sourceware.cygnus.com
mailing list for the eCos project.
RE: Re: MBX Board
- To: Jonathan Larmour <jlarmour at redhat dot co dot uk>
- Subject: RE: [ECOS] Re: MBX Board
- From: Gary Thomas <gthomas at redhat dot com>
- Date: Tue, 30 May 2000 15:29:29 -0600 (MDT)
- Cc: ecos-discuss at sourceware dot cygnus dot com, "amassa at cts dot com" <amassa at cts dot com>
The MBX boards we have actually have two separate flash chips. Based on the
use of jumper J4 you can select between the two. My board has EPPC-bug in one
flash chip and eCos GDB stubs in the other.
On 30-May-00 Jonathan Larmour wrote:
> "amassa@cts.com" wrote:
>>
>> I am using the MBX860 board for development. This board has the EPPC-bug
>> firmware programmed into flash.
>>
>> What I want to do is to be able to download my own programs - initially just
>> a basic program. I would like to have GDB support present as well.
>>
>> I don't know if I need to compile a gdb stub and download that first into
>> RAM and then use that to connect insight and download my application code.
>>
>> I would like to leave the EPPC-bug firmware as is in ROM, and not program
>> over it.
>
> You should include the GDB support in the application you download, in the
> form of GDB stubs.
>
> To do this, go to the "eCos HAL" package and under "Source-level debugging
> support" there is the "Include GDB stubs in HAL" option (aka
> CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS), which you should enable. If you want
> Ctrl-C to work with stubs enabled, you should also enable GDB break support
> for stubs (CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT).
>
> Jesper may have some more input.
>
> Jifl
> --
> Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
> "Plan to be spontaneous tomorrow." || These opinions are all my own fault
>