When I need technical support, what information should I prepare before contacting processor support?
MuE wrote: When I need technical support, what information should I prepare before contacting processor support?
Before contacting technical support, please first ensure that you have read the appropriate manual, and read the corresponding release notes. If you still require support, please provide as much of the following information as possible:
1. Version Information
Which version of VisualDSP++ is being used? Please open VisualDSP++ and send the HTML file generated via 'Help'->'Product Info'. If you use VisualDSP++ prior to VisualDSP++ 4.5, please send the details found under the 'General', 'Components' and 'Tools' tabs of 'Help'->'About VisualDSP++'. Alternatively, you can contact support from the Support tab.
What kind of license do you have (Full, Evaluation, Test Drive)?
Is the target a simulator, an emulator, or an EZ-Kit?
What is the target processor (21369, BF537, 2181, TS101, etc)? If it is a hardware target, is it a custom board? Is it a multiprocessor board?
If you use an emulator to connect to your target, which emulator are you using (HPUSB, USB, HPPCI, 218x EZ-ICE, etc)?
If you are having problems related to connection to a target 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:
Describe the problem in full, including details of expected and actual behaviour.
Where possible, please provide a Zip file containing a project that demonstrates the problem, along with all files needed to build and run it. Please also send in a step-by-step procedure that will enable us to reproduce the problem.
Generally, we will need a project that demonstrates the problem, but for certain types of problem we will only require a preprocessed version of the problematic source file (yourfile.i). Please send us a preprocessed file if:
A preprocessed file can be created by adding –ED to the command line or, if using the IDDE, by selecting the ‘Generate preprocessed file’ box in the Compile Tab within Project Options. Please also send us the output from compiling your test case with the "-v" option. This can be done by going to "Project Options|Compile" and entering "-v" in the "Additional Options" box. If you have been able to identify the incorrect code sequence in the assembly code, please send us any relevant information.
Note that should confidentiality be an issue, we are happy to sign a Mutual Non Disclosure Agreement.
If the test case produces an executable it may be useful if you send this in also.
Retrieving data ...