Re: urjtag and PROM to FPGA Configuration Mode
Reply #3 –
Hey,
ok i guess I got all parts together.
since a certain release impact has a function call "One step SVF". From there help
An SVF file named default.svf is created in your project directory. For PROMs and CPLDs, the SVF file contains device erase, program, and verify sequences using the specified configuration data file. For FPGAs, the SVF file contains a device program sequence using the specified device bitstream file.
Sounded good and valid to me. Erasing, Programming, Verifying... what else, right?!
Apparently NOOOOOO, thanks Xilinx!!!
This svf file does not contain any config option.
If you go the more complex way, creating a new project->Prepare a Boundary-Scan File (choose) SVF and do all the steps manually (really all, since they will be recorded ALL in the SVF file). It seems to work.
E.g., in the "hand-made" svf file, I found
//Operation: Program -p 0 -e -r -loadfpga -master -internalClk -clkFreq 20 -defaultVersion 0
TIR 0 ;
HIR 0 ;
TDR 0 ;
HDR 0 ;
TIR 0 ;
HIR 0 ;
HDR 0 ;
TDR 0 ;
//Loading device with 'idcode' instruction.
SIR 16 TDI (00fe) ;
SDR 32 TDI (00000000) SMASK (ffffffff) TDO (f5058093) MASK (0fffffff) ;
The program operation was exactly what was missing within the "One step" SVF files. Thanks again Xilinx for making things more complicated!
I have now more or less a good overview of what to do and hope to update the wiki soon.
This is on the list at the moment:
* Using the busblaster with impact directly under Linux via the opensrouce drivers
* Creating valid SVF files from within impact
* Using urjtag and the busblaster under Linux
* Getting steppings and bsdl stuff right
I still want to check if I can manage to compile urjtag with the "native" ftdi_sio modules. That would avoid the usage and installation of the ftd2xx drivers and the necessary fiddling between those two modules.