Re: FEL request: opencores and user demos

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello, Chitlesh GOORAH,

	I am interested in doing PIC development with the one of the following
setups:

	1.  PIKLAB
		Piklab, gpasm, gpsim, gputils, etc.
	2.  Ktechlab
		Ktechlab, gpasm, gpsim, gputils, etc.

	The primary devices will be:
	pic16f887
	pic16f690
	pic32 (not decided yet)

	I know that the 887 is not supported yet by some of the above, but I am
not above getting my hands dirty and doing some coding or control or
script file generation to make it work.  I would like a good tutorial
and documentation to begin the effort, but the stuff I have been able to
locate on line is pretty thin.  I can also do documentation.  I am a
test engineer who rose to Test Specialist inside of Teradyne, and my
forte was writing program translators from one
language/system/instrument set to another across Operating systems,
platforms and languages (I am a polyglot programmer).  I also developed
training and manuals that are still being used by that company.

	I attempted to find which mailing list to subscribe to, by browsing the
FEL portion of the Fedora website, but couldn't tell which group(s)
would provide the types of information I would need.

	The environment I would create would ultimately be used by several
programmers locally who have some C knowledge, limited assembly
knowledge and no embedded experience at this time, so I have my work cut
out for me.  I expect the total effort to take between 6 and 9 months.
At the end I would like to have the following:
	
	1.  A simple installable environment for pic development, plug and go.
		1.A  Examples for the PICs currently supported.  These must be
executable and tracable, and reflect reasonable programming practices.
		1.B. Programming Templates similar to the ones furnished by Microchip.

/********************** 8 months max to this point ********************/
	2.  A simple file method to describe a new pic and enable its
simulation, code generation, and simulator debug, so that new devices
would require coding only when core processes change.
	3.  Documentation that would include coding examples and stepping
through a bit of code to show the FSR's, variables, system operation,
perhaps even the waveforms if the IDE supports that.  Schematic capture
compatible with the GEDA stuff would be ideal.
	4. Internal linking to the Microchip website for documentation support,
and adobe reader support for the pdf documents.
	5.  A manual explaining the operation of the system.

	I know that a lot of this already exists.  I know this can be done, I
am pretty sure about the possible time line, and I believe I have the
generic knowledge to do it.  What I lack is the specific knowledge about
the tools, and I am a bit dense I guess, because the documents I have
found seem circular in reference and not completely clear how the links
are created and set up.  

I have PIC lab and Ktech lab both installed, and they both appear to
more or less compile code, but the hooks to the other utilities seem
quite bad.  They do not seem to recognize the two PICs, the simulator is
not integrated, although I can run gpsim from the command line, and some
fonts are missing.  

Once I get to the right mailing lists, I can provide more information to
the correct folks there.

Thanks,
Les H
	
On Fri, 2009-12-04 at 21:59 +0100, Chitlesh GOORAH wrote:
> Hello there,
> 
> As many of you already know that the FEL[1] team wants to ensure that
> opensource tools can be used for the real life, we would appreciate
> some help in terms of such documentation.
> 
> If you are familiar with tools like iverilog and ghdl, you can help us
> show the world what opensource EDA tools and opensource design flows
> can achieve. I welcome you to take one of the _completed_ opencores[2]
> projects and try to simulate it with ghdl or iverilog. Detail your
> procedures on
> 
> https://fedorahosted.org/fedora-electronic-lab/wiki/Demos/opencores/CHOSENPROJECT
> You can also upload your screenshots to that wiki page. To edit on
> that wiki page, please login with your FAS[4] username.
> 
> However if you encounter a bug with ghdl or iverilog during that
> process, please file a bug to [3].
> 
> https://fedorahosted.org/fedora-electronic-lab/wiki/Demos/opencores
> 
> Your help will be greatly appreciated.
> 
> Kind regards:
> 
> Chitlesh Goorah
> on the behalf of the Fedora Electronic Lab team
> 
> Other interesting urls which might interest you:
> * Openmoko hardware development on Fedora:
> http://chitlesh.wordpress.com/2009/10/07/openmoko-hardware-development-on-fedora/
> * Gallery http://publictest6.fedoraproject.org/gallery2/main.php
> 
> [1]: website: http://spins.fedoraproject.org/fel/
> [2]: http://opencores.com/
> [3]: https://bugzilla.redhat.com/frontpage.cgi
> [4]: https://admin.fedoraproject.org/accounts/
> 

-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux