Dangerous Prototypes

Dangerous Prototypes => Bus Blaster JTAG debugger => Topic started by: brian on January 05, 2011, 03:58:10 am

Title: FT2232H EEPROM needed?
Post by: brian on January 05, 2011, 03:58:10 am
Is the only purpose of the EEPROM to store the USB ID info for the device? (As per Debug Board v3 page note).
Title: Re: FT2232H EEPROM needed?
Post by: ian on January 05, 2011, 08:57:31 am
Yup, the EEPROM is just for configuration stuff. It will use default settings if there is no EEPROM present. BBv1 does not have the EEPROM populated to save on costs, we were way over budget  because of the buffer chips.
Title: Re: FT2232H EEPROM needed?
Post by: tjtag on January 05, 2011, 10:23:45 am
@drwho9437

The answer to this question is NO, to be more exact, the eeprom allows the configuration of different available modes of the FT2232H chip. Some modes can only be entered into, by programming the eeprom chip. See page 44 od DS_FT2232H.

Does that answer your question more specifically ?
Title: Re: FT2232H EEPROM needed?
Post by: ian on January 05, 2011, 10:53:01 am
That's right, I forgot there are a couple modes that require the EEPROM. This table shows them. The ASYNC Serial is a little misleading because the chip starts in that mode regardless of the EEPROM being present.
Title: Re: FT2232H EEPROM needed?
Post by: arhi on January 05, 2011, 03:59:58 pm
for e.g. if you want to use FT245 mode you have to have eeprom to store channel types otherwise you can't go 60MHz
Title: Re: FT2232H EEPROM needed?
Post by: brian on January 05, 2011, 10:41:35 pm
[quote author="tjtag"]
Does that answer your question more specifically ?
[/quote]

Got it. I will read the man soon. So little time...
Title: Re: FT2232H EEPROM needed?
Post by: ian on January 13, 2011, 02:58:44 pm
Just a friendly note if you're following this topic...

I split the monster Bus Blaster v2 thread into several small parts that should be easier to surf, but you will not get more notifications until you comment or click 'notify' on the new threads.

Bus Blaster v2 design thread http://dangerousprototypes.com/forum/in ... pic=1490.0 (http://dangerousprototypes.com/forum/index.php?topic=1490.0)
BBv2 CPLD design and implementation http://dangerousprototypes.com/forum/in ... pic=1659.0 (http://dangerousprototypes.com/forum/index.php?topic=1659.0)
urJTAG for BBv2 JTAG B http://dangerousprototypes.com/forum/in ... pic=1655.0 (http://dangerousprototypes.com/forum/index.php?topic=1655.0)
UART on BBv2 MSSPE2? http://dangerousprototypes.com/forum/in ... pic=1656.0 (http://dangerousprototypes.com/forum/index.php?topic=1656.0)
FT2232H EEPROM discussion http://dangerousprototypes.com/forum/in ... pic=1658.0 (http://dangerousprototypes.com/forum/index.php?topic=1658.0)

( ! ) Fatal error: Uncaught exception 'Elk_Exception' with message 'Please try again. If you come back to this error screen, report the error to an administrator.' in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
( ! ) Elk_Exception: Please try again. If you come back to this error screen, report the error to an administrator. in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
Call Stack
#TimeMemoryFunctionLocation
10.01012075296session_write_close ( )...(null):0
20.01042206888ElkArte\sources\subs\SessionHandler\DatabaseHandler->write( )...(null):0
30.01042207664Database_MySQL->query( ).../DatabaseHandler.php:119
40.05282346400Database_MySQL->error( ).../Db-mysql.class.php:273