Skip to main content ↑ ↓

Messages

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

Messages - pppd

48
General discussion / Free USB IR Toy V1 PCB + RLC parts
Some time ago I got an USB IR Toy PCB from Ian but I don't think I will have time to build it any time soon ( too many other things to play with ).

So if anybody, preferably from Europe, would like to make one just write here ( so everyone knows its taken ) and then PM me with your address and I will send you the PCB + all basic RLC parts, NPN transistor and the IR LED required to build one.
49
General discussion / Re: Forum migration
Thanks Ian! It was a nice surprise to get a pop-up stating that this forum is now available for Tapatalk :) Now I can read it without using my nose to zoom in while on a bus:)
50
Bus Blaster JTAG debugger / Re: SWD - BBv2 CPLD KT-link implementation
I haven't had time to get any deeper on this.. but does it mean that I will have to reflash the CPLD every time I want to switch between SWD and regular JTAG or it will be possible to change it preferably by placing a jumper on two of the JP2 pins?
52
Bus Blaster JTAG debugger / Re: Re: urJTAG for Bus Blaster v2 JTAG B
Sure thing, I will have a breakfast and then post an updated utility. Right now it uses FTDI Vendor ID ( 0x0403 ) and the PID was selected to be an abbreviation of BusBlaster02. I will also add a restore option to bring the default VID/PID back.

I don't think you should use anything different than the original 0x0403/0x6010 when selling it. I guess Mac users are minority anyway and I believe Linux/Windows customers aren't affected by this problem. They can still put name strings though.
53
Bus Blaster JTAG debugger / Re: urJTAG for Bus Blaster v2 JTAG B
I have updated XCode to the version 4 and I am no longer able to build PPC binaries so this is an Intel only build. It includes source code and a Makefile so anyone can build it for their own platform and OSX version if necessary.

Libusb-1.xx is required for both compiling and working but you need it anyway for JTAG/OpenOCD. You can install it from Macports with the following command: "sudo port install libusb"

It is a command line utility which has a predefined EEPROM values, no fancy GUI there. It takes no arguments and detects devices by itself. Below is an extract from a successful session:
Code: [Select]
BusBlaster rename utility
Initializing libusb-1.0...OK
Initializing libftdi...OK
Listing USB devices...OK
Found 1 FTDI device(s):

 ID	VID  	PID  	Description (serial)
 01	0x0403  0x6010  FT2232H (1a74e44)

Which device would you like to program (1-1):1

Your device will be programmed with the following values:

 Vendor  ID  : 0x0403
 Product ID  : 0xBB02
 Manufacturer: Dangerous Prototypes
 Description : BusBlasterV2
 Serial      : BBv2
 Current req : 200mA

Are you sure you want to write EEPROM (yes/no):yes
Opening selected FTDI device...OK
Writing EEPROM...OK

You can now load the FTDI kernel driver back :)

[attachment=0]
55
Bus Blaster JTAG debugger / Re: urJTAG for Bus Blaster v2 JTAG B
So Far, So Good :)

OpenOCD is happy to accept custom vid/pid so it seems it will work just fine after all.
Code: [Select]
#
# Bus Blaster v2
#
# http://dangerousprototypes.com/docs/Bus_Blaster
#
interface ft2232
ft2232_device_desc "BusBlasterV2"
ft2232_serial "BBv2"
ft2232_layout jtagkey
ft2232_vid_pid 0x0403 0xbb02
56
Bus Blaster JTAG debugger / Re: urJTAG for Bus Blaster v2 JTAG B
It has always been like that in MacOSX. I remember I had to disable the driver for libftdi use as well when coding the renaming utility.

There is a workaround for that, but it is a trick and should be used by individuals only, surely not in the production device. You can change the VID/PID of BBv2 to something non-existing and [s:]then patch the urJTAG to recognize the new VID/PID pair as FT2232H[/s:]. This does work well on my computer :)

edit: Actually there is no need to patch urJTAG at all, as you can specify VID/PID when connecting. I have changed my PID to 0xBB02 and it works perfectly along with FTDI serial drivers. All I have to do is use vid parameter when connecting:
Code: [Select]
cable ft2232 pid=0xbb02
I don't think this will work with other apps that depend on default VID/PID though.. so I guess I will need to unload the driver anyway.
57
Bus Blaster JTAG debugger / Re: urJTAG for Bus Blaster v2 JTAG B
I have finished populating BBv2 board and I was about to go through the patching process but it turns out the latest GIT version already includes all the patches.

However, it seems that the interface should be set to "1", default is "0" and not "2" as the Wiki says. At least this way I was able to program it with MacOSX. The only irritating thing about it is that I have to unload FTDIUSBSerialDriver.kext serial driver every time I want to use it, but I can live with that.
Code: [Select]
jtag> cable ft2232 interface=1
Connected to libftd2xx driver.
jtag>

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