Skip to main content ↑ ↓

Show Posts

This section allows you to view all Show Posts made by this member. Note that you can only see Show Posts made in areas you currently have access to.

Messages - Grapsus

1
General discussion / Re: Analog Discovery - 7400 competition price
[quote author="Colfaxmingo"][quote author="Grapsus"]Very cool !

Here is the Xula2 FPGA kit I got from Xess corp a few days ago. The documentation and the examples are superb. I can't wait to make a project with it.[/quote]

I can't be the first one to notice the LEDs in this picture.... right?  Please don't tell me I'm still 12 years old... right?[/quote]

I don't see what you are talking about :D

@Matseng sorry I posted the photo of my prize in your thread, I first thought it was for all 7400 prizes. Do you want me to move it ?
3
USB serial LCD backpack / Re: Using universal USB LCD backpack as FT232 breakout
You're right, those shift registers are output only, so there no use in reading data back.

I thought about your 2) solution, but sadly DSR disables only parallel outputs of the shift registers, and RXD is driven by the "serial output" pin, which doesn't have a high impedence mode. Moreover I'd like to be able to use the DSR signal as I wish.

So I think I will go with your first solution and cut the serial output trace.

Thank you !
4
USB serial LCD backpack / Using universal USB LCD backpack as FT232 breakout
Hi there !

I noticed that the documentation for the FT232 backpack says, it can be used as FT232 breakout :
http://dangerousprototypes.com/docs/USB ... D_backpack
The problem is that RXD input is driven by a shift register output, and there seems to be no way to disable it.
Do I have to desolder the shift registers to use the PCB as FT232 breakout, or is there a smarter way to do it ?

Thank you in advance
5
Bus Blaster JTAG debugger / Re: Bus Blaster v4.1a BOM
@ian What is the speed requirement for the 4066 chips ? I used SN74AHC4066D from TI in my build, which works so far, but I'd like to be sure it won't have glitches at high speed.
6
Bus Blaster JTAG debugger / Re: Bus Blaster v4 power up test success, bitstream next
Here is a patch so that the test utility builds both on Linux and Windows :
Code: [Select]
Index: main.cpp
===================================================================
--- main.cpp	(revision 2034)
+++ main.cpp	(working copy)
@@ -11,14 +11,23 @@
  * 
  */
 
+#ifdef _WIN32
 #include <Windows.h>
 #include <WinDef.h>
+#else
+#include <inttypes.h>
+typedef uint32_t DWORD;
+#endif
 #include <stdio.h>
 #include <stdlib.h>
 #include <malloc.h>
 #include <time.h>
 
+#ifdef _WIN32
 #include "ftdi/ftd2xx.h"
+#else
+#include <ftd2xx.h>
+#endif
 
 #define MAX_DEVICES 10
 
@@ -37,17 +46,16 @@
 FT_STATUS     ftStatus;
 int           shortDelay;
 
-
+#ifdef _WIN32
 struct timespec {
-   int tv_sec;        /* seconds */
-   long   tv_nsec;       /* nanoseconds */
+   int tv_sec;        /* seconds */ 
+   long   tv_nsec;        /* nanoseconds */
 };
+#endif
 
-
 struct timespec T;
 
-
-
+#ifdef _WIN32
 void nanosleep(struct timespec *x, struct timespec *y){
 	if (shortDelay){
 	   Sleep(10);
@@ -55,6 +63,7 @@
        Sleep(1000*x->tv_sec+x->tv_nsec/100000000);
 	}
 }
