<div dir="ltr">yep, its the whole purpose of all this noise. <div>But the bram on the targetboard that started the discussion is a bit small, so back to software we go. </div><div>Perhaps we need to look again which board to use.</div><div><br></div><div>cheers,</div><div>j.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 28, 2015 at 10:26 PM, Walter Gallegos <span dir="ltr"><<a href="mailto:walter@waltergallegos.com" target="_blank">walter@waltergallegos.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I read several post about RISC5, FPGA, BRAM, FLASH, etc.<br>
<br>
My point is, software guys need redirect your minds when in FPGA arena due<br>
the new resources available; new issues and challenges too.<br>
<br>
We are in the programmable logic world; so, limit our horizon to software<br>
only solutions is a big mistake.<br>
<br>
Trying to illustrate with an example, a bootloader is a typical software<br>
solution. The usual way to do this in FPGA is by JTAG, the TAP<br>
controller -available in any FPGA- is connected to the BRAMs, or to a FLASH<br>
controller, to load new memory contents. This is the way how are working<br>
JTAGLoader in PicoBlaze and indirect programming in XILINX.<br>
<br>
Regards,<br>
<br>
<br>
<br>
<br>
<br>
<br>
--<br>
<a href="mailto:Oberon@lists.inf.ethz.ch">Oberon@lists.inf.ethz.ch</a> mailing list for ETH Oberon and related systems<br>
<a href="https://lists.inf.ethz.ch/mailman/listinfo/oberon" rel="noreferrer" target="_blank">https://lists.inf.ethz.ch/mailman/listinfo/oberon</a><br>
</blockquote></div><br></div>