[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[microblaze-uclinux] Setting up for Microblaze work.

    Being a stuborn (not so) old coot, I have started trying to setup to
provide a MicroBlaze Linux BSP for current and Future Pico boards.

    I have:

          Patched my development tree (based on Linux's linux-2.6.git
from kernel.org) with the uClinux linux-2.6.20-bigpatch.
       There were a few m68k issues I chose to ignore  - I am not doing
any 68k work, otherwise all these patches either went in smoothly
    or will only minor fixes.

          Patched my development environment with the collection of
Linux-2.6.19 Microblaze patches from petalogics development site (thank you)
    This was somewhat more difficult as the patches were against the
petalogic uClinix development tree not a stock Linux source tree with
uClinux patches.
    This required a number of fixes, but nothing that looked scary, evil
or appeared to have a high probability of biting me in the ass later.

    Installed the microblaze-uclinux crosscompilers also from petalogix.

    put together a build script to run make specifying a microblaze
target and the microblaze crosscompiler.

    Actually built the sucker - alright it took several hours to work
through a small collection of problems that mostly seem to stem from
differences between 2.6.19 and 2.6.21.rc#

    Now I have a small collection of questions ?

    uClinux seems to be partial to flat format files ? Is there some
reason the absence of an MMU makes loading an elf file difficult ?
    Our bootloader already handles elf files. Must I use flat files on a
MicroBlaze ?

    There is a huge collection of CONFIG_XILINX_ macros inside the
.config file that seem to correspond to xparameters.h.
    First I can not seem to kill the ones I am not using, and second
don't these really belong in a header file not .config ?
    How and  where do I kill them off ?

    I am explicitly using an initramfs build. I am trying to use the
standard Linux build facilities for that.
    As best as I can tell the kernel binary that gets built does not
include my initramfs files.
    Any clue what I need to change (inside arch/microblaze ?) to fix this ?

   
   








-- 
Dave Lynch 					  	    DLA Systems
Software Development:  				         Embedded Linux
717.627.3770 	       dhlii@xxxxxxxxxx 	  http://www.dlasys.net
fax: 1.253.369.9244 			           Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.

"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein

___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/