Mentor Graphics Communities : Document List - All Communities

VHDLdesignStandards.pdf

community_admin@mentor.com — Fri, 08 Feb 2013 12:10:36 GMT

Instructions to Opt-in and Opt-out of the Sourcery CodeBench Customer Experience Improvement Program

community_admin@mentor.com — Fri, 05 Apr 2013 15:57:45 GMT

These instructions are applicable to the 2013.05 and newer releases of Sourcery CodeBench.

Opt-In Instructions - Sourcery CodeBench

During Installation

During the installation process for Sourcery CodeBench, select the "Yes" option (under "Improvement Program") when prompted to opt-into the CEI Program.

Opt-In/Out Instructions Through the "Preferences" Settings

Within Sourcery CodeBench, under Window > Preferences > Sourcery CodeBench, select the right appropriate choice.

Opt-Out Instructions for Sourcery CodeBench Lite Edition

Temporary Opt-Out

To opt-out temporarily, via the environment:

export CS_CLOUD_MODE = offline

Permanent Opt-Out

To opt-out permanently, via the configuration file :

/etc/cs.conf | ~/.cs.conf | <cache-dir>/cs.conf

CLOUD_MODE = offline

5月14日CES研讨会录像资料

community_admin@mentor.com — Mon, 20 May 2013 02:31:08 GMT

在本次研讨会中,大家将会学习到:

1. 什么是约束编辑系统（CES）

2. CES中的物理约束

网络分类（Net class）
间距约束（Clearance）
- 基本的间距约束
- 常规的间距约束
- Z轴间距约束
- 器件之间的间距约束
区域规则（Scheme）

注：本录像资料分为五个压缩包，请全部下载之后再解压。本资料仅供工具使用者学习之用。

Automation Manager

community_admin@mentor.com — Wed, 05 Sep 2012 19:28:59 GMT

Don't like how AATK's menu system is setup? Want to add tools to DxD-AU?

The Automation Manager is a program created to help users customize DxDesigner, Expedition, Library Manager and Cell Editor menu systems without knowing how to write the underlying code. This benefits the user by saving time and resources, allowing them to focus on the tools while having a customized "out of the box" feel. The average user will spend a day to do the research on how to implement custom menu structures for each of the different types of automation scripts (.vbs, .efm and .exe) Mentor supports. With the Automation Manager, custom menu structures can easily be added within minutes of starting the tool from scratch and modifications can be made in seconds.

The Automation Manager, paired with the Automation Community, will allow users to easily customize their own Mentor experience.

v1.5:

Added ability to add items to Cell Editor

v1.4:

Added ability to edit items
Added option to remove scripts from the computer when removing them from Automation Manager
Various bug fixes
Improved documentation

v1.3

Initial Release

To receive updates on when this script is updated, enable "Recieve E-mail Notifications" in the Actions tab on this page.

For any problems or enhancement requests, please contact Jeremy Parker at Jeremy_Parker@mentor.com

Always remember to back up your library or design before running any Automation script.

Requires Microsoft .NET Framework 4

Cell Editor: Pattern Place from Excel

community_admin@mentor.com — Thu, 16 May 2013 16:20:23 GMT

This program is a standalone program, based off of ALE's BGA creator. The intent of this program is to place pads based off of cordinates found in an excel spreadsheet.

To run the program:

Create a new cell
With Cell Editor open, open the program "ALE - Pattern Place.exe"
Provide the required information
Press "Place Pins" to start the process.

Want to add this script to Cell Editor menu system? Use Automation Manager:

http://communities.mentor.com/mgcx/docs/DOC-3199

To receive updates on when this script is updated, enable "Recieve E-mail Notifications" in the Actions tab on this page.

For any problems or enhancement requests, please contact Jeremy Parker at Jeremy_Parker@mentor.com

Always remember to back up your library or design before running any Automation script.

Requires Microsoft .NET Framework 4

Rapid Part Creator

community_admin@mentor.com — Fri, 16 Nov 2012 20:40:07 GMT

