[Fedora-electronic-lab] [Fedora Electronic Lab] #71: package hct : The HDL Complexity Tool is a simple tool to provide measurement data.
by fedora-badges
#71: package hct : The HDL Complexity Tool is a simple tool to provide
measurement data.
--------------------------+-------------------------------------------------
Reporter: chitlesh | Owner: chitlesh
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 13
Component: VHDL/Verilog | Version: devel
Keywords: |
--------------------------+-------------------------------------------------
http://hct.sourceforge.net/index.html
The goal of the HCT is to generate scores that represent the complexity of
the constituent modules of large IC design projects – i.e. SOCs. The
design's complexity scores are useful to verification teams so as to
efficiently focus resources based on the dynamic complexity profile of a
design. The scores are a useful tool to guide HDL designer's refactoring
efforts. This data provides an efficient way to "come up to speed", by
pointing you to the most important modules of a legacy design.
Importantly, the complexity scores allow managers to estimate schedules
and resources in a more robust and effective way than any one standard
metric can provide (SLOC for example).
--
Ticket URL: <https://fedorahosted.org/fedora-electronic-lab/ticket/71>
Fedora Electronic Lab <https://fedorahosted.org/fedora-electronic-lab>
Design, Simulate and Program electronics.
13 years, 12 months
[fedora-electronic-lab] MCU 8051 IDE
by Tom varghese
Hi there,
MCU 8051 IDE not run on fel 12. I got the following results.
$ mcu8051ide --check-libraries
MCU 8051 IDE v1.3.3
Checking libraries...
1/9 Checking for library BWidget
Library present ... NO !
Version 1.7 ... NO !
2/9 Checking for library Itcl
Library present ... YES
Version 3.4 ... YES
3/9 Checking for library Tcl
Library present ... YES
Version 8.2 ... YES
4/9 Checking for library md5
Library present ... YES
Version 2.0 ... YES
5/9 Checking for library crc16
Library present ... YES
Version 1.1 ... YES
6/9 Checking for library Tk
Library present ... NO !
Version 8.5 ... NO !
7/9 Checking for library img::png
Library present ... NO !
Version 1.3 ... NO !
8/9 Checking for library tdom
Library present ... YES
Version 0.8 ... YES
9/9 Checking for library Tclx
Library present ... YES
Version 8.0 ... YES
RESULTS:
Number of fails: 3
PROGRAM WILL NOT RUN, please install the missing libraries
Please Help.
--
Knowledge is free. Free means open source...
http://opentechlab.blogspot.com
13 years, 12 months
[fedora-electronic-lab] DGC GUI (was Re: Introduction)
by Shakthi Kannan
Hi,
--- On Sat, Jan 9, 2010 at 3:27 PM, Sikku <sikandar.sio(a)gmail.com> wrote:
| Got familiar with git. Its awesome. Has the request which u mentioned
| been granted?
\--
Not yet. Still awaiting response from FI.
---
| A small correction in the
| command u mentioned.
| $ rpm2cpio dgc-0.98-3.fc12.src.rpm | cpio -idv
\--
Thanks.
---
| Which means the GUI has already been written?
\--
Yes, but, uses old GTK+ API. You can look into the current source code.
---
| Will look into the documentation now. Before that I have to get
| familiar with GTK+ which I haven't used it till now.
\--
Please go through the latest GTK+ tutorial, and try out the examples.
---
| So some enhancements I have to work with?
\--
No. Tobias Dichtl enhancements will not be affected by your DGC GUI code.
Regards,
SK
--
Shakthi Kannan
http://www.shakthimaan.com
14 years, 2 months
[fedora-electronic-lab] configuring toolchains crashes PIKLAB
by Howard Howell
Here is the scenario....
If you close the current project, or start piklab with no project, then
select configure toolchains, the menu never opens and piklab crashes.
Alain knew about the case of starting piklab with no projcet, but I
didn't see any mention of the close the existing project and then try to
configure tool chains. The message is:
We are sorry, Piklab closed unexpectedly.
You can help us improve KDE Software by reporting this error,
Learn more about bug reporting.
Note it is save to close this dialog if you do not want to report this
bug.
(((( several line feeds))))
Details
Executable: piklab PID: 4157 Signal:11 (segmentation fault)
Unfortunately I don't seem to have the requisite symbol information so
the bug report won't finish, nor can I get valgrind to produce anything
useful.
The toolchain settings are probably going to make some change in the
project file, So my first guess is that with no project file open, there
is an attempt to write to an empty file. I am going to research this,
but I thought that some one here may have already isolated the bug to a
specific area in the software.
If that is the case, the (hopefully simple) solution is to open a
default project file, so that setups can be reported to it, and during
project creation, the system wizard will prompt if you want to use that
file. Or maybe simpler is just to load that file and modify it by the
project wizard.
I will reply either to this message or whoever follows up with what I
find.
Regards,
Les H
14 years, 2 months
[fedora-electronic-lab] piklab
by Howard Howell
Hi, everyone,
I have PikLab loaded, and the latest subversion as of a week ago.
I have also loaded Kdevelop.
What started me down this path is the issue where piklab can find the
gpasm, gpsim and gputils executables, but responds with the message
"gp***" not recognized in the configure toolchains dialog. If you click
the search button, it brings up a message box which shows:
Command for executable detection:
gpasm -v
Version string:
gpasm-0.13.7 beta
My guess is that the word beta on the end of the version string is
confusing the comparison used in the program. Alain has tried to make a
fix on this but was unsuccessful.
So, I obtained the subversion copy, loaded Kdevelop and attempted to
open the project. The project was not populated. My various attempts
to populate the project with the files have all failed.
I am unaccustomed to programs of this structure. I have used C and C++
before, and while not a power user in terms of systems programming, I do
write a lot of code. However this user interface, while probably simple
to all of you has me baffled. If someone could write up the procedure
they use to bring up the debugger, it would be very helpful, and I will
return my work to upstream.
Some of the projects I have done include program translation utilities,
simulation translation to program data for test systems and other
utilities as well as more than 100 test programs on main frame IC
testers running a variety of languages and operating systems.
And while the coding is intense in these programs, they are essentially
tightly bound, runtime sensitive and so a loose coupling is not
optional.
I have forgotten much about loosely coupled programming, but not
everything. I am also a very quick learner once I get my initial
hurdles cleared so I can experiment and develop techniques.
Regards,
Les Howell
14 years, 2 months