Network Builds

[James Yates]

After doing the configure as shown, I perform a 'make all' followed by a
'make all install'. I then use  
export RTEMS_MAKEFILE_PATH=/opt/rtems/builds/fu0018_net/sh-rtems/fu0018/

Then in the app directory I perform a make clean followed by a make
VARIANT=DEBUG.

  I should mention that this is all done under CYGWIN.


	I guess this is probably a problem with either the BSP or CPU
port I have done, but I am completely stumped.

		James


-----Original Message-----
From: Joel Sherrill [mailto:joel.sherrill at oarcorp.com] 
Sent: 16 March 2004 14:44
To: James Yates
Cc: Chris Johns; rtems-users at rtems.com
Subject: Re: Network Builds

James Yates wrote:

>I have built the new cs8900 driver into rtems using:
>
>/opt/rtems/rtems-4.6.0/configure --target=sh-rtems \
>    --enable-posix --enable-networking --disable-cxx \
>    --enable-rtemsbsp=fu0018 \
>    --prefix=/opt/rtems/builds/fu0018_net
>
>When I build a network app based on the netdemo tests, I get warnings
>and so cannot build the app. I get implicit declaration warnings for
>functions such as listen, connect, send etc. I have included
>rtems/rtems_bsdnet.h but it warns me that the directory
>/opt/rtems/sh-rtems/sys-include doesn't exist.
>
>
>     Can anyone help?
>
>  
>
How are you trying to compile the network demos?  You have to install 
the BSP and
then use the provided Makefile after setting RTEMS_MAKEFILE_PATH to
something like /opt/rtems/builds/fu0018_net/

>		James Yates
>
>-----Original Message-----
>From: Joel Sherrill [mailto:joel.sherrill at OARcorp.com] 
>Sent: 15 March 2004 17:38
>To: James Yates
>Cc: Chris Johns; rtems-users at rtems.com
>Subject: Re: Network Builds
>
>James Yates wrote:
>
>  
>
>>Port I have done is for a custom board based around an SH2 7145f cpu.
>>    
>>
>I
>  
>
>>am still in the process of testing what I have so far, but I can build
>>    
>>
>a
>  
>
>>very basic application with 3 tasks, plus main, each task simply
>>flashing an LED but using a semaphore to block each task. I also have
>>the serial driver implemented so that all 4 on-board UARTs can be
>>    
>>
>used.
>  
>
>>I do however have problems with getting the console to work, although
>>    
>>
>I
>  
>
>>think this is just a misunderstanding on my part.
>>    
>>
>
>I should have already asked... if you have any specific questions or
>issues, ask on the list.  There are plenty of people here who might
>shed some insight.
>
>Eventually, whatever changes you have which to libcpu/sh would be
>welcome.
>
>  
>
>>   I haven't done any major work on this, it is simply based on the
>>SH7045 although I have made some changes. At the moment I have rtems
>>applications running via serial connected gdb through a standard GDB
>>stub on the board that was based on the gdb_stubs project.
>>    
>>
>
>There is some shared code (libbsp/shared) which might be useful
>if you want to add thread awareness.
>
>
>  
>
>>-----Original Message-----
>>From: Joel Sherrill [mailto:joel.sherrill at OARcorp.com] 
>>Sent: 10 March 2004 12:25
>>To: James Yates
>>Cc: Chris Johns; rtems-users at rtems.com
>>Subject: Re: Network Builds
>>
>>James Yates wrote:
>>
>>
>>    
>>
>>>That would be great. Although I have attempted a cpu and bsp port for
>>>rtems, I am still a relative newbie, so any help is very much
>>>appreciated. 
>>>
>>>
>>>      
>>>
>>What CPU?  Is it a new family?
>>
>>
>>    
>>
>>>	Many thanks in advance.
>>>
>>>		James Yates
>>>
>>>-----Original Message-----
>>>From: Chris Johns [mailto:cjohns at cybertec.com.au] 
>>>Sent: 10 March 2004 06:21
>>>To: James Yates
>>>Cc: rtems-users at rtems.com
>>>Subject: Re: Network Builds
>>>
>>>James Yates wrote:
>>>
>>>
>>>
>>>      
>>>
>>>>Can anyone also point me in the direction of some
>>>>more information on using the CS8900 driver located in libchip.
>>>>
>>>>  
>>>>
>>>>        
>>>>
>>>I have an updated libchip driver for the CS8900 with a new readme
that
>>>      
>>>
>>I
>>
>>    
>>
>>>hope helps. It provides the missing doco I think you are looking for.
>>>
>>>I have cleaned up some driver issues when getting support for DIMMPC 
>>>(pc386) working and so may break some existing users of the driver.
>>>      
>>>
>The
>  
>
>>    
>>
>>>changes are worth making.
>>>
>>>Joel, is it ok if I commit the changes to head ?
>>>
>>>
>>>
>>>      
>>>
>>
>>
>>    
>>
>
>
>
>  
>