m68k BSP's, conclusion

[joel at OARcorp.com (joel at OARcorp.com)]

On Fri, 30 Apr 1999, Michael Collins wrote:

>   After a few more iterations, I've been able to successfully build
> the efi332 BSP under Solaris.  Haven't tried others yet, but will
> next week.  The only thing I found after being clued-in about the
> problem involving "wildcard" function, was a failure involving the
> install-sh script which didn't put packhex (and other) binaries
> in place as it should have.  Consequently, bit_rtems failed later
> when it was attempting to build "hello.exe".  I got around this
> by installing "install" from the GNU fileutils-4.0 package.

This is a problem Erik Ivanenko has also run into and I ran into myself
last week on a Solaris box.  The Solaris "install" is in /usr/ucb which is
likely not in your PATH.  (It was not in mine.)  For some reason, the GNU
default install-sh does not install multiple files at the same time.  That
is the install-sh used by RTEMS, egcs, and binutils when a suitable
install program is not found.

Looking at the egcs use of install, it seems that no other package assumes
that multiple files can be installed by a single invocation of the install
script.  The solution is to put something like this in
build-tools/scripts/Makefile.in and build-tools/src/Makefile.in

all:    $(ARCH) $(DESTDIR) $(SRCS) $(PGMS)
        @for f in $(PGMS) xxx; \
        do if [ $$f != xxx ] ; then \
            @INSTALL@ $(INSTBINFLAGS) $$f $(DESTDIR); \
        fi ; done ;

If there is someone on the list who could comment on the assumptions on
the INSTALL program, I would appreciate some insight.

>   Once I had a BSP, I built the "hello_world_c" sample as described
> in Chapter 5 of the tutorial, and through inspection, it appears that
> the S-record file is useful.

I hope so. :)

>   For comparison, I built the entire toolchain on my home Linux
> system last night, and encountered no problems.  In that case, I
> built all the m68k BSP's.  It eats a lot of disk space, but everything
> worked.  Because I didn't have the printed manual at home, I didn't
> build the sample application, however I don't expect to encounter
> any problems when I do so tonight.

The hello_world tar file includes a README with about the same
instructions as the documentation.

>   Thanks for the help so far.  My goal is to build a BSP for an
> MC68331-based board with an ethernet interface for an in-house
> project.  I'll probably have a few more questions along the way.
> 
> 					-- MC --
> 
> ...now that I think about it, here's one: in "user.cfg", there's
> a "BSP=" line.  If I put my BSP name here, is that value picked-up
> by bit_rtems?

Unfortunately no.

>  Can I specify multiple BSP's, or is the choice between
> one and all?

I think the bit_rtems script is actually limited on this matter to a
single BSP or all of them.  The actual configure parameter is
--enable-rtemsbsp and it does take a list of multiple BSPs:

--enable-rtemsbsp="BSP1 BSP2"

The quoting in shell scripts makes getting the list of BSPs to this point
hard to get right for me.

I know the starting point is to fix where BSP_TO_TEST is set to a single
parameter in the shell script. :)

--joel
Joel Sherrill                    Director of Research & Development
joel at OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985