08-02-2017 06:27 PM
I have a problem with SDSoC 2016.4.
With the event tracing mode, the following errors were occured.
ERROR: [SDSoC 0-0] Trace Error: couldnt get adapter for aximm monitored comp 'sample_hw_1' ERROR: [SDSoC 0-0] An error has occurred reading the system description file apsys_0.xml. If targeting a custom platform or hardware library, ensure that hardware function mappings accurately map software function prototypes to IP port interfaces and register offsets. Please consult the log files in _sds/reports for additional ERROR messages. You may find it helpful to run sdscc with the '-verbose' option. ERROR: [SDSoC 0-0] Exiting system_linker: Error when calling 'C:/Xilinx/SDx/2016.4/bin/cf2xd -i apsys_0.xml -o top.xml -r E:/Projects/sample/Release/_sds/.cdb/xd_ip_db.xml -trace 1024 -mc ' ERROR: [SDSoC 0-0] Exiting sds++ : Error when calling 'system_linker -cf-input E:/Projects/sample/Release/_sds/.llvm/apsys_0.xml -cf-output-dir _sds/p0 -ip-db E:/Projects/sample/Release/_sds/.cdb/xd_ip_db.xml -ip-repo E:/Projects/sample/Release/_sds/iprepo/repo -sds-pf C:/Xilinx/SDx/2016.4/platforms/zc706:standalone -sds-sys-config standalone -sds-proc a9_0 -software-only -target-os standalone -trace 1024 -sdsoc ' sds++ log file saved as E:/Projects/sample/Release/_sds/reports/sds.log ERROR: [SDSoC 0-0] Build failed
There is nothing wrong in the nomal mode.
Does anyone know the reason why the errors occur?
08-08-2017 12:21 AM
I solved it.
When I got the errors, I set the pragma "#pragma HLS INTERFACE m_axi port=..." in the code.
After commentouting the pragma, I got no errors.
That means, current version of SDSoC may not trace memory-mapped AXI I/Fs.
01-10-2018 11:02 PM
hi, I met the same problem. what's the meaning of "..." after "#pragma HLS INTERFACE m_axi port=".