AES16e Firmware Build 12 now available

Lynx Studio Technology is proud to announce the availability of Build 12 Beta firmware for the AES16e card.

Firmware Revision History

Version 1.00.12 September 12, 2011

• Fixed PCI Express issue that occurred with some P67 and Z68 motherboards (Gigabyte & Intel).
• Fixed volume indexing issue at 4X sample rates.

Please post your success and failure messages to this thread.  Once we have enough test information, we will post the final release version.


Edited by David A Hoatson - September/12/2011 at 4:17pm

You may need to set the C-States to "Disable" in your BIOS (see this thread) before you flash the firmware.

Once you have successfully flashed the firmware, set your EEPROM jumper back to 2 (to activate the new firmware) and then you can turn your C-States back to "Enable".

I can't find details around how to "set your EEPROM jumper" in the AES16e manual. 

Steven Bell wrote: I can't find details around how to "set your EEPROM jumper" in the AES16e manual.

AFAIK it's not in the manual, but the process was fairly self-evident to me as a 'computer person.' :)

Basically, shut down, find the only jumper on the card, move it to the "1" position (first two pins rather than last two pins). Boot up, run flash utility. Shut down, move the jumper back to the "2" position. Boot up and you are on the newly-flashed firmware again.

One more thing, can you just jumper between the two boards AES50 ports and pass audio that way?

I downgraded the boards to 11 as per the instructions sent. Still no dice with the AES50 side of things.



Just tried patching the two aes50 cards together and set one for internal clock and the other to aes50 clock sync. No luck there either, the box stays red and actually claims the incoming aes50 samplerate from the other card is always twice what I actually have it set at.
Also the connection LED on both cards ports stays amber, no green light.

Edited by dasbin - September/18/2011 at 3:49pm

I have actually tried that, using 6ft cables, and even removed each of the cards from the system one at a time to take the other out of the equation. Also tried patching into the redundant port of the Midas, in case some power surge took out the first two as they were connected during the update. But no luck. I agree that technically it is quite baffling. Only thing I can think of is some power spike fried them simultaneously. Perhaps upon the system's hard-lockup on flashing the second card.

Thanks so much for your help on a Sunday.

Where do I go from here? I've got the show back up and running using only LS-ADAT (sacrificed a lot of channels, but it'll have to do). After our run ends next month, should I be talking to someone for an RMA on the cards?


Edited by dasbin - September/19/2011 at 11:48am

Sorry to hear you had trouble.  Just jumper the card to EEPROM 1 (you will probably have to remove it from the slot to do this) and try flashing the firmware again.  The FWUpdate program can only update EEPROM 2, so you always have a protected version of the firmware on the card.

Once you have successfully updated to Build 12 firmware, set the jumper back to EEPROM 2 so the card will boot with the new firmware.


Edited by David A Hoatson - September/30/2011 at 7:40pm

Thanks for the update!  Glad it hear it worked out OK for you.