Re: [Balloon] A few questions about SVN trunk...

Hi David,
I noticed that there was no VHDL code in trunk and asked the list
about that. Hector copied the the VHDL code over from stable and
committed that change. I updated my SVN working copy to pull in
Hector's change, and now the build system is broken. I can work
around that, but I thought I would let the list know, in case somebody
else ran into the same problem and/or somebody else had a quick fix.

I did manage to build the FPGA code with V13, which I downloaded
sometime recently. If V9 or V10 is recommended, I can install those
tools instead.

--wpd


On Sat, May 14, 2011 at 5:02 AM, David Bisset
<david_bisset@btconnect.com> wrote:
> Patrick,
> I'm not sure what your exact problem is but I managed to build from trunk  at the current SVN rev a week or so
> ago, and that was what was shipped with your board. I also cautiously use a Debian V5 system rather than the more recent V6.
> I did have to alter the default build to the CUED build but that was the only change I needed to make as the standard build is broken is subtle ways.
> However there are a number of additional packages you need installed (Wiki has details) otherwise make will break.
>
> With respect to VHDL building you should find a common core of VHDL that is shared between the CPLD and FPGA versions of Balloon. There are then two VHDL files that act as veneer layers to this common code, one for the FPGA and one for the CPLD. There are some compatibility issues when building new modules caused by a lack if address lines in the CPLD but this should't bother you as you are not trying to build code common to both board types.
>
> I would strongly recommend using the Xilinx tools, the command line build will be broken and I wouldn't waste time trying to fix it because no one builds using it.
>
> You should be able to just checkout the VHDL and pull it into the Xilinx tools (probably at V9). I'm using V10 OK and I'm now contemplating moving to V12 since V13 has just come out.
>
> The main body of VHDL is needed to keep the Balloon board running so anything you add should be as a module. Your best bet is to look at the SAMOSA code and circumvent that to your needs. There is also a old Wishbone module (doesn't work for good fundamental reasons) but would also provide a skeletal module interface for you to start with.
>
> Let me know if you need help.
>
> Kind regards
>
> David
>
>
>
> On 14 May 2011, at 02:20, Patrick Doyle wrote:
>
>> On Fri, May 13, 2011 at 5:50 PM, Hector Oron <hector.oron@gmail.com> wrote:
>>> Hi,
>>>
>>> 2011/5/13 Hector Oron <hector.oron@gmail.com>:
>>>> 2011/5/13 Patrick Doyle <wpdster@gmail.com>:
>>>
>>>>> 1) Where is the VHDL code?  package/vhdl contains only 3 files:
>>>>> Config.in, vhdl.deps, and vhdl.mk.
>>>
>>>> It is now on trunk, merged from tags/1.0-stable [0].
>>>
>>> [0] http://www.balloonboard.org/trac/browser/balloon/tags/1.0-stable/vhdl
>>> --
>> Oops... that seems to have broken the build process altogether...
>>
>> balloonboard$ script ../buildlog6 -c make
>> Script started, file is ../buildlog6
>> grep: %XILINX%/readme.txt: No such file or directory
>> grep: %XILINX%/readme.txt: No such file or directory
>> Can't open perl script "./get_option_values.pl": No such file or directory
>> Can't open perl script "./get_option_values.pl": No such file or directory
>> Can't open perl script "./get_option_values.pl": No such file or directory
>> Can't open perl script "./get_project_files.pl": No such file or directory
>> Can't open perl script "./get_option_values.pl": No such file or directory
>> Can't open perl script "./get_option_values.pl": No such file or directory
>> Can't open perl script "./get_option_values.pl": No such file or directory
>> Can't open perl script "./get_project_files.pl": No such file or directory
>> make: *** No rule to make target `balloonboard.config', needed by
>> `config'.  Stop.
>> Script done, file is ../buildlog6
>>
>> I'll sort through what I need to sort through in order to turn off
>> building the FPGA code (at worst) or fix the build process (at best),
>> but I thought I would toss this out for now in case someone more
>> knowledgeable than I can step in and say something like "oh yeah --
>> you need to create a symbolic link to to get_option_values.pl", or
>> something like that.  It won't happen (for me) tonight though... and
>> the weekend looks iffy.
>>
>> --wpd
>>
>> _______________________________________________
>> Balloon mailing list
>> Balloon@balloonboard.org
>> http://balloonboard.org/mailman/listinfo/balloon
>
>