When working in DMS, librarians are required to create a symbol, part (PDB), and cell before checking the part into DMS and releasing it to the Production Library cache. Some companies prefer to release the symbol as quickly as possible for engineers to use and then finish the part and cell later. Since DMS requires a part and cell, Rapid Part Creator (RPC) assists by automatically creating those items from one or more symbols. This allows the librarian to load the part into DMS and release it to the cache for engineers to use. The cell created by RPC cannot be used for layout, and is just a dummy to satisfy the DMS data loading requirements. The librarian must correct the cell after the symbol is released.

Librarians in non-DMS environments may like to use RPC to create the PDB and dummy cell just as a convenience. The dummy cell is not actually required in a non-DMS environment but the rapid creation of the PDB from symbol data may still be appealing.

User documentation installed with program.

NOTE: Please see Installation Guide before installing this product.

v1.3.90:

Fixed several bugs that kept the original release from working under certain conditions.

v1.3.15:

Initial Release

To receive updates on when this script is updated, enable "Recieve E-mail Notifications" in the Actions tab on this page.

For any problems or enhancement requests, please contact Jeremy Parker at Jeremy_Parker@mentor.com

Always remember to back up your library or design before running any Automation script.

Requires Microsoft .NET Framework 4

Delphi CES Automation Use Case Description Form-2.docx

community_admin@mentor.com — Thu, 09 May 2013 17:32:08 GMT

Hardware Key (Dongle) Discontinuations and Replacement FAQ

community_admin@mentor.com — Thu, 31 May 2012 17:28:43 GMT

This FAQ describes hardware key (dongle) discontinuations in recent releases of Mentor Standard Licensing and the process to follow for hardware key replacements.

As of the Mentor Standard Licensing v2013_2 release (targeted for Q2 2013), only the Aladdin USB FlexID 9- key is supported.

As of the Mentor Standard Licensing v2012_1 release, the following hardware keys (dongles) are no longer supported:

Rainbow Sentinel CPLUS

PADS SSI/Pink Key

FLEXID 6-/7- (depending on platform - see table)

Dallas FLEXID 8- (depending on platform - see table)

v2012_1 Supported OS	CPLUS	Pink Key	FLEXID
v2012_1 Supported OS	CPLUS	Pink Key	6-	7-	8-	9-
Windows XP SP 3 32-bit	no	no	Yes	Yes	no	Yes
Windows XP Pro x64	no	no	no	no	no	Yes
Windows Vista (Business, Enterprise, Ultimate) 32-bit	no	no	Yes	Yes	Yes	Yes
Windows Vista 64 SP2 (Business, Enterprise, Ultimate)	no	no	no	no	no	Yes
Windows 7 (Professional, Enterprise, Ultimate) 32-bit	no	no	no	no	no	Yes
Windows 7 64 (Professional, Enterprise, Ultimate)	no	no	no	no	no	Yes
Windows Server 2003 32-bit	no	no	Yes	Yes	Yes	Yes
Windows Server 2003 64-bit	no	no	no	no	no	Yes
Windows Server 2008 SP2 32-bit	no	no	Yes	Yes	no	Yes
Windows Server 2008 SP2 64-bit	no	no	no	no	no	Yes
Windows Server 2008 R2 64-bit	no	no	no	no	no	Yes

Q: Which product releases are affected by this change?

A: Currently, the following releases are shipping with MSL v2012_1:

Expedition Enterprise Flow EE 7.9.4
Board Station XE Flow 7.9.4
PADS Flow PADS9.5

Please visit SupportNet to see the latest product downloads.

Q: Is my hardware key one that needs to be replaced?

A: You can visually confirm that your dongle needs to be replaced using A Field Guide to Mentor Graphics Hardware Keys.

Q: Which hardware key replaces my current one?

A: Your current hardware key will be replaced with the Aladdin USB FlexID 9- key.

Q: Will my existing license file still work?

A: No. After your hardware key is replaced, you will receive a new license file tied to your new key.

Q: How do I start the replacement process?

A: To start your replacement process:

Go to SupportNet and log in.
Click on the “Service Request” tab.
Select radio button for “Other Request Type” & choose “H/W Key Replacement ” from the menu.
Click “Next Step”.
Enter a “Short Description” of: Request to replace my current discontinued key with a USB key or Ethernet address XXXXXXXXXXX. Your Ethernet address is a 12 digit hexadecimal number; for example: 00C0A8F1798F. If you don't know how to find your Ethernet address, please read Determining the Hostid for Licensing.
Enclose your current authorization codes (license file) by clicking the “Browse” button to find the file, then the “Upload” button to attach it to your Service Request.
Click “Submit”.
Within 48 business hours, we will send you a temporary 30 day authorization code.
During the 30 day period return your hardware key following the instructions we will send you with the temporary authorization code.
Once we receive your returned hardware key, we will issue new authorizations codes for up to 15 months for the current software releases on a new USB hardware key.
We will send you the new USB hardware key.

