Folks,

The 25P10A from ST do work fine.

> Looking at the *.pof for a Cyclone configured to load from an EPCS4, the
> string EPCS4 is included at the start.

Yes the *.pof  knows what is the target device.

> I'm not sure of why I think this, but I've an idea that the devices check
> the device ID at the start of config, although this might be wrong.

That info on the *.pof file is for the programmer soft-module to know how to
program, and that doesn't go into the device.

> If this is the case you'd have to use a device with the same ID.

The Cyclone device check the device ID to know how much data it
may have to load, just that... I think.

I can't tell what ID's are recognized by the Cyclone load engine... but
at least the ones corresponding to the EPCS1 and EPCS4 are for sure.


The bottom line is still, ST25P10A has the exact same ID as the EPCS1 and 
quartus II
still fails to load them.
However is a fact that once programmed (by other means) Cyclone devices
do read them without trouble.


Luis C.



"Nial Stewart" <nial@nialstewartdevelopments.co.uk> wrote in message 
news:4321c8d9$0$21184$db0fefd9@news.zen.co.uk...
>> I have no idea which of these parts might work. The SST parts are pin
>> compatible but have different IDs. They probably cannot program from
>> quartus but they might read OK.
>
>
> Looking at the *.pof for a Cyclone configured to load from an EPCS4, the
> string EPCS4 is included at the start.
>
> I'm not sure of why I think this, but I've an idea that the devices check
> the device ID at the start of config, although this might be wrong.
>
> If this is the case you'd have to use a device with the same ID.
>
>
> Nial.
>
>
>
> -------------------------------------------------------------
> Nial Stewart Developments Ltd
> FPGA and High Speed Digital Design
> www.nialstewartdevelopments.co.uk
>

Can you just change the ID in the POF file manually?

> I have no idea which of these parts might work. The SST parts are pin
> compatible but have different IDs. They probably cannot program from
> quartus but they might read OK.


Looking at the *.pof for a Cyclone configured to load from an EPCS4, the
string EPCS4 is included at the start.

I'm not sure of why I think this, but I've an idea that the devices check
the device ID at the start of config, although this might be wrong.

If this is the case you'd have to use a device with the same ID.


Nial.



-------------------------------------------------------------
Nial Stewart Developments Ltd
FPGA and High Speed Digital Design
www.nialstewartdevelopments.co.uk

"jai.dhar@gmail.com" <jai.dhar@gmail.com> wrote in 
news:1126271541.652158.82620@g47g2000cwa.googlegroups.com:

> Do you think the A version works? I can't get an SST part from Digikey,
> my only source, which means I'm out of luck :(
> 
> I just can't seem to grasp that one of these parts costs $17....
> 
> 

I have no idea which of these parts might work. The SST parts are pin 
compatible but have different IDs. They probably cannot program from 
quartus but they might read OK.

-- 
Al Clark
Danville Signal Processing, Inc.
--------------------------------------------------------------------
Purveyors of Fine DSP Hardware and other Cool Stuff
Available at http://www.danvillesignal.com

Do you think the A version works? I can't get an SST part from Digikey,
my only source, which means I'm out of luck :(

I just can't seem to grasp that one of these parts costs $17....

Al Clark wrote:

>>Apparently the difference has to do with the WP pin!

Hmmm, this info came from my colleague when I mentioned this thread in 
passing. He recalled that there was a difference with the WP pin...

...however we've just checked the 25P10 and EPCS1 datasheets and they do 
indeed look pin-compatible w.r.t. the WP pin, so we're at a loss to explain.

Sorry 'bout the red herring...

Regards,
Mark

"jai.dhar@gmail.com" <jai.dhar@gmail.com> wrote in 
news:1126241509.799550.314080@o13g2000cwo.googlegroups.com:

> What are you referring to Mark? The WP pin on the ST micro device is
> active low, and it's held at Vcc on the EPCS4 Config device (you are
> supposed to keep it at Vcc I mean).... meaning no write protect. This
> is essentially the same, correct?
> 
> I just tried configuration with an ST Micro 4 Mbit device and it didn't
> work :( It was the M25P40.
> 
> 

I think there is a difference between an M25P40 & M25P40A. I'm not sure 
since we moved to SST for serial flash (for other purposes).

-- 
Al Clark
Danville Signal Processing, Inc.
--------------------------------------------------------------------
Purveyors of Fine DSP Hardware and other Cool Stuff
Available at http://www.danvillesignal.com

What are you referring to Mark? The WP pin on the ST micro device is
active low, and it's held at Vcc on the EPCS4 Config device (you are
supposed to keep it at Vcc I mean).... meaning no write protect. This
is essentially the same, correct?

I just tried configuration with an ST Micro 4 Mbit device and it didn't
work :( It was the M25P40.

Mark McDougall <markm@vl.com.au> wrote in news:4320d893$0$14486$5a62ac22
@per-qv1-newsreader-01.iinet.net.au:

> Apparently the difference has to do with the WP pin!
> 
> Regards,
> Mark
> 

Mark, Do you want to comment further?

-- 
Al Clark
Danville Signal Processing, Inc.
--------------------------------------------------------------------
Purveyors of Fine DSP Hardware and other Cool Stuff
Available at http://www.danvillesignal.com