Michal Simek wrote:
Okay, Thank you Michal and Ken!!Dan Miller wrote:In various recent discussions with me on this mailing list, regarding my efforts to build the current (as of a week ago) SVN version of PetaLinux, several people (including Michal Simek and John Williams) have made references to the version of EDK that is being used to build the Linux package. I don't understand what they are referring to; I go to the PetaLogix SVN server, download the current version of the software package, extract, run "make menuconfig" (but don't actually change anything) and "make all". I then spend some period of time resolving the various failures which pop up. As far as I can tell, this has nothing to do with the Xilinx EDK...Actually, I'm trying to figure out how to build this package *before* the hardware engineer gets involved (he's the one who is busy with the EDK right now). I *thought* I would be coming up with a .elf file and passing it to the Xilinx developer, who would somehow link it into the design somehow, but it looks like it isn't that simple. Clearly I'm misunderstanding something fundamental about how this process works, I would be grateful if someone could clarify it for me. If there's some tutorial somewhere that engineers are supposed to read before they try to develop for embedded Linux, feel free to point me there. And thank you all, again, for all the help that you've provided so far!!ok. The main point which you miss is that linux kernel depends on your hardware. In distribution are prepared many reference design in menuconfig. These reference designs are related with 1. ref boards (for example ml505) and 2. real hw connection on that ref board (we called it design) We did for some ref boards some designs. (I hope you understand that is possible to have millions design for one ref board). We can't support all of them but we did some designs for one boards. If you look to hardware folder you can see that there are folders with edk suffix. This is because there were changes between EDK version and some older designs can be compile on newest EDK. Back to your problem. The main question is what you want to do. 1. if you want to do test on ref board, you should use ref design then you can just compile software and kernel will run. (or you can use prebuilt images) 2. If you want to run Linux on custom board, you have to get setting from hw guys to run Linux on it. That HW guy must run EDK software part which generate Kconfig.auto. I think you should take a look at developer.petalogix.com there you can find a lot of answers to your questions. Regards, Michal
Now that I'm re-reading the Custom Tutorial link that Ken sent, I realize that I read it before, but it just didn't mean anything to me at the time; I understand it better now.
I also realize why they were saying that we *had* to use the Linux version of the EDK, which we are not currently using. I wonder if it will work on a Linux running as a VirtualBox guest platform?? That's how I'm running Linux now. I'll have to look into that.
Thank you again for the responses; it looks like we *will* have to buy a second Xilinx installation here so I can do this work.
___________________________ 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/