Q: How long will the replacement process take?

A: The length of the replacement process depends largely on the time it takes to receive your old hardware key. We strive to send new keys and license files within 48 hours.

Q: Will I be unable to use my application during that time?

A: The replacement process is designed to minimize downtime. Generally, your downtime will amount to the time it takes to load the new hardware key driver driver and install the new license file. We have resources here on the Licensing and Installation community that will help you complete that process.

Q: I run both current and older versions of the application. Will I be able to use the new hardware key with all the versions of the software I'm running?

A: It depends. Support for the Aladdin USB FLEXID 9- has been available for ten years . Applications that shipped since that time most likely support the Aladdin USB FLEXID 9-. You can consult the release notes and product documentation for the release in question to determine which IDs are supported.

Q: What are the next steps after I've received my new hardware key and license file?

A: You'll need to follow the procedure for Downloading and Installing the Mentor Licensing Software (video), followed by Using the Mentor Install Program (MIP) to Update Your Hardware Key Driver (Video) and Installing a Mobile Compute License (video)

Q: What if my hardware key is my server ID?

A: After you complete the replacement process, follow the procedure for Downloading and Installing the Mentor Licensing Software (video) and Using the Mentor Install Program (MIP) to Update Your Hardware Key Driver (Video) followed by the procedure for Updating Your Licensing Manager (Server) on Windows (Video).

Workaround for DC2DX converted design's @CurrFileName Title Block property

community_admin@mentor.com — Fri, 26 Apr 2013 06:59:15 GMT

'Ver 1.0 Mentor Graphics Finland, Timo Kyyronen, 24.04.2013

'Originally created as a workaround for DC2DX conversion.

'In this case the property "@CurrFileName" used in DC can not be used in DxD.

'This is an unsupported automation script making a modification to the title block's

'predefined property, changing the project path as the value.

'In this example code it is "timo_test", replace with your actual property name.

'This script creates a temporary temp_borders.in into the project folder.

'temp_borders.ini file is used while updating title blocks in the design.

'You can think this also as an example how to modify more properties as well if needed.

'Caution, use at your own risk.

Upload the code from the attached zip file.

DxDesigner: Swap Schematic Properties

community_admin@mentor.com — Tue, 23 Apr 2013 18:52:58 GMT

During translations, sometimes it is decided that a property's values should be mapped to a new property in DxDesigner. A good example is copying a corporate part number to Part Number.

This script will loop through a schematic and copy the values from one property to another. If the destination property is not found, the script will create the property on the schematic part and update the value. There is an option to also remove the old property, if the property is no longer needed.

Adding filters will instruct the script to skip over any source property that has a value of what is defined in the filter. For multiple filters, add one string per each line.

Example:

DxDesigner

Expedition

Library Manager

Release Info:

v1.1:

Added Filter

v1.0:

Release to Community

To receive updates on when this script is updated, enable "Recieve E-mail Notifications" in the Actions tab on this page.

For any problems or enhancement requests, please contact Jeremy Parker at Jeremy_Parker@mentor.com

Always remember to back up your library or design before running any Automation script.

Requires Microsoft .NET Framework 4

Advanced Library Editor

community_admin@mentor.com — Mon, 01 Aug 2011 22:01:41 GMT

Advanced Library Editor (ALE) is a utility written by the Mentor Customer Migration Team. It is helpful for bulk modifying of DxDesigner/Expedition libraries, usually when translating from other systems.

http://communities.mentor.com/mgcx/docs/DOC-2383

For any problems or enhancement requests, please contact Scott Williams at scott_williams@mentor.com and Jeremy Parker atJeremy_Parker@mentor.com

Always remember to back up your library or design before running any Automation script..

Requires Microsoft .Net Framework

How to configure my Windows machine as the license server (video)

community_admin@mentor.com — Thu, 05 Jan 2012 19:28:35 GMT

