Remote System Update : Arria V (EPCQ 256), failed to configure the application image

--- Quote Start ---

Interestingly, I also found that the conf_done is showing up error when the re-config is triggered with the application address 0x0. Normally it should load the Factory FPGA, right?

--- Quote End ---

Hello,

While debugging with the AS interface of the FPGA, I had found that the SPI sends the address as 24 bits even though the EPCQ used is 256.

For example, to know the behavior at FPGA configuration , I tried an address 0xABCDEF98 and confirmed with signal tap that the address is written correctly at the data_in port of the RSU module!

Surprisingly, the data in SPI bus is 0x0b, 0xAB, 0xCD, 0xEF 0x00 ... Seems the EPCQ 256 controller communicates 24 bit address, instead of 32 bit.

Does this mean that I forgot to use some options for the FPGA, to enable 4 byte address access of the EPCQ-256 ??

Thanks in advance for your advice.

Hello,

The analysis of the wavefroms at SPI interface reveals that in the Application mode, the EPCQ device started sending the configuration image data to FPGA just after 3 bytes of address were received, instead of 4 bytes of address. In both the cases the dummy cycles were 4 clocks. I guess there is a difference in the Address Configuration in the Application mode; the EPCQ controller is in 4 bytes mode whereas the EPCQ device is in 3 bytes.

To confirm this, I have tried a function call "epcs_enter_4_bytes_mode" (obtained from the epcs_commands.c provided in HAL) at NIOS side before the reconfig command, with the belief that it would enable "4 Byte Address Mode" corresponding to 4BYTEADDREN (defined in the Datasheet of EPCQ device). The result was positive. The FPGA at Application Mode configured well (the blinking LED @ Application comfirmed the config)

Can anyone please tell me :

If 4BYTEADDREN mode is causing the issue, why doesn't it make a problem in configuration of FPGA after POR?

Is there any "Non Volalite Configuration register" (NVCR) to activate this mode premenantly?

How can I write "4 Byte Address Enable" in this NVCR? Is there any special NIOS2 command or JTAG operations available? Please share us, if it exists.

Has anyone modified the boot_loader_epcq256_bits_cv.s to obtain a customised boot loader?

--- Quote Start ---

Hello,

While debugging with the AS interface of the FPGA, I had found that the SPI sends the address as 24 bits even though the EPCQ used is 256.

For example, to know the behavior at FPGA configuration , I tried an address 0xABCDEF98 and confirmed with signal tap that the address is written correctly at the data_in port of the RSU module!

Surprisingly, the data in SPI bus is 0x0b, 0xAB, 0xCD, 0xEF 0x00 ... Seems the EPCQ 256 controller communicates 24 bit address, instead of 32 bit.

Does this mean that I forgot to use some options for the FPGA, to enable 4 byte address access of the EPCQ-256 ??

Thanks in advance for your advice.

--- Quote End ---

After analysing the wave forms of the SPI interface of EPCQ in the Application mode, I have found that the EPCQ device started sending the configuration image data to FPGA just after receiving 3 bytes of address, instead of 4 bytes of address. In both the application and factory mode, the dummy cycles were 4 clocks. It seems, there is a difference in the Address Configuration in the Application mode; the EPCQ controller is in 4 bytes mode whereas the EPCQ device is in 3 bytes.

To confirm this, I have tried a function call "epcs_enter_4_bytes_mode" (obtained from the epcs_commands.c provided in HAL) at NIOS side before the reconfig command, with the belief that it would enable "4 Byte Address Mode" corresponding to 4BYTEADDREN (defined in the Datasheet of EPCQ device). The result was positive. The FPGA at Application Mode configured well (the blinking LED @ Application comfirmed the config)

Can anyone guide for:

If 4BYTEADDREN mode is causing the issue, why doesn't it make a problem in configuration of FPGA after POR?

Is there any "Non Volalite Configuration register" (NVCR) to activate this mode premenantly?

How can I write "4 Byte Address Enable" in this NVCR? Is there any special NIOS2 command or JTAG operations available for this?

I have resolved my issues. May be my findings help some one else in the future.

The address send by the EPCQ controller was correct in the SPI mode:

The hardware only stores the 24 most significant bits of the address, and then transmits 0 for the least significant byte. This is what is described on page 8-38 of the device handbook: https://www.altera.com/content/dam/altera-www/global/en_us/pdfs/literature/hb/arria-v/av_5v2.pdf

Why there is a mismatch in address mode even though the Factory configures well.

The answer is the default boot loader. Even though there is an NVCR corresponds to the 4 BYTE Address Mode, the operation code 4BYTEARREX (EPCQ 256 Datasheet) overrides this value. I have observed the presence of 4BYTEARREX in SPI interface when the default boot copier runs. So the solution is to force the EPCQ256 device in 4BYTE ADDRESS MODE before reconfig either by epcs_enter_4_bytes_mode call or some other method.

Hi maddyn,

which EPCQ controller are you using? The Legacy EPCS/EPCQx1 or the Serial Flash Controller?

Jens

--- Quote Start ---

Hi maddyn,

which EPCQ controller are you using? The Legacy EPCS/EPCQx1 or the Serial Flash Controller?

Jens

--- Quote End ---

We have used EPCS/EPCQx1 flash controller.