Activity for Kactus2
-
Kactus2 released /Kactus2SetupWin64bit3.13.2.exe
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
chris chaleki posted a comment on discussion General Discussion
I successfully executed kactus2 by creating a kactus2.conf file and placing it in the /etc/ld.so.conf.d folder. I added the line /usr/lib64 to the kactus2.conf file, which is where the libIPXACTmodels.so.1 file is located. I then executed sudo ldconfig, which reloaded the list of system wide library paths. Thanks for the help!
-
Esko Pekkarinen posted a comment on discussion General Discussion
Hi Chris, The issue is that the shared libraries cannot be found. By default, the libraries are installed in /usr/lib or /usr/lib64. Check first, if you can find libIPXACTmodels.so.1 in either of these locations. Also did you see section 3a in the README? It shows ways to run Kactus2 in different environments.
-
I was able to compile by changing the following lines in .qmake.conf: PYTHONCFLAGS=$$system($$PYTHONCONFIG --cflags --embed | grep -o -e "-I[^[:space:]]" | uniq) PYTHONLIBS=$$system($$PYTHONCONFIG --embed --ldflags | grep -o -e "-[lL][^[:space:]]")* Unfortunately, when executing I get the following error: "kactus2: error while loading shared libraries: libIPXACTmodels.so.1: cannot open shared object file: No such file or directory" Could someone please tell me how to fix this?
-
-
-
-
-
-
-
-
-
-
-
-
-
So returning to your original question, I'm afraid there is no "easy" way to get the full memory map in HTML. However, I do see two options that are available: First is to use the MemoryViewGenerator plugin. It creates a listing of the memory maps and their contents similar to MemoryDesigner, but in CSV format. Extracting relevant information from that should be straightforward, yet convertion to HTML will require some effort. Second, the summary of the memory maps could be added in the current document...
-
-
-
-
-
-
-
-
-
Kevin Lovell posted a comment on discussion General Discussion
Hi Esko, Yes, HTML is the preferred format, and I'd like to see in an output the same content that appears in Memory Designer, which specifies the full design from several different xml sources. More particularly, the output simply needs to be the "top level" memory map, which describes, in a single map, all of the memory maps of each instantiated component.
-
Hi Kevin, Would you kindly describe in a bit more detail your desired document output? From your description I gather you would like an HTML document listing all the memory maps through the complete hierarchy of a design i.e. a textual representation of the view you see when you select the Memory Designer. Is this correct ? Is HTML your prefered format?
-
Hello In the GUI, a fully specified hierarchical design will display the memory map and address space of the entire design from a top level perspective. However, when using the documentation generator, only the local memory maps of the currently selected component are described. Is there an easy way in Kactus to edit a plugin to use the parsed IP-XACT files to generate a document describing the full address space and all its component memory maps for a design in a single file?
-
Hi Kevin, Unfortunately there is no support for custom fields within memory maps in the current version.
-
Hello, I'm evaluating the tool for use in generating address maps for our designs. Is there any way to add custom fields for registers, bit fields, etc. that are not part of the IP-XACT standard? Thanks
-
-
-
-
-
-
-
Hi, Unfortunately, registers are not yet included in the generation. Earlier we actually had an experimental register feature in Verilog, but the end result was not satisfactory, so we decided to withdraw it until we could re-design it properly.
-
Antipov Mikhail modified a comment on discussion General Discussion
Hello! I'm working with the program and I have a question. I have: Next, I want to...
-
Hello! I'm working with the program and I have a question. I have: Next, I want to...
-
-
-
-
-
-
-