Wiki

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
resources:tools-software:sigmastudiov2:support [13 Feb 2023 13:17] – FAQ updated John Josephresources:tools-software:sigmastudiov2:support [23 Oct 2023 13:42] (current) – [Download] Chiranjeevi Palle
Line 20: Line 20:
 \\ \\
 \\ \\
-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: +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 application is not loaded properly. 
-  Target is executing properly. However, SigmaStudio+ is not able to read the status of the target. +  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. +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
 +\\ 
 +{{:resources:tools-software:sigmastudiov2:USBiFirmwareVersionSettings.jpg?400|}}\\ 
 +\\ 
 +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”).  
 +\\ 
 +{{:resources:tools-software:sigmastudiov2:USBiConnection.png?400|}}\\ 
 +\\  
 +  * “SW1” switches should be in off condition on carrier board as shown in the below image. 
 +\\ 
 +{{:resources:tools-software:sigmastudiov2:CarrierBoardSwitchSettings.jpg?400|}}\\ 
 +\\ 
 +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 
 +\\ 
 +{{:resources:tools-software:sigmastudiov2:Custom_App_Host_Settings.jpg?400|}}\\ 
 +\\ 
 +**<fc #ff0000>Note</fc>:** 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.
 \\ \\
 \\  \\ 
resources/tools-software/sigmastudiov2/support.txt · Last modified: 23 Oct 2023 13:42 by Chiranjeevi Palle