Dan Miller wrote:
John Williams wrote:Okay, we see what's going on; I can't just change the entry in the output system.mss file; the copy-autoconfig is looking for derived paths based on those entries, we need to have *built* the project with those names from the beginning. Our HW engineer is looking into this; we'll rebuild and try again.Hi Dan, On Wed, Jun 3, 2009 at 6:26 AM, Dan Miller <dan@xxxxxxxxxx> wrote:Okay, we finally got our project completely built, using Xilinx 11.1. I'm using the mixed-build process, where we build on Windows XP, I map the target drive onto my Ubuntu 9.04 machine (which worked), and am now trying to build PetaLinux 0.40-rc3. First I ran: root@damien:/home/petalinux-v0.40-rc3/software/petalinux-dist# petalinux-new-platform -v Krommos -p ip3new -k 2.6 -m New platform for Krommos ip3new successfully created Please use petalinux-copy-autoconfig tools with the same parameters (-v, -p) Then I attempt copy autoconfig, but it fails: root@damien:/home/petalinux-v0.40-rc3/software/petalinux-dist# petalinux-copy-autoconfig -v Kromos -p ip3new -k 2.6 /media/petalinux/system.xmp ERROR: Only single-cpu PetaLinux OS type supported. I've never seen this message before, has anyone else?? I can't imagine that that we've built multiple cpus into our project!! What does this mean?What option do you have for "PARAMETER OS_NAME="? It should be "petalinux". We used to get this error if you had an old but commented out "OS" fragment in your MSS file. But, for quite some time now, the script disregards comment blocks in MSS. Just post your MSS file and we'll have a look. Regards, John Dan ___________________________ 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/ |