Dangerous Prototypes

Other projects => Past projects => CPLD programmable logic => Topic started by: miro on December 14, 2011, 01:25:27 am

Title: XC9572XL board - the pin 7 issue still there
Post by: miro on December 14, 2011, 01:25:27 am
Guys, I've got the board a week ago and while working with it I see the pin 7 is still connected to V+ and C1. This has been discussed since May this year.. Is that such a problem to fix a board you sell ? :( Miro
Title: Re: XC9572XL board - the pin 7 issue still there
Post by: ian on December 14, 2011, 10:22:10 am
Hi Miro,

I'm really sorry about the bug. We scrapped the broken boards and put in a replacement design immediately, v1a and later v1b with date code May 2011:
http://code.google.com/p/dangerous-prot ... e%2FXilinx (http://code.google.com/p/dangerous-prototypes-open-hardware/source/browse/#svn%2Ftrunk%2FCPLD_Breakout%2Fhardware%2FXilinx)

Can you please tell me the version and date on the back of your PCB? I will check with Seeed to see if this is back stock, a mistake in manufacturing, or what. I can send you a v1a or v1b replacement as soon as I confirm what is going on.
Title: Re: XC9572XL board - the pin 7 issue still there
Post by: miro on December 14, 2011, 03:26:44 pm
Ian, the board has following on its backside:
CPLD  Breakout v1.0
QC Passed
I cannot see any date on the backside except your logo and www, and seeeds www.
Order #39163, paid Nov26,2011, shipped Nov28,2011

I soldered the pin headers on it, uploaded my design (pin7 as output) to it, and then I started to seek the pin7. Not sure how is the pin7 health, however.
Miro
Title: Re: XC9572XL board - the pin 7 issue still there
Post by: ian on December 14, 2011, 03:49:16 pm
Thank you Miro,

I'm really sorry about that. I wrote to seeed to see if it is isolated or the whole batch.
Title: Re: XC9572XL board - the pin 7 issue still there
Post by: miro on December 15, 2011, 03:31:40 pm
Ian, thanks. I would be happy to get the latest release of the board from seeeds..
Regards,
M.
Title: Re: XC9572XL board - the pin 7 issue still there
Post by: miro on December 16, 2011, 03:49:41 pm
Ian, pls contact Kevin from seeeds as they consider v1b is only "*Silk update" "*Capacitor C1 removed" and they ship v1.0.
1. the pin7 is missing on the header
2. C1 is connected to pin7
3. pin7 is hard-wired to VCCIO (ie +3V3).
I would be happy to get a fixed board from them..
M.
Title: Re: XC9572XL board - the pin 7 issue still there
Post by: ian on December 16, 2011, 04:55:13 pm
We have a handle on the situation now, thank you. Please PM me your address and I will send a replacement.
Title: Re: XC9572XL board - the pin 7 issue still there
Post by: ian on December 19, 2011, 03:59:39 pm
Hi Miro,

Of course I will replace the board. Now that the stock is accounted for I can ensure you get the v1b board. I am so sorry for the difficulties caused, thank you for altering me to the issue.

Please do not let this negatively reflect on Seeed. Seeed only acts as my fulfillment team, I am responsible for the hardware inventory and replacements. We caught the bug in May, you rightly expected to receive the v1b board at this late date. My sincerest apologies.

When a user reported the problem with pin 7 we made v1a, then v1b to fix a small silk update. We put the v1b into production in the next batch immediately. I thought we used the last few v1.0 boards as freebies, but we ended with with a mix of stock. It is my fault and I am sorry.

Thank you again for bringing it to my attention. Seeed will separate the versions and we'll sell the v1.0 with a note of the defect so this does not happen again.

I also replied via email.

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