This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Debug Error
- To: "Jonathan Larmour" <jlarmour at redhat dot com>
- Subject: Re: [ECOS] Debug Error
- From: "james chen" <james_ch1 at sina dot com>
- Date: Wed, 21 Mar 2001 14:23:49 +0800
- Cc: <ecos-discuss at sources dot redhat dot com>
>james chen wrote:
>>
>> When I debug eCos example between insight5.0 and redboot, when
goes
>> into hal_if_init(hal_if.c). it will response nothing(that is say redboot
>> doesn't send packages back to insight).
>Does it work if you don't try and debug this function? Depending on what
>version of hal_if.c you have, and your configuration, you might find that
>trying to debug hal_if_init is doomed to failure as it changes the debug
>channel midway.
first I set breakpoint in cyg_start, it doesn't reach this breakpoint, so I
debug step by step and get no response at hal_if_init. if I skip debug
hal_if_init. it is still no response.
my CPU is ARM7TDMI, and I use the default configure in eCos HAL packages
>> When redboot already run in ROM, does I need to re-call
hal_if_init
>> function in my hal_hardware_init function?
>You mean in your RAM startup application? Then yes. As ever, use the
>existing implementations in eCos as your guide.
>> if I releaes a version of eCos, how to config eCos HAL package?
>Sorry, this question seems a bit vague. Can you please clarify it?
sorry, I mean the component of CYGPKG_HAL_ROM_MONITOR, it seems that it
correlate to ROM monitor and applications doesn't it, is it right? :-)
Jifl, thanks very much!