| | 1 | |
| | 2 | = Cross-compilation issues = |
| | 3 | |
| | 4 | == Wrong cross-compiler == |
| | 5 | |
| | 6 | In a bunch of GCC error messages, you see |
| | 7 | {{{ |
| | 8 | as: unrecognized option `-EL' |
| | 9 | }}} |
| | 10 | |
| | 11 | Your mips gcc has been created wrongly, it's using your native (most probably x86) assembler. Recreate your [CrossCompiler cross-compilation toolchain]. |
| | 12 | |
| | 13 | = Simulation issues = |
| | 14 | |
| | 15 | == Bus simulation and multiple drivers == |
| | 16 | |
| | 17 | Using !PiBus under SystemC-2.2, you see |
| | 18 | {{{ |
| | 19 | Error: (E115) sc_signal<T> cannot have more than one driver |
| | 20 | signal `pibus_d' (sc_signal) |
| | 21 | first driver `tty_wrapper.port_8' (sc_inout) |
| | 22 | second driver `multiram_wrapper.port_8' (sc_inout) |
| | 23 | In file: ../../../../src/sysc/communication/sc_signal.cpp:137 |
| | 24 | }}} |
| | 25 | |
| | 26 | SystemC got picky about multiple drivers. This probably needs a fix in simulation models, using SystemC-2.1 is a workaround for now. |
