Problems with a Virtex-II Engineering Sample

Tjena,

Yes, The executable can be directly merged into the bitfile, if your executable is running from internal BRAM. If you run out of external memory, you need to download executable to the external memory.

How did you create your system? Did you use the Base System Builder?

Göran Bilski

J> Hello all,

Hejsan,

We created the system in Platform Studio (was unable to use BSB because we've got a custom board) and added the required components and ports according to the tutorial on

A few modification were made but we are pretty sure we got this bit right. We reckon the main problem is that Platform Studio won't let us select "executable" under S/W Settings -> Mode. Well, actually it can be selected, but if you go "OK" and then check again it is back to "XmdStub". Is it the case that if XmdStub is selected, then the program will not execute without the debugger? How can this be changed?

The program is included in the bitfile through the "Update Bitstream" option in XPS.

Many thanks for any replies,

executable is running from internal BRAM.

external memory.

F19AEF520806E86FB2EF70C5 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit

Hi,

im currently trying to config a virtexII (xc2v2000) by the slave selectMap mode via a vme interface.

the fpga react fine the stimuli on the prog_b signal (init goes low and back to to high )

then i set rdwr_b to low, present the first data byte (oxff) and set then cs_b to low

the busy signal is low also cclk is low

the i generate one cclk cycle 010 (very slow rate, 8µs high periode )

shortly before the cclk signal goes again to low, the busy signal is be asserted (high) by the fpga and will only be de-asserted after deselect the fpga (cs_b = high)

the configuration fails

Any idea to solve this problem ?

Regards

andreas

Jonas, I'm assuming you are using EDK 6.2. The mode of XMDSTUB v/s EXECUTABLE can be selected on per application basis. Go to the Sw Applications tab in the left column and for your application, right click --> Compiler Options.

In this dialog box,you will fix option to choose between xmdstub and executable mode.

Amit

J> Hello all,

Hello,

unfortunately we have edk 6.1, where that tab doesn't exist.

// Jonas

I've had this exact problem. Here's how I solved it. I'm using version

6.2 of the Xilinx ISE and EDK.

Make sure you are downloading the bootloop application to the PowerPC target during development. When you download a user application that enables interrupts and then try and connect to the PowerPC with XMD the PowerPC may have already wedged itself (especially if your code is incorrect). Once I initialized the target with a bootloop to execute and then later used XMD to download my interrupt supported code did the error go away.

Zach Pfeffer

Thank you for your information.

Am I correct that a bootloop application would bee something as simple as

loop: b loop

and be placed at address 0xFFFFFFFE (the start address for the PPC405)

How would I do that? Do I need to do it manually? We are using EDK and ISE version 6.1

Cheers

// Jonas

Ok, this is how I eventually solved it

bootloop.asm: loop: b loop

powerpc-eabi-as bootloop.asm -o boot.o powerpc-eabi-ld -e 0xFFFFFFFC -Ttext 0xFFFFFFFC -l /ppc405_0/lib -o bootloop.elf

data2bram -bm /implementation/system.bmm

-bd bootloop.elf -bt /implementation/system.bit

-o b download.bit -p

And then the JTAG connection worked! Tnx for the help!

// Jonas

That's great!

Sorry I didn't get back to you sooner.

-Zach

We have discovered that we have some voltage problems, and probably thats why we have so much problems...

Thanks for all your help!

// Jonas