Prev: Xilinx ISim and FSM states names
Next: How to inspect values in a Xilinx core FIFO with Modelsim?
From: rickman on 18 Oct 2009 17:22
The dreaded License expiration has bitten me in the butt again. I
don't recall if I had this exact same problem before, but I am pretty
sure I was told at one point that my tools would not expire when
maintenance ran out, because that is what is stuck in my head.
However, that is not the case. My copy of ispLever from Lattice will
not run compile or simulate because neither of these tools will run
due to the license expiring. Maybe the deal is that I have to update
the license file periodically, but I just did that earlier this
year.

The real problem is that I can't get anyone to talk straight with me
about this. I had an email exchange with licensing the last time I
updated the license and they never answered my questions about this.

So now I am trying to use the Xilinx Webpack to allow me to continue
working until I can get a new license file, but it won't run either.
I think that it somehow is using networking to communicate between
processes and it won't go through the firewall! Talk about making
simple things difficult! This is the error message I get.

IPC connection failed port=58676 hostname=localhost

I am using Sophos for AVS and firewall. Anyone know what has to be
turned on to allow ISE to talk to the simulator?

Rick
From: Charles Gardiner on 18 Oct 2009 19:35
Regarding Lattice ispLever,

this is a statment I got from them a while back:

"The Warranty maintenance expiration and Third party OEM License feature
expiration are separate functions. Contractually we license the third
party tools annually from the latest license generation. You own the
license and we renew the features at any time regardless of the Warranty
maintenance status, for the life of the product. The Warranty
maintenance allows for distribution of new versions of the tool suite as
they are released."

I guess that means if you renew maintenance you always get the latest,
if you don't, they lock <ou into the last maintained version of the OEM
tools (e.g. Synplify)

rickman schrieb:
> The dreaded License expiration has bitten me in the butt again. I
> don't recall if I had this exact same problem before, but I am pretty
> sure I was told at one point that my tools would not expire when
> maintenance ran out, because that is what is stuck in my head.
> However, that is not the case. My copy of ispLever from Lattice will
> not run compile or simulate because neither of these tools will run
> due to the license expiring. Maybe the deal is that I have to update
> the license file periodically, but I just did that earlier this
> year.
>
> The real problem is that I can't get anyone to talk straight with me
> about this. I had an email exchange with licensing the last time I
> updated the license and they never answered my questions about this.
>
> So now I am trying to use the Xilinx Webpack to allow me to continue
> working until I can get a new license file, but it won't run either.
> I think that it somehow is using networking to communicate between
> processes and it won't go through the firewall! Talk about making
> simple things difficult! This is the error message I get.
>
> IPC connection failed port=58676 hostname=localhost
>
> I am using Sophos for AVS and firewall. Anyone know what has to be
> turned on to allow ISE to talk to the simulator?
>
> Rick
From: rickman on 19 Oct 2009 06:24
Yeah, I am fine with that. I'm just not happy with the license
expiring and having to be renewed. That can happen at very
inconvenient times (like this weekend). It's not like I use the
software every day. I guess I'll have to add license expiration to my
calendar and make sure I keep it up to date even when I'm not using
the tool.

Rick

On Oct 18, 7:35 pm, Charles Gardiner <inva...(a)invalid.invalid> wrote:
> Regarding Lattice ispLever,
>
> this is a statment I got from them a while back:
>
> "The Warranty maintenance expiration and Third party OEM License feature
> expiration are separate functions. Contractually we license the third
> party tools annually from the latest license generation. You own the
> license and we renew the features at any time regardless of the Warranty
> maintenance status, for the life of the product. The Warranty
> maintenance allows for distribution of new versions of the tool suite as
> they are released."
>
> I guess that means if you renew maintenance you always get the latest,
> if you don't, they lock <ou into the last maintained version of the OEM
> tools  (e.g. Synplify)
>
> rickman schrieb:
>
> > The dreaded License expiration has bitten me in the butt again.  I
> > don't recall if I had this exact same problem before, but I am pretty
> > sure I was told at one point that my tools would not expire when
> > maintenance ran out, because that is what is stuck in my head.
> > However, that is not the case.  My copy of ispLever from Lattice will
> > not run compile or simulate because neither of these tools will run
> > due to the license expiring.  Maybe the deal is that I have to update
> > the license file periodically, but I just did that earlier this
> > year.
>
> > The real problem is that I can't get anyone to talk straight with me
> > about this.  I had an email exchange with licensing the last time I
> > updated the license and they never answered my questions about this.
>
> > So now I am trying to use the Xilinx Webpack to allow me to continue
> > working until I can get a new license file, but it won't run either.
> > I think that it somehow is using networking to communicate between
> > processes and it won't go through the firewall!  Talk about making
> > simple things difficult!  This is the error message I get.
>
> > IPC connection failed port=58676 hostname=localhost
>
> > I am using Sophos for AVS and firewall.  Anyone know what has to be
> > turned on to allow ISE to talk to the simulator?
>
> > Rick
>
>

From: Colin Paul Gloster on 20 Oct 2009 09:47
On Sun, 18 Oct 2009, Rickman wrote:

|---------------------------------------------------------------------|
|"[..] |
|[..] My copy of ispLever from Lattice will |
|not run compile or simulate because neither of these tools will run |
|due to the license expiring. [..] |
| |
|[..] |
| |
|So now I am trying to use the Xilinx Webpack to allow me to continue |
|working until I can get a new license file, but it won't run either."|
|---------------------------------------------------------------------|

Xilinx Webpack used to be licensed such that it was forbidden to use
it for Lattice FPGAs. I do not recall that prohibition being removed.

|---------------------------------------------------------------------|
|"I think that it somehow is using networking to communicate between |
|processes and it won't go through the firewall! Talk about making |
|simple things difficult! [..] |
| |
|[..]" |
|---------------------------------------------------------------------|

OpenSolaris had a very complicated way to simulate X-Windows of
GNU/Linux (on top of X-Windows of OpenSolaris) via networking.
From: rickman on 20 Oct 2009 15:19
On Oct 20, 9:47 am, Colin Paul Gloster <Colin_Paul_Glos...(a)ACM.org>
wrote:
> On Sun, 18 Oct 2009, Rickman wrote:
>
> |---------------------------------------------------------------------|
> |"[..]                                                                |
> |[..]  My copy of ispLever from Lattice will                          |
> |not run compile or simulate because neither of these tools will run  |
> |due to the license expiring.  [..]                                   |
> |                                                                     |
> |[..]                                                                 |
> |                                                                     |
> |So now I am trying to use the Xilinx Webpack to allow me to continue |
> |working until I can get a new license file, but it won't run either."|
> |---------------------------------------------------------------------|
>
> Xilinx Webpack used to be licensed such that it was forbidden to use
> it for Lattice FPGAs. I do not recall that prohibition being removed.

How is this about Lattice FPGAs? I'm trying to compile VHDL code and
simulate it.

Rick
 |  Next  |  Last
Pages: 1 2
Prev: Xilinx ISim and FSM states names
Next: How to inspect values in a Xilinx core FIFO with Modelsim?