• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Allegro X PCB Editor
  3. AutosilkUtils in 17.2

Stats

  • Replies 19
  • Subscribers 161
  • Views 20730
  • Members are here 0
More Content

AutosilkUtils in 17.2

EvanShultz
EvanShultz over 9 years ago

I suspect eDave may be the best person to answer, but any feedback is welcome. After upgrading to 17.2 from 16.6, invoking Allegro shows the following error in the console:

E- *Error* loadContext: could not open file - "64bit/AutosilkUtils_public.cxt"

Is there an updated utility for 17.2? Perhaps I'm doing something wrong?

  • Sign in to reply
  • Cancel
Parents
  • EvanShultz
    EvanShultz over 8 years ago
    Thanks Dave!

    Can the new version be used with Allegro 16.x as well as 17.2? Trying it I get the following:
    W- *WARNING* context read failure: can't read 64-bit context on 32-bit platform
    E- *Error* loadContext: context I/O failed - "AutosilkUtils_public.cxt"

    For now I've renamed the older and newer versions of ASU and edited allegro.ilinit to:
    if(axlVersion('version) >= 17 then
    loadContext("AutosilkUtils_public172.cxt")
    else
    loadContext("AutosilkUtils_public166.cxt")
    )
    axlCmdRegister("silkutils" 'ASU_start ?cmdType "interactive")

    While all used to be well with Allegro 16.6 I now get the following when executing ASU (still using the old version of ASU):
    E- File save problem: Not enough storage is available to process this command.
    E- *Error* axlGRPDrwInit: argument #1 should be any user-defined (other) type (type template = "otg") - nil

    Any ideas? I'm on 16.6 S085 so maybe it was broken by a hotfix? It could have also broken since installing 17.2 as that happened since I last used ASU. Not sure...

    Anyway, when launching Allegro 17.2 I see:
    E- *Error* loadContext: could not open file - "64bit/AutosilkUtils_public172.cxt"

    Maybe I'm just tired, but I can't figure out what might be the problem or where to troubleshoot next. I'm on Windows 7 Ultimate x64 with 8GB RAM.

    TIA and we really appreciate all your work!
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • EvanShultz
    EvanShultz over 8 years ago
    Thanks Dave!

    Can the new version be used with Allegro 16.x as well as 17.2? Trying it I get the following:
    W- *WARNING* context read failure: can't read 64-bit context on 32-bit platform
    E- *Error* loadContext: context I/O failed - "AutosilkUtils_public.cxt"

    For now I've renamed the older and newer versions of ASU and edited allegro.ilinit to:
    if(axlVersion('version) >= 17 then
    loadContext("AutosilkUtils_public172.cxt")
    else
    loadContext("AutosilkUtils_public166.cxt")
    )
    axlCmdRegister("silkutils" 'ASU_start ?cmdType "interactive")

    While all used to be well with Allegro 16.6 I now get the following when executing ASU (still using the old version of ASU):
    E- File save problem: Not enough storage is available to process this command.
    E- *Error* axlGRPDrwInit: argument #1 should be any user-defined (other) type (type template = "otg") - nil

    Any ideas? I'm on 16.6 S085 so maybe it was broken by a hotfix? It could have also broken since installing 17.2 as that happened since I last used ASU. Not sure...

    Anyway, when launching Allegro 17.2 I see:
    E- *Error* loadContext: could not open file - "64bit/AutosilkUtils_public172.cxt"

    Maybe I'm just tired, but I can't figure out what might be the problem or where to troubleshoot next. I'm on Windows 7 Ultimate x64 with 8GB RAM.

    TIA and we really appreciate all your work!
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information