re: [ECOS] question about redboot

[Gary Thomas <gthomas@redhat.com>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2696 bytes --]

Are you running/building from the latest sources from CVS?  The problems
you mention (^C not working, as well as no thread support) were fixed
a few weeks ago (on 17 Sept).

On 28-Sep-2000 lqx wrote:
> 
> -----Original Message-----
> ·¢¼þÈË: Gary Thomas <gthomas@redhat.com>
> ÊÕ¼þÈË: lqx <liqx@term.star.com.cn>
> ³­ËÍ: Ecos-Discuss@Sourceware. Cygnus. Com
> <ecos-discuss@sourceware.cygnus.com>
> ÈÕÆÚ: 2000Äê9ÔÂ21ÈÕ 20:37
> Ö÷Ìâ: RE: [ECOS] question about redboot
> 
> 
>>
>>On 20-Sep-00 lqx wrote:
>>>  Hi,all
>>>  I download eCos from anoncvs, and  have got ecos running on our board
> using the CL_PS7500FE ARM
>>> processor. I have included  DM9008  ethernet chip and added our
> driver.The chip really works.I
>>> run all the  test files,they all work correctly.Now I want to use
> redboot,but how can redboot
>>> work on my board?From the document with anoncvs,I really don't know how
> to start?What I have
>>> tried is as following:
>>>
>>>  I modified redboot.RAM,and let start from ROM,then I do
>>>
>>>  #ecosconfig new edb7xxx redboot
>>>  #ecosconfig import /tmp/redboot.RAM
>>>  #ecosconfig tree
>>>  #make
>>>
>>>  Now,I wrote the install/bin/redboot.bin to my flash,and run it in the
> flash,When I run on host
>>> as this:
>>>  #minicom -o ttyS0
>>>  I received
>>>  RAM 0x00000000-0x001c0000
>>>  $T0050f:30001b00;0d:a4280000;#42
>>>  when I pressed any key on the host,I received the same
>>> messages"$T0050f:30001b00;0d:a4280000;#42"from the ecos board,what is the
> problem? Anyone can
>>> help me?
>>>
>>
>>This message indicates that your RedBoot is failing at 0x1b0030.  Look at a
> map (from
>>arm-elf-nm) or use GDB to analyze where it is failing.
>>>
>>>
>>>
> 
> Hi,all
> Now I can run redboot on my board,and I can connect redboot through insight
> 5.0 under x window,using remote tcp target,then load my applications,run my
> applications well, but I meet another problem--I can not break(use ^c) my
> application when it is running,and when the application is over,I can not
> close the gdb window either,and gdb can not connect redboot afterward,until
> I kill the gdb,and run gdb again,is that the way redboot works? If so ,it is
> too unconvenient,isn't it?Are you going to add ^c function to new redboot
> version? When will it release? If I want to do it myself,will you please
> give me a tip?
> 
> I know from the document that the redboot is thread aware,what is the
> meaning? Because when I use "info thread" in gdb ,it always report "can not
> get remote thread list",is anything I do wrong?how can I get thread info?
> 
> Any help will be highly appreciated!