electronic-lab March 2010

electronic-lab@lists.fedoraproject.org

10 participants
28 discussions

[fedora-electronic-lab] How to search archives?
by Robert Peruzzi 17 Mar '10

17 Mar '10

How do I search archives for solutions to my common problem before posting it? The one list of dated archives I found had no convenient way to search all of them. Just in case somebody is kind enough to re-answer my original common problem, here it is: I have tried several ways to install Fedora Electronic Lab (FEL), all of them unsuccessfully, and am seeking a procedure or recipe to do so: * About a year ago I installed Red Hat Enterprise Linux (RHEL) onto an external disk drive, hoping to find something like FEL. Last Autumn an email arrived, announcing FEL. I was busy on a contract and didn't get to try it until this month. * I downloaded FEL into my RHEL environment and got a desktop icon with a "?" and can't figure out how to execute it. * My expertise is in circuit design, and obviously not in operating systems. I only know UNIX and Linux well enough to get to the CAD tools and do file editing/managing and c-programming, perl etc. So a lot of the acronyms and terminology I see in the documentation and discussions go right over my head. Thanks very much for your patient help. Cheers, Bob P.

2 1

[fedora-electronic-lab] Piklab
by Howard Howell 16 Mar '10

16 Mar '10

Continuing to work on Piklab and Ktechlab, I have gone back to piklab for now and discovered the following: 1. When you configure the toolchains, piklab looks in the exec path for gpasm and gplib and apparently ignores the environment, because when gputils installs the library manager and assembler are loaded in the /usr/bin directory and found via path from the command line. 2. I added a symbolic link to the /usr/share/libexec/sdcc directory (the search path for the executables used by piklab) to both gpasm and gplib, they show up as: "gpsim" not recognized "gplib" not recognized But pressing the find button for gpasm shows a textbox with the following in it: Command for executable detection: /usr/libexec/sdcc/gpasm -v Version string: gpasm-0.13.7 beta Pressing the button for gplib shows: Command for executable detection: /usr/libexec/sdcc/gplib -v Version string: gplib-0.13.7 beta So thinking the beta deal is bad and probably causing the problem, I did "yum info *gputils*" and got: Installed Packages Name : gputils Arch : i686 Version : 0.13.7 Release : 2.fc12 Size : 16 M Repo : installed >From repo : fedora Summary : Development utilities for Microchip (TM) PIC (TM) microcontrollers URL : http://gputils.sourceforge.net License : GPLv2+ Description: This is a collection of development tools for Microchip (TM) PIC : (TM) microcontrollers. : : This is ALPHA software: there may be serious bugs in it, and it's : nowhere near complete. gputils currently only implements a subset : of the features available with Microchip's tools. See the : documentation for an up-to-date list of what gputils can do. At this point, I believe there is a disconnect between the Piklab software and the current state of gputils in the upstream. Does anyone have anything to add to this or any suggestions of where to go from here? Should I bugzilla this? Regards, Les H

3 5

[fedora-electronic-lab] SWG Spins discussion and follow-up actions
by Matt Domsch 04 Mar '10

04 Mar '10

