Custom Query (93 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (7 - 9 of 93)

1 2 3 4 5 6 7 8 9 10 11 12 13
Ticket Resolution Summary Owner Reporter
#7 fixed installation fails somebody turbo07
Description

Hi,

I reinstalled soclib from scratch on a new computer following the installation note page.

SystemC is installed and $SYSTEMC is set. The cross compilers are installed for both mipsel and powerpc target. They are installed in a $CXTOOL directory and the $PATH variable is correctly set.

When performing the Testing part of my new installation, the make command fails:

make

soclib-cc -P -p platform_desc -o simulation.x [========================W + ] 18 left /home.local/soclib/Soclib/soclib/lib/elf_loader/src/elf_loader.cpp:28:17: error: bfd.h: Aucun fichier ou répertoire de ce type

After investigation, bfd.h can be found into $CXTOOL/i686-pc-linux-gnu/{mipsel|powerpc}-unknown-elf/include

As indicating, I tried to modify my ~/.soclib/global.conf configuration file in order to specify the correct toolchain. I think the SoclibConf page is not quite clear: my configuration file looks like

" config.mipsel = Config(

base = config.toolchain, prefix = "i686-pc-linux-gnu/mipsel-unknown-elf" )

config.use_mipsel = Config(

base = config.default, toolchain = config.mipsel )

"

then, the following command line soclib-cc -t mipsel -P -p platform_desc -o simulation.x* gets the following answer: Traceback (most recent call last):

File "/home.local/soclib/Soclib/utils/lib/python/soclib-cc-main.py", line 237, in ?

sys.exit(main())

File "/home.local/soclib/Soclib/utils/lib/python/soclib-cc-main.py", line 113, in main

change_config(opts.type)

File "/usr/lib/python2.4/site-packages/cairo/init.py", line 107, in change_config

AttributeError: Config instance has no attribute 'doConfigure'

My questions are:

  • how can I tell to soclib-cc the correct path to find the appropriate missing header file?
  • how shall a correct toolchain be declared in a global.conf configuration file?

Thank for your help

Christophe

PS: In the Installation Notes, I would suggest to add an external link for SystemCass in order to directly access the trac pages for systemcass (www-asim.lip6.fr/trac/systemcass/)

#8 duplicate test platforms fails somebody turbo07
Description

Hello,

I have succeeded in installing SoClib using the Installation Notes page. The caba-vgmn-multi_timer-mipsel platform is OK.

However, when I try to run the soclib-test-platforms test, the caba-pibus-hello_world-mipsel fails : the resulting command line is

set -o pipefail;SOCLIB_TTY=TERM ./simulation.x < /dev/null 2>&1 | tee test.out 

SystemC 2.2.0 prints the following message:

             SystemC 2.2.0 --- Sep  8 2008 15:39:21
        Copyright (c) 1996-2006 by all Contributors
                    ALL RIGHTS RESERVED
Error: (E115) sc_signal<T> cannot have more than one driver: 
 signal `pibus_d' (sc_signal)
 first driver `tty_wrapper.pi_d' (sc_inout)
 second driver `multiram_wrapper.pi_d' (sc_inout)
In file: ../../../../src/sysc/communication/sc_signal.cpp:129

I have also installed the SystemCASS simulator. In this case, the test does not report any specific message other than the SystemCASS banner.

Is there any issue with the pibus?

I thought SystemCASS used a strict subset of SystemC. Shall these two simulators differ while simulating this platform?

Thanks,

Christophe

#9 fixed Can't compile caba-vgmn-tc4200enc-mipsel and caba-vgmn-tc4200-mipsel somebody silicomp
Description

I manage to install Soclib with installation notes.

I passed the Test.

But when i try to compile caba-vgmn-tc4200enc-mipsel i have this error: soclib/module/streaming_component/tc4200_enc/caba/source/src/../include/tc4200_enc.h:42:27: error: tc_tc4200_enc.h: Aucun fichier ou répertoire de ce type

IN fact the file tc4200_enc.h is in $SOCLIB/binary/module/stream_components/tc4200enc/caba/source

There is the same error with caba-vgmn-tc4200-mipsel

Thank you

  1. Rouland (Orange Business Services)
1 2 3 4 5 6 7 8 9 10 11 12 13
Note: See TracQuery for help on using queries.