What's wrong with the Flash-programmer?

[Altera_Forum]

I use flash-programmer to download the sof+elf files to the EPCS4(ref=U13), the actual project is called dl900, and my own target board called dl900_200, I use mk_target_board command to create it; 

 use nios II IDE to new project, then open the flash-programmer tool, but the NIOS IDE tell me this messenge, what's wrong?  make: Entering directory `/cygdrive/e/mydoc/myPrj/.../v1/logic/software/hello_world_0/Debug' Aug 12, 2004 8:56:41 AM - (??) nios2-flash-programmer: Launching Quartus Programmer to download:  e:/mydoc/myprj/.../v1/logic/dl900_200/system/dl900_200.sof Pre-Reading 6KBytes of data from U13:  |----.----+----.----|  ********************* (1.797 sec). Writing 64KBytes :  |----.----+----.----|  ********************* (1.078 sec). Verifying 64KBytes of data:  |----.----+----.----|  *********************Aug 12, 2004 8:56:54 AM - (??) nios2-flash-programmer: Verification failure after write.WARNING: Default charset GBK not supported, using ISO-8859-1 instead make: *** [epcs_controller_boot_rom_programflash] Error 8 make: Leaving directory `/cygdrive/e/mydoc/myPrj/.../v1/logic/software/hello_world_0/Debug'   (Quartus 4.0 + sp1, Nios II 1.0 build 316, usb blaster Version B)

[Altera_Forum]

another messenge is here: 

 make: Entering directory `/cygdrive/e/mydoc/myPrj/.../v1/logic/software/hello_world_0/Debug' Aug 12, 2004 9:36:16 AM - (??) nios2-flash-programmer: Launching Quartus Programmer to download:  E:/mydoc/myPrj/.../v1/logic/dl900_200/system/dl900_200.sof Pre-Reading 6KBytes of data from U13:  |----.----+----.----|  ********************* (0.75 sec). Aug 12, 2004 9:36:23 AM - (??) nios2-flash-programmer: Success. Zero bytes written to U13-  (because device matched contents of epcs_controller_boot_rom.flash) Aug 12, 2004 9:36:23 AM - (??) nios2-flash-programmer: Flash programming complete WARNING: Default charset GBK not supported, using ISO-8859-1 instead sof2flash --flash=U13 --offset=0x00000000 --output=safe.flash --input=\"E:/mydoc/myPrj/.../v1/logic/dl900.sof\" --epcs Info: ******************************************************************* Info: Running Quartus II Convert_programming_file Info: Command: quartus_cpf --no_banner --convert --device=EPCS4 --option=safe.opt E:/mydoc/myPrj/.../v1/logic/dl900.sof safe.pof Info: Quartus II Convert_programming_file was successful. 0 errors, 0 warnings  Info: Processing ended: Thu Aug 12 09:36:25 2004  Info: Elapsed time: 00:00:00 Info: ******************************************************************* Info: Running Quartus II Convert_programming_file Info: Command: quartus_cpf --no_banner --convert safe.pof safe.rpd Info: Quartus II Convert_programming_file was successful. 0 errors, 0 warnings  Info: Processing ended: Thu Aug 12 09:36:25 2004  Info: Elapsed time: 00:00:00 WARNING: Default charset GBK not supported, using ISO-8859-1 instead nios2-flash-programmer --input=safe.flash --sof=`D:/quartus/sopc_builder/bin/find_sopc_component_dir dl900_200`/system/dl900_200.sof --device=1 "--cable='USB-Blaster [USB-0]'" --epcs --relocate Aug 12, 2004 9:36:27 AM - (??) nios2-flash-programmer: Launching Quartus Programmer to download:  E:/mydoc/myPrj/.../v1/logic/dl900_200/system/dl900_200.sof Pre-Reading 186KBytes of data from U13:  |----.----+----.----|  ********************* (6.094 sec). Erasing 7 Sectors:  |----.----+----.----|  ********************* (6.328 sec). Writing 448KBytes :  |----.----+----.----|  ********************* (6.468 sec). Verifying 448KBytes of data:  |----.----+----.----|  ***Aug 12, 2004 9:36:54 AM - (??) nios2-flash-programmer: Verification failure after write. WARNING: Default charset GBK not supported, using ISO-8859-1 instead make: *** [epcs_controller_boot_rom_safe_configuration] Error 8 make: Leaving directory `/cygdrive/e/mydoc/myPrj/.../v1/logic/software/hello_world_0/Debug'

[Altera_Forum]

:( I've had exactly the same problem with my EP1C6 based custom board named 'cleverscope'. At first I thought it was that I was writing too much data to the serial EEPROM, but then I used the small version of the Newlib library, and got exactly the same verification failure with less than 128k of data.  

 I'm using 4M bit serial eeproms - they are made by ST (25P40) and I'm wondering if there is a timing fault in the SPI driver. Looking at the data sheets the 25P40 is identical to the EP1S4, so that shouldn't be it. However will do some independant comparison testing of writing and reading data, and keep you posted.   cheers, Bart

[Altera_Forum]

The first thing that comes to mind is a cable issue that we've seen intermittently. 

can you try restarting your machine, and re-powering your board. Then try again? If it still happens we can try to figure it out from there. I see it's a custom board. If you can send the project to us we can try modifying it to match a board we have.

[Altera_Forum]

Thanks everyone. 

 I have find the answer.  I only use EPCS4 to store the elf+sof, so when i made the target board, i didn't add the tri-state-bridge, and now i add a tri-state-bridge, a virtual flash-chip (maybe lan91c111 also can work, i haven't try it), dont make pin assignments for this virtual flash-chip, then rebuild the target board project, and my actual project, and in IDE rebuild the niosII project, then the flash-programmer is ok.

[Altera_Forum]

I thought I had already posted about this problem. We are doing the same in our design. In fact, all we had to do was insert a PIO and have the out put go to a virtual pin. That fixed everything. Altera is aware of this problem and the fix because we were on the phone to them with our FAE as we fixed it.

[Altera_Forum]

--- Quote Start ---  originally posted by doleksy@Aug 12 2004, 07:34 PM i thought i had already posted about this problem.  we are doing the same in our design.  in fact, all we had to do was insert a pio and have the out put go to a virtual pin.  that fixed everything.  altera is aware of this problem and the fix because we were on the phone to them with our fae as we fixed it.  --- Quote End ---   I have read your post, so i know what you said, I have added a PIO to the niosCPU, but it doesn't work, until add a tri-state-bridge and a component can connect to that tri-state-bridge. It is seemed that the niosCPU need a tri-state-bridge, not a PIO.

[Altera_Forum]

I think the important bit is to connect the ouput to a Virtual Pin in the Assignment Editor. This works for us and I have no tri-state bridge.