<mithro>
sb0: They don't appear to be linked from the misoc README, so took me a while to find them. Do you think it is worth adding it there?
<mithro>
rjo: ping? - Why doesn't the package matter in your bscan_spi stuff?
<sb0>
mithro, migen/misoc/artiq flashing support needs some overhaul. switch to openocd, remove any inferior flasher superseded by it, update the documentation
<mithro>
rjo: Your bscan_spi seems to work on my fgg484-3 part - yet on that part T13 is a VCC pins rather than one of the SPI config pins. Is there some special magic which maps from the csg324-2?
<sb0>
mithro, i would think the silicon die is the same in all package variants of a given fpga
<sb0>
and the bitstreams refer to a given location on the die, not on the package. and the SPI pins have special function, as they are also used for configuration from the flash
* mithro
is trying to modify the flash stream to toggle a LED at the same time - slowly getting there
<sb0>
mithro, the problem with toggling LEDs is it is board-dependent
<mithro>
sb0: yeah - this flash proxy will be specific to my board
<sb0>
why not use a generic flash proxy that will work on all boards with that FPGA?
<sb0>
in fact, they should work on all boards with the same FPGA die, if we make some assumptions that are actually reasonable
<mithro>
sb0: because this board has an error on it (fixed on prod boards) which means if you pull a given pin low it resets the USB JTAG programming chip
<mithro>
sb0: so once I have a custom flash proxy, making it flash an LED so I can see what is going on seems like a simple thing to do
<mithro>
sb0: actually adding a "-g UnusedPin=PullNone" to the bitstream generation would make the generic flash proxy work on this board
<sb0>
mithro, i'd recommend that...
<mithro>
sb0: I'll send a pull request with that
<mithro>
sb0: I'd be skeptical that anything from Xilinx is reasonable ;)