<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">RRR, Phil. Understood. Thanks!<div><br></div><div>What is interesting about my recent experience with the Metis EEPROM losing it's mind is that I could not recover from this fault by using the HPSDRProgrammer bootloader mode. It was necessary for me to use the Quartus II Programmer to load the file "output_file.pof" (which Jeremy kindly provided to me!) in order to recover from this particular failure. </div><div><br></div><div>After loading the output_file.pof using a blaster cable in conjunction with the Quartus II Programmer utility I now am able to use both the normal programming mode and the bootloader mode in the HPSDRProgrammer utility to update code in the Metis board that previously had failed. However, should the "no-LEDs-at-all-showing" failure occur again on this board, I suspect that the bootloader mode in HPSDRProgrammer will once again not allow me to recover. I suspect that in this failure mode it will be necessary for me to once again load the "output_file.pof" into the EEPROM using a blaster cable and the Quartus II Programmer to recover. </div><div><br></div><div>In any case, thank you all very much for your helpful comments and providing me with the necessary files to get back up with this Metis board!</div><div><br></div><div>73, Joe K5SO</div><div><br></div><div><br></div><div><br><div><div>On Feb 20, 2011, at 6:27 PM, Phil Harman wrote:</div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font>With Metis we have tried to move away from the Altera Quartus programming<br>software since it changes frequently and is not as user friendly as John's<br>HPSDRProgrammer software. We feel that being able to update the code, both<br>in Metis and other HPSDR boards, via Ethernet is a step forward.<br></div></blockquote></div><br></div></body></html>