FYI, these were the notes from last Monday's Board Strategic Working Group meeting, where your responses to the Board's questions were noted and discussed. From this, there are several specific actions we would like to see taken: # the problems hampering Spins due to long GNOME dependency chain requirements has a ticket open for FESCo to discuss. https://fedorahosted.org/fesco/ticket/345 # hosting space for Spins for direct http downloads will be made available by Infrastructure. Each spin should file a request for space with infrastructure. http://fedoraproject.org/wiki/Infrastructure/RFR # being able to offer AutoQA individual Spins should get involved with QA Team to ensure their needs are addressed as well as those of the rest of the Project. This is highly dependent on Spins owners contributing to the QA methodologies and even direct test efforts - QA is already feeling overwhelmed, and we need to scale this process out across more volunteers. # banners on get.fp.o -> spins.fp.o https://fedorahosted.org/fedora-websites/ticket/16 People with web site building experience are asked to participate in the websites team to remove "waiting on someone who can" as a possible bottleneck. I thank you all for your valuable input and continuing contributions to Fedora. Thanks, Matt ----- Forwarded message from John Poelstra <poelstra(a)redhat.com> ----- Date: Mon, 01 Mar 2010 16:17:37 -0800 From: John Poelstra <poelstra(a)redhat.com> To: advisory-board(a)lists.fedoraproject.org Subject: Board SWG Meeting 2010-03-01 Recap User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc12 Thunderbird/3.0.1 https://fedoraproject.org/wiki/Meeting:Board_strategic_working_group_2010-0… == Roll Call == * Attendees: John Poelstra, Paul Frields, Chris Tyler, Mike McGrath, Colin Walters, Matt Domsch * Notes from last meeting: https://fedoraproject.org/wiki/Meeting:Board_strategic_working_group_2010-0… == Spins Work == * Background: ** Matt and Colin have been collecting feedback to questions asked ** https://fedoraproject.org/wiki/User:Walters/SpinsSigsRemixes_TargetAudience ** https://fedoraproject.org/wiki/User:Walters/SpinsSigsRemixes_ChangeDistribu… ** http://lists.fedoraproject.org/pipermail/spins/2010-February/000996.html ** https://fedoraproject.org/wiki/User:Mdomsch/SWG_Spins * Each spin producing group does believe they can and should define a target audience * John: would it help clarify our message to refer to the live gnome desktop as the ''default offering'' rather than referring to it as a spin? ** Paul: Spins were initially conceived as a range of things the community can produce that are alternatives to what we feel must be created, or add-ons that narrowly focus on special use cases * Matt: Rel-eng sits in the middle of the spin creation process right now -- a couple communication breakdowns have happened over time, sometimes spin producers didn't know their spin was being built ** Matt: semi-OT -- at some point need to reconsider the question of who builds the spins. Does it always have to be Release Engineering? ** Paul: more narrowly aimed spins (FEL, Games, ...) seem to nail their use cases quite well * Top of mind problem seems to be some dependency chains (system-config-keyboard), whether or not that is the most serious problem or not isn't clear * '''PAIN POINT IDENTIFIED''': Dependency chain requirements cause alternate desktop spins to still pull in a large portion of the GNOME stack. ** '''NEXT STEPS''': Mike will file ticket with FESCo requesting they look at dependency chain requirements. This could be a Fedora Engineering Services task. ** Colin willing to look at helping with dependency chain issues ** ''TICKET''': https://fedorahosted.org/fesco/ticket/345 * '''NON PAIN POINT''': Spins SIG does feel that resolution processes have been working well when they're needed. * Resources: ** Infrastructure now has the ability to host additional content, including spins. This has been a long time incoming, and needs to be implemented and announced, but the capacity is there now. ** Ambassadors who want to pass out specific spins can make requests for monetary resources to CommArch, to be evaluated in the scope of media requests and budget. *** The Board is not taking a stance on what medias should be produced for any particular event. * Not sure what to do with feedback from survey work that showed that some people don't want the board to help or ask questions about how they can help === Next Steps & Positive Outcomes === # dependency chain requirements #* https://fedorahosted.org/fesco/ticket/345 # hosting space for Spins #* Each spin should file a request for space with infrastructure # (tentative) being able to offer AutoQA #* individual Spins should get involved with QA Team to ensure their needs are addressed as well as those of the rest of the Project. # banners on get.fp.o #* https://fedorahosted.org/fedora-websites/ticket/16 # Update wiki pages for information collected == Default Offering == * https://fedoraproject.org/wiki/User:Pfrields/Current_default_offering * https://fedoraproject.org/wiki/User:Pfrields/Different_default_offering * Give feedback to Paul by tomorrow, 2010-03-02 * Paul will send to Board for approval on 2010-03-02 == Topics and plan for next meeting == * John/Chris will take up topic of "What is a target audience?" * Meet next week, 2010-03-08 at 20:00 UTC (3:00pm EST/12:00pm PST) _______________________________________________ advisory-board mailing list advisory-board(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/advisory-board ----- End forwarded message -----

2 1

[fedora-electronic-lab] arm-elf gcc/gdb/binutils packages for FEL?
by Chris Shucksmith 02 Mar '10

02 Mar '10

