Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 2303
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to change design for ADE XL/Assembler test using SKILL and preserve analysis, variables and outputs

alexstepanov75

Hi,

I need to change the design for ADE XL/Assembler test using SKILL.

I am tryed to do this as folowing:

testSession=axlGetTest(axlGetMainSetupDB(axlGetWindowSession()) "aa")

toolargs=axlGetTestToolArgs(testSession)

rplaca( cdr( assoc( "view" toolargs ) ) "schematic" )

axlSetTestToolArgs(testSession toolargs) 

This indeed changes the design but also resets analysis, variables, and outputs.

Is it any other way to change the design without resetting analysis, variables, and outputs?

Best regards,

Alex.

  • Hi Alex,

    There's a CCR (number 1271081) for this - although sometimes I see it works, sometimes it fails. Not quite sure why. I suggest you contact customer support asking for a duplicate to be filed to increase the priority.

    Since you're talking about Assembler, maybe instead you can use maeCreateTest and use the ?sourceTest to import an existing test with a new design, and then delete the original test. I didn't test this, but it may be a workaround.

    Regards,

    Andrew

  • Hi Andrew,

    I tried maeCreateTest with ?sourceTest and ?view "newviewname". It doesn't work. Test created with the same design.

    So I suppose it is no workaround and I need to save analysis, variables, and outputs, then change the design, then set analysis, variables, and outputs.
    I generally have an idea how to save and then create variables and outputs. Can you please suggest how to save a list of analysis and then add them to test?

    Thank you,
    Alex.
  • Alex,

    I didn't read the documentation carefully enough. Looks as if using ?sourceTest just creates a copy of each test but doesn't change the lib/cell/view in the process.

    Any workaround is likely to get a little complicated, so please log a case with customer support as I suggested earlier, as I suspect it will take more time than I have at the moment to investigate.

    Regards,

    Andrew.

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.