Sideload problems

Nice !? .... tested on two PC

{"Name":"APP_AZURE","Capabilities":{"SystemTime":true,"Uart":["ISU0"],"SpiMaster":[],"I2cMaster":[],"Gpio":[],"AllowedConnections":[],"WifiConfig":true},"CmdArgs":[],"EntryPoint":"/bin/app","SchemaVersion":1,"ComponentId":"1640B7FB-4924-46DF-AE72-38998065455B","TargetApplicationRuntimeVersion":2,"TargetBetaApis":"Beta1905"}

azsphere device sideload deploy --imagepackage PATH/app.image --verbose

Azure Sphere Utility version 19.5.4.53731

Start time (UTC): Thursday, 10 October 2019 07:31:03

Deploying 'PATH\app.image' to the attached device.

verbose: No SerialSlipToTunService port is set in the registry; defaulting to 56665.

error: This app targets Beta APIs that may no longer be supported by this device. The app may fail to start or otherwise behave unexpectedly. Please upgrade your app

to target the API sets that this device supports. Use the '--force' flag to force this operation.

error: Command failed in 00:00:02.1843316.

After recover:

Azure Sphere Utility version 19.5.4.53731 ( there is no new versions ) same error

Parents

peterfenn over 5 years ago

Georgi

If your Azure Sphere OS has updated to 19.09, then you also need to install the new 19.09 SDK and rebuild the application.
https://docs.microsoft.com/en-us/azure-sphere/resources/release-notes-1909

In Visual Studio you will need to adjust the target API Set that's used in the build (previous 2+Beta1905 APIs are no longer applicable)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
peterfenn over 5 years ago in reply to peterfenn

More info on this topic is available here:
https://docs.microsoft.com/en-us/azure-sphere/app-development/use-beta#target-api-sets-arv-and-sysroots

PS: Beta APIs can change. Builds with an older SDK that only made use of production APIs are not affected by OS updates
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
peterfenn over 5 years ago in reply to peterfenn

Latest 19.09 SDK reports as follows:

Azure Sphere Utility version 19.9.5.42479
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
peterfenn over 5 years ago in reply to peterfenn

To see the SDK version:
azsphere show-version

To see the OS version:
azsphere device show-ota-status
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
wizio over 5 years ago in reply to peterfenn

I haven't changed anything.
This came as a surprise today...
I find workaround for now: pack image as --sysroot 2 ( but is compiled with Beta1905 ) no errors, work ....
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

wizio over 5 years ago in reply to peterfenn

azsphere show-version                                                                            
19.05                                                                                                
Command completed successfully in 00:00:00.1611137.

BTW: I test on Windows 10, 8 and 7 too

wizio over 5 years ago in reply to peterfenn

so 19.09 not work with Beta1905 ??

$ ./azsphere device show-ota-status                                                                  
Your device is running Azure Sphere OS version 19.09.                                                
The Azure Sphere Security Service is targeting this device with Azure Sphere OS version 19.09.       
Your device has the expected version of the Azure Sphere OS: 19.09.                                  
Command completed successfully in 00:00:04.9280898.

Reply

wizio over 5 years ago in reply to peterfenn

so 19.09 not work with Beta1905 ??

$ ./azsphere device show-ota-status                                                                  
Your device is running Azure Sphere OS version 19.09.                                                
The Azure Sphere Security Service is targeting this device with Azure Sphere OS version 19.09.       
Your device has the expected version of the Azure Sphere OS: 19.09.                                  
Command completed successfully in 00:00:04.9280898.

Children

No Data