Manual steps:

Refer to the following PDF for instructions:mgc_licen.pdf

Automated steps:

Demonstration:

(Embedded movie requires Flash. Click here to view MPEG-4 version)

To run the Mentor License Utility to automate the installation:

Download the "Full" version of the Mentor License Utility from SupportNet
Run the Mentor_License_Utility_INSTALL.exe which extracts all the program files, creates a shortcut*, and launches the Mentor License Utility program. (See README.txt for version information)
Click the Install License button (bottom right corner)
Select the Install a Nodelocked or Floating license to this machine option
Follow the remaining prompts to complete the license installation

* A shortcut to the Mentor License Utility is created under Start > Programs > Mentor Graphics License Utility

Note: If licensing errors are encountered after running the Install License to set up the license manager: Run a diagnostic report from the Tools > Create Diagnostic Report > Standard menu option, and attach the resulting diag_file.txt to a new Service Request on SupportNet, to expedite the troubleshooting process.

The Mentor License Utility automates the license server configuration tasks, including:

Separation of Nodelocked/Floating licenses by HostID (you don't need to separate license file manually)
Installation of hardware key drivers (if necessary)
Installation of PCLS / license server software (if necessary)
Creation of license manager (as a Windows/Lmtools service, and as "automatic")
Updating of existing license manager service with new licenses
Pointing clients to the server via port@host value
Setting the MGLS_LICENSE_FILE environment variable

Note: The Mentor License Utility only supports licenses under the Mentor Graphics Vendor Daemon ("mgcld")

Expedition/Cell Editor: What's Inside/Outside?

community_admin@mentor.com — Thu, 14 Oct 2010 22:21:40 GMT

The InsideOutside.vbs script reports on objects with coordinates inside or outside a specified rectangular area and aids the user in removing unwanted objects not readily seen on the screen. This will generate an "InsideOutside.txt" file to the pcb\LogFiles directory allowing it to be viewed using Expedition's FileViewer and will automatically open it in the system's default text editor upon completion. It will report the Object's Type, Name, (Number of Coordinates) to aid in looking for polygons with insufficient number of coordinates, or, a Text's [Width/Height] to aid in looking for oversized texts, and an X/Y location of the coordinate found to be inside or outside the area (only one pt - x,y - is reported per object). In the case of Text, the Extrema bounds is also checked.

Upon Execution of the script, the user will be prompted for the desired Mode: 1=Report Only, 2=Interactive Delete, 3=Auto Delete.

The user will also be promted to Check: 1=Inside Area, 2=Outside Area

The script will then prompt and wait for two mouse clicks (not drag) to define the rectangular area and will draw and fill the rectangle before executing its search. It will remove this rectangle when the script completes.

Initial intent was to look for objects outside of the intended design area. For instance, things causing Fit View to be oversized, or anomolies in the Gerber Plot.

This script is written for Document Collections as defined in EE7.9u5, hence execution in previous releases that do not contain a certain collection requires modification of the "CheckInOutsideRect" Subroutine. For instance, if your Expedition Version does not have BondPads then you would comment out or remove the line

"If Not checkPt(dObj,pcbDoc.BondPads,"Bond pad",True) Then Exit Sub

Version 2: Added Support for execution in Cell Editor. If there is no existing user layer on which to draw the rectangle, script will create one called "InsideOutside", but the display control will be off so you will not see the rectangle as in normal operation. It will remove this user layer after run.

Version 3: Fixed capability to delete Dimensions.

Version 4: Fixed problem with opening notepad in Win7

Version 5: Fixed Capability to report and delete Glue Spots. These can only be removed from within Cell Editor but will now be reported in Expedition & Cell Editor.

Version 6: Added Capability to report Geometry LineWidths <= 0 by inserting an "*" before NumPts e.g. "(*5)" indicates 5 pts of zero linewidth. Hence, you could search the resulting document for "(*" if you wanted to search for <=0 LineWidth items.

Version 7: Added capability for user to control Precision of coordinates for cleaner printout - At the top of the script, Modify the Const PRECISION to change the number of digits after the decimal (currently set at 4). Depending on your Display Units, you may need to modify the Const XYSPACE to correctly reflect the total number digits in a coordinate (currently set at 12). Added reporting of the Cell Owner of an object via its Refdes and/or CellName. Enhanced column alignment of the Object Name. Added new object TestFixture Outline which updates the script to 7.9.4 objects level.

Version 8: Fixed bugs related to single point objects (Component and Text).

Version 9: Fixed reporting of Component GlueSpot's Owner.

Version 10: Added Capability to report and delete Groups based on a groups center location.

Advanced Library Editor - v3.0

community_admin@mentor.com — Wed, 22 Jun 2011 14:18:33 GMT

Version 3.0 of ALE has been released to the community at:

http://communities.mentor.com/mgcx/docs/DOC-2383

NOTE: There is a bug in the communites that doesn't allow for proper links to other documents. Please copy and paste the link in your browser to find the program.

In ALE v3.0:

New Features:

PDB:

Update Top Cell
Add Alternate Cell
Part Height Report
Add Part Property
Modify Existing Property
Duplicate Part
Search Parts

Cell:

Add Pins to Cell
Compare Cell in PCB to Library
Change Text
Change Outline Strokes
Change Padstacks in Cell
Modify / Add Properties
Remove Properties
Rename User Layer

Bug Fixes:

Padstack Editor was not properly saving after modifications

For any problems or enhancement requests, please contact Jeremy Parker atJeremy_Parker@mentor.com

Always remember to back up your library or design before running any Automation script.

Requires Microsoft .NET Framework 4

Cell Editor : Batch Cell Library Editor

community_admin@mentor.com — Mon, 13 Sep 2010 22:23:52 GMT

New Version Available 1/26/2012: Removed the work-around for memory bug fixed in 7.9.2. The download includes both versions (Pre 792 and 792+)

New Version Available 3/25/2013: Fixed minor bug in the 792+ version.

The EditLibraryCells.vbs script provides the mechanics for Editing Cells in the Central Library's Cell Partition. It begins by compiling a list of partitions and cells to process. It does this in a way that allows you to easily customize the resulting compilation by allowing you to define and specify filter functions that specifiy whether or not to include or exclude a partition and cell. After compilation it will execute the edit process which will open each cell and feed its document object to an edit function that you define and specify. This function is required to return a true or false value to indicate whether or not to save the cell. Below is an example use of the Subroutine "EditCLCells" that is included in the script and the functions that it uses, specified and defined by you.

'Modify the call to EditCLCells to sepcify your

'Partition Filter Function name (IE "myPartitionFilter")

'Cell Filter Function name (IE "myCellFilter")

'Editor Function name (IE "TextCell")

'Do not change the Subroutine name "main()"

Sub main()
EditCLCells libPath & libName,"myPartitionFilter","myCellFilter","TextCell"
End Sub

'Define your Partition Filter Function

'Return True to include

'This example excludes all partitions except the "smd_conn" partition

Function myPartitionFilter(oPartition)
myPartitionFilter=False
If oPartition.Name="smd_conn" Then myPartitionFilter=True
End Function

'Define your Cell Filter Function

'Return True to include

'This example includes every cell except testpoints and jumpers

Function myCellFilter(oCell)
myCellFilter=False
If oCell.Type=epcbCelltypePackage Then
If Not oCell.PackageGroup=epcbPackageJumper And Not oCell.PackageGroup=epcbPackageTestPoint Then myCellFilter=True
End If
End Function

'Define your Editor

'Return True to save

'This example creates a FabricationLayerText at 0,0 in each cell

Function TextCell(oCellDoc)
TextCell=False
Dim tObj
Set tObj=oCellDoc.PutFabricationLayerText("EditCLTest",0,0,epcbFabAssembly,epcbSideMount,.065,0,10,"VeriBest Gerber 0",0,epcbJustifyLeft,epcbJustifyBottom,Nothing,epcbUnitInch,epcbAngleUnitDegrees)
If Not tObj Is Nothing Then TextCell=True
End Function

At the top of the script is a Const DBUG=0 statement that controls the maximum number of cells to process where 0=All. This will allow you to minimize the runtime for debug purposes.

The script may be executed one of two ways:

1) Executed via "mgcscript" in a windows command prompt with the Pathname of the library given as the sole argument:

