Hi,
I am using a cylcone V along with EPCQ128 flash memory. The design incorporates a remote update block to switch between factory and application image.
POF checking is on and I have signals running from remote update block and the ASMI interface via multiplexer (I'm using the ASMI block to write and read from the flash).
I have the factory configuration starting from address 0x000000. I have double checked the settings, and the configuration mode is active serial X 1, remote.
Watchdog is enabled and the timeout value is set to 4 seconds - 0x149.
The state machine is exactly same as what is in the reference design for remote update.
Application image starts at address 0x400000 - sector boundary. Both factory and application bitstreams are compressed (Factory image ends way before address 0x400000; No overlap)
Using the ASMI interface, I double checked the presence of application configuration by comparing the read data with the .rpd file.
During power-up, I see the factory configuration. I see all the signals and states on signal tap - So far so good.
I provide the ANF start strobe, which in-turn provides the reconfigure strobe, and I see that there is no POF error (Which I believe indicates that the core located the application image), but the FPGA freezes. The application image is not loaded.
Initially, the logic inside application image did not have the remote IP instantiated. I then experimented by instantiating the core, and resetting the reset_timer pin by providing a high to low signal (high for 250ns as per the data sheet). I still see the same result as mentioned above.
One thing worth noticing was the nSTATUS pin. I was under the impression that the nSTATUS pin goes low when there is an error during configuration. What I see is a periodic signal. Attached the waveform snapshot. I don't know if anything can be made out of this.
nSTATUS and nCONFIG pin are pulled up to 3.3V via 10k resistors.
Any help regarding this issue would be really appreciated.
Thanks,
Kamath
I am using a cylcone V along with EPCQ128 flash memory. The design incorporates a remote update block to switch between factory and application image.
POF checking is on and I have signals running from remote update block and the ASMI interface via multiplexer (I'm using the ASMI block to write and read from the flash).
I have the factory configuration starting from address 0x000000. I have double checked the settings, and the configuration mode is active serial X 1, remote.
Watchdog is enabled and the timeout value is set to 4 seconds - 0x149.
The state machine is exactly same as what is in the reference design for remote update.
Application image starts at address 0x400000 - sector boundary. Both factory and application bitstreams are compressed (Factory image ends way before address 0x400000; No overlap)
Using the ASMI interface, I double checked the presence of application configuration by comparing the read data with the .rpd file.
During power-up, I see the factory configuration. I see all the signals and states on signal tap - So far so good.
I provide the ANF start strobe, which in-turn provides the reconfigure strobe, and I see that there is no POF error (Which I believe indicates that the core located the application image), but the FPGA freezes. The application image is not loaded.
Initially, the logic inside application image did not have the remote IP instantiated. I then experimented by instantiating the core, and resetting the reset_timer pin by providing a high to low signal (high for 250ns as per the data sheet). I still see the same result as mentioned above.
One thing worth noticing was the nSTATUS pin. I was under the impression that the nSTATUS pin goes low when there is an error during configuration. What I see is a periodic signal. Attached the waveform snapshot. I don't know if anything can be made out of this.
nSTATUS and nCONFIG pin are pulled up to 3.3V via 10k resistors.
Any help regarding this issue would be really appreciated.
Thanks,
Kamath