Re: [microblaze-uclinux] can a windows OS be used to install uclinux?

[Todd Harless <tharless@xxxxxxxxx>]

I was successful in porting uClinux onto the XUP-V2PRO board using a
Windows XP SP2 OS but I must stress that the way that I did this was
by using a pre-made set of folders that were designed to target this
board. If anyone out in this world has an XUP-V2PRO board then all
that one needs to do is go to: www.digilentinc.com and find the
XUP-V2PRO board on their site and there will be a plethara of designs
to download to that board including a how-to on porting uClinux by no
other than our friend John Williams who deserves a thank you from me.
Two problems occured while doing this though. The image.bin file is
located inside a folder labeled "binaries" and XMD could not find it
so I copied it and pasted it in the main folder where everything was
including the system.xmp file. After that I tried XMD again and this
time it found it and uClinux was installed just fine. The other issue
is that I soon realized that if I wanted to add anything to this
"pre-made" set of files and compile it then i would still need a linux
enviroment since I would need to get that new image.bin file. Eitehr
way I see it is a small success and wish to thank everyone for their
support. Thanks.

On 8/15/05, John Williams <jwilliams@itee.uq.edu.au> wrote:
> Hello Todd,
> 
> Todd Harless wrote:
> > I also bookmarked this website :
> >
> > http://www.itee.uq.edu.au/~wu/downloads/uClinux_ready_Microblaze_design.pdf
> >
> > which I found to be very helpful for a person with a linux OS and was
> > wondering if things like this could be done by someone to show how one
> > can port uClinux using a windows OS.
> 
> The EDK/Base System Builder steps in Jason's tutorial can be done under
> Windows, as can the final bitstream and kernel download.
> 
> The bit that's missing is the actual embedded Linux kernel build, which
> currently requires either a Linux PC or Linux virtual machine running
> under Windows.
> 
> If a dedicated Linux PC is not an option, the most promising approach is
> to use a virtual machine solution like CoLinux.  We are trialing this in
> our group and are pretty pleased with the results.  You should be able
> to download a default CoLinux install from the CoLinux website, import
> the uClinux sources and the modified mb-gcc toolchain, and get started
> with that as though it's a regular Linux PC.
> 
> A mild inconvenience arises since you need to copy the auto-config.in
> file into the virtual machine, and get the cross-compiled kernel image
> out of it.  CoLinux lets you do all the usual network drive mounts and
> shares, so this doesn't have to be too painful.  You can also do a
> regular Xilinx tool install inside CoLinux, for fully integrated goodness.
> 
> My personal opinion is that with the cost of a grey-box PC down in the
> noise these days, it's more efficient and effective to slap down a
> generic PC with a free Linux distro on it (I recommend CentOS 3 for full
> Xilinx tool compatability) and do your embedded Linux work on that.
> However, in Microsoft-centric corporate IT environments it's not an
> option for everyone.  At the moment, CoLinux looks good from where I'm
> sitting.
> 
> Regards,
> 
> John
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@itee.uq.edu.au
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
> 
>

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