"mgcscript C:\VBScripts\EditLibraryCells.vbs C:\Libraries\20078\Library.lmc"

2) Open the script in IDE - Library Manager's File->Open Script Form and execute the "Play" button. However, this may require an Automation Pro license. It does in Expedition

The script will write to "EditCLCells.txt" in the library's LogFile directory. Use this file to determine status of the run. Use an editor to view the file that will open files in use, ie Notepad.exe. When completed, this file will open in Notepad. At This posting, it is known that after script "completion" & "Data CellDB Saved", IDE/Libray Manager will crash due to bug in IDE. Hence, I recommend using command prompt until this is fixed.

HINT: when writing/debugging your Editor Function, do so first in a separate script, drag & drop unto an open cell in the cell editor. Otherwise, it will take considerably longer for debug.

How-to Video: Install Nucleus SmartFit for STMicroelectronics STM32

community_admin@mentor.com — Wed, 06 Mar 2013 22:44:48 GMT

This video describes the process of downloading and installing the Nucleus SmartFit for STM32 product.

How-to Video: Install Nucleus SmartFit for Texas Instruments Stellaris

community_admin@mentor.com — Wed, 06 Mar 2013 22:42:27 GMT

This video describes the process of downloading and installing the Nucleus SmartFit for Stellaris product.

