Wiki

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
resources:tools-software:sigmastudiov2:support [10 Feb 2021 14:33]
John Joseph FAQ added
resources:tools-software:sigmastudiov2:support [13 Feb 2023 13:17]
John Joseph FAQ updated
Line 1: Line 1:
 [[resources:​tools-software:​sigmastudiov2|Return to the parent page]] [[resources:​tools-software:​sigmastudiov2|Return to the parent page]]
  
-======Support======+======Support ​and FAQ======
 If you have a technical problem and you can't find a solution, you can contact for Technical Support by email: **ssplus_support@analog.com** ​ If you have a technical problem and you can't find a solution, you can contact for Technical Support by email: **ssplus_support@analog.com** ​
 \\ \\
 \\ \\
 =====FAQ===== =====FAQ=====
 +\\
 ====Communication==== ====Communication====
 \\ \\
Line 12: Line 13:
 \\ \\
 A: When USBi is used as the communication device, the "​FirmwareVersion"​ property of the USBi in SigmaStudio+ project should be set based on the version of the hardware. "​FirmwareVersion"​ should be set as "​v1.5"​ when the version of the USBi board is 1.5 or later and "Pre v1.5" should be used for 1.4 or earlier versions. This property can be updated using the SigmaStudio+ Property Window. Failure to set the proper version number can affect the readback operation. ​   A: When USBi is used as the communication device, the "​FirmwareVersion"​ property of the USBi in SigmaStudio+ project should be set based on the version of the hardware. "​FirmwareVersion"​ should be set as "​v1.5"​ when the version of the USBi board is 1.5 or later and "Pre v1.5" should be used for 1.4 or earlier versions. This property can be updated using the SigmaStudio+ Property Window. Failure to set the proper version number can affect the readback operation. ​  
 +\\
 +\\
 +====Download====
 +\\
 +**Q: Why does SigmaStudio+ throw "​Target execution could not be verified"​ error while downloading a project, even though my target is active?**
 +\\
 +\\
 +A: "​Target execution could not be verified"​ indicates that SigmaStudio+ could not verify that the code has been downloaded on to the target and the target is running. This can happen primarily due to two reasons:
 +  - Target application is not loaded properly.
 +  - Target is executing properly. However, SigmaStudio+ is not able to read the status of the target.
 +When USBi is used as the communication device, the "​FirmwareVersion"​ property of the USBi in SigmaStudio+ project should be set based on the version of the hardware. "​FirmwareVersion"​ should be set as "​v1.5"​ when the version of the USBi board is 1.5 or later and "Pre v1.5" should be used for 1.4 or earlier versions. This property can be updated using the SigmaStudio+ Property Window. Failure to set the proper version number can affect the readback operation and target verification. ​
 +\\
 +\\ 
 +====Platform====
 +\\
 +**Q: Project download on to ADSP-21489 fails when the target application is loaded from serial (SPI) flash. What is the reason?**
 +\\
 +\\
 +A: On ADSP-21489, SPI Flash and USBi shares the same SPI lines. As a result, the SPI boot fails when USBi is connected.
 +  * When SPI boot fails, LED 1-8 will be ON
 +  * When SPI boot succeeds, LED 1 will be ON. LED 2-8 will be OFF.
 +Workaround is to disconnect the USBi, reset the board (then successful boot happens and LED1 will be ON). Now connect the USBi and download the project from SigmaStudio+. Upon successful download, you will find LED 1-4 ON.
 +   
 + 
resources/tools-software/sigmastudiov2/support.txt · Last modified: 13 Feb 2023 13:17 by John Joseph