Dangerous Prototypes

Dangerous Prototypes => Bus Blaster JTAG debugger => Topic started by: sjdavies on September 22, 2013, 08:36:46 am

Title: Bus Blaster v3c unable to modify EEPROM
Post by: sjdavies on September 22, 2013, 08:36:46 am
Hi all,
have recently received a BB v3c and have been unable to reprogram the devices EEPROM using the FTDI FT Prog utility.

I have tried FT Prog versions 2.6.8 and 2.8.2.0, both issue an index out of bounds error. Have previously used v2.6.8 to modify the EEPROM on the Dangerous Prototypes FT2232H breakout board.

Has anyone else experienced this problem?

Cheers,
Steve
Title: Re: Bus Blaster v3c unable to modify EEPROM
Post by: jkoleszar on October 15, 2013, 12:20:48 am
Hi Steve,

I also experienced this problem with 5 different BB v3c I purchased around the same time as you (9/17). I diagnosed it with a logic analyzer as the eeprom being bad. Replacing the eeprom on one board with a known good one allowed me to write to it as expected. I suspect that a number of boards from this production batch will have the same problem. I've got parts on order to fix my other 4, and I'll post back if the fix doesn't work on the others.
Title: Re: Bus Blaster v3c unable to modify EEPROM
Post by: sjdavies on November 19, 2013, 05:37:27 am
Thanks,
will try this myself.
Title: Re: Bus Blaster v3c unable to modify EEPROM
Post by: sjdavies on November 27, 2013, 03:45:23 am
Tried replacing the EEPROM, no joy, FT Prog still failing with index bounds error. Tried the previous programming utility MPROG, it fails as well.
Title: Re: Bus Blaster v3c unable to modify EEPROM
Post by: anzas on January 21, 2014, 12:47:05 pm
Hi
Have you found any solutions to this programming issue. I also get the same "Index was outside the bounds of the array" error while trying to program the chip with ft_prog. Erase seems to work. I measured the eeprom serial bus and one thing I noticed was that  there is no signaling on the bus when the programming starts. So this could point that the problem could actually be on the software side.

//-nza
Title: Re: Bus Blaster v3c unable to modify EEPROM
Post by: anzas on January 29, 2014, 07:47:05 am
I tried to flash the thing with Linux ftdi_eeprom and from there I got a read checksum error. So it seemed that the eeprom in my BB was faulty as well. Everything started to work after I replaced the chip.
Title: Re: Bus Blaster v3c unable to modify EEPROM
Post by: dtkav on February 19, 2014, 09:08:12 am
I tried flashing through both windows tools (mprog and ft_prog) as well as the linux libftdi eeprom example code without luck. I looked into the chip, and it looks like the eeprom selected might not have a sufficient input voltage. Check out the device selection table in the datasheet for the 93C46B. (sorry i'm a new user so I can't post a link)

The 93C46B parts have an operating range from 4.5V-5.5V, but the schematics show VCC connected to 3V3.

Can anyone confirm this possible problem? In the mean time i'm going to order some of the 93LC46B's. They seems to be a low voltage drop in replacement.

Best,
DK
Title: Re: Bus Blaster v3c unable to modify EEPROM
Post by: dtkav on February 21, 2014, 01:27:42 am
I lifted the VCC pin of the eeprom (U6, pin 8) and wired it to the 5V input of the voltage regulator (U1, pin 3) and the eeprom programmed fine using ft_prog. I believe this is a design flaw with the board / BOM as built by Seeedstudio :(.
Title: Re: Bus Blaster v3c unable to modify EEPROM
Post by: dtkav on February 23, 2014, 06:49:59 pm
I got the low voltage eeprom parts in (93LC46B) and reworked 6 bus blasters. They all worked great with FT_PROG with the new part.
Title: Re: Bus Blaster v3c unable to modify EEPROM
Post by: sjdavies on February 05, 2015, 12:47:51 pm
A big thanks all, this was driving me crazy. Didn't make the 3.3V vs 5V connection.
Title: Re: Bus Blaster v3c unable to modify EEPROM
Post by: sjdavies on February 11, 2015, 07:09:36 am
In Feb 2015 attempted to order a Bus Blaster v3 from Seeedstudio, heard there was a new batch. Made it clear that I wanted one with the 93LC46B part installed. They were unable to supply and the order was cancelled (new batch still has wrong part).

Bottom line, this is a problem if you want to use a custom USB VID/PID.

( ! ) 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.01032065912session_write_close ( )...(null):0
20.01072197488ElkArte\sources\subs\SessionHandler\DatabaseHandler->write( )...(null):0
30.01072198264Database_MySQL->query( ).../DatabaseHandler.php:119
40.05472336984Database_MySQL->error( ).../Db-mysql.class.php:273