hi,
could someone post the busblaster v2 eeprom content in hex here? I need to rewrite it on mine.
You could blur the serial bytes if needed.
I can't find anything related in the svn repository, nor the build process page.
Thank you
I would guess that it is empty then (all 0xFFs) :-)
It is just guess, my came without one.
Yup, we ship it blank. The FT2232 should use default settings if it is blank. You can grab the (windows) program utility here:
http://www.ftdichip.com/Support/Utilities.htm (http://www.ftdichip.com/Support/Utilities.htm)
If you need an alternate (Mac) program utility, robots or PPPD (sorry, a long time ago, and they are both the best programmers I know, and live in the same general region, I forget who did it) wrote one a while ago that I can dig up for you.
Thanks,
that's perfectly clear now.
Hi Ian,
We have allocated an additional 8 PIDs to your company from 8878 through 887F (hex).
The PIDs must be used with VID 0403.
To reprogram the EEPROM use MPROG (http://www.ftdichip.com/Support/Utilities/MProg3.5.zip (http://www.ftdichip.com/Support/Utilities/MProg3.5.zip) ) or FT_PROG (http://www.ftdichip.com/Support/Utiliti ... _v1.10.zip (http://www.ftdichip.com/Support/Utilities/FT_Prog_v1.10.zip) )
You can easily create customized INF files by using our FT_INF utility:
http://www.ftdichip.com/Support/Utilities/FT_INF.zip (http://www.ftdichip.com/Support/Utilities/FT_INF.zip)
NOTE 1: Editing the driver for your new identity will invalidate any current driver certification.
NOTE 2: It will be necessary for you to maintain your own edited driver release for distribution to your customers.
NOTE 3: Please send us a copy of your INF files when you have completed your changes to them. We will review them for you.
Please reference the following application and technical notes:
http://www.ftdichip.com/Support/Documen ... elines.pdf (http://www.ftdichip.com/Support/Documents/TechnicalNotes/TN_100_USB_VID-PID_Guidelines.pdf)
http://www.ftdichip.com/Support/Documen ... oducts.pdf (http://www.ftdichip.com/Support/Documents/TechnicalNotes/TN_102_OEM_Technical_Support_Requirements_for_FTDI_Products.pdf)
http://www.ftdichip.com/Support/Documen ... rocess.pdf (http://www.ftdichip.com/Support/Documents/AppNotes/AN_101_WHQL_Certified_Driver_Process.pdf)
Regards,
Savyasaachi Keshava Murthy
Applications Engineer
I applied for and received some PIDs for the Bus Blaster. You can use these as dedicated PIDs if you need something other than the default. Suggested use:
0403 8878 for Bus Blaster v2 serial channel A
0403 8879 for Bus Blaster v2 serial channel B
Other PIDs are reserved for future projects. We will not release custom .infs for the time being, but the libftdi install package will create a custom .inf you can use.