tapasco issueshttps://git.esa.informatik.tu-darmstadt.de/groups/tapasco/-/issues2020-05-05T12:05:05Zhttps://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/78Rename tapasco_api.h/hpp to tapasco.h/hpp2020-05-05T12:05:05ZJens KorinthRename tapasco_api.h/hpp to tapasco.h/hppThe `_api` suffix is unusual.The `_api` suffix is unusual.2017.1Jens KorinthJens Korinthhttps://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/173Synthesis options are not passed to the import task2020-04-30T14:34:05ZJulian OppermannSynthesis options are not passed to the import task[Patch](/uploads/b5ef0d4693878182488bca7a98599b1d/synthOptions.patch)[Patch](/uploads/b5ef0d4693878182488bca7a98599b1d/synthOptions.patch)https://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/172`corestats` don't work with alternative `coreDir`2020-04-30T14:19:04ZLukas Sommer`corestats` don't work with alternative `coreDir`If a alternative `coreDir` was used for import, the `corestats`-command does not report statistics for the cores in the alternative `coreDir`, even if the directory is specified in the command.If a alternative `coreDir` was used for import, the `corestats`-command does not report statistics for the cores in the alternative `coreDir`, even if the directory is specified in the command.Lukas SommerLukas Sommerhttps://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/171Fix IRQs on ZYNQ platform2020-04-14T16:24:05ZMicha OberFix IRQs on ZYNQ platformThe kernel driver is already aware of all available platform interrupts, but they are not provided by the device tree. The attached patch provides a fix for this issue and has been tested on a PYNQ board.
[zynq_irq.patch](/uploads/9f812...The kernel driver is already aware of all available platform interrupts, but they are not provided by the device tree. The attached patch provides a fix for this issue and has been tested on a PYNQ board.
[zynq_irq.patch](/uploads/9f8127756e328d25915a2045603887e8/zynq_irq.patch)https://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/159Merge TaPaSCo's loadable kernel modules?2019-11-28T10:00:11ZJens KorinthMerge TaPaSCo's loadable kernel modules?I think it would be possible (and extremely nice) to merge the loadable kernel modules of all TaPaSCo platforms. This would make closing #134, #135, #157 and #158 easier, and reduce the amount of maintenance overall. This also affects #1...I think it would be possible (and extremely nice) to merge the loadable kernel modules of all TaPaSCo platforms. This would make closing #134, #135, #157 and #158 easier, and reduce the amount of maintenance overall. This also affects #143, because we'd require the status core changes to detect the actual device(s).
I'm strongly in favor of this consolidation, but it is a lot of work, so I'm not sure if I will be able to do it.Jens KorinthJens Korinthhttps://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/138Implement Import option to skip evaluation2019-11-26T14:03:13ZJens KorinthImplement Import option to skip evaluationEvaluation/OOC can take a very long time, which is wasted if one does not intend to use DSE. `Import` should have an option to skip evaluation all together; maybe even make that the default behavior and only trigger evaluation before run...Evaluation/OOC can take a very long time, which is wasted if one does not intend to use DSE. `Import` should have an option to skip evaluation all together; maybe even make that the default behavior and only trigger evaluation before running a DSE, or a `corestats` job?2017.2Jens KorinthJens Korinthhttps://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/158PCIe: logging in driver too coarse-grained2019-11-20T12:08:06ZJens KorinthPCIe: logging in driver too coarse-grainedThe logging in the PCIe driver is not very useful: You can either activate each and every message, or nothing at all. This nothing then includes vital warnings, which won't be shown either. I think the logging system used on Zynqs is muc...The logging in the PCIe driver is not very useful: You can either activate each and every message, or nothing at all. This nothing then includes vital warnings, which won't be shown either. I think the logging system used on Zynqs is much more flexible, we should port it to PCIe.https://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/25Rewrite "Getting Started" Guide2019-11-19T15:28:08ZJens KorinthRewrite "Getting Started" GuideGetting started is significantly outdated.Getting started is significantly outdated.Jens KorinthJens Korinthhttps://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/152Device driver does not detect missing device for VC7092019-11-13T11:38:05ZLukas SommerDevice driver does not detect missing device for VC709Jaco HofmannJaco Hofmannhttps://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/153FileAssetManager ignores directory switches2019-11-12T18:04:05ZJens KorinthFileAssetManager ignores directory switchesSteps to reproduce:
* import a core into standard directory
* then import same core with `--coreDir /tmp/x`
TaPaSCo will copy existing report from `$TAPASCO_HOME/core` and skip OOC evaluation.Steps to reproduce:
* import a core into standard directory
* then import same core with `--coreDir /tmp/x`
TaPaSCo will copy existing report from `$TAPASCO_HOME/core` and skip OOC evaluation.https://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/151Cannot insmod tapasco-platform-zynq.ko on zc7062019-11-12T17:34:06ZLukas SommerCannot insmod tapasco-platform-zynq.ko on zc706When trying to load a bit-stream on the ZC706, tapasco-load-bitstream will fail due to an error in insmod.
If I try to load the corresponding kernel-module `tapasco-platform-zynq.ko` manually, insmod also fails due to unresolved symbols...When trying to load a bit-stream on the ZC706, tapasco-load-bitstream will fail due to an error in insmod.
If I try to load the corresponding kernel-module `tapasco-platform-zynq.ko` manually, insmod also fails due to unresolved symbols in the module.
The missing symbol (according to the error-message in the output of `dmesg`) is
`[401669.151177] tapasco_platform_zynq: Unknown symbol _GLOBAL_OFFSET_TABLE_ (err 0)`
I'm using the master-branch of Tapasco, i.e. release 2017.2.Jens KorinthJens Korinthhttps://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/148Replace tapasco-status subtree by .jar2019-11-05T16:07:05ZJens KorinthReplace tapasco-status subtree by .jarBuilding the TaPaSCo status core Chisel project led to all kinds of issues in the CI processes (and probably elsewhere). So we should remove the subtree and replace it by a `.jar` file, which can be run to produce status IP cores.Building the TaPaSCo status core Chisel project led to all kinds of issues in the CI processes (and probably elsewhere). So we should remove the subtree and replace it by a `.jar` file, which can be run to produce status IP cores.2018.1Jens KorinthJens Korinthhttps://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/145Building status core fails2019-11-05T16:03:05ZJaco HofmannBuilding status core failsBuilding the status core currently fails with the attached error.
Build was done on CentOS 7 and full logs are available in Pipeline 103
[tapasco_status.json.log](/uploads/9ac7bb6ae3e55220b38e1ce75047b301/tapasco_status.json.log)
[axi4...Building the status core currently fails with the attached error.
Build was done on CentOS 7 and full logs are available in Pipeline 103
[tapasco_status.json.log](/uploads/9ac7bb6ae3e55220b38e1ce75047b301/tapasco_status.json.log)
[axi4mm-zc706--arraysum_1_arrayupdate_1--100.0.log](/uploads/5a7535b7246202d24c56e5537b343d69/axi4mm-zc706--arraysum_1_arrayupdate_1--100.0.log)Jens KorinthJens Korinthhttps://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/147Implement maxTasks option2019-11-05T15:36:05ZJens KorinthImplement maxTasks optionSee #146 - it would be useful to explicitly limit the number of parallel task executions in TaPaSCo.See #146 - it would be useful to explicitly limit the number of parallel task executions in TaPaSCo.2018.1Jens KorinthJens Korinthhttps://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/131Bitstream file name in log does not match real file name2019-11-05T14:50:06ZJens KorinthBitstream file name in log does not match real file nameAt the end of successful `compose` runs, the reported bitstream still uses the old schema with the hash value, instead of the new schema consisting of arch, platform etc.At the end of successful `compose` runs, the reported bitstream still uses the old schema with the hash value, instead of the new schema consisting of arch, platform etc.2017.2Jens KorinthJens Korinthhttps://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/139MultiFileWatcher: truncated logs are not updated2019-11-04T15:55:04ZJens KorinthMultiFileWatcher: truncated logs are not updatedIf a log gets truncated (e.g., same run repeated), then `MultiFileWatcher` will not be notified of any more changes. Should be fixed, so that new file contents after truncation trigger log events again.If a log gets truncated (e.g., same run repeated), then `MultiFileWatcher` will not be notified of any more changes. Should be fixed, so that new file contents after truncation trigger log events again.https://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/140Support AXI System ILA for debugging2019-11-04T15:42:05ZJens KorinthSupport AXI System ILA for debuggingThe new System ILA IP is much more comfortable when debugging AXI connections, both in wiring as in usage. Extend `Debug` feature plugins to use it: `Debug` feature should have a `interfaces` property, which contains an array of
1. n...The new System ILA IP is much more comfortable when debugging AXI connections, both in wiring as in usage. Extend `Debug` feature plugins to use it: `Debug` feature should have a `interfaces` property, which contains an array of
1. name of the AXI interface
2. clock of the AXI interface
3. reset for this clock
Should probably be wired in `post-bd` event.2017.2Jens KorinthJens Korinthhttps://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/142COS simulation fails with errors2019-11-04T15:41:05ZCarsten HeinzCOS simulation fails with errors```bash
INFO: [RTGEN 206-500] Setting interface mode on port 'arrayinit/maxi_arr' to 'm_axi'.
INFO: [RTGEN 206-500] Setting interface mode on port 'arrayinit/arr' to 's_axilite & ap_none'.
INFO: [RTGEN 206-500] Setting interface mode on ...```bash
INFO: [RTGEN 206-500] Setting interface mode on port 'arrayinit/maxi_arr' to 'm_axi'.
INFO: [RTGEN 206-500] Setting interface mode on port 'arrayinit/arr' to 's_axilite & ap_none'.
INFO: [RTGEN 206-500] Setting interface mode on function 'arrayinit' to 's_axilite & ap_ctrl_hs'.
INFO: [RTGEN 206-100] Bundling port 'arr' and 'return' to AXI-Lite port AXILiteS.
INFO: [RTGEN 206-100] Finished creating RTL model for 'arrayinit'.
INFO: [HLS 200-111] Elapsed time: 0.05 seconds; current allocated memory: 59.102 MB.
INFO: [HLS 200-111] Finished generating all RTL models Time (s): cpu = 00:00:03 ; elapsed = 00:00:23 . Memory (MB): peak = 583.598 ; gain = 144.703 ; free physical = 690 ; free virtual = 12449
INFO: [SYSC 207-301] Generating SystemC RTL for arrayinit.
INFO: [VHDL 208-304] Generating VHDL RTL for arrayinit.
INFO: [VLOG 209-307] Generating Verilog RTL for arrayinit.
INFO: [COSIM 212-47] Using XSIM for RTL simulation.
INFO: [COSIM 212-14] Instrumenting C test bench ...
ERROR: [COSIM 212-24] TB preprocess failed : In file included from /opt/cad/xilinx/vivado/Vivado_HLS/2017.2/lnx64/tools/gcc/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.6.3/include-fixed/features.h:339:0,
from /usr/include/bits/libc-header-start.h:33,
from /usr/include/stdio.h:28,
from /home/wimi/cjh/tapasco/kernel/arrayinit/arrayinit-tb.c:23:
/usr/include/sys/cdefs.h:481:49: error: missing binary operator before token "("
In file included from /home/wimi/cjh/tapasco/kernel/arrayinit/arrayinit-tb.c:23:0:
/usr/include/stdio.h:320:43: error: missing binary operator before token "("
/usr/include/stdio.h:399:17: error: missing binary operator before token "("
/usr/include/stdio.h:657:43: error: missing binary operator before token "("
In file included from /home/wimi/cjh/tapasco/kernel/arrayinit/arrayinit-tb.c:24:0:
/usr/include/stdlib.h:183:17: error: missing binary operator before token "("
ERROR: [HLS 200-70] Cannot find file /home/wimi/cjh/tapasco/core/arrayinit/axi4mm/pynq/hls/axi4mm/solution/./sim/autowrap/testbench/arrayinit-tb.c_pre.c.
ERROR: [COSIM 212-4] *** C/RTL co-simulation finished: FAIL ***
24
while executing
"source [lindex $::argv 1] "
("uplevel" body line 1)
invoked from within
"uplevel \#0 { source [lindex $::argv 1] } "
```Jaco HofmannJaco Hofmannhttps://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/111Add CLI log tracking switch2019-11-01T14:37:04ZJens KorinthAdd CLI log tracking switchImplement a new global option which activates log file tracking similar to the log file panel in `itapasco`: Starting from a base logfile, output should be matched to regexes to find subsequent logfile mentions. These logfiles should be ...Implement a new global option which activates log file tracking similar to the log file panel in `itapasco`: Starting from a base logfile, output should be matched to regexes to find subsequent logfile mentions. These logfiles should be recursively added to the watcher, giving a complete picture of the outputs of, e.g., Vivado runs.2017.1Jens KorinthJens Korinthhttps://git.esa.informatik.tu-darmstadt.de/tapasco/tapasco/-/issues/136VC709: full-slave wrapper does not support multiple AXI4 slave interfaces2019-10-25T11:47:05ZJens KorinthVC709: full-slave wrapper does not support multiple AXI4 slave interfaces2017.2Jens KorinthJens Korinth