+#endif
 
 unsigned char kbhit_getc()
 {
Index: Makefile
===================================================================
--- Makefile	(revision 0)
+++ Makefile	(working copy)
@@ -0,0 +1,7 @@
+all: BusPiratev2Test
+
+BusPiratev2Test: main.o
+	gcc -o $@ $< -lftd2xx
+
+clean:
+	rm -f *.o BusPiratev2Test

Assuming you installed ftd2xx.h and libftd2xx.so to /usr or /usr/local, just use make to build.

Code: [Select]
$ make
g++    -c -o main.o main.cpp
gcc -o BusPiratev2Test main.o -lftd2xx
$ sudo ./BusPiratev2Test -n0
Select device:
Device 0 (Serial Number: 4.1A
Device 1 (Serial Number: 4.1B

======================================================
SUCCESS (Connected to the FTDI.4.1A)
SUCCESS (reset)
SUCCESS (usb parameters set)
SUCCESS (event chars disabled)
SUCCESS (timeouts set)
SUCCESS (latency set)
SUCCESS (flow control disabled)
SUCCESS (MSSPE reset)
SUCCESS (MPSSE on)
START TESTING

======================================================
	00000001	00000001
	00000010	00000010
	00000100	00000100
	00001000	00001000
	00010000	00010000
	00100000	00100000
	01000000	01000000
	10000000	10000000
	00000000	00000000
	10101010	10101010
	01010101	01010101
	00000000	00000000
	11111111	11111111
Testing complete, errors: 0
7
Bus Blaster JTAG debugger / Re: Bus Blaster v4 power up test success, bitstream next
I soldered an I2C EEPROM and customized the VID/PID data with the utility from FTDI :

Code: [Select]
[  113.023463] usb 2-1.1: new high-speed USB device number 4 using ehci_hcd
[  113.120867] usb 2-1.1: New USB device found, idVendor=0403, idProduct=8879
[  113.120879] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  113.120887] usb 2-1.1: Product: Bus Blaster
[  113.120893] usb 2-1.1: Manufacturer: Dangerous Prototypes
[  113.120899] usb 2-1.1: SerialNumber: 4.1

As expected the device stopped being recognized by Windows, so I had to create an inf file and install it manually, which is kind of painful. Hopefully I don't use Windows much.
For Linux there seems to be a big drawback : urJTAG doesn't recognize the chip anymore, even with "cable ft2232 vid=... pid=...".
The solution I found is to provide a file named "libft2dxx_table.so" which tells the FTDI driver to take your custom PID into account. It can build using this source :
http://svn.icmb.utexas.edu/svn/reposito ... lib_table/

It will be pretty annoying to do that on every computer on which I will use my bus blaster, so I'm not sure if I will keep the custom PID.

@Ian please could you please release the source code of the test utility ? I'd like to study it and port it to Linux, which shouldn't be too complicated.
9
Bus Blaster JTAG debugger / Re: Bus Blaster v4 power up test success, bitstream next
Code: [Select]
C:UsersGrapsusDesktop>BusPiratev2Test_VisualC++Express.exe -delay -n0
Select device:
Device 0 (Serial Number: A
Device 1 (Serial Number: B

======================================================
SUCCESS (Connected to the FTDI.A)
SUCCESS (reset)
SUCCESS (usb parameters set)
SUCCESS (event chars disabled)
SUCCESS (timeouts set)
SUCCESS (latency set)
SUCCESS (flow control disabled)
SUCCESS (MSSPE reset)
SUCCESS (MPSSE on)
START TESTING

======================================================
        00000001        00000001
        00000010        00000010
        00000100        00000100
        00001000        00001000
        00010000        00010000
        00100000        00100000
        01000000        01000000
        10000000        10000000
        00000000        00000000
        10101010        10101010
        01010101        01010101
        00000000        00000000
        11111111        11111111
Testing complete, errors: 0

I confirm that my Bus Blaster v4.1 is up and running without any patch wire.

I'm kind of ashamed : at first the test was giving 4 errors suggesting a short between TRST and DBGRQ and indeed I left a small blob of solder between two legs of RN3 which is so easy to solder compared to the CPLD.

@mikelelere thank you for sharing the SVF for XC2C128 test image !
10
Bus Blaster JTAG debugger / Re: Bus Blaster v4 power up test success, bitstream next
Hi there !

@Ian I got the PCB last friday, thank you very much !

I got the components I didn't have already this morning from Farnell. I had to take the 128 cells CPLD version as the 64 one was sold out. A photo of my build is attached.

Man, this VQFP100 CPLD chip was such a pain to solder !
I didn't populate the I2C EEPROM yet, I will do it later to customize the VID/PID if everything else works fine.

My board powered up OK, the FT2232 was recognized. Then I spent two hours building urJTAG with libftd2xx. Finally the CPLD is alive :

Code: [Select]
warning: UrJTAG may damage your hardware!
Type "quit" to exit, "help" for help.

jtag> cable ft2232 interface=0
Connected to libftd2xx driver.
jtag> detect
warning: TDO seems to be stuck at 1
jtag> cable ft2232 interface=1
Connected to libftd2xx driver.
jtag> detect
IR length: 8
Chain length: 1
Device Id: 00010110110110001010000010010011 (0x16D8A093)
  Manufacturer: Xilinx (0x093)
  Unknown part! (0110110110001010) (/usr/local/share/urjtag/xilinx/PARTS)

I will try to flash the JTAGKey image tomorrow.

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