Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
17268 Discussions

Problems programming config device via .jic file.

Altera_Forum
Honored Contributor II
2,719 Views

Greetings. 

 

I am trying to program my configuration device (Numonyx M25P16, same size as EPCS16) via the JTAG port of a Cyclone4E EP4CE30F23 using Quartus v9.1sp2. 

 

When I try programming the device, I get a 'verification failed for device number 1' error. 

 

I know my configuration device is connected and working properly because I can successfully program it using a NIOS2 processor and an EPCS flash controller from within the fpga itself. 

 

I have created a .jic file via the Quartus 'Convert Programming Files...' feature. My settings are as follows: 

Config Device: EPCS16 

File Name: PS850.jic 

Memory Map File is checked 

Flash Loader : EP4CE30 

SOF Data : PS850.sof, EP4CE30F23, page_0, <auto> 

 

In the Quartus programmer, I select the PS850.jic file and select the 'Program/Configure' and 'Verify' checkboxes for the SFL image and PS850.jic. 

 

Here is what Quartus tells me: 

Info: Started Programmer operation at Mon Apr 11 17:41:23 2011 

Info: Configuring device index 1 

Info: Device 1 contains JTAG ID code 0x020F40DD 

Info: Configuration succeeded -- 1 device(s) configured 

Info: Device 1 silicon ID is 0x14 

Info: Erasing ASP configuration device(s) 

Info: Programming device(s) 

Info: Performing CRC verification on device(s) 

Error: Verification failed for device number 1 

Error: Operation failed 

Info: Ended Programmer operation at Mon Apr 11 17:41:38 2011 

 

Any help would be greatly appreciated 

 

Thank you 

Scott Wild
0 Kudos
1 Reply
Altera_Forum
Honored Contributor II
1,858 Views

Looks like upgrading to 10.1sp1 fixes this problem.

0 Kudos
Reply