Text only | Text with Images

Dangerous Prototypes

Other projects => Past projects => CPLD programmable logic => Topic started by: arhi on February 14, 2012, 04:40:44 pm

Title: maybe someone have a clue why it don't program (xc2c256)
Post by: arhi on February 14, 2012, 04:40:44 pm
Impact log looks like:
Code: [Select]
INFO:iMPACT - Current time: 2/13/12 11:16 PM 
// *** BATCH CMD : Program -p 1 -e -v 
PROGRESS_START - Starting Operation. 
Maximum TCK operating frequency for this device chain: 0. 
Validating chain... 
Boundary-scan chain validated successfully. 
'1': Erasing device... 
'1': Erasure completed successfully. 
'1': Programming device... 
done. 
'1': Verifying device... 
'1': Verification terminated due to errors 
'1': Failed at address 0. 
'1': Programming of user selected options failed. 
PROGRESS_END - End Operation. 
Elapsed time = 1 sec.

Anyone have any idea why it won't program?
Title: Re: maybe someone have a clue why it don't program (xc2c256)
Post by: arhi on February 14, 2012, 07:06:51 pm
Weird, the problem was with bus blaster ... I successfully loaded the bitstream with urjtag and olimex-usb-ocd ... weird .. now I need to figure out what happened to bblaster ?!
Title: Re: maybe someone have a clue why it don't program (xc2c256)
Post by: AndThen on February 14, 2012, 10:43:23 pm
I know you are looking for answers, not more questions. I'll apologize in advance. 
Perhaps a version issue with the blaster, it worked "once upon a time"?
Is it a code protection, maybe a missing reset between the erase and writes?


You had another thread for this and it had better information, did you loose it or just want to cast a wider net =)
This is the same issue, Done bit not getting set? Or did you get past that only to find more.
Title: Re: maybe someone have a clue why it don't program (xc2c256)
Post by: arhi on February 14, 2012, 11:23:30 pm
the other issue was about connection (and the connection is ok) and I wanted to separate the programming part to separate issue for easier search for clues later (google friendly etc)

exactly the same blaster worked on exactly the same board with exactly the same software ... many times .. donno what happened in the meantime ... anyhow, "tweaking" stuff lead to not being able to connect to busblaster from linux at all now :D :D :D so now I first need ti figure out how to recompile stuff so that I can connect to BB (check the FTDI eeprom settings as that's also something I was tweaking etc etc..)
Title: Re: maybe someone have a clue why it don't program (xc2c256)
Post by: arhi on February 15, 2012, 12:07:47 am
solved, and the whole thread is actually pretty useles, I'll write solution in the busblaster thread (http://http://dangerousprototypes.com/forum/viewtopic.php?p=36686#p36686) .. ian might merge this one there or just delete this topic completely as it is utterly useles
Text only | Text with Images

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