Andrew Leech wrote: > two typical ways of using a SVF on a chain, either the SVF file has to > be generated to know about the chain or the jtag software has to be > aware of the chain.
Yeah, makes sense. > There's specific HDR and similar commands in svf to define these > paddings. Can you say more about them? Did you study the SVF output by FlashPro? It would be interesting to diff a failing SVF with a working one. > Some software like UrJtag ignores these commands if they even exist > and figures them out itself by scanning the chain, this is neat. I think this is the only sensible behavior. > The svf player in openocd doesn't have anything like this (and I don't > have time right now how to figure out how to add it, maybe later), so > you're left with generating the svf files to be aware of the chain, if > the software making the svf has this functionality. Or maybe OpenOCD can patch in the neccessary stuff into the SVF? 3 minutes is also really slow imo, but it is what it is because of how the simple interfaces work. I've ranted enough about that before. > The basic openocd command then for me are simply: > > source [find interface/luminary-icdi.cfg] # > My programmer > source [find target/lpc3131.cfg] > # This is now in mainline :) > jtag_khz 6000 > # Going to try to optimise this later... > reset_config srst_only srst_pulls_trst # > My board's only wired to do this > jtag newtap a3p125 tap -irlen 8 -expected-id 0x02a121cf # The FPGA > init > scan_chain > # just to be sure they're connected properly > svf Chain_PROGRAM_ARRAY.svf quiet # runs my > svf file from flashpro > > and it sits there quietly for just over 3 minutes before informing > me it's all done nicely, and I have a working fpga! > When I get a chance I'll make a patch/updates to the wiki page on > the svf player to be a bit more explicit on how to use it. Thanks! Maybe another option would be for you to just submit a patch with the above board file for your board, with some comments in it? //Peter _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
