Cisco has graciously agreed to donate a library of several utilities packages to the e community. Please refer to the LIBRARY_README.txt for general information, and to each of the packages' PACKAGE_README.txt file for more information on each package. The tar file containing the utilities library is attached to this message.
The zip file containing informational slides on Cisco's utility library packages is also attached. The zip file is 9 mg so may take a bit to download. The file is too big to fit on this post, so the unzipped files are posted in three separate entries below.
For your convenience, we have also extracted the document “Directory Structure.doc” from the csco_base_env/docs location.
Note: The library contains the csco_testflow package, adding phases to e's run phase. Cadence strongly encourages Customers to adopt the testflow phases feature that Cadence is releasing in Specman6.2. The new phases in e will be similar to the phases defined in the csco_testflow package, but will be a formal part of the e language. For more information please contact IPCM@cadence.com.
Meirav,Where are the slide shows that go along with the code? I'm told there are about 26MB of slideshows that will help you ramp on the whole ball o' wax.
Hi,We're aware of such a slide show, and are trying to get it from Cisco.
Here are three of the Cisco slidedecks describing their utilities
and three more
and the last three
Have succusfully ported much of the base_env_package. Testflow is already having a big impact.Some quick questions.For testflow, will it conflict with what gets released in 6.2?In addition to testflow, are there any plans to formally adopt any of the other packages?Config,trans, at rate_stats are must haves for us and are being incorporated into our environment. Having the full support from Cadence would be ideal.For addrmap, we are already well down the path of using vr_ad for addr/mem map and register abstraction. Very much like the features in the addrmap package but not sure if it can co-exist with vr_ad. We need to do some work on our side before I can artuculate a specific question on this, but am curious if there are any known gotchas that would prevent these packages from working together.The evc_topology package makes reference to a "mkevc.pl" script. Looks like it is used to fram out new evc developments to be used with the base_env package. Scipt is not included in the package. Could it be added?Thank you Mierav!
hi,Glad to hear about the success with Cisco's library.Regarding testflow phases: there will be no confilct between base_env_package testflow and Cadence's, in the sense they can run in parallel. More than that, code developed using base_env_package can be converted to using Cadence's Specman's testflow by modiyfing TCM names. Since there will be same 8 phases with similar functionality, migration should not be problematic.Currently, there are no plans to adopt more features of this library within Specman.