Ok, so all that worked - it WAS necessary to choose "[*] Default all settings (lose changes)" in order for it to work though. Without this option checked I needed to add information and variables and constants and definitions that were not added into necessary files after make menuconfig and make dep were completed. <br> But I still have nothing working with the ML310 board. I did a "dow image.elf" at the XMD command prompt, then "con" and it showed up with a "RUNNING>" prompt, but nothing showed up on the hyperterminal window. I compiled using 115200 baud and I changed my hyperterminal to match this, but nothing shows up ...at all. Where do you think I would need to start looking to resolve this issue? <br> <br> -Vincent<br><br><b><i>Aidan Williams <aidan@nicta.com.au></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> <br>After generating
a new auto-config.in using the BSP,<br>you'll need to:<br><br> 0. put new auto-config.in into kernel directory<br> linux-2.4.x/arch/ppc/platforms/xilinx_auto<br><br> 1. change to the top uClinux-dist directory<br> (*NOT* the kernel directory)<br><br> 2. In "Vendor/Product Selection --->"<br> Choose "Xilinx"<br> Choose "powerpc-auto"<br><br> 3. In "Kernel/Library/Defaults Selection --->"<br> Choose linux-2.4.x as your kernel, making sure that<br> this is a symlink to or copy of the linuxppc-2.4<br> tarball from UQ.<br><br> 4. In "Kernel/Library/Defaults Selection --->"<br> Choose "[*] Default all settings (lose changes)"<br><br> 5. Save and quit..<br><br>This process will pull in default Xilinx/powerpc config<br>files from vendors/Xilinx/powerpc-auto/config.*<br>for the kernel and for other uClinux components.<br><br>It will also generate a new linux-2.4.x/.config<br>based on your auto-config.in and the
defaults<br>in vendors/Xilinx/powerpc-auto/config.linux-2.4.x.<br><br>btw, I don't have an ML310 board. I have however gotten<br>the UQ kernel + uclinux to work on a v2pro FF1152 board<br>and a virtex-4 FX-12 minimodule.<br><br>another btw, the linuxppc-2.4 code has an auto-config.in<br>inside it which, if you follow the above steps (without<br>doing step 0), should compile. The supplied auto-config.in<br>won't match your board, but it should at least compile.<br><br>- aidan<br><br><br>Vincent Winstead wrote:<br>> guess what - I got the BSP to work! But now I have a problem with the <br>> make command. I put the auto-config.in where it needs to be then I did <br>> a make menuconfig to configure it, then I did a make dep, but when I did <br>> a make is when an error came up that I can't seem to figure out:<br>> <br>> In file included from <br>> /home/ml310_linux/uClinux-dist/linuxppc-2.4/include/linux/pagemap.h:16,<br>> from
<br>> /home/ml310_linux/uClinux-dist/linuxppc-2.4/include/linux/locks.h:8,<br>> from <br>> /home/ml310_linux/uClinux-dist/linuxppc-2.4/include/linux/blk.h:5,<br>> from init/main.c:25:<br>> /home/ml310_linux/uClinux-dist/linuxppc-2.4/include/linux/highmem.h: In <br>> function `kmap':<br>> /home/ml310_linux/uClinux-dist/linuxppc-2.4/include/linux/highmem.h:68: <br>> error: `CONFIG_KERNEL_START' undeclared (first use in this function)<br>> init/main.c: In function `start_kernel':<br>> init/main.c:393: error: `CONFIG_KERNEL_START' undeclared (first use in <br>> this function)<br>> make[1]: *** [init/main.o] Error 1<br>> make[1]: Leaving directory `/home/ml310_linux/uClinux-dist/linuxppc-2.4'<br>> make: *** [linux] Error 1<br>> <br>> This CONFIG_KERNEL_START is the problem. It doesn't seem to be defined <br>> anywhere and I guess it needs to be. Is this something I need to get <br>> from
somewhere? Or is it maybe generated along with the BSP so I would <br>> have to put a start number into the platform Studio configuration?<br>> <br>> -Vincent<br>> <br>> <br>> */Aidan Williams /* wrote:<br>> <br>> <br>> Vincent Winstead wrote:<br>> > Now, as far as step 5, am I supposed to have a symbolic link that is<br>> > named linux-2.4.x placed into the uClinux-dist directory? Because<br>> > there's already a folder named linux-2.4.x which was in there<br>> already<br>> > when I untarred everything. At the command prompt in the<br>> uClinux-dist<br>> > directory I entered the following line:<br>> ><br>> > ln -s ../linuxppc-2.4 linux-2.4.x<br>> ><br>> > and the result of this operation was to put a symbolic link into my<br>> > linuxppc-2.4 directory with the name of linux-2.4.x - is this<br>> correct?<br>>
><br>> <br>> First, you'll need to move the existing directory aside using<br>> a command like:<br>> <br>> mv linux-2.4.x linux-2.4.x-dist<br>> <br>> and then re-run the ln -s command above.<br>> <br>> > Now on to Step 6 problem.<br>> > How am I supposed to make use uClinux EDK Board Support Package 1.0<br>> > files? I'm not sure how to go about using them in the Xilinx<br>> Platform<br>> > Studio in order to generate the necessary auto-config.in file.<br>> ><br>> <br>> See the document below for the general approach:<br>> <br>> > Even though it is about the microblaze rather than<br>> > the PPC, a helpful "getting started" document is:<br>> ><br>> http://www.itee.uq.edu.au/~wu/downloads/uClinux_ready_Microblaze_design.pdf<br>> ><br>> <br>> Look particularly at the section "Software Platform
Settings"<br>> on page 29, steps 67,68.<br>> <br>> If you are not overly familiar with the EDK, it would<br>> be best to find someone locally who can help walk you<br>> through the process of generating a system.<br>> <br>> - aidan<br>> <br>> <br>> --------------------------------------------------------------------------<br>> This email and any attachments may be confidential. They may contain<br>> legally<br>> privileged information or copyright material. You should not read, copy,<br>> use or disclose them without authorisation. If you are not an intended<br>> recipient, please contact us at once by return email and then delete<br>> both<br>> messages. We do not accept liability in connection with computer virus,<br>> data corruption, delay, interruption, unauthorised access or<br>> unauthorised<br>> amendment. This notice should not be
removed.<br>> <br>> <br><br></blockquote><br>