RE: [microblaze-uclinux] First *real* PetaLinux build attempt

Dear Dan,

In UTIA, we have managed to port MicroBlaze 7.10.d based designs from XPS 10.1.03/petalinux-v040.rc3 to XPS 11.1/petalinux-v040.rc3.

Up to now it has been done for designs and applications on Xilinx ML402, 3sd1800a and 3s700an boards:

(1) Modify petalinux_v2_1_0.tcl to use:

{edk_path}/sw/lib/bsp/standalone_v2_00_a/data/standalone_v2_1_0.tcl

Instead of:

{edk_path}/sw/lib/bsp/standalone_v1_00_a/data/standalone_v2_1_0.tcl

This helps to respect that Xlinx 11.1 is recognizing standalone v2_00_a and not standalone v1_00_a

(2) Compile your HW in Xilinx XPS 10.1.03. Use MicroBlaze 7.10.d.

This is to respect that Xlinx 11.1 can import and compile the MicroBlaze 7.10.d version of MB.

(3) Generate Kconfig.auto in Xilinx XPS 10.1.03. This is done in the petalinux BSP

(4) Open your XPS 10.1.03 project in Xilinx XPS 11.1 and let the tool to import the project,

but without changing (upgrading) the HW IP and SW drivers if possible.

The resulting platform will have the instance of MicroBlaze 7.10.d. processor (not the actual MicroBlaze 7.20.a)

(5) Compile your HW in Xilinx XPS 11.1

(6) Select standalone v2_00a as the board support package in Xilinx XPS 11.1 to compile SW drivers.

(7) Use petalinux-copy-autoconfig in the petalinux-v040.rc3 to autoconfig from the Kconfig.auto of the original Xilinx XPS 10.1.03 project.

(8) Compile kernel and applications in petalinux-v040.rc3.

(9) In XPS 11.1 use XMD to boot the image.bin

Best regards,

Jiri

Jiri Kadlec

Institute of Information Theory and Automation

Academy of Sciences of the Czech republic (UTIA),

Department of Signal processing

Pod vodarenskou vezi 4

18208 Prague 8, Czech Republic

tel. 00420 2 66052216

fax 00420 2 66052511

kadlec@xxxxxxxxxxx

http://zs.utia.cas.cz

From: owner-microblaze-uclinux@xxxxxxxxxxxxxxxxxxxx [mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Dan Miller
Sent: Wednesday, June 03, 2009 1:31 AM
To: microblaze-uclinux@xxxxxxxxxxxxxx
Subject: Re: [microblaze-uclinux] First *real* PetaLinux build attempt

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.

Well, not really.

Your MSS refers to the standalone OS - you have to change this to

PetaLinux, and make the appropriate selections relevant to that OS -

main memory peripheral, flash, rs232 etc.

Check that link I just sent.

Cheers,

John

Aye, I see what you're referring to. I'll work on that and get back here.
I got a little confused by new-platform, which told me to remember to run copy-autoconfig... I just didn't realize it meant "after you've done all the other necessary things first!" 8-{O

Dan