Generating the LVM File (Microprocessor SDK)
Complete the following steps to generate the LVM file, which is generated during the build process into the directory you specify in EMB_Debug_DD_Save.vi.
- Call EMB_Debug_DD_Init.vi to initialize the debug database and erase records from any previous builds.
- Call EMB_Debug_DD_ParseCFile.vi for every generated C file. This VI performs the following:
- Opens the generated C file.
- Parses the C file for OCDI comments.
- Inserts breakpoint, signal, and control records into the debug database.
- Resolve breakpoint addresses and symbols. For all breakpoints, call EMB_Debug_DD_GetBP.vi in a loop to map the breakpoint line numbers into absolute target addresses. Call EMB_Debug_DD_SetAbsoluteBP_Address.vi to update the absolute address of each breakpoint record.
- Resolve memory records. For all memory records, call EMB_Debug_DD_GetMem.vi in a loop to map the memory line numbers into absolute target addresses. Call EMB_Debug_DD_SetAbsoluteMemAddress.vi to update the absolute address of each memory record.
Note You must resolve all breakpoints, symbols, and memory records when an embedded VI is built into an embedded application. Resolving is the most complicated part of generating the LVM file because it involves integration with your third-party resolver that can parse the built application and resolve all memory symbols and map breakpoint line numbers to absolute target addresses. - Use EMB_Debug_DD_GetSetAttrib_Numeric.vi and EMB_Debug_DD_GetSetAttrib_Numeric_Pair.vi to set all of the attributes in the [Offset_Table] section.
Note You must set all attributes in the [Offset_Table] section to ensure the LabVIEW debugger correctly dereferences the pointers. - Call EMB_Debug_DD_Save.vi to save the debug database to the LVM file.