[ECOS] Question about redboot

[ECOS] Question about redboot

[john albert]

Hi,
I am trying to rebuild redboot. When I run the following command
ecosconfig new psim redboot, I got

U CYGDBG_HAL_COMMON_CONTEXT_SAVE_MINIMUM, new inferred value 0
U CYGFUN_LIBC_STRING_BSD_FUNCS, new inferred value 0
U CYGPKG_NS_DNS_BUILD, new inferred value 0
C CYGBLD_BUILD_REDBOOT, "requires" constraint not satisfied: 
CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT

Then, I open hal.cdl and look for
"cdl_component CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT". Inside the component, 
there is the line "active_if  CYGINT_HAL_VIRTUAL_VECTOR_SUPPORT". 
CYGINT_HAL_VIRTUAL_VECTOR_SUPPORT is not defined in the same file.
To work around, I lock the line "active_if  
CYGINT_HAL_VIRTUAL_VECTOR_SUPPORT", and type the command again, it seems to 
be OK. After building the tree and compiling, I receive these errors:
powerpc-ecos-eabi-gcc -c  -I/local/nam/redboot-psim/install/include 
-I/local/nam/ecos/packages/hal/common/current 
-I/local/nam/ecos/packages/hal/common/current/src 
-I/local/nam/ecos/packages/hal/common/current/tests -I. 
-I/local/nam/ecos/packages/hal/common/current/src/ -mcpu=603 -msoft-float 
-Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef 
-Woverloaded-virtual -g -O2 -ffunction-sections -fdata-sections -fno-rtti 
-fno-exceptions -fvtable-gc -finit-priority -Wp,-MD,src/hal_if.tmp -o 
src/hal_common_hal_if.o 
/local/nam/ecos/packages/hal/common/current/src/hal_if.c
/local/nam/ecos/packages/hal/common/current/src/hal_if.c: In function 
`reset':
/local/nam/ecos/packages/hal/common/current/src/hal_if.c:186: warning: 
implicit
declaration of function `HAL_PLATFORM_RESET'
/local/nam/ecos/packages/hal/common/current/src/hal_if.c:196:2: #error " no 
RESET_ENTRY"
/local/nam/ecos/packages/hal/common/current/src/hal_if.c: At top level:
/local/nam/ecos/packages/hal/common/current/src/hal_if.c:244: 
`CYGNUM_HAL_VIRTUAL_VECTOR_COMM_CHANNELS' undeclared here (not in a 
function)
/local/nam/ecos/packages/hal/common/current/src/hal_if.c:244: size of array 
`comm_channels' has non-integer type
/local/nam/ecos/packages/hal/common/current/src/hal_if.c: In function 
`hal_if_init':
/local/nam/ecos/packages/hal/common/current/src/hal_if.c:904: 
`CYGNUM_HAL_VIRTUAL_VECTOR_COMM_CHANNELS' undeclared (first use in this 
function)
/local/nam/ecos/packages/hal/common/current/src/hal_if.c:904: (Each 
undeclared identifier is reported only once
/local/nam/ecos/packages/hal/common/current/src/hal_if.c:904: for each 
function
it appears in.)
/local/nam/ecos/packages/hal/common/current/src/hal_if.c:926: 
`CYGNUM_HAL_VIRTUAL_VECTOR_DEBUG_CHANNEL' undeclared (first use in this 
function)
make[1]: *** [src/hal_if.o.d] Error 1
make[1]: Leaving directory `/local/nam/redboot-psim/hal/common/current'
make: *** [build] Error 2

I dont know how to fix it. Please help.




_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

[ECOS] question about redboot......

[Roy Chung]

Hi! I am using redboot to boot my linux in the intel xscale 
platform(lubbock).
    However,    I found that the current version of Redboot support 
ethernet thorugh the SMC chip and CF only . But I want the one for PCMCIA, 
do anyone have idea about how t odo it? Actually I deicde to use NB2000 
PCMCIA ethernet card to be the   ethernet controller!!
thx a lot

_________________________________________________________________
Chat with friends online, try MSN Messenger: 
http://messenger.microsoft.com/tc 


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] question about redboot......

[Jonathan Larmour]

Roy Chung wrote:
> Hi! I am using redboot to boot my linux in the intel xscale
> platform(lubbock). However,    I found that the current version of
> Redboot support ethernet thorugh the SMC chip and CF only . But I want
> the one for PCMCIA, do anyone have idea about how t odo it? Actually I
> deicde to use NB2000 PCMCIA ethernet card to be the   ethernet
> controller!! thx a lot

Intel have never contributed their lubbock port. So as far as the net eCos
project is concerned, there's not much we can do as they are unknown
sources. Ask Intel to do the obvious thing.

Jifl
-- 
eCosCentric       http://www.eCosCentric.com/       <info@eCosCentric.com>
--[ "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

re: [ECOS] question about redboot

[lqx]

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

-----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!

re: [ECOS] question about redboot

[Gary Thomas]

[-- 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!

[ECOS] question about redboot

[lqx]

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

 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?
 
                                                            
lqx
 
 
 

RE: [ECOS] question about redboot

[Gary Thomas]

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.
> 
> 
>