Application Deploy Exception

Meadow Development
1

Trying to deploy the template Meadow project app and got error. Log:
1>------ Deploy started: Project: MeadowApplication1, Configuration: Release Any CPU ------
1>[24.11.2020 1:05:02] Deploying to Meadow on COM4…
1>Exception of type ‘MeadowCLI.DeviceManagement.MeadowDeviceManagerException’ was thrown.
========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========

When trying to update Meadow.OS got error:
[24.11.2020 1:16:28] Begin ‘Flash Device’
[24.11.2020 1:16:28] Upload Meadow.OS.bin (~2 mins)
[24.11.2020 1:17:41] Initialize device (~30s)
[24.11.2020 1:17:48] An unexpected error occurred. Please try again.

any suggestions?

2

I get the same error when deploying various sample projects.
I was able to deploy the HelloMeadow sample project successfully without error.
I then tried to deploy the Simon project and received the error below.
Now when I go back and try to deploy the HelloMeadow sample project, I continue to get the MeadowDeviceManagerException error, though the app is deployed and runs successfully.
Tried re-flashing the Meado.OS… didn’t help.

=======================
Deploying to Meadow …
Initializing Meadow
Checking files on device (may take several seconds)
Found Meadow.Foundation.dll
Found App.exe
Found mscorlib.dll
Found Meadow.dll
Found System.dll
Found Mono.Security.dll
Found System.Configuration.dll
Found System.Xml.dll
Found System.Security.dll
Found System.Core.dll
Found System.Numerics.dll
Error: Exception of type ‘MeadowCLI.DeviceManagement.MeadowDeviceManagerException’ was thrown.

3

I am also getting the same issue with no way to fix it, I tried re-flashing the micro and tried following the install directions again and had the same issues

=======================

Deploying to Meadow …
Initializing Meadow
Checking files on device (may take several seconds)
Found Meadow.Foundation.dll
Found App.exe
Found mscorlib.dll
Found Meadow.dll
Found System.dll
Found Mono.Security.dll
Found System.Configuration.dll
Found System.Xml.dll
Found System.Security.dll
Found System.Core.dll
Found System.Numerics.dll
Error: Exception of type ‘MeadowCLI.DeviceManagement.MeadowDeviceManagerException’ was thrown.

4

Hey folks,

I’m sorry to hear you’re having trouble. Can you make sure that your Visual Studio extensions is updated to the latest and also use the Meadow CLI to flash the latest OS to your Meadow?

Let me know if this helps.

-Pete

5

I had similar issues upgrading from 3.10 to 4.4. I updated my VS extension and my CLI at which point I could no longer update my meadow or deploy to it. I used dfu-util to copy over the 4.4 os file and after that I was able to perform the regular download and flash sequence using the latest CLI.

This was the dfu-util command I used (from my firmware directory):

dfu-util -a 0 -S 306735813238 -D Meadow.OS.bin -s 0x08000000 &&
dfu-util -a 0 -S 306735813238 -D Meadow.OS.Runtime.bin -s 0x08040000

1 Like
6

canderson, did you upgrade from 3.10 directly to 4.4? Looking at your solution I assume there was a compatibility issues between the FW on the board and the VS extension?

7

I am seeing the same problem when deploying the sample application.

I just ran through the Getting Started Guide so I assume I have the latest of everything.

I’m developing under a VM (Latest VMWare with Windows 10).

Note I get the same exception thrown when run meadow --MonoEnable during the setup guide.

Any suggestions?

EDIT: I use USB-C adapter to connect it to my Mac.
EDIT2: I tried on my Windows laptop and getting the same error.

8

I also have this error now.

A week ago I was able to successfully complete the update and also provide a program again.
Now I wanted to continue actually and also encountered the exception error as described here in the beginning.

What have I changed? The connection with the industrial interface I²C. Also from the template whose test application can not be provided.

The exception ‘MeadowCLI.DeviceManagement.MeadowDeviceManagerException’ always comes when the Meadow is restarted. That’s all I’ve noticed so far.

9

Hi.

I am getting the same exception:

Build started…
1>------ Deploy started: Project: HelloMeadowF7v2, Configuration: Debug Any CPU ------
1>[11/04/2021 20:47:08] Deploying to Meadow on COM3…
1>[11/04/2021 20:47:13] /meadow0/App.exe [0xa25cbe71] 8 KB (6144 bytes) (00:00:04.8457253 since last.)
1>[11/04/2021 20:47:14] /meadow0/mscorlib.dll [0x16bb8459] 4532 KB (4639232 bytes) (00:00:01.3144889 since last.)
1>[11/04/2021 20:47:14] /meadow0/Meadow.dll [0x0e39b4cb] 232 KB (236544 bytes) (00:00:00.0602160 since last.)
1>[11/04/2021 20:47:15] /meadow0/System.dll [0x9fd26f51] 2608 KB (2667008 bytes) (00:00:00.6900783 since last.)
1>[11/04/2021 20:47:15] /meadow0/Mono.Security.dll [0xa46c1abb] 236 KB (240128 bytes) (00:00:00.0609552 since last.)
1>[11/04/2021 20:47:15] /meadow0/System.Configuration.dll [0x7f3a61f3] 120 KB (122880 bytes) (00:00:00.0001676 since last.)
1>[11/04/2021 20:47:16] /meadow0/System.Xml.dll [0x78e21391] 3100 KB (3174400 bytes) (00:00:00.7479856 since last.)
1>[11/04/2021 20:47:16] /meadow0/System.Security.dll [0xe56b8f6a] 304 KB (308224 bytes) (00:00:00.1250804 since last.)
1>[11/04/2021 20:47:16] /meadow0/System.Core.dll [0x0e2ff108] 1064 KB (1086976 bytes) (00:00:00.2488002 since last.)
1>[11/04/2021 20:47:16] /meadow0/System.Numerics.dll [0xac5d36b9] 120 KB (119808 bytes) (00:00:00.0000787 since last.)
1>[11/04/2021 20:47:16] /meadow0/Meadow.Foundation.dll [0xebfd9e8b] 92 KB (92160 bytes) (00:00:00.0629533 since last.)
1>[11/04/2021 20:47:16] A total of 11 files using 12416 KB (12693504 bytes) (00:00:00.0000413 since last.)
1>[11/04/2021 20:47:16] Meadow file download of ‘App.exe’ has begun (00:00:00.1721537 since last.)
1>[11/04/2021 20:47:16] File 16% downloaded (00:00:00.0615915 since last.)
1>[11/04/2021 20:47:16] File 25% downloaded (00:00:00.0001105 since last.)
1>[11/04/2021 20:47:16] File 33% downloaded (00:00:00.0000442 since last.)
1>[11/04/2021 20:47:16] File 41% downloaded (00:00:00.0000278 since last.)
1>[11/04/2021 20:47:16] File 50% downloaded (00:00:00.0000683 since last.)
1>[11/04/2021 20:47:16] File 66% downloaded (00:00:00.0000494 since last.)
1>[11/04/2021 20:47:16] File 75% downloaded (00:00:00.0654336 since last.)
1>[11/04/2021 20:47:16] File 83% downloaded (00:00:00.0001776 since last.)
1>[11/04/2021 20:47:16] File 91% downloaded (00:00:00.0002740 since last.)
1>[11/04/2021 20:47:17] Download of ‘App.exe’ success (checksums calc:0x0A44694D, expected:0x0A44694D) (00:00:00.3086980 since last.)
1>Exception of type ‘MeadowCLI.DeviceManagement.MeadowDeviceManagerException’ was thrown.
========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========

It was working, but something went wrong, and now I am stock and I cannot get it to work again.

I believe everything is fully update.

Best regards,
Kristian.

10

Just adding my voice to the chorus. Seeing the same thing here too - after installing what I believe to be the latest beta4 build/tooling

PS C:\Users\h3tec> meadow --version
Meadow.CLI 0.12.3
PS C:\Users\h3tec> meadow --GetDeviceInfo
Opening port 'COM5'
Data: Meadow will not start MONO because it didn't run correctly last time
Data: Mono enabled, will run app.exe
ID: Meadow by Wilderness Labs, Model: F7Micro, MeadowOS Version: 0.4.6.2 (Mar 24 2021 10:49:52), Processor: STM32F777IIK6, Processor Id: 22-00-1e-00-0d-51-38-32-37-35-36-30, Serial Number: 305435633238, CoProcessor: ESP32, CoProcessor OS Version: 0.4.6.2, Mono Version: 0.0.0.1, Device Name: MeadowF7
ID: Meadow by Wilderness Labs, Model: F7Micro, MeadowOS Version: 0.4.6.2 (Mar 24 2021 10:49:52), Processor: STM32F777IIK6, Processor Id: 22-00-1e-00-0d-51-38-32-37-35-36-30, Serial Number: 305435633238, CoProcessor: ESP32, CoProcessor OS Version: 0.4.6.2, Mono Version: 0.0.0.1, Device Name: MeadowF7
11

Update - got some action from this thread here but still nibbling around the edges.

I’m genuinely curious why there’s a special step to update Mono - and why that’s also not documented in a way that says “oh hey - when you update to use the latest beta you need to these steps…” that includes running “meadow --UpdateMonoRt”

Did I miss a memo?

12

The latest CLI has rolled all the updates into 1 command, meadow flash os so you shouldn’t have to worry about mismatched versions anymore.