uclinux on spartan-3e starter kit

hi i am looking for any step by step guide to use uclinux on the starter kit. i try the site:

formatting link
but i didnt find anything in english or spanish. just japanese. thanks you David

Reply to
David
Loading thread data ...

"David" schrieb im Newsbeitrag news: snipped-for-privacy@i42g2000cwa.googlegroups.com...

formatting link

hm checked the images from that site in XSIM and they work just fine. I dont have the boards so can not test in hardware but I assume they will defenetly work as well

antti

Reply to
Antti Lukats

i get this errors using the rev02 i get 2 errors and one warning how i can resolve it?

WARNING:MDT - The installed version of EDK tools is 8.1, while project was created with version 8.1.01 ERROR:MDT - I:\Documents and Settings\aaa\Escritorio\s3eboard_uclinux_ready_rev02\s3eboard_uclinux_ready_v8101_rev02\system.mss line 5 - Can not find MLD for the os uclinux 1.00.d INFO:MDT - Directories Searched :

- I:\Documents and Settings\aaa\Escritorio\s3eboard_uclinux_ready_rev02\s3eboard_uclinux_ready_v8101_rev02\bsp/uclinux_v1_00_d/data

- I:\EDK\sw\ThirdParty\bsp/uclinux_v1_00_d/data

- I:\EDK\sw\XilinxProcessorIPLib\bsp/uclinux_v1_00_d/data

- I:\EDK\sw\lib\bsp/uclinux_v1_00_d/data ERROR:MDT - Can not find MLD for the os uclinux 1.00.d INFO:MDT - Directories Searched :

- I:\Documents and Settings\aaa\Escritorio\s3eboard_uclinux_ready_rev02\s3eboard_uclinux_ready_v8101_rev02\bsp/uclinux_v1_00_d/data

- I:\EDK\sw\ThirdParty\bsp/uclinux_v1_00_d/data

- I:\EDK\sw\XilinxProcessorIPLib\bsp/uclinux_v1_00_d/data

- I:\EDK\sw\lib\bsp/uclinux_v1_00_d/data

thanks you very much

Antti Lukats wrote:

formatting link

Reply to
David

"David" schrieb im Newsbeitrag news: snipped-for-privacy@b28g2000cwb.googlegroups.com...

Settings\aaa\Escritorio\s3eboard_uclinux_ready_rev02\s3eboard_uclinux_ready_v8101_rev02\system.mss

you have to download it seperatly and install in some dir where it can be found, the arhc is on the same site, or then also available from petalogix site

Antti

Reply to
Antti Lukats

A Linux-ready reference design for the Spartan3E500 starter kit is available now from PetaLogix:

formatting link

Regards,

John

--
Dr John Williams
www.PetaLogix.com
(p) +61 7 33652185  (f) +61 7 33654999

PetaLogix is a trading name of UniQuest Pty Ltd
Reply to
John Williams

"John Williams" schrieb im Newsbeitrag news:newscache$q14h4j$xmi$ snipped-for-privacy@lbox.itee.uq.edu.au...

Thanks Jihn

the 1600 thing was really useless, as you seem to be only one havng those s3e-1600 boards despite the fact that Xilinx website says that 'coming in June'

Antti

Reply to
Antti Lukats

Hi folks,

I'm happy to announce that a binary demo package showing off embedded Linux on the Xilinx Spartan3E-500 Starter Kit (Revision C) is now available from PetaLogix. Go to

formatting link

and follow the links to Resources->Reference Designs to get the package.

Supported board features include TCP/IP networking (via the Xilinx EthernetLite core), buttons, switches, LEDs and rotary encoder, flash, and an embedded webserver demo including web-based kernel image update.

Please contact snipped-for-privacy@petalogix.com with any queries or for more info.

Regards,

John

Reply to
John Williams

John Williams schrieb:

Dear John,

a binary demo for Linux isnt much interesting or useful - everybody is waiting when does PetaLogix finally release the PetaLinux, but so far there has been to release date information announced by PetaLogix? Can we assume that the actual PetaLinux release date is coming closer also, or is PetaLogix still holding back information about possible release date?

I see the 'binary demo' is still based on EDK 8.1 tools - so it can not fully support the MicroBlaze version 5, I wonder why hasnt PetaLogix used EDK 8.2 tools? To what I know PetaLogix had early access to EDK

8.2 (and GNU code?) and those would have been in the position to use the latest GCC toolchain.

As of the '500e binary demo' I can only confirm that it boots in XSIM ver 1.1.a succesfully, free download here:

formatting link

Antti

Reply to
Antti

Antti, a binary demo may not be useful to you, but it's obviously of some value to the people who've been asking for it, and the numerous people who've downloaded it in the just last 12 hours.

One reason binary demos are valuable is for people who want a quick evaluation, a proof of concept, or even just be able to show their boss that indeed Linux on an FPGA works, and might make sense for their project. They don't want to take the time to learn how to build it themselves, they just want the "5 minute demo", and that's what this is about.

One of the goals of PetaLinux, of course, is to enable people to build the

5-minute demo themselves, as well as provide an environment for major FPGA-based embedded Linux development. This is a lofty goal, which is why it's taking a while to get it developed and documented to a state where we are happy to release it.

Yes, we do have early access to the 8.2 tools, and indeed the current demo is based on 8.1. Why? Because as a small organisation operating out of a university research group we have limited resources which we must manage carefully.

We also have paying clients who expect us to deliver what we have promised. If this means that PetaLinux, and other nice-to-have features that we will be giving aware free to the community (including you) must sometimes take a back-seat, then I can make no apologies for that fact.

Regards,

John

Reply to
John Williams

John Williams schrieb:

on

FPGA-based

Hi John,

ok, I see while you are busy with paying clients you have no longer interest to work on mb-uclinux improvement. Good point. That is possible the reason why Xilinx did choose lynuxworks to deliver the microblaze 2.6.x port.

For those who want to use GPL tools to compile MicroBlaze 5.0 applications on WinXP platform here is the cygwin compiled MicroBlaze toolchain from EDK 8.2 release.

formatting link

I have only tested it to succesfully compile MicroBlaze u-boot, so the toolchain is working at least.

Antti Lukats

Reply to
Antti

I'm speechless. You win.

Reply to
John Williams

Digilent has a 3S1600E board out right now:

formatting link

The best part is, they actually fixed some of the gripes I had about the previous 3S500E board.

Reply to
radarman

Antti,

Is there somewhere I can download the source for this? I'd like to modify it to drop its xil dependancy:

/cygdrive/f/hw/mbgcc/bin/../lib/gcc/microblaze/3.4.1/../../../../microblaze/bin/ld: cannot find -lxil

Thanks, Todd

Antti wrote:

Reply to
Todd Fleming

Todd Fleming schrieb:

/cygdrive/f/hw/mbgcc/bin/../lib/gcc/microblaze/3.4.1/../../../../microblaze/bin/ld:

Hi Todd,

try adding

-nostartfiles to command line options, also look at XAPP482 the -lxil is the default xilinx runtime library what is created at EDK system build time so the content of it depends on the system drivers and options, those there is no source code of it. look at the lib srces of any EDK project, there are the sources the libxil is made of. I think most of those sources are also GPL (the are also part of uclinux as example) so it is possible to have a 3rd party libxil I think by using the GPL drivers and adding some small portion of runtime init code

the binary mb-gcc that I made available is just 1:1 compile result of the GPL licensed GNU GCC code from Xilinx website (EDK 8.2 release) - that source code is available from Xilinx. You can recompile it yourself or study the source code if you wish. The Xilinx source compiles 'out of box' on WinXP/Cygwin - only change I had todo was the default path to tcsh

one hint though, if you let cygwin to update your cygwin install it renders EDK non functional. so after compiling mb-gcc goto cygwin/bin and delete or rename make.exe

next start of XPS will copy make exe from EDK tree back into Cygwin bin and everything will work again. there is an Xilinx AR about the make incompatibility (eg the explanation why EDK doesnt work with latest cygwin make)

Antti

Reply to
Antti

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.