Wiki

This version (26 Oct 2023 11:22) was approved by Sakthivel Perumal.The Previously approved version (13 Feb 2023 13:17) is available.Diff

Return to the parent page

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

FAQ


Communication


Q: Why does the readback from target fails even though the download is successful and there is audio playback?

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 below 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.


If we are using SOM-Carrier board, below settings should be configured properly.

  • Please check whether the USBi connection is as per the below image which is connected to carrier board (brown

color wire should be connected near the Starting letter of SigmaStudio “S”).


  • “SW1” switches should be in off condition on carrier board as shown in the below image.




For custom applications, please uncheck the target verification option in the Settings window of SigmaStudioPlus (Tools menu ⇒ Settings button ⇒ Processor Group ⇒ uncheck Target Verification checkbox) as shown in the below image


Note: Even after confirming the above-mentioned configuration, If we are still facing an issue, please select the arm core and suspend all the cores in CrossCore Embededd Studio and check the status if any target exception is showing in the console window.

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: 23 Oct 2023 13:42 by Chiranjeevi Palle