> For the complete documentation index, see [llms.txt](https://docs.v-nova.com/technologies/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.v-nova.com/technologies/mpeg-5.lcevc/decoder/ndk/lcevc-decoder-ip-core/lcevc-decoder-ip-core-deliverables.md). # LCEVC Decoder IP Core Deliverables The V-Nova LCEVC Decoder IP package contains the following and can be made available on V-Nova's [Download Portal](https://download.v-nova.com/) upon request: * **RTL source code** ​ * Verilog & System-Verilog code base​ * **Example C control software**​ * Host driver code fully integrated with FFmpeg​ * **Bit accurate executable software reference model**​ * MPEG-5 LCEVC software decoder reference model (with built-in RTL vector generation hooks)​ * **Documentation​**​ * Block and system level specification and architectural descriptions​ * **Simulation test benches** ​ * System Verilog behavioural test benches for RTL and gate-level verification​ * **Integration support** ​ * Basic conformance stream set * Design and development support by V-Nova Integration Services team * Compliance and performance test suite​ (available from V-Nova partners) * On-going technical support​ (optional) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.v-nova.com/technologies/mpeg-5.lcevc/decoder/ndk/lcevc-decoder-ip-core/lcevc-decoder-ip-core-deliverables.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.