We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nanoFramework area: (Visual Studio extension)
VS version:
VS extension version: 1.0.3.81
Target:
Firmware image version:
Device capabilities output:
Worked before? If so, with which nanoFramework image version:
Deploy attached solution
output window
2019-03-18 22:36:17Z [Check and start debug engine on nanoDevice.] 2019-03-18 22:36:17Z [Connect successful.] 2019-03-18 22:36:18Z [Erase deployment area successful.] 2019-03-18 22:36:18Z [Request full reboot of nanoDevice.] 2019-03-18 22:36:29Z [Computing deployment blob.] 2019-03-18 22:36:30Z [Deploying assemblies.] 2019-03-18 22:36:37Z [Deploying assemblies. Second attempt.] 2019-03-18 22:36:46Z [Deployment failed.] 2019-03-18 22:36:46Z [Exception occurred during deployment. Deploy failed. at nanoFramework.Tools.VisualStudio.Extension.DeployProvider.<DeployAsync>d__17.MoveNext()] 2019-03-18 22:36:46Z [Incrementally deploying assemblies to the device] 2019-03-18 22:36:46Z [Error writing to device memory @ 0x00110000 (59076 bytes). Error code: 0.] 2019-03-18 22:36:46Z [Error deploying assemblies to the device.]
...
NfSpiTest.zip
The text was updated successfully, but these errors were encountered:
josesimoes
No branches or pull requests
Details about Problem
nanoFramework area: (Visual Studio extension)
VS version:
VS extension version: 1.0.3.81
Target:
Firmware image version:
Device capabilities output:
Worked before? If so, with which nanoFramework image version:
Detailed repro steps so we can see the same problem
Deploy attached solution
output window
...
Other suggested things
Sample Project (if applicable)
NfSpiTest.zip
The text was updated successfully, but these errors were encountered: