Hello world with leon2 problem

Arquer Stephane stephane.arquer at c-s.cnes.fr
Fri Jan 25 10:30:43 UTC 2008


Hello,

Thanks for the answer, effectively I added a new bsp provided with the board in my rtems-4.7.1 branch. I believed the configure was well done but it seems not to be the case. I didn't execute the ./bootstrap script effectively.
The things I did to add the new bsp are:
 - add a new .cfg file in ./src/make/custom/my_leon2.cfg
 - modification of ./src/c/src/lib/libbsp/sparc/acinclude.m4  to add my subdir

When I run the ./boostrap script there is the following error message:
Autoheader: error: AC_CONFIG_HEADERS not found in configure.ac
Automake: cannot open < ../../../../../../automake/compile.am: file not found


Thanks for the help.

sa


This is the configure.ac file for the bsp:
## Process this file with autoconf to produce a configure script.
## 
## configure.ac,v 1.9 2003/03/11 10:43:29 ralf Exp

AC_PREREQ(2.57)
AC_INIT([rtems-c-src-lib-libbsp-sparc-microsat],[_RTEMS_VERSION],[rtems-bugs at OARcorp.com])
AC_CONFIG_SRCDIR([bsp_specs])
RTEMS_TOP(../../../../../..)

RTEMS_CANONICAL_TARGET_CPU
AM_INIT_AUTOMAKE([no-define foreign 1.7.2])
RTEMS_BSP_CONFIGURE

RTEMS_PROG_CC_FOR_TARGET([-ansi -fasm])
RTEMS_CANONICALIZE_TOOLS

RTEMS_CHECK_NETWORKING

AM_CONDITIONAL(HAS_NETWORKING,test "$HAS_NETWORKING" = "yes")

RTEMS_CONFIG_BUILD_SUBDIRS(tools)

## bsp-specific options
RTEMS_BSPOPTS_SET([CONSOLE_USE_INTERRUPTS],[*],[0])
RTEMS_BSPOPTS_HELP([CONSOLE_USE_INTERRUPTS],
[The erc32 console driver can operate in either polled or interrupt mode.
Under the simulator (especially when FAST_UART is defined), polled seems to operate 
better.  It is common for a task to print a line (like the end of test message) and
then exit.  In this case, the program returns control to the simulator command line
before the program has even queued the output to the uart.  Thus sis has no chance
of getting the data out.])

RTEMS_BSPOPTS_SET([SIMSPARC_FAST_IDLE],[*],[])
RTEMS_BSPOPTS_HELP([SIMSPARC_FAST_IDLE],
[If defined, speed up the clock ticks while the idle task is running so
 time spent in the idle task is minimized.  This significantly reduces
 the wall time required to execute the RTEMS test suites.])

# Explicitly list all Makefiles here
AC_CONFIG_FILES([Makefile
clock/Makefile
console/Makefile
leon_cs8900/Makefile
gnatsupp/Makefile
include/Makefile
start/Makefile
startup/Makefile
timer/Makefile
i2c/Makefile
oslink/Makefile
wrapup/Makefile])
AC_OUTPUT

> -----Message d'origine-----
> De : André Neves [mailto:drakferion at gmail.com] 
> Envoyé : jeudi 24 janvier 2008 20:16
> À : Arquer Stephane
> Objet : re: TR : Hello world with leon2 problem (Arquer Stephane)
> 
> 
> Hello.
> 
> It is possible that you forgot to do ./bootstrap in RTEMS 
> source's root after making the changes to the BSP code, 
> before recompiling the cross-compiler. If so, the changes you 
> did were not propagated.
> 
> Hope this helps.
> - André Neves
> 
> ps: I apologise for not replying earlier. I got replies when 
> I asked questions, so I ought to deliver answers when I have them too.
> 
> On Thu, January 24, 2008 19:00, rtems-users-request at rtems.org wrote:
> > Send rtems-users mailing list submissions to
> > 	rtems-users at rtems.com
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > 	http://rtems.rtems.org/mailman/listinfo/rtems-users
> > or, via email, send a message with subject or body 'help' to
> > 	rtems-users-request at rtems.com
> >
> > You can reach the person managing the list at
> > 	rtems-users-owner at rtems.com
> >
> > When replying, please edit your Subject line so it is more specific 
> > than "Re: Contents of rtems-users digest..."
> >
> >
> > Today's Topics:
> >
> >    1. test message (Joel Sherrill <joel.sherrill at OARcorp.com>)
> >    2. Some thoughts about the flash device driver and the flashdisk
> >       block	driver (Astrid Hanssen)
> >    3. TR : Hello world with leon2 problem (Arquer Stephane)
> >    4. Re: netdemo ip and route table
> >       (Joel Sherrill <joel.sherrill at OARcorp.com>)
> >
> >
> > 
> ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Wed, 23 Jan 2008 16:00:22 -0600
> > From: "Joel Sherrill <joel.sherrill at OARcorp.com>"
> > 	<joel.sherrill at OARcorp.com>
> > Subject: test message
> > To: RTEMS Users <rtems-users at rtems.org>
> > Message-ID: <4797B8F6.30501 at oarcorp.com>
> > Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
> >
> > Hi,
> >
> > We have been doing some upgrades and this is a test.
> >
> > --joel
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Thu, 24 Jan 2008 12:52:17 +0100
> > From: "Astrid Hanssen" <Astrid.Hanssen at ghipsystems.com>
> > Subject: Some thoughts about the flash device driver and 
> the flashdisk
> > 	block	driver
> > To: rtems-users at rtems.org
> > Message-ID:
> > 	
> <"L5509BF0B3296460cBCA168E8835AFE2A.1201175563.mail-1.local*"@MHS>
> > Content-Type: text/plain;	charset="US-ASCII"
> >
> > Hello,
> >
> > I am happy to find there was a new concept invented recently, the 
> > libchip/flash device driver(s) and a flashdisk block 
> driver. Because I 
> > believe this to be a very nice thing and opens the door to many new 
> > applications, I immediately decided to integrate this to 
> the BSP I am 
> > working on.
> >
> > Its the Coldfire MCF5208 evaluation board, which contains an AMD 
> > AM29BDD160G 16/32-bit flash device. Although I already 
> started writing 
> > my own flash chip driver, now I like to switch over to the 
> chip driver 
> > format defined by flashdisk.h and the example that can be found in 
> > libchip/flash. After the flash driver will be thoroughly tested, I 
> > feel like submitting it to libchip/flash.
> >
> > However, not the whole area of the flash chip shall be available to 
> > the libblock flashdisk block driver. The device will also have to 
> > contain the RTEMS software itself as well as some type of 
> an optimized 
> > flash parameter storage system. The latter may also use the flash 
> > device driver, but not the flashdisk block driver.
> >
> > What I was now looking for is a way to let the flashdisk 
> driver know 
> > which area of the device(s) it may use and which not. 
> Unfortunately I 
> > found nothing like that yet. As this might going to be a 
> very common 
> > case (BSPs that contain a flash chip tend to have their 
> RTEMS software 
> > booting from it) perhaps there should be a method to manage this.
> > Maybe I missed something.
> > Otherwise, a solution might become necessary.
> >
> > A quick hack will be to define a board-specific chip driver that 
> > contains only the segments the flashdisk shall have access 
> to. But I 
> > would prefer a general-purpose chip library and handle such area 
> > definitions in the rtems_flashdisk_config structure. Another useful 
> > idea might be to separate the libchip flash device handlers 
> definition 
> > from the libblock flashdisk to have it more generally 
> available, but 
> > to include it and use it in flashdisk.
> >
> > I am wondering what you are thinking about this, or what I have 
> > missed.
> >
> > Astrid Hanssen
> >
> >
> > ------------------------------
> >
> > Message: 3
> > Date: Thu, 24 Jan 2008 15:10:12 +0100
> > From: "Arquer Stephane" <stephane.arquer at c-s.cnes.fr>
> > Subject: TR : Hello world with leon2 problem
> > To: <rtems-users at rtems.org>
> > Message-ID:
> > 	
> > 
> <092785B790DCD043BA45401EDA43D9B5F262AF at cst-xch-003.cnesnet.ad.cnes.fr
> > >
> >
> > Content-Type: text/plain;	charset="iso-8859-1"
> >
> > Hello,
> >
> > I'm trying to execute the hello world example compiled with rtems 
> > 4.7.1, Bsp leon2 on an AX2000 target with a LEON2-LGPL . 
> The following 
> > error is catched by grmon . For the moment I don't know where the 
> > problem is. As I explained in my previous mail, the same program 
> > compiled with rtems v4.6.6 works.
> >
> > Thanks ahead for your help.
> >
> > Sa.
> >
> > grlib> lo o-optimize/hello.exe
> > section: .text at 0x40060000, size 81520 bytes
> > section: .jcr at 0x40073e70, size 4 bytes
> > section: .data at 0x40073e78, size 3480 bytes
> > total size: 85004 bytes (89.0 kbit/s)
> > read 657 symbols
> > entry point: 0x40060000
> > grlib> run
> > IU in error mode (tt = 0x01)
> >  a7580000  00000000   unimp
> > grlib>
> >
> >
> >
> >
> >>  -----Message d'origine-----
> >> De : 	Arquer Stephane
> >> Envoy? :	mardi 22 janvier 2008 16:47
> >> ? :	rtems-users at rtems.com
> >> Objet :	Hello world with leon2 problem
> >>
> >> Hi,
> >>
> >> I'm trying to compile a simple hello_world.c example with rtems 
> >> v4.7.1 using the BSP leon2. The same example compiled with rtems 
> >> v4.6.6 runs on the target, but when I compile it with 
> rtems v4.7.1 an 
> >> error occurs just after the "go". I don't have grmon for 
> the moment, 
> >> so I don't know anything else about the error.
> >>
> >> Is there something else to configure regarding the previous rtems 
> >> version ?
> >>
> >> Thanks ahead for any help.
> >>
> >> Sa.
> >>
> >>
> >> I use the following linkcmds file:
> >> /*  linkcmds
> >>  *
> >>  *  linkcmds,v 1.4 2003/01/20 20:19:35 joel Exp
> >>  */
> >>
> >> OUTPUT_ARCH(sparc)
> >> __DYNAMIC  =  0;
> >>
> >> /*
> >>  * The memory map looks like this:
> >>  * +--------------------+ <- low memory
> >>  * | .text              |
> >>  * |        etext       |
> >>  * |        ctor list   | the ctor and dtor lists are for
> >>  * |        dtor list   | C++ support
> >>  * |        _endtext    |
> >>  * +--------------------+
> >>  * | .data              | initialized data goes here
> >>  * |        _sdata      |
> >>  * |        _edata      |
> >>  * +--------------------+
> >>  * | .bss               |
> >>  * |        __bss_start | start of bss, cleared by crt0
> >>  * |        _end        | start of heap, used by sbrk()
> >>  * +--------------------+
> >>  * |    heap space      |
> >>  * |        _ENDHEAP    |
> >>  * |    stack space     |
> >>  * |        __stack     | top of stack
> >>  * +--------------------+ <- high memory
> >>  */
> >>
> >>
> >> /*
> >>  * User modifiable values:
> >>  *
> >>  * _CLOCK_SPEED               in Mhz (used to program the
> >> counter/timers)
> >>  *
> >>  * _PROM_SIZE                 size of PROM (permissible 
> values are 128K,
> >> 256K,
> >>  *                               512K, 1M, 2M, 4M, 8M and 16M)
> >>  * _RAM_SIZE                  size of RAM (permissible 
> values are 256K,
> >> 512K,
> >>  *                               1M, 2M, 4M, 8M, 16M, and 32M)
> >>  *
> >>  */
> >>
> >> /* Default values, can be overridden */
> >>
> >> /*_CLOCK_SPEED = 8;*/ /* carte inicore */
> >> /*_CLOCK_SPEED = 5;*/ /* carte bertin */
> >> _CLOCK_SPEED = 20;
> >>
> >> _PROM_SIZE = 4M;
> >> _RAM_SIZE =  2M;
> >>
> >> /* _RAM_START = 0x60000000;*/
> >> /*_RAM_START = 0x40020000;*/
> >> _RAM_START = 0x40060000;
> >> _RAM_END = _RAM_START + _RAM_SIZE;
> >>
> >> _PROM_START = 0x00000000;
> >> _PROM_END = _PROM_START + _PROM_SIZE;
> >>
> >> /*
> >>  *  Alternate names without leading _.
> >>  */
> >>
> >> PROM_START = _PROM_START;
> >> PROM_SIZE = _PROM_SIZE;
> >> PROM_END = _PROM_END;
> >>
> >> RAM_START = _RAM_START;
> >> RAM_SIZE = _RAM_SIZE;
> >> RAM_END = _RAM_END;
> >>
> >> /*
> >>  *  Base address of the on-CPU peripherals
> >>  */
> >>
> >> _LEON_REG = 0x80000000;
> >> LEON_REG = 0x80000000;
> >>
> >> /* these are the maximum values */
> >>
> >> MEMORY
> >> {
> >>   rom     : ORIGIN = 0x00000000, LENGTH = 256M
> >> /*  ram     : ORIGIN = 0x60000000, LENGTH = 1024M */
> >>   ram     : ORIGIN = 0x40060000, LENGTH = 1024M
> >> }
> >>
> >> /*
> >>  * stick everything in ram (of course)
> >>  */
> >> SECTIONS
> >> {
> >>   .text :
> >>   {
> >>     CREATE_OBJECT_SYMBOLS
> >>     text_start = .;
> >>     _text_start = .;
> >>     *(.text)
> >>     . = ALIGN (16);
> >>
> >>     /*
> >>      * Special FreeBSD sysctl sections.
> >>      */
> >>     . = ALIGN (16);
> >>     __start_set_sysctl_set = .;
> >>     *(set_sysctl_*);
> >>     __stop_set_sysctl_set = ABSOLUTE(.);>
> >>     *(set_domain_*);
> >>     *(set_pseudo_*);
> >>
> >>     *(.eh_frame)
> >>     . = ALIGN (16);
> >>
> >>     *(.gnu.linkonce.t*)
> >>
> >>     /*
> >>      * C++ constructors
> >>      */
> >>     __CTOR_LIST__ = .;
> >>     LONG((__CTOR_END__ - __CTOR_LIST__) / 4 - 2)
> >>     *(.ctors)
> >>     LONG(0)
> >>     __CTOR_END__ = .;
> >>     __DTOR_LIST__ = .;
> >>     LONG((__DTOR_END__ - __DTOR_LIST__) / 4 - 2)
> >>     *(.dtors)
> >>     LONG(0)
> >>     __DTOR_END__ = .;
> >>
> >>     _rodata_start = . ;
> >>     *(.rodata*)
> >>     *(.gnu.linkonce.r*)
> >>     _erodata = ALIGN( 0x10 ) ;
> >>
> >>     etext = ALIGN(0x10);
> >>     _etext = .;
> >>     *(.init)
> >>     *(.fini)
> >>     *(.lit)
> >>     *(.shdata)
> >>     . = ALIGN (16);
> >>     _endtext = .;
> >>   } > ram
> >>   .dynamic	  : { *(.dynamic) 	} >ram
> >>   .jcr		  : { *(.jcr) 		} >ram
> >>   .got		  : { *(.got) 		} >ram
> >>   .plt   	  : { *(.plt) 		} >ram
> >>   .hash		  : { *(.hash)		} >ram
> >>   .dynrel	  : { *(.dynrel)	} >ram
> >>   .dynsym	  : { *(.dynsym)	} >ram
> >>   .dynstr	  : { *(.dynstr)	} >ram
> >>   .hash		  : { *(.hash)		} >ram
> >>   .data :
> >>   {
> >>     data_start = .;
> >>     _data_start = .;
> >>     _sdata = . ;
> >>     *(.data)
> >>     *(.gnu.linkonce.d*)
> >>     *(.gcc_except_table)
> >>     . = ALIGN(0x10);
> >>     edata = .;
> >>     _edata = .;
> >>   } > ram
> >>   .shbss :
> >>   {
> >>     *(.shbss)
> >>   } > ram
> >>   .bss :
> >>   {
> >>     __bss_start = ALIGN(0x8);
> >>     _bss_start = .;
> >>     bss_start = .;
> >>     *(.bss)
> >>     *(COMMON)
> >>     end = .;
> >>     _end = ALIGN(0x8);
> >>     __end = ALIGN(0x8);
> >>   } > ram
> >>   .stab . (NOLOAD) :
> >>   {
> >>     [ .stab ]
> >>   }
> >>   .stabstr . (NOLOAD) :
> >>   {
> >>     [ .stabstr ]
> >>   }
> >> }
> >>
> >>
> >
> >
> > ------------------------------
> >
> > Message: 4
> > Date: Thu, 24 Jan 2008 08:48:31 -0600
> > From: "Joel Sherrill <joel.sherrill at OARcorp.com>"
> > 	<joel.sherrill at OARcorp.com>
> > Subject: Re: netdemo ip and route table
> > To: $B<k00Jv(B <fall4ufeng at gmail.com>
> > Cc: "rtems-users at rtems.org" <rtems-users at rtems.org>
> > Message-ID: <4798A53F.2040307 at oarcorp.com>
> > Content-Type: text/plain; charset="ISO-2022-JP"
> >
> > $B<k00Jv(B wrote:
> >> hi:
> >> when i test the netdemo routine , but there is nothing 
> happen after 
> >> the console print the information :
> >> Destination Gateway/Mask/Hw Flags Refs Use Expire Interface
> >> default 192.168.1.1 <http://192.168.1.1> UGS 0 0 0 rhine_eth1
> >> 192.168.1.0 <http://192.168.1.0> 255.255.255.0 
> <http://255.255.255.0>
> >> U 0 0 1 rhine_eth1
> >> 192.168.1.1 <http://192.168.1.1> UHL 1 0 1 rhine_eth1
> >>
> > Read the README with the test. This is a simple network application 
> > for testing purposes. It can only do a few things:
> >
> > + reply to pings
> > + has echo servers on two sockets
> > + can print statistics if you type "s" at the console
> >
> > --joel
> >> and my computer's ip is 192.168.1.1 <http://192.168.1.1>, virtule 
> >> machine's ip is 192.168.1.5 <http://192.168.1.5>, target 
> board's ip 
> >> is 192.168.1.4 <http://192.168.1.4> Here is my networkconfig.h
> >>
> >> static struct rtems_bsdnet_ifconfig netdriver_config = { 
> >> "rhine_eth1", /* name */ rtems_rhine_driver_attach, /* attach 
> >> function */
> >>
> >> NULL, /* No more interfaces */
> >> "192.168.1.4 <http://192.168.1.4>", /* IP address */ 
> "255.255.255.0 
> >> <http://255.255.255.0>", /* IP net mask */ NULL, /* Driver 
> supplies 
> >> hardware address */ 0 /* Use default driver parameters */
> >> };
> >>
> >> /*
> >> * Network configuration
> >> */
> >> struct rtems_bsdnet_config rtems_bsdnet_config = { 
> &netdriver_config,
> >> NULL,
> >>
> >> 100, /* Default network task priority */
> >> 128*1024, /* Default mbuf capacity */
> >> 256*1024, /* Default mbuf cluster capacity */
> >>
> >> "rtems_host", /* Host name */
> >> "localnet.com <http://localnet.com>", /* Domain name */
> >> " 192.168.1.1 <http://192.168.1.1>", /* Gateway */ "192.168.1.1 
> >> <http://192.168.1.1>", /* Log host */ {" 192.168.1.1 
> >> <http://192.168.1.1>" }, /* Name server(s) */ {"192.168.1.1 
> >> <http://192.168.1.1>"},
> >>
> >> };
> >>
> >> Thanks for your attention.
> >>
> >
> >
> >
> > ------------------------------
> >
> > _______________________________________________
> > rtems-users mailing list
> > rtems-users at rtems.com 
> > http://rtems.rtems.org/mailman/listinfo/rtems-users
> >
> >
> > End of rtems-users Digest, Vol 16, Issue 22
> > *******************************************
> >
> 



More information about the users mailing list