How-to Video: Install Nucleus SmartFit for Freescale Kinetis

community_admin@mentor.com — Wed, 06 Mar 2013 22:45:58 GMT

This video describes the process of downloading and installing the Nucleus SmartFit for Kinetis product.

Nucleus SmartFit Getting Started Guide

community_admin@mentor.com — Mon, 04 Mar 2013 21:56:55 GMT

Color Schemes

community_admin@mentor.com — Thu, 28 Feb 2013 19:58:38 GMT

Attached to this document are several color schemes you can use in DxDesigner to enhance your documentation. Color schemes are personal to each user and when a scheme is imported it changes the DxDesigner.xml file in your local writable wdir directory location.

FAQ - Nucleus SmartFit

community_admin@mentor.com — Thu, 28 Feb 2013 00:35:45 GMT

1. The BSP selection for each vendor targets specific evaluation boards by that vendor. My target will be a custom design. How do I use the SmartFit BSP on my target?

If the final target does not use any peripherals that are off-chip from the MCU, then the “board”, as viewed by the BSP, is the MCU itself. The pre-built Nucleus RTOS image will follow the MCU to the final target with no modification. If the BSP is designed to use an off-chip support device that is present on the vendor evaluation board, then the final target must use either the same device, or one that is functionally identical from the software perspective. Any greater variation would require the use of the Nucleus ReadyStart product.

2. Some of the BSP options are close to the peripheral usage that I require, but none hit the exact combination that I require. How do I work around this?

The most straightforward solution is to use a BSP that is a superset of the required peripheral support. The driver code for the unused peripherals will still be present in the Flash image, and will be initialized during start-up, but its presence does not require usage by the final application. An application that demands a very specific peripheral configuration not in the published list will require a Nucleus Ready Start license to allow full customization. Mentor Graphics is always interested in customer feedback on desired software configurations for future releases.

3. I use an MCU that is a member of the device family from a particular vendor, but is not the same exact device that is specified in the BSP name. Can I use the SmartFit image for another device in a vendor MCU family?

That would depend on the compatibility between devices in the specific family. Most families have a very high level of software compatibility between devices; however some contain differences that would prevent portability. The Nucleus RTOS image is supplied in object format that is already compiled, but not yet linked or located. The user can edit the linker command file to align the Flash and RAM usage of the final image, however moving code to a device with lesser memory resources must be done with caution. The final symbol table will indicate actual memory usage. Peripheral devices cannot be accessed if their base addresses change between device implementations, thus the inherent peripheral initialization code can be expected to fail in such situations.

4. If my application doesn’t use a peripheral that is included in the BSP that I select, do I need to do anything special to the I/O pins for that module?

All of the peripherals included in the BSP will go through their normal initialization process to bring them online in anticipation of usage by the application. An unused peripheral will assert and read the values of I/O pins in a way that is consistent with its normal operation. The external signals for these peripherals must be left unconnected or terminated as would be appropriate for their expected use. If the design requires the signal to assume a value that is different than the quiescent state after proper initialization, the control registers of these peripherals must be directly accessed by the application software to change their state. After initialization, if a peripheral is not used by the application, it will not be accessed by the Nucleus RTOS and can be safely placed into whatever state is convenient for the application. The hardware design must take into consideration the fact that the signal pins will go through the initialization process prior to the application code assuming control of the device.

