AD9912 evaluation board -- Cypress EZ-USB FX2 (68613) - EEPROM missing

Hello,

I have an AD9912 evaluation board which when connected via USB to the computer shows up as "Cypress EZ-USB FX2 (68613) - EEPROM missing". This board is then not recognized by the AD control software. I have another identical evaluation board with identical configuration which shows up normally first as "AD9549 Firmware Loader" and then as "AD9549 Evaluation Board" when connected via USB and is recognized by the AD control software. I tested it with three different computers always with the same result.

Is the first board broken or is there a way to reflash/initialyze/reset the EEPROM. Jumper JMP2 (Enable EEPROM) is closed on both boards.

Thanks a lot.

Christian

Parents
  • 0
    •  Analog Employees 
    on Oct 28, 2012 5:46 PM

    Hi Christian,

    The first board was not broken. "Cypress EZ-USB FX2 (68613) - EEPROM missing" only means that the firmware was not loaded into the EEPROM, or the firmware might be loaded but the way it was written in the EEPROM  wasn't configured to read the EEPROM firmware when it boots. The solution is to load the firmware of the AD9912 evaluation board in the EEPROM.

    To do that you can download the EZ-USB development kit software and load the firmware which is a hex file format. I apologize if i don't have a copy of the downloader and of the firmware hex file.

    Regards,

    Louijie

Reply
  • 0
    •  Analog Employees 
    on Oct 28, 2012 5:46 PM

    Hi Christian,

    The first board was not broken. "Cypress EZ-USB FX2 (68613) - EEPROM missing" only means that the firmware was not loaded into the EEPROM, or the firmware might be loaded but the way it was written in the EEPROM  wasn't configured to read the EEPROM firmware when it boots. The solution is to load the firmware of the AD9912 evaluation board in the EEPROM.

    To do that you can download the EZ-USB development kit software and load the firmware which is a hex file format. I apologize if i don't have a copy of the downloader and of the firmware hex file.

    Regards,

    Louijie

Children
No Data