From: Jan Panteltje on 11 Feb 2007 09:46 On a sunny day (11 Feb 2007 05:41:28 -0800) it happened "larwe" <zwsdotcom(a)gmail.com> wrote in <1171201288.811537.158980(a)j27g2000cwj.googlegroups.com>: >On Feb 11, 6:40 am, Jan Panteltje > >> Expect learning curve for FPGA. > >Wow, what an understatement. It took me over a month of playing with >the ML403 just to get to the stage where I knew where to look for >[xyz]. FPGA tools are unique, quirky and really take some serious >experience to use properly. Mm I started with digilab-2 from Digilent, webpack, couple of hours. hehe ;-)
From: larwe on 11 Feb 2007 09:50 On Feb 11, 9:46 am, Jan Panteltje > >Wow, what an understatement. It took me over a month of playing with > >the ML403 just to get to the stage where I knew where to look for > > Mm I started with digilab-2 from Digilent, webpack, couple of hours. > hehe > ;-) Really? It took me an entire day (actually more than an 8-hour working day) to install ISE and EDK. Much of that time was downloading almost 1GB of mandatory service packs.
From: Jan Panteltje on 11 Feb 2007 10:20 On a sunny day (11 Feb 2007 06:50:20 -0800) it happened "larwe" <zwsdotcom(a)gmail.com> wrote in <1171205420.456343.52590(a)m58g2000cwm.googlegroups.com>: >On Feb 11, 9:46 am, Jan Panteltje > >> >Wow, what an understatement. It took me over a month of playing with >> >the ML403 just to get to the stage where I knew where to look for >> >> Mm I started with digilab-2 from Digilent, webpack, couple of hours. >> hehe >> ;-) > >Really? It took me an entire day (actually more than an 8-hour working >day) to install ISE and EDK. Much of that time was downloading almost >1GB of mandatory service packs. Well I hope you noted the ';-)' smily..... Yes I had a very hard time with the X software too, and sometimes still. It has improved a bit (9.1 running now on Linux). I also use the Quartus from Altera, sometimes it helps to try your design on both.. OTOH it really did not take that much time once the soft was running, but I come from a hardware background, so for example Verilog is natural to me. I do not consider myself an expert on FPGA, but I get along.
From: larwe on 11 Feb 2007 10:40 On Feb 11, 10:20 am, Jan Panteltje > Well I hope you noted the ';-)' smily..... Sure, but I'm still curious about whether other people had difficulties. > Yes I had a very hard time with the X software too, and sometimes still. It's really hard to hit the ground running with these tools. For example, I wanted to start small, by just building a piece of sample PowerPC code from the EDK CD-ROM and loading it onto the FPGA (already configured by SystemACE from the CF card). In order to build the code, EDK checked dependencies and tried to build the bitstream. It discovered that the Ethernet, I2C and 16550 UART had no license, so I had to cut out those cores and add the opb_uartlite. In the process I discovered several places where the GUI fails to make all the correct changes - you have to edit the mhs files, etc. Of course I only found this through having the build process fail, checking the files and editing stuff, trying the build again, ... I THEN discovered that the synthesis process dies executing synthesis.sh (I think due to conflict with a newer version of cygwin on my PC). Found a workaround for that, manually running the relevant command and then retrying the build operation. Then the uartlite driver is misnamed, the directory and filename version numbers don't match. I had to modify the sample code to use uartlite instead of ns16550, too. Etc, etc. It all feels very much not ready for primetime. In summary, it took me two days to build and download "hello world!". Having example code on the disk that ALL requires further buyware cores is stupid, IMHO - people need to have a working build environment so they can use it as a basis for their own projects. > I come from a hardware background, so for example Verilog is natural to me. It's funny you say this, because I was going to say I come from primarily a software background, and VHDL is not too alien to me. My difficulties rarely come from code bugs, etc. It's more a case of "I need to simulate this piece of code. Where do I put the stimulus file, how is it formatted, where do I go in the GUI for this massive program?" And the time to build everything... at least half an hour to build the entire project. Wow.
From: Al on 11 Feb 2007 10:48
In article <1171201288.811537.158980(a)j27g2000cwj.googlegroups.com>, "larwe" <zwsdotcom(a)gmail.com> wrote: > On Feb 11, 6:40 am, Jan Panteltje > > > Expect learning curve for FPGA. > > Wow, what an understatement. It took me over a month of playing with > the ML403 just to get to the stage where I knew where to look for > [xyz]. FPGA tools are unique, quirky and really take some serious > experience to use properly. > > At Olin College in Needham, MA, that is part of a freshman course. Al |