5. If I want to move an application to a different SmartFit BSP, is this possible without altering my application code?

Nominally, yes. As long as the application code accesses the hardware thorough the Nucleus RTOS API, it can be moved freely across all Nucleus platforms. An obvious limitation would be that the new target would be required to provide appropriately matching peripherals used by the application code. Some subtle differences would be changes to the amount of available memory, as well as the timing of the code execution on the new target. Moving within a device family would provide the greatest level of compatibility, followed by remaining with the same silicon vendor, with moving across device vendors as having the largest potential impact on system behavior.

6. Can I move a SmartFit application to the Nucleus Ready Start in the future?

Yes. SmartFit uses the exact same application development environment, Nucleus RTOS code, device driver code, and programming API as Ready Start. Migration is simply a matter of moving the application source files into the CodeBench Eclipse workspace provided with Nucleus ReadyStart.

7. While SmartFit is designed to operate as a turnkey development environment, I still have questions that I need answered. How do I get straightforward answers to a few simple questions?

Information and resources can be found on this community’s Overview page. This community site is monitored by the Nucleus technical staff. Periodically we will update this FAQ to reflect the wishes of the community.

如何进行DFT测试

community_admin@mentor.com — Mon, 25 Feb 2013 01:47:25 GMT

1.测试点没有测试点属性；

2.所以测试点全是以零件的形式存在；

3.如何进行DFT测试

第一次遇到这种情况，求助...

Expedition PCB : Safety Net

community_admin@mentor.com — Wed, 20 Feb 2013 17:35:37 GMT

The SafetyNet.vbs script runs in the background and copies the Work\Layout_temp folder to a folder named "Layout_temp_" + datetime stamp of the LayoutDB.lyt file (IE. "Layout_temp_022020131032"), prior to the upcoming save made by Autosave or File > Save. It will maintain a number of copies specified by the Const MAXSAVES=2. You can change this to a number you prefer. Hence, the folder name reflects the time the LayoutDB.lyt file was last saved. The zip file contains both the scripts.ini file and the SafetyNet.vbs script. Put the SafetyNet.vbs file in any location, change the path entry in the scripts.ini file to reflect the location, then put the scripts.ini file in the WDIR folder or add its contents to a scripts.ini file currently being used.

Warning! Scripts obtained through TechNotes, the Mentor Communities Site, or any resource not the Mentor Graphics Installer, are not supported software. Use with caution. Backup your data before executing any such script.

Expedition PCB: Run PCBDiagnostics

community_admin@mentor.com — Thu, 25 Oct 2012 21:55:15 GMT

This script will execute pcbdiagnostics.exe on the expedition design it is executed from and open its logfile. You should save the design first as it runs on disk data. For more information on pcbdiagnostics.exe, consult expedition documentation. If you are not able to open the pcb in Expedition, then you will have to run this manually via a command prompt.

NOTE: Some Fixes are made to disk data directly. There are also some fixes that can only be applied on re-invocation of Expedition. Hence, if any fixes are reported, user must exit Expedition without saving, and then reopen.

Manual Execution of pcbdiagnostics.exe shown below.

Expedition/Cell Editor/Drawing Editor: Copy Gfx & Txt

community_admin@mentor.com — Wed, 11 Aug 2010 22:10:17 GMT

This script will copy selected User Layer and Fabrication Layer Objects to a user specified User Layer (Need not be predefined).

Update 1: Enhanced to include copying of selected Conductive Areas, Plane Shapes and Traces to the user layer.

Update 2: Enhanced to include copying of selected pin and via pads.

Update 3: Enhanced to include copying of selected teardrops.

Update 4: Fixed to maintain source object fill type.

Update 5: Enhanced to include copying of mounting holes.

Update 6: Enhanced to include all other graphical objects not previously copied (Obstructs, Rule Areas, Placement Outlines, Fiducials, etc) and execute from Dialog (shown below). Also enhanced to limit copy of selected conductive objects to those on a specific signal layer or All. Also enhanced to allow either Overwriting Existing output layer or Add to Layer via the Clear option.

