> Hi Francesco,
>
> Thanks for your effort,
>
> Take a look at the following article for accessing jtag port in a user
> design.
>
> http://www.xilinx.com/publications/xcellonline/xcell_53/xc_jtag53.htm
>
> Best regards,
> Alper YILDIRIM
>
> > Does anybody know how to read/write the BRAM using the JTAG?
> > I need this to design the debugger....
> Does anybody know how to read/write the BRAM using the JTAG?
> I need this to design the debugger....
Reply by Jim Granville●April 27, 20062006-04-27
Francesco wrote:
>>Have you also looked at the quite similar ( but open sourced )
>>Lattice Mico8,
>
>
> Yes I had a look at Lattice Mico8,
> but to be honest at work I use only Xilinx...
FWIR, when I looked at them both, the Mico8 lacked the
Return with Flag option, and the Mico8 looked to have
an easier way to extend the JMP/CALL, to allow
larger code. [which will matter to C users :) ]
- ie when doing a compiler, look at allowing different
call sizes, as legal/error, and some simple means to
modify the opcode generation to match that detail
of the core.
>>and also the PacoBlaze ?
>
>
> I think Pacoblaze is compatible with picoblaze,
> so you can use the compiler with pacoblaze in any FPGA.
I think there are some (optional) extensions in PacoBlaze,
that could make sense to support in a compiler.
-jg
Reply by Francesco●April 27, 20062006-04-27
>Have you also looked at the quite similar ( but open sourced )
>Lattice Mico8,
Yes I had a look at Lattice Mico8,
but to be honest at work I use only Xilinx...
>and also the PacoBlaze ?
I think Pacoblaze is compatible with picoblaze,
so you can use the compiler with pacoblaze in any FPGA.
>In the examples section, you could add the output files,
>with the source, so users can easily see the code generated ?
OK I will do.
Does anybody know how to read/write the BRAM using the JTAG?
I need this to design the debugger....
Thanks all you.
Francesco
Reply by Francesco●April 27, 20062006-04-27
Yes,
binary only for windows!
Reply by Jim Granville●April 26, 20062006-04-26
Francesco wrote:
> Hi all,
> On www.poderico.co.uk you can download the free C compiler for
> Picoblaze version 1.7.7
> In the next 2 months the optimizer should be ready and the code
> generated will be shorter.
> I' wish to design the debugger too.
> Any help and suggestions is welcome.
Reply by bluetooth with FPGA●April 26, 20062006-04-26
so wonderful site !!!!!!
Reply by Mike Harrison●April 26, 20062006-04-26
On Wed, 26 Apr 2006 11:08:19 -0700, Stephen Williams <spamtrap@icarus.com> wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Francesco wrote:
>> Hi all,
>> On www.poderico.co.uk you can download the free C compiler for
>> Picoblaze version 1.7.7
>> In the next 2 months the optimizer should be ready and the code
>> generated will be shorter.
>> I' wish to design the debugger too.
>> Any help and suggestions is welcome.
>
>
>Binary only?
>Windows only?
There's no pleasing some people....
Reply by Stephen Williams●April 26, 20062006-04-26
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Francesco wrote:
> Hi all,
> On www.poderico.co.uk you can download the free C compiler for
> Picoblaze version 1.7.7
> In the next 2 months the optimizer should be ready and the code
> generated will be shorter.
> I' wish to design the debugger too.
> Any help and suggestions is welcome.
Binary only?
Windows only?
- --
Steve Williams "The woods are lovely, dark and deep.
steve at icarus.com But I have promises to keep,
http://www.icarus.com and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFET7cTrPt1Sc2b3ikRAo1KAKCKJHOLp4gMojLU17RSSuLKwc0w0gCfVdgT
WT+pcUQR2wGuFLTNZx+E6p8=
=BqYQ
-----END PGP SIGNATURE-----
Reply by Francesco●April 26, 20062006-04-26
Hi all,
On www.poderico.co.uk you can download the free C compiler for
Picoblaze version 1.7.7
In the next 2 months the optimizer should be ready and the code
generated will be shorter.
I' wish to design the debugger too.
Any help and suggestions is welcome.
Francesco