<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Just fyi,<br>
<br>
These are the prices for Quartus per seat per year.
<a class="moz-txt-link-freetext" href="https://www.altera.com/buy/design-software.html#note">https://www.altera.com/buy/design-software.html#note</a><br>
<br>
If we go this route, you exclude any hobbyist who wants to make his
own modifications to the code.<br>
<br>
Just my opinion,<br>
<br>
Stijn PE1RKS<br>
<br>
<div class="moz-cite-prefix">Op 10-02-17 om 18:33 schreef Scott
Traurig:<br>
</div>
<blockquote
cite="mid:CAGK9zXqpdrxoSi5e9UqwYNOhiuJjWuRkj-L=ASf+O4C1-vpmcw@mail.gmail.com"
type="cite">
<pre wrap="">***** High Performance Software Defined Radio Discussion List *****
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<div dir="ltr">
<div>How is it that the free version of Quartus is sufficient
when just recently both the Angelia and Orion firmware updates
required multiple, rapid iterations and still apparently
either don't work at all, don't work for everyone, or work but
have to trade-off previous functionality for new
functionality?<br>
</div>
<div><br>
</div>
<div>Given the current complexity of the firmware (which, by the
way, only underscores the really tremendous amount of
phenomenal work that Joe and Phil have completed over the
years), timing closure has had to become more and more
difficult with the free tool. This is even more of an issue
with the new firmware protocol where there is more data,
moving faster, than ever before.</div>
<div><br>
</div>
<div>Another factor that is driving the need to go to a more
capable development environment is the fact that there is no
lab where a firmware build can be fully validated on a range
of Hermes, Angelia or Orion boards, over temperature, before
release. This makes achieving tight timing about the nominal
range even more important such that builds that work for some
and not others are less likely.</div>
<div><br>
</div>
<div>Here's another suggestion: the firmware source code remains
open source, of course. And those who wish to develop on the
free version of Quartus can still do so. But it would seem
that Apache Labs might want to obtain the standard version of
Quartus and someone willing and able to use it to polish up
the timing of a given build such that it will reliably work on
all Apache Labs radios under most conditions.</div>
<div><br>
</div>
<div>73,</div>
<div><br>
</div>
<div>Scott/w-u-2-o</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
HPSDR Discussion List
To post msg: <a class="moz-txt-link-abbreviated" href="mailto:hpsdr@openhpsdr.org">hpsdr@openhpsdr.org</a>
Subscription help: <a class="moz-txt-link-freetext" href="http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org">http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org</a>
HPSDR web page: <a class="moz-txt-link-freetext" href="http://openhpsdr.org">http://openhpsdr.org</a>
Archives: <a class="moz-txt-link-freetext" href="http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/">http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/</a></pre>
</blockquote>
<br>
</body>
</html>