Update 7: Enhanced to run on any release objects between 2005.3 up to EE7.9.4

Rotate a layout by 90 degree

community_admin@mentor.com — Thu, 17 Jan 2013 18:11:26 GMT

Expedition - Export ODB++, HLDRC6.0 and Layer Stackup Data

community_admin@mentor.com — Mon, 14 Jan 2013 15:42:26 GMT

Glossary of Licensing Terminology

community_admin@mentor.com — Fri, 30 Nov 2012 19:36:28 GMT

atomic license: An atomic license authorizes the use of a single application or option to an application.

Client: The host requesting a license from a server.

composite license: A composite license usually ends in a "_c" suffix and typically authorizes the use of more than one application under the same license, although a composite license does not usually authorize as many applications as a station license.

Exact Access Date: Date encoded in a FEATURE or INCREMENT line. Allows access to software updates for existing licensed software released prior to a support contract expiration date.

feature: A portion of the license file that contains the Mentor Graphics software license. Features are either composite, station, or atomic licenses and can be node-locked or floating.

FEATURE or INCREMENT line/name: The actual license with an encrypted string and other information that enables a product in the license file.

Flexera: Software company that produces FlexNet Licensing.

FlexNet/FLEXlm Licensing: Flexible license manager provided by Flexera Software. The Mentor Graphics licensing software uses FlexNet Licensing as the basis of the licensing system.

floating license: Type of license that can run on any workstation.

hardware key/dongle: Device plugged into a parallel port or USB port. Provides a unique hostid for the licensing system (Windows only).

hostid: A unique hardware based number for each machine. Ties licenses to a specified server or workstation.

independent server: Contains a unique set of license data. If an independent server is off the network, then all licenses associated with the server are unavailable.

license daemon: The daemon process that sends client processes to the correct vendor daemon on the correct machine. Mentor Graphics licensing includes two daemons, lmgrd (license daemon) and mgcld (vendor daemon).

license file: A text file that contains the customer site identification, license server and daemon information, and FEATURE or INCREMENT lines, which are the actual licenses for the supported products.

license server/manager: A workstation that runs the license daemons and provides licenses to client workstations.

lmgrd: The FlexNet license manager daemon.

mgcld: The Mentor Graphics vendor daemon.

MGLS: Mentor Graphics Licensing System. This software contains the lmgrd, mgcld, and other utilities/programs, to assist the system admin with the license server setup.

Mobile Compute License: Equivalent to a node-locked uncounted license.

node-locked license: Type of license that is tied to a particular system's hostid.

node-locked uncounted license: Node-locked uncounted licenses (Windows only) are locked to hardware keys or Ethernet addresses of PCs and can be used remotely. This type of license does not require a license server or network connection.

PCLS: PCLicensing System (equivalent of MGLS on Windows).

redundant servers/cluster/triad: Configured in a group of three license servers that all contain the same license data allowing for fail-over. Allows access to all licenses on the servers when a majority of the servers are operational.

Server ID: Hostid of the license server machine.

station license: A station license usually ends in a "_s" suffix and authorizes the use of any applications contained in that station.

vendor daemon: The daemon that dispenses licenses for the requested feature. This daemon is built by the application’s vendor and contains the vendors unique encryption. Mentor Graphics vendor daemon is mgcld.

What's New in the Fall 2012 Release of Sourcery Tools

community_admin@mentor.com — Fri, 21 Dec 2012 23:25:59 GMT

Automation: DxDesigner change property name

community_admin@mentor.com — Tue, 18 Dec 2012 10:47:25 GMT

This is an utility which renames wanted properties in the active DxDesigner project.

'Remove the defined property name and add the new one with the original's value and coordinate locations.

'Warning! This is an unsupported script and should be used with caution.

'Version 1.0 Mentor Graphics Finland, Timo Kyyronen, 18.12.2012

'Backup your design

'Save this code like C:\tmp\change_property_name.vbs

'Modify ORIG_PROP_NAME ,NEW_PROP_NAME to match your needs

'In the command line type "run C:\tmp\change_property_name.vbs"

'Also ensure by your self that “NEW_PROP_NAME” is defined in the Library’s Property Definition Editor (Eliminate Non Common Property effect)