On Oct 23, 2011, at 11:15 PM, V G <x.solarwind.x@gmail.com> wrote:

> On Sun, Oct 23, 2011 at 11:03 PM, <martin@davintech.ca> wrote:
>=20
>> Doesn't picoblaze run out of block ram? I think block ram is pretty easy
>> to change (on the fly with a dual port ram or just a new fpga load with =
the
>> changed block ram init values).  A new fpga load is stored in the flash
>> anyway.
>>=20
>=20
> I don't want to resynthesize every time I recompile my picoblaze code.
>=20

 I am pretty sure there is a way to reload a block ram with new init values=
 post place n route. Check fpga_editor as a last resort method.

>=20
>> I have looked at using picoblaze many times but always went to a dedicat=
ed
>> state machine due how slow picoblaze is. I am sure it has its uses thoug=
h.
>=20
>=20
> Slow? I don't understand. I thought it can do 2 cycles per instruction at=
 up
> to 200MHz.

But you can do lots of stuff in parallel @ 200.=20

MD



> --=20
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist

--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.