Forum Discussion

Bill_A's avatar
Bill_A
Icon for New Contributor rankNew Contributor
4 years ago

Cyclone V E AS Configuration with MX25L256

Trying to configure a Cyclone V 5CEFA2U19I7 with an MX25L256 fails. The device is MX25L25645GZ2I-08G. It is configured to use Active Serial x4. Here is more information. Programming .SOF throu...
Bill_A's avatar
Bill_A
Icon for New Contributor rankNew Contributor
4 years ago

The MSEL pins are connected through zero Ohm resistors. We have tried AS Standard (R370 out and R367 in) and AS Fast(R370 in and R367 out) . I have attached a picture.

Bill_A's avatar
Bill_A
Icon for New Contributor rankNew Contributor
4 years ago

Do you need a copy of the .JIC file? We have created one with all combinations of the Advanced options and all behave the same.

Disable EPCS/EPCQ ID check

Disable AS mode CONF_DONE error check.

  • Bill_A's avatar
    Bill_A
    Icon for New Contributor rankNew Contributor
    4 years ago

    I have attached a picture with the connections to the SPI FLASH

    • Bill_A's avatar
      Bill_A
      Icon for New Contributor rankNew Contributor
      4 years ago

      More information.

      I have created a custom device to try different settings. Can you get me information about how the programmer sets up the FLASH and the commands that the Cyclone V issues to configure the FPGA.

      We tried an ASx1 JIC file and looked at the transactions. The FPGA issued a RDSR (Read Status Register) command and read back 0x40. This indicates that QUAD ENABLE bit is set. This was supposed to be an ASx1 file so I thought that the programmer would have cleared that bit. The FPGA also issues a RDID which returns the expected data. After that, the FPGA reads data and tries to configure. The DCLK changes frequency but the configuration fails.

      Does the programmer set values in non-volatile memory in the FPGA to configure the type of SPI FLASH? What should the programming sequence be? I noticed the defaults in the custom device set 4 byte addressing and then turn it off under termination. When we monitored the configuration sequence, we never see 4 byte addressing get enabled.