Custom Query (93 matches)

quand j'ai executé "soclib-cc -l -t systemc" j'ai rencontré l'erreur suivante:

Traceback (most recent call last):
  File "/home/wael/Soclib/Soclib/utils/lib/python/soclib-cc-main.py", line 316, in <module>
    sys.exit(main())
  File "/home/wael/Soclib/Soclib/utils/lib/python/soclib-cc-main.py", line 162, in main
    change_config(opts.type)
  File "/home/wael/Soclib/Soclib/utils/lib/python/soclib_cc/config/__init__.py", line 110, in change_config
    newconf.doConfigure(_cur_soclib, _configs._desc_paths)
AttributeError: Config instance has no attribute 'doConfigure'

SoCLib-cc failed unexpectedly. To submit a bug report,
 please re-run soclib-cc with --bug-report
 (i.e run: 'soclib-cc -l -t systemc --bug-report')

j'arrive pas à corriger l'erreur

The platform is based on the topcell example : caba-ring-ccxcachev1_memcachev1-mipsel. Here are the main differences:

• Sparcv8 instead of mipsel32
• Different memory segments
• No MMU define in the segmentation.h file
• Different linker script for soft (in order to meet sparcv8 requirements)
• Only 4 irqs instead of 5 (sparcv8 requirement)

The problem is that the platform compiles but there is a binding error when launching the system.

Error: (E109) complete binding failed: 2 binds exceeds maximum of 1 allowed: port 'proc3.vci_ini_rw_rspack' (sc_out)

I checked all connexions and it seems ok for me. If anyone could help, this would be great.

Many thanks, Fabien.

I experienced problems using soclib-cc.

Please see the attached log