Digilent 3S200 pcb + webpack ISE 8.2 + service pack

All,

I was recently asked to do a course, which involves actually showing
folks real hardware, with real software.

So, like a good teacher, I went and personally purchased the Digilent
pcb (this is not for work!), the USB programming cable, and went at it.

I also downloaded 8.2 webpack, and the service pack.

Actually trying to use your own product can be very educational.

First, I was never able to use the small "boot" loader for webpack
(perhaps firewalls, virus checkers, etc. wouldn't let me).  Instead, I
had to download the 900 Mb full file.  Since at home is 144 Kb/sec, I
went somewhere where I had 100 Mb/sec access.  My recommendation, get
the DVD.

Then I had to download the service pack, which is 300 Mb.

OK.  Now I just install and go?  YES!  I am using Windoze XP, not Linux,
so I can't say how easy that route would be.

Then I asked a few friends to send me links to projects that run on the
pcb.  Building very simple (one VHDL module, one ucf file) to more
complex projects went well.  As long as I did not try to move any files
around (never do that:  project navigator believes it 'owns' the file
system), everything is just fine.  Since the last time I actually had to
sit down and make bit streams (6.3), the tool (to me) is greatly improved.

I also took a while to find FPGA_Editor, as most people don't care about
it anymore, it is relegated to a sub-bullet in the tree of tools.  Most
of what I do at work involves FPGA_Editor, as I am usually verifying
hardware functions, and I do not want the software to "get in my way."
But, that is no way to do a real design.

OK.  So, I didn't make the pcb, and I didn't have to debug any hardware,
but I was able to modify vhdl, compile, place, route, and make bit
streams (and they worked).

So, for those who don't know anything, or know a lot and want to know
more, I can personally suggest going the Digilent 3S200 $99 pcb route:
it is simple, easy, and works.  The pcb has a 50 MHz clock, a socket for
another clock oscillator, SDRAM for soft processor apps, flash with
extra area in it, VGA interface, RS232C interface, pc keyboard
interface, and a slew of IOs brought out.  Oh, and a 3S200.  Which is
huge (to me).  I usually always try to verify the smallest part (things
happen faster).  I begin to have an appreciation for someone trying to
compile a xcv5lx330 design...

Find the zipped projects for this board, and have at it.  Start with
something small that already works (like the simple seconds/minutes
"clock" -- really a stopwatch), and play around and get more exotic.

San Jose State University, and many other schools and colleges use this
platform, so there is a lot of 'underground' stuff there, along with
more hardware (if you need it) from Digilent (like A/D, D/A, IO, etc).

It is also quite nostalgic for me, as the Spartan 3 is the old Virtex II
in a completely new 90nm cost reduced form (so it feels like an old
friend).  For those who are reading this for the first time, Virtex II
was the part that I was personally involved in.  Because I was in the
Virtex II DCM team, I also did some of the pre-tapeout verification for
the Spartan 3 DCM.

http://www.digilentinc.com/Products/Detail.cfm?Nav1=Products&Nav2=Programmable&Prod=S3BOARD

Austin

Austin Lesea wrote:
> ...
> I was recently asked to do a course, which involves actually showing
> folks real hardware, with real software.
> 
> So, like a good teacher, I went and personally purchased the Digilent
> pcb (this is not for work!), the USB programming cable, and went at it.
>...

This was a good post, thanks.

-Dave

-- 
David Ashley                http://www.xdr.com/dash
Embedded linux, device drivers, system architecture

Austin Lesea wrote:
> All,
>
> I was recently asked to do a course, which involves actually showing
> folks real hardware, with real software.
>
> So, like a good teacher, I went and personally purchased the Digilent
> pcb (this is not for work!), the USB programming cable, and went at it.
>
> I also downloaded 8.2 webpack, and the service pack.
>
> Actually trying to use your own product can be very educational.
>
> First, I was never able to use the small "boot" loader for webpack
> (perhaps firewalls, virus checkers, etc. wouldn't let me).  Instead, I
> had to download the 900 Mb full file.  Since at home is 144 Kb/sec, I
> went somewhere where I had 100 Mb/sec access.  My recommendation, get
> the DVD.
>
> Then I had to download the service pack, which is 300 Mb.
>
> OK.  Now I just install and go?  YES!  I am using Windoze XP, not Linux,
> so I can't say how easy that route would be.
>
> Then I asked a few friends to send me links to projects that run on the
> pcb.  Building very simple (one VHDL module, one ucf file) to more
> complex projects went well.  As long as I did not try to move any files
> around (never do that:  project navigator believes it 'owns' the file
> system), everything is just fine.  Since the last time I actually had to
> sit down and make bit streams (6.3), the tool (to me) is greatly improved.
>
> I also took a while to find FPGA_Editor, as most people don't care about
> it anymore, it is relegated to a sub-bullet in the tree of tools.  Most
> of what I do at work involves FPGA_Editor, as I am usually verifying
> hardware functions, and I do not want the software to "get in my way."
> But, that is no way to do a real design.
>
> OK.  So, I didn't make the pcb, and I didn't have to debug any hardware,
> but I was able to modify vhdl, compile, place, route, and make bit
> streams (and they worked).
>
> So, for those who don't know anything, or know a lot and want to know
> more, I can personally suggest going the Digilent 3S200 $99 pcb route:
> it is simple, easy, and works.  The pcb has a 50 MHz clock, a socket for
> another clock oscillator, SDRAM for soft processor apps, flash with
> extra area in it, VGA interface, RS232C interface, pc keyboard
> interface, and a slew of IOs brought out.  Oh, and a 3S200.  Which is
> huge (to me).  I usually always try to verify the smallest part (things
> happen faster).  I begin to have an appreciation for someone trying to
> compile a xcv5lx330 design...
>
> Find the zipped projects for this board, and have at it.  Start with
> something small that already works (like the simple seconds/minutes
> "clock" -- really a stopwatch), and play around and get more exotic.
>
> San Jose State University, and many other schools and colleges use this
> platform, so there is a lot of 'underground' stuff there, along with
> more hardware (if you need it) from Digilent (like A/D, D/A, IO, etc).
>
> It is also quite nostalgic for me, as the Spartan 3 is the old Virtex II
> in a completely new 90nm cost reduced form (so it feels like an old
> friend).  For those who are reading this for the first time, Virtex II
> was the part that I was personally involved in.  Because I was in the
> Virtex II DCM team, I also did some of the pre-tapeout verification for
> the Spartan 3 DCM.
>
> http://www.digilentinc.com/Products/Detail.cfm?Nav1=Products&Nav2=Programmable&Prod=S3BOARD
>
> Austin

I have this board at home (just for fun). It is well designed.  Just
add an old VGA monitor and PS2 keyboard and you can do lots of
interesting projects.  I bought the board from XIlinx online store last
year.  I think the Xilinx store is no longer selling it (only the S3E
board now).  Dose this mean that the S3 family is going to be
discontinued soon?

Mike G.

Austin Lesea wrote:
>
> So, like a good teacher, I went and personally purchased the Digilent
> pcb (this is not for work!), the USB programming cable, and went at it.
>
> I also downloaded 8.2 webpack, and the service pack.
>

I am sure you are not having as much fun as some of us do !    :-)

>...
>...
>
> I also took a while to find FPGA_Editor, as most people don't care about
> it anymore, it is relegated to a sub-bullet in the tree of tools.  Most
> of what I do at work involves FPGA_Editor, as I am usually verifying
> hardware functions, and I do not want the software to "get in my way."


I care about FPGA_Editor, as it is the only tool that lets you see the
internals of the FPGA, and lets you see how your code translates to the
FPGA.
I thought it was not included in the Webpack. Since when is Xilinx
including the FPGA-Editor in the Webpack ?

Time to upgrade my software.



Regards 

Josep Duran

Mike,

Heavens No!  The S3 family is very alive, and doing very well.  Now that
the Spartan Business Group is well into providing a large part of the
consumer electronics programmable logic, and because of their previous
business models, and their original customers, they plan on having a
longer product life than the Virtex group.

Spartan still has its original family member, based on the 4KXLA device
family, as well as a 5V 4K device!  Still shipping.

Even with the new Spartan 3E, and perhaps more new Spartan parts, there
is no plan to stop selling what is probably the most successful FPGA out
there (>>10 million shipped, and still shipping strong).

Xilinx in general obsoletes very few products.  The 2000 family was
available for 20 years.  The 3000 family is still available (some family
members).  Selected members of the 4, 4E, 4X, 4XL, 4XLA families are
discontinued, but not all.  4XV was completely discontinued, as Virtex
was a better solution, and cost less (so 4XV never 'took off' anyway).
Virtex, Virtex E, Virtex II, Virtex II Pro, Virtex II Pro-X, Virtex 4
are all doing very well, and we have no plans to obsolete any of them.

Old version of software are archived so that people with old parts may
continue to support those products.

Of course, we recommend only those parts for new designs which are
prominently displayed on the documentation web pages, and those that are
not recommended are also so indicated.

Austin

Joseph,

I was worried that FPGA_Editor was also not in webpack, but, the worry
was unfounded.

My only other comment on your post, is that remember that FPGA_Editor is
a software fictional view of the hardware.

For example, there are no "switch-boxes" in the actual hardware, and
there are no "pips".  It is just a convenient fantasy so you can
visualize what the design is doing.  If you saw the real hardware, you
would be lost in it, while trying to use it.  That is what software is for.

Austin

Austin Lesea wrote:
> I was recently asked to do a course, which involves actually showing
> folks real hardware, with real software.
> 
> So, like a good teacher, I went and personally purchased the Digilent
> pcb (this is not for work!), the USB programming cable, and went at it.
> 
> I also downloaded 8.2 webpack, and the service pack.
...
> Find the zipped projects for this board, and have at it.  Start with
> something small that already works (like the simple seconds/minutes
> "clock" -- really a stopwatch), and play around and get more exotic.

Hi Austin,

I'm glad you had a nice experience.  I finally got a round to unpacking 
my very nice ML401 board and fired up the latest ISE WebPack 8.2.  First 
freeze came within a few minutes while in the text editor.  ISE simply 
displayed an hour glass and didn't respond. I had to terminate it and 
start over. Finally got a to compile. Double clicked on one of the ERROR 
links (*) - followed by an ISE crash.  Sigh.  Start
over.  Five minutes more and it hung again.

How can people use this?

Tommy
PS: My PC is stable and up to date. WinXP Pro SP2.

(*): The error was:

   NgdBuild:756 - Line 661 in 'B:/..../system.ucf': Could not find
   net(s) 'gpio_char_lcd<*>' in the design. To suppress this error
   specify the correct net name or remove the constraint.

Does that really mean that I can't have a master .ucf file without using 
every single pin in every design?  (I do have "Allow Unmatched LOC 
Constaints" checked.)

Tommy Thorn schrieb:

> Austin Lesea wrote:
> > I was recently asked to do a course, which involves actually showing
> > folks real hardware, with real software.
> >
> > So, like a good teacher, I went and personally purchased the Digilent
> > pcb (this is not for work!), the USB programming cable, and went at it.
> >
> > I also downloaded 8.2 webpack, and the service pack.
> ...
> > Find the zipped projects for this board, and have at it.  Start with
> > something small that already works (like the simple seconds/minutes
> > "clock" -- really a stopwatch), and play around and get more exotic.
>
> Hi Austin,
>
> I'm glad you had a nice experience.  I finally got a round to unpacking
> my very nice ML401 board and fired up the latest ISE WebPack 8.2.  First
> freeze came within a few minutes while in the text editor.  ISE simply
> displayed an hour glass and didn't respond. I had to terminate it and
> start over. Finally got a to compile. Double clicked on one of the ERROR
> links (*) - followed by an ISE crash.  Sigh.  Start
> over.  Five minutes more and it hung again.
>
> How can people use this?
>
> Tommy
> PS: My PC is stable and up to date. WinXP Pro SP2.
>
> (*): The error was:
>
>    NgdBuild:756 - Line 661 in 'B:/..../system.ucf': Could not find
>    net(s) 'gpio_char_lcd<*>' in the design. To suppress this error
>    specify the correct net name or remove the constraint.
>
> Does that really mean that I can't have a master .ucf file without using
> every single pin in every design?  (I do have "Allow Unmatched LOC
> Constaints" checked.)

the allow unmatched LOC doesnt always do the trick :(

NET MYPIN<*> PULLUP;

is nice to have, but if the net doesnt exist then it will complain.
its real pain sometimes

Antti

Antti wrote:
> the allow unmatched LOC doesnt always do the trick :(
> 
> NET MYPIN<*> PULLUP;
> 
> is nice to have, but if the net doesnt exist then it will complain.
> its real pain sometimes

Thanks Antti.

FWIW, it appears that ISE have major issues with mapped network drives. 
  I moved my directory to the local disk and now everything works much 
better.

Cheers,
Tommy

Austin Lesea schrieb:
> Joseph,
> 
> I was worried that FPGA_Editor was also not in webpack, but, the worry
> was unfounded.

This is great news. I was not there in earlier versions.
FPGA Editor was the only reason for our university to file donation
requests for foundation software.

It is good for teaching to show the students that there actually is
a circuit generated from their VHDL.

Kolja Sulimma