Guidelines for Posting VisualDSP++ Development Tools Issues by CraigG
This document provides guidelines on the type of information the Support team requires in order to reproduce and investigate reported issues. Please post all information that may be relevant to the issue you are reporting.
Information which may be required for all issues:
Describe the problem in full, including details of expected and actual behaviour.
2. Test Case
If appropriate, please make a project that demonstrates the problem available to us, along with all files needed to build and run it. Please also give us a step-by-step procedure that will enable us to reproduce the problem.
If the test case produces an executable it may be useful if you make this available to us also.
NOTE: If you need to make your code or executables available to us, and do not wish to do so on the public forum, please submit a support request at: www.analog.com/support, along with a link to your thread, if applicable.
Should confidentiality be an issue, we are happy to arrange a Non-Disclosure Agreement.
4. ADI Software Version Information
Please give us full version details of any ADI Software you are using, such as VisualDSP++, Software Modules, SDK, SigmaStudio, etc.
Please connect to the relevant session and go to Help->Product Info, save the resulting page as a file and attach to your email. This also generates a file at:
[Win XP] C:\Documents and Settings\<username>\My Documents\VisualDSP Projects\ProductInfo.html
[Win 7] C:\Users\<username>\Documents\ProductInfo.html
Note: Your Product Info will contain your license serial numbers in the <div class="licenseinfo"> section. Please remove the serial numbers before posting.
5. Target processor
What is the target processor (ADSP-21369, ADSP-BF537, ADSP-2181, ADSP-TS101, etc)? What is the silicon revision of the target processor?
Is the target a simulator, emulator, or EZ-Kit session?
Please specify whether you are using a runtime operating system or not. If you are, which operating system are you using and which version?
Additional information which may be required if you are reporting a problem with the VisualDSP++ Development Tools:
What kind of license do you have? Full (ADI), Evaluation (KIT), Test Drive (TST)?
Please do NOT post your license serial number or your license.dat file to the forum. If we require either of these things we will open a private support ticket for your issue.
9. EZ-KIT Information
If you are using an EZ-KIT Lite or EZ-Board, please provide the PCB version number (printed on the PCB) the BOM number (on a sticker on the under-side of the board), and the silicon revision (printed on the processor).
If you are using a Debug Agent Board together with an EZ-BOARD, please let us know whether you use an ADZS-DBGAGENT-BRD or an ADZS-SADA2, together with the PCB version number (printed on the PCB) the BOM number (on a sticker on the under-side of the board).
If the target is an emulator, which emulator are you using (HPUSB, USB, HPPCI, 218x EZ-ICE, etc)? What is the serial number of the emulator (on a sticker on the back of the pod)?
If you are encountering a connection issue related to your emulator, please read EE-175, our ‘Emulator Troubleshooting Guide’, and after following its guidelines let us know the results. This EE Note can be downloaded from:
Emulator Trouble Shooting Guide
11. If your issue relates to the VisualDSP++ Compiler
Generally, we need a project that demonstrates the problem, but for certain types of problem we only require a preprocessed version of the problematic source file (yourfile.i).
We need a preprocessed file if:
A preprocessed file can be created by adding –ED to the command line or, if using VisualDSP++ this can be enabled by selecting the ‘Generate preprocessed file’ box in the Compiler options, via:
Project: Project Options: Compile: General: Generate Preprocessed File
Please also send us the output from compiling your test case with the "-v" option. If using VisualDSP++ this can be done by entering a "-v" in the "Additional Options" box in the Compiler Options. If you have been able to identify the incorrect code sequence in the assembly code, please send us any relevant information.