He guys.
Just found this project a couple of days ago and after a few lines of code, I can flash our boards just fine!
I would like to throw a few ideas around. I expect the ft2232 programmer to be tweaked by quite a bit of people. I had to program an SPI flash but pull down a line on an FPGA to disable it from bus contention. I implemented a shutdown function to allow the FPGA to restart.
On another board, I have 2 spi flash to program using the same channel but separate chip selects.
I have implemented the changes using the same paradigm used for the JTAGkey. Just because we have a different USB PID, I had to duplicate some code. In this case, the same I/O lines were used.
The issue I have with this implementation is that the list of devices in there could fill up quite a bit. A lot of implementations may use the same I/O lines (we did...) If I go and submit my patches, it won't be of much use since our hardware is embedded in our product and won't be public domain.
So what do you prefer, complicating the command line parameters by adding PIDs/VIDs, sub-channels (multiple flash chips per channels), Chip select masks or keeping the code simple as is but knowing the code may grow and there may be tons of weird ways to use the chip that may not be usable by all.
I believe that while I was writing this, I answered myself...
On another note: I had to disable file size checking in the code since I don't have fixed size images. I did not want to pad the files since the last sector of flash is used for other means. Would people mind if I add another switch or change the behaviour of -f to disable file size checking?
CONFIDENTIALITY CAUTION This e-mail and any attachments may be confidential or legally privileged. If you received this message in error or are not the intended recipient, you should destroy the e-mail message and any attachments or copies, and you are prohibited from retaining, distributing, disclosing or using any information contained herein. Please inform us of the erroneous delivery by return e-mail. Thank you for your cooperation. DOCUMENT CONFIDENTIEL Le présent courriel et tout fichier joint à celui-ci peuvent contenir des renseignements confidentiels ou privilégiés. Si cet envoi ne s'adresse pas à vous ou si vous l'avez reçu par erreur, vous devez l'effacer. Vous ne pouvez conserver, distribuer, communiquer ou utiliser les renseignements qu'il contient. Nous vous prions de nous signaler l'erreur par courriel. Merci de votre collaboration.