This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

VOLIB lib name meaning

Other Parts Discussed in Thread: OMAPL138

i'm using VOLIB, after installation i found many libs for use, like "ecu16_a.a64P", "ecu16_a.a64Pe", "ecu16_c.a64P", "ecu16_cm.a64P", "ecu_a.a64P", what do the prefix and postfix of file name mean ? how to choose the correct lib to use, i'm using omapl138

  • Hi huang jack,

    I'll ask the VOLIB team to help you.

    In the meantime, these extensions are used to know which target hardware the library was built for.

    So ...

    ".a64P" --> library was built for the C64x+ processor

    ".a64Pe" --> same as above but for Big Endian

    Steve

  • Hi Jack,

    The naming convention is generally described in the documentation for each component.  You can find the documentation in the "docs" folder of the root installation directory.  To answer your specific question:

    • You are looking at the Echo Canceller Unit (ECU) component.
    • The ECU has separate libraries for 8k and 16k sampling rate operation.  The 8k libraries have the prefix "ecu" the 16k libraries have the prefix "ecu16".  Note that the 16k libraries are provided as-is and have not undergone extensive testing.
    • The rest of the name, after the underscore, indicates what kind of code the library was generated from "c" means C-code, "a" means optimized assembly code and "cm" means C-model for the optimized assembly code.
    • Only the "c" and "a" libraries should be linked.  The C-model is provided in the case the assembly is not working correctly (though it is not guaranteed to work).
    • The extension always begins with "a" for archive (library)
    • The remaining extension indicates the core for which the code was compiled:  "64P" for C64x+ (little endian), "64Pe" for C64x+ big-endian. "66" for C66x (little endian), etc.

    Please let me know if this clarifies.  If you want further details please reference the documentation.  It should all be there.

    Regards, Charlie

  • thanks, Charlie