Clarification, there is output on the terminal but the program doesn't do
anything visible..

$ make sim_pipe1
lm32-elf-objcopy -O verilog pipe1.elf pipe1.vh
rm pipe1.vh



On Fri, Jan 10, 2014 at 12:20 PM, Salman Sheikh <salmanishe...@gmail.com>wrote:

> Okay, got a new binutils installed and the
>
> make sim_hello_world spits out "Hello World"..
>
> but the make sim_pipe1 doesn't seem to do anything on the screen (no
> output but no errors)...
>
> but the make unittest fails....I suspect (and dread) I might have to
> recompile the entire gcc for lm32...its still using the lm32-elf-gcc from
> Lattice...
>
> >make unittest
> make -C unittests check
> make[1]: Entering directory
> '/cygdrive/c/GMSAG/CPU_TESTING/lm32-master/test/unittests'
> lm32-elf-gcc -x assembler -Wa,-I,. -c crt.S -o crt.o
> crt.S: Assembler messages:
> crt.S:88: Error: unrecognized keyword/register name `rcsr r24,TLBVADDR'
> crt.S:98: Error: unrecognized keyword/register name `rcsr r24,TLBVADDR'
> crt.S:108: Error: unrecognized keyword/register name `rcsr r24,TLBVADDR'
> Makefile:103: recipe for target 'crt.o' failed
> make[1]: *** [crt.o] Error 1
> make[1]: Leaving directory
> '/cygdrive/c/GMSAG/CPU_TESTING/lm32-master/test/unittests'
> Makefile:52: recipe for target 'unittest' failed
> make: *** [unittest] Error 2
>
>
>
>
>
>
> On Fri, Jan 10, 2014 at 11:06 AM, Sébastien Bourdeauducq <
> sebastien.bourdeaud...@lekernel.net> wrote:
>
>> On 01/10/2014 05:08 PM, Yann Sionneau wrote:
>> > issues with your lm32 objcopy not supporting the -O verilog backend
>>
>> Do those issues manifest themselves with a fresh binutils, or the
>> outdated Lattice binaries?
>>
>> _______________________________________________
>> Devel mailing list
>> Devel@lists.milkymist.org
>> https://ssl.serverraum.org/lists/listinfo/devel
>>
>
>
>
> --
> Even a Smile is charity :)
> - Prophet Muhammad
>
>
>


-- 
Even a Smile is charity :)
- Prophet Muhammad
_______________________________________________
Devel mailing list
Devel@lists.milkymist.org
https://ssl.serverraum.org/lists/listinfo/devel

Reply via email to