May be comapanies likes http://www.nangate.com may be interested in supporting integration the same way as various SoC design companies are usinc Eclipse for creating their mixed SW/HW SDK-s?
They would probably reduce costs and attract more customers for their products likes "*The NanGate 45nm Open Cell Library is an open-source, standard-cell library provided for the purposes of testing and exploring EDA flows" * *if they offer support of their libaries, DRC tools and so on with opensource tool likes Electric.* On Mon, Mar 27, 2017 at 10:07 PM, Alexandre Rusev <[email protected]> wrote: > *Which one of "TCL horrors" would be better? The native libtcl based > implementation with JNI or Pure-Java?* > > > Pure-java has some worser support of TCL Tk, which is sometimes used in > various EDA core generators as I know. > > Supporting ot TCL natevely would likely provide more integration with that > set of vendor-specific hucked TCL-s, creating of which any vendor is > considering as a "good tone". > > > > > Tcl Blend > > Tcl Blend is a Tcl extension that makes use of JNI > <https://en.wikipedia.org/wiki/Java_Native_Interface> to facilitate > communication between a Java interpreter and a Tcl interpreter. Tcl Blend > is typically used to load a Java interpreter into an existing Tcl process, > so that functionality implemented in Java can be accessed in a Tcl script. > For example, one could allocate a Java object in a Tcl script and > interactively invoke Java methods on the object. > > One can also load Tcl Blend and Tcl into a Java process, which adds > scripting functionality to an existing Java application. Because Tcl Blend > is a normal Tcl extension, one can use it with other popular Tcl extensions > like Tk, Expect, and Itcl <https://en.wikipedia.org/wiki/Itcl>. > Jacl > > Jacl is a self-contained implementation of a Tcl interpreter, written > entirely in Java. Jacl also includes features that facilitate communication > between a Java interpreter and a Tcl interpreter. Jacl is typically used to > incorporate Tcl scripting functionality into an existing Java application, > without dealing with the complexities of native code that come with loading > Tcl Blend into a Java process. > > JTcl, a fork of Jacl, was released on November 17, 2010. One of the main > goals of JTcl is to continue the modernization of Jacl that began with the > Jacl Modernization Project in the Google Summer of Code (GSOC) 2009.[1] > <https://en.wikipedia.org/wiki/Tcl/Java#cite_note-1> > > > > > http://tcljava.sourceforge.net/docs/website/faq.html > > > > > > > On Sat, Mar 25, 2017 at 9:41 AM, <[email protected]> wrote: > >> [email protected] >> <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/electricvlsi/topics> >> Google >> Groups >> <https://groups.google.com/forum/?utm_source=digest&utm_medium=email/#!overview> >> <https://groups.google.com/forum/?utm_source=digest&utm_medium=email/#!overview> >> Topic digest >> View all topics >> <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/electricvlsi/topics> >> >> - Fully open source SoC >> <#m_-8413904755353309426_m_1686096997905863549_group_thread_0> - 3 >> Updates >> - Digest for [email protected] - 2 updates in 1 topic >> <#m_-8413904755353309426_m_1686096997905863549_group_thread_1> - 1 >> Update >> >> Fully open source SoC >> <http://groups.google.com/group/electricvlsi/t/56b11324395373c4?utm_source=digest&utm_medium=email> >> "Maurício Carvalho" <[email protected]>: Mar 24 02:30AM -0700 >> >> Hi Luis, >> >> Thanks for the prompt response! >> >> Since my goal is to prepare/gather a number of open source hardware, >> tools, >> scripts and PDKs to elaborate a design that can be manufactured, I >> wouldn't >> want to tie this project to any of the big companies (Cadence, Synopsys >> ... >> Nangate) unless they are willing to help open source design for actual >> real >> projects. The idea is to totally remove NDA contracts, but I'm sure this >> is >> not a reality for now, therefore I will try to minimize the number of >> NDA's. >> In addition, I'd also like to point out that this project is not related >> to >> any university or program, therefore I cannot benefit from any tools and >> PDKs. However, it might be beneficial to University students (undergrads >> to >> researchers) as well as independent designers. >> >> As a response to your answers: >> >> 1) , 3) and 4) Does the Electric developers plan on embedding distributed >> processing, SDCs and DFT? If not, have they thought about it? How can >> they >> help one to modify/implement them? (I have, in the past, built some >> ad-hoc >> scripts running bash and awk to implement distributed processing as well >> as >> implementing scan-chains. Still a work in progress) >> 2) 200nm is a good technology to start off with. >> 5) I thought this would be a bit of an issue. >> >> Adding another question >> 6) I really like command prompts where I can run scripts with almost no >> effort. Electric has some reasonable options for running scripts, but it >> doesn't have a command prompt (at least in the version I have) that I can >> quickly copy and paste or add specific commands similarly to the >> commercial >> tools without moving the mouse too much. >> >> Regards, >> Mauricio De Carvalho >> >> On Thursday, March 23, 2017 at 5:50:50 PM UTC, Luis Vitorio Cargnini >> wrote: >> Steven Rubin <[email protected]>: Mar 24 01:31PM -0700 >> >> > 1) , 3) and 4) Do the Electric developers plan on embedding >> > distributed processing, SDCs and DFT? If not, have they thought about >> > it? How can they help one to modify/implement them? >> None of the things you listed are planned for Electric. But any of them >> can be done, by you or other interested developers. As always, I am >> available for guidance and question answering. >> >> > but it doesn't have a command prompt (at least in the version I have) >> > that I can quickly copy and paste or add specific commands similarly >> > to the commercial tools without moving the mouse too much. >> You *can* script Electric but it's not easy. You have to use the Java or >> Python interface, which gives you complete access to the entire code >> base. With that much power, you can create circuitry, run tools, write >> files, and feed arbitrary commands to Electric, all from a script >> written in either Java or Python. The user's manual explains these >> interfaces, but you'll have to study the code to know the methods to >> call for each of the commands you want to script. Also note that the >> Java interface comes built-into Electric, but Python needs to be added >> separately). >> >> -Steven Rubin >> "Luís Vitório Cargnini" <[email protected]>: Mar 24 03:11PM -0700 >> >> Hi Mauricio, >> >> I had made some attempts in the past to embed the OpenCell 45 nm, still >> doesn't work well. Since it is an open-source project, I got your idea. >> So, >> Electric it is a great tool already, it can become better I agree. So, the >> best would increase the screens capability and the capability of the tool >> to assimilate all the parameters from FreePDK 45 and 16. They are open >> still as 'process', so anyone still can use the tool, however, cannot >> fabricate, they are highly detailed, as well as any foundry PDK, so they >> are a great start (Not talking about the OpenCell libraries, that are >> built >> on top of the FreePDKs). >> >> >> So, my $0.02, the idea have icarus verilog, but l would be incorporate >> icarus verilog parsing and exchange so you have to have it installed, but >> you c run and simulate from inside Electric. Also, there are other tools >> like Yosis (http://www.clifford.at/yosys/) also look into >> http://opencircuitdesign.com/, because there are some tools that can be >> incorporated. >> >> Since you mentioned Scripts, most probably the ideal would be integrated >> into Electric like the same way it have an add-on the Bean Shell, but >> find and create support for TCL, since every EDA tool, and mostly everyone >> uses TCL, so you can create a TCL shell (the classes for TCL in Java most >> probably already exist, somewhere) >> >> >> That is what I can contribute to you right now. >> >> Regards, >> Vitorio. >> >> >> >> On Fri, Mar 24, 2017 at 2:30 AM, Maurício Carvalho < >> [email protected]> >> wrote: >> >> Back to top <#m_-8413904755353309426_m_1686096997905863549_digest_top> >> Digest for [email protected] - 2 updates in 1 topic >> <http://groups.google.com/group/electricvlsi/t/a66805789214b27?utm_source=digest&utm_medium=email> >> Alexandre Rusev <[email protected]>: Mar 24 04:28PM +0300 >> >> Amount of requests likes "let's design real chip with real process PDK >> using Electric and fabricate it then" is growing? >> >> Can we get support from some factory or at least from IP-core design >> company? >> I encounted Electric prsentation in Imagination Thech presentation on >> their >> MIPS cores, recently. >> >> >> >> Back to top <#m_-8413904755353309426_m_1686096997905863549_digest_top> >> You received this digest because you're subscribed to updates for this >> group. You can change your settings on the group membership page >> <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/electricvlsi/join> >> . >> To unsubscribe from this group and stop receiving emails from it send an >> email to [email protected]. >> > > -- You received this message because you are subscribed to the Google Groups "Electric VLSI Editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
