intermitent boot in V4

I have an SOC design built in EDK 8.2.03 for a v4fx12. The fpga boots from an xcf08p serial prom. I have an intermittent problem that seems to come and go with every rebuild. What happens is the chip will configure from prom okay but the software doesn't run. I can tell the chip is fully configure because my debug led lights and the current jumps to full. The design always runs fine when I load the fpga over jtag so something is squirelly with the boot from prom. Also, when it misconfigures the PPC core doesn't appear on the jtag scan path with xmd so I can't even load the software manually.

Here is my bitgen options:

-g ConfigRate:4

-g CclkPin:PULLUP

-g TdoPin:PULLNONE

-g M1Pin:PULLNONE

-g DonePin:PULLUP

-g DriveDone:Yes

-g StartUpClk:JTAGCLK

-g DONE_cycle:4

-g GTS_cycle:5

-g M0Pin:PULLNONE

-g M2Pin:PULLNONE

-g ProgPin:PULLUP

-g TckPin:PULLUP

-g TdiPin:PULLUP

-g TmsPin:PULLUP

-g DonePipe:No

-g GWE_cycle:6

-g LCK_cycle:NoWait

-g Security:NONE

-m

-g Persist:No

Any help is appreciated, Clark

Reply to
cpope
Loading thread data ...

[...]

Howdy Clark,

I didn't go over your bitgen options, but are you using the DONE to let you know when to stop sending CCLK's? Numerous people (including myself) have been bit by the "ALMOST DONE" pin:

In select-map mode, when DONE goes high, it really means "not quite done yet" or "you're almost done". By default, CCLK has to be strobed several more times after DONE goes high.

Whatever your solution, be sure to post it here.

Good luck,

Marc

Reply to
Marc Randolph

We had a similar issue with a V2 pro system last year and the issue was related to timing, the DONE light would always signal completion, but the memory test built into the BRAM to run on the PPC would fail. The part that was spec'd to be on the board was a -6 but the item was changed on the BOM to a -5 (b/c of availability) and no one told the firmware / software team, so we were meeting all timing according to XPS / ISE, but that was for the wrong part. You might want to verify that everything has been specified correctly for the system you are targeting.

Greg

Reply to
Greg Crocker

from

and

configure

always

the

on

Don't think this is it because (a) this had been booting fine for several months on the same hardware (b) I'm already using the slowest speed grade (-10)

but thanks for the lead. -Clark

Reply to
cpope

With the PPC in the Virtex-IIPro, the advice is to _pulse_ the Prog pin at the appropriate time (Impact does this for me) - that was after JTAG config. I can't recall hearing a satisfactory explanation why; but it DID give an utterly reliable boot after a 10-20% success rate previously.

Perhaps the same is true of the PPC in the V4? Searching Xilinx support for "pulse PROG pin" may yield more info

- Brian

Reply to
Brian Drummond

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.