[Coco] DE-1 Clarification Please

[tim franklinlabs.com]

   Same here. I've been working with the DE1, DE2 and several other
   (Chinese) FPGA development boards and I've never had a problem with the
   flash or RAM burning using the Quartus programmers.
   And yeah, the comment about the burn cycles was deserved. I'm anal
   about the details and wanted Mr. Boss to know that Flash does have
   limits. LOL

     On October 29, 2017 at 7:23 AM Mark McDougall wrote:
     On 29/10/2017 9:30 AM, James Ross wrote:

     It should not be the fact that one must program their device
     multiple
     times before it takes (not saying that you are implying that
     either).
     Just saying, that there has got to be a precise explanation of what
     folks are doing wrong and why that does not work when they do that.

     Given the manual, multi-step, nature of the programming process, and
     the
     variances across PC hardware and driver versions, odds are the
     issues
     can be traced back to a fault on the PC side of the cable, rather
     than
     the DE1 itself.
     For the record, I've used the DE1 for years on a number of projects,
     mostly non-Coco-related and haven't had a systemic issue that I can
     recall with programming the flash via the Control Panel.
     Not to say that I haven't been simply lucky and that the
     TerASIC-supplied software isn't temperamental.
     Regards,
     --
     Mark McDougall
     --
     Coco mailing list
     [1]Coco at maltedmedia.com
     [2]https://pairlist5.pair.net/mailman/listinfo/coco

References

   1. mailto:Coco at maltedmedia.com
   2. https://pairlist5.pair.net/mailman/listinfo/coco