Hello,
Because git simply does not clone submodules on its own.
just do : rm
/cygdrive/c/GMSAG/CPU_TESTING/MiSOC/misoc/verilog/lm32/lm32_config.v
and then git submodule update --init
then retry the make.py
On 23/01/2014 22:49, Salman Sheikh wrote:
> Okay, got past that error. I did a dos2unix o
Okay, got past that error. I did a dos2unix on the build
file build_simplesoc-papilio_pro.sh and ran it by manually...
Now, notice in /cygdrive/c/GMSAG/CPU_TESTING/MiSOC/misoc/verilog/lm32 there
is an lm32_config.v and a submodule directory but its empty.
When I ran the following command in my mi
Got two different versions of lm32 tools conflicting...had lots of
headaches trying to compile the 4.5.4 gcc so I just used the lattic
toolchain tools only for now: Got to this point but I can't quite figure
what script is failing. I suspect it has something to do with a DOS file
type (as I sometim
Okay, I fixed the path...I set the PYTHONPATH in the environment settings
of Windows..when I had it as export PYTHONPATH=/cygdrive/C... it would
append c:\\ to that cygdrive\c path.
Now, I am getting another error related to lm32-elf-ld.exe which I compiled
about 10 days ago...
CC main.o
make -
On 01/22/2014 06:06 PM, Salman Sheikh wrote:
> then it still gives an error about misclib not being Importedis the
> above path correct?
It is obviously incorrect, you need to remove misoclib. Please read up
on the way Python import modules.
___
Dev
I used export. Like so:
export PYTHONPATH=/cygdrive/c/GMSAG/CPU_testing/MiSOC/misoc/misoclib/
then it still gives an error about misclib not being Importedis the
above path correct?
make: Entering directory
'/cygdrive/c/GMSAG/CPU_TESTING/MiSOC/misoc/software/bios'
Traceback (most recent c
> No difference. PYTHONPATH was empty before I defined it to the MiSOC
> directory and after no difference.
Did you use "export PYTHONPATH=..." or just "PYTHONPATH=..."? The 1st
one would be better.
___
Devel mailing list
Devel@lists.milkymist.org
http
No difference. PYTHONPATH was empty before I defined it to the MiSOC
directory and after no difference.
ssheikh@gs-560g2333030n /cygdrive/d/GMSAG/CPU_TESTING/MLABS/misoc
$ echo $PYTHONPATH
/cygdrive/d/GMSAG/CPU_TESTING/MLABS/misoc
ssheikh@gs-560g2333030n /cygdrive/d/GMSAG/CPU_TESTING/MLABS/misoc
On 01/16/2014 05:42 PM, Salman Sheikh wrote:
> ImportError: No module named 'misoclib'
Add the MiSoC directory to your PYTHONPATH.
___
Devel mailing list
Devel@lists.milkymist.org
https://ssl.serverraum.org/lists/listinfo/devel
It got further than ever before but no joy yet :|
./make.py -p papilio_pro -t simple
make: Entering directory
'/cygdrive/d/GMSAG/CPU_TESTING/MLABS/misoc/software/bios'
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named 'misoclib'
CC isr.o
CC sdram.o
CC ma
Yes of course, you need to adapt the SoC design to your board. The
simple SoC, as it is included in MiSoC, only supports the Papilio Pro
(but only requires minor modifications for other boards). I guess it
works with the Papilio Pro now?
Sébastien
___
D
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
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 imp
Does some of the migen, migen get installed in the Python install
directories? I can start from scratch then...
On Jan 15, 2014 4:32 PM, "Sébastien Bourdeauducq" <
sebastien.bourdeaud...@lekernel.net> wrote:
> On 01/15/2014 05:49 PM, Salman Sheikh wrote:
> > ssheikh@gs-560g2333030n /cygdrive/d/GMS
On 01/15/2014 05:49 PM, Salman Sheikh wrote:
> ssheikh@gs-560g2333030n /cygdrive/d/GMSAG/CPU_TESTING/misoc
> $ ./make.py -p papilio_pro -t simple
> platform.add_verilog_include_path(os.path.join("verilog", "lm32"))
> AttributeError: 'Platform' object has no attribute
> 'add_verilog_include_path
Okay before I punt on getting MiSOC/Migen/Mibuild and just try to use the
LM32 files generated by that LatticeMico32 tool try to get them to compile
in Altera (they give all kinds of verilog syntax errors in Quartus but not
in Xilinx which is weird) I got to this point when trying to generate a soc
On 01/13/2014 07:36 PM, Salman Sheikh wrote:
> Okay, I have python3 and tried to run setup.py as per this suggestion in
> migen.pdf. So, if complains about a command following the script name,
> should I set PYTHONPATH to the migen subdirectory or migen-master?
http://stackoverflow.com/questions/1
Okay, I have python3 and tried to run setup.py as per this suggestion in
migen.pdf. So, if complains about a command following the script name,
should I set PYTHONPATH to the migen subdirectory or migen-master?
**
Either run the setup.py installation script or simply set PYTHONPATH to the
roo
18 matches
Mail list logo
