I deleted out the stuff related to migen in the following directory:
/cygdrive/c/Python33/lib/site-packages
then I cloned the migen and installed it. Then I cloned the misoc and try
to run this:
./make.py -p de0nano -t simple
Traceback (most recent call last):
File "./make.py", line 112, in <module>
main()
File "./make.py", line 59, in main
soc = top_class(platform, **top_kwargs)
File "D:\GMSAG\CPU_TESTING\MLABS\misoc\targets\simple.py", line 15, in
__init__
self.comb += self.cd_sys.clk.eq(platform.request("clk32"))
File
"C:\Python33\lib\site-packages\migen-unknown-py3.3.egg\mibuild\generic_platform.py",
line 155, in request
return self.constraint_manager.request(*args, **kwargs)
File
"C:\Python33\lib\site-packages\migen-unknown-py3.3.egg\mibuild\generic_platform.py",
line 83, in request
resource = _lookup(self.available, name, number)
File
"C:\Python33\lib\site-packages\migen-unknown-py3.3.egg\mibuild\generic_platform.py",
line 45, in _lookup
raise ConstraintError("Resource not found: " + name + ":" + str(number))
mibuild.generic_platform.ConstraintError: Resource not found: clk32:None
***
I thought I saw a pdf explaining the entire process last night written by
Sebastian but I can't find it..
Salman
On Thu, Jan 16, 2014 at 4:02 AM, Sébastien Bourdeauducq <
[email protected]> wrote:
> On 01/15/2014 11:08 PM, Salman Sheikh wrote:
> > Does some of the migen, migen get installed in the Python install
> > directories? I can start from scratch then...
>
> Yes. My guess is you installed some old version of Migen (or Mibuild)
> into your Python library directories, and that old version gets imported
> instead of your fresh git download.
>
> Sébastien
>
> _______________________________________________
> Devel mailing list
> [email protected]
> https://ssl.serverraum.org/lists/listinfo/devel
>
--
Even a Smile is charity :)
- Prophet Muhammad
_______________________________________________
Devel mailing list
[email protected]
https://ssl.serverraum.org/lists/listinfo/devel