I use Fedora FEL for the prepackaged gEDA suite. Recently, I needed to compile C code for an embedded ARM processor, the Cortex-M3. While FEL/Fedoras Extra ships with an *arm-gp2x* tool chain, and another for *avr* it does not have an *arm-elf* toolchain. It was fairly easy to modify the avr-gdb.spec, avr-gcc.spec and avr-binutils.spec files found online from the Fedora public build CVS (eg. at http://cvs.fedoraproject.org/viewvc/rpms/avr-gdb/F-11/ ) to work for arm-elf, then build RPMs using rpmbuild. I removed a few avr specific patches, and upgraded binutils version to a later release to produce valid code for the cortex architecture (there were some fixes to the ARM call veneers in the last 12 months). These packages contain an arm-elf-gcc which accepts "-mcpu=cortex-m3 -mthumb" arguments. It seems worthwhile to submit these SPEC files for consideration for the FEL repositories. It would be great next time to have this pre-packaged, working on the assumption FEL might be more appropriate than Fedora Extras to carry them. The SPEC files (and FC11 RPMs) are on my blog at www.shucksmith.co.uk [1]. I would be happy to add them to the FEL CVS and look after keeping the packages building if this is an option. While I have no connection to either the gcc/gdb/binutils developers or FEL, I would still like to try and maintain them. Chris [1] http://www.shucksmith.co.uk/blog/olimexstm32-h103olimexjtagusbminifedoralin…

3 3

[fedora-electronic-lab] GNUSim8085 v1.3.6 Released
by Aanjhan R 02 Mar '10

02 Mar '10

GNUSim8085 development team is pleased to release version 1.3.6 of its 8085 simulator for Linux and Windows platforms. This is the first stable version after moving over to launchpad for our project management. With this release we bring to our users a wide range of new additions. To read the complete release announcement head here [1]. We appreciate your continued support in the form of bug reports (with patches ;)) and general feedback. Feel free to ask questions and get support through Launchpad's Answers interface. You can join our development team here - https://launchpad.net/~gnusim8085-devel . We always have some work. Some key highlights of this release are as follows * The UI is now internationalized. Translations for Arabic, Asturian, Catalan, Esperanto, French, German, Gujarati, Italian, Kannada and Spanish languages are now in place. * Printing support is added. * Improved Windows installer with multi-language interface. * Several UI modifications to enhance user experience. * A dozen bug fixes. [1] https://lists.launchpad.net/gnusim8085-devel/msg00050.html Kindly update your distro packages. -- GNUSim8085 devel team

2 2

[fedora-electronic-lab] F12 with Electronic Lab software
by Howard Howell 02 Mar '10

02 Mar '10

Hi, everyone, I finally got F12 fully installed, and now have added the EL package to it. I want to develop code for the PIC series microcontrollers. What I have now has Piclab setup and the compiler working with SDCC, but the software cannot find the supported processors for gpsim. I know that this is separate from Piclab, but the Help button doesn't bring up any help listing for gpsim. It would be nice if that happened. If there is no document for doing that, I can write up the steps as I figure them out. I don't know how to integrate such a document into the Help menu, but I can look that up with some guidance. So what I am suggesting is that I do the research and get it working, document the process, then give someone the document to see if they get it setup correctly, then we can package that as part of the EL package. Regards, Les H

3 2

[fedora-electronic-lab] Ktechlab help access needs Kdebase
by Howard Howell 02 Mar '10

02 Mar '10

Hi, guys and gals, Ktechlab of the FEL and 'Electronic Lab' rpm package requires the kdebase to get access to the help files. I tried to submit a bug, but bugzilla.redhat.com and I are not speaking to each other well right now. Anyway, when I attempted to run Ktechlab, I couldn't figure out what I needed to say to get some assembly code to work. I tried to open the help files using the help application, but it said it needed khelpcenter. Using yum whatprovides, I came up with KDE base. I had loaded all the system updates (460 of them) and all of the 'Electronics Lab' on my system, but this was not loaded. So I used yum to load: yum install kdebase-runtime-4.3.2-4.fc12.i686 After the install it works fine. Anyway, you all may want to add that to the dependency list for 'Electronic Lab' group. Someday real soon now bugzilla and I will come to an understand. Regards, Les H

2 1

[fedora-electronic-lab] SRAM/ROM IPs for Layout
by Chitlesh GOORAH 02 Mar '10

02 Mar '10

Hello there, I'm currently doing some testing with respect to Magic VLSI's LEF capabilities. Though it lacks many new definitions in LEF such antenna,.., could you please try to read your LEF files into magic, especially those LEF files which are being used in the semiconductor industry in terms of SRAM/ROM IPs. Any issue encountered related to LEF please, post it here and do mention the number of metal layers you are using. I'll try to spend some time to ensure Magic can at least read LEF 5.7. Cheers, Chitlesh -- Chitlesh GOORAH Fedora Electronic Lab http://spins.fedoraproject.org/fel

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

electronic-lab March 2010