Stats

  • Replies 2
  • Subscribers 159
  • Views 13439
  • Members are here 0
More Content

Simple Skill script made Allegro frozen

JGONG

Hi, I got a very strange issue: my skill script made the Allegro "busy" and frozen. Please refer to the attached picture:

 When I typed in the function name "sp",  the script seems not even started, because it didn't print the "start:" at line 5.  If I click on "X" on up-right corner of Allegro editor windows to close it, Win7 would pop "Application is not responding..." message. 

Any help or clue would be appreciated.   Thanks in advance.

Jun Gong

BTW:

 I am thinking whether SKILL has certain limitations that not publish and easy trap a new skill programmer. ex, a string length may have maxim limit, maximum total script length, function length? etc.  Does any one know which document has this information? 

 

 

Parents
  • SKILL is interpreted and, as such, it's quite easy to upset the interpreter and not get an answer. Outputs from "printf"s are buffered so you may not see the output until the script completes, if the script never completes... As a preference, use the axlMsgPut to output messages. Start off with something simple, like output a message and then go from there so that you can identify the "break" easily. Refer to the algroskill.pdf, in the doc\algroskill directory of the installation, for PCB Editor specific SKILL functions and the sklangref.pdf, in the doc\sklangref directory for "generic" SKILL functions. Refer to other working examples that have been contributed, like the PCB SKILL forum and the Allegro SKILL Code Library from the Cadence Online Support site, there are also examples in the product installation at share\pcb\examples\skill to illustrate specific SKILL principles.
Reply
  • SKILL is interpreted and, as such, it's quite easy to upset the interpreter and not get an answer. Outputs from "printf"s are buffered so you may not see the output until the script completes, if the script never completes... As a preference, use the axlMsgPut to output messages. Start off with something simple, like output a message and then go from there so that you can identify the "break" easily. Refer to the algroskill.pdf, in the doc\algroskill directory of the installation, for PCB Editor specific SKILL functions and the sklangref.pdf, in the doc\sklangref directory for "generic" SKILL functions. Refer to other working examples that have been contributed, like the PCB SKILL forum and the Allegro SKILL Code Library from the Cadence Online Support site, there are also examples in the product installation at share\pcb\examples\skill to illustrate specific SKILL principles.
Children
No Data
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.