Community

Meadow board will not run app.exe

I’m stuck, I have 2 Meadow boards (that I just received a few days ago, and this is my first experience with Meadow) and both boards will not run app.exe using the HelloMeadow Example and OS 0.4.2

I feel like everything is set up correctly. However, I must be missing something.

The following is the Build info…

1>------ Build started: Project: HelloMeadow, Configuration: Debug Any CPU ------
1>HelloMeadow -> C:\Users\Work\source\repos\HelloMeadow\HelloMeadow\bin\Debug\net472\App.exe
2>------ Deploy started: Project: HelloMeadow, Configuration: Debug Any CPU ------
2>[12/16/2020 5:41:07 AM] Deploying to Meadow on COM10…
2>[12/16/2020 5:41:15 AM] Checking files on device (may take several seconds) (00:00:07.8208337 since last.)
2>[12/16/2020 5:41:24 AM] Found App.exe (00:00:09.6133008 since last.)
2>[12/16/2020 5:41:24 AM] Found mscorlib.dll (00:00:00.0000076 since last.)
2>[12/16/2020 5:41:24 AM] Found Meadow.dll (00:00:00.0000040 since last.)
2>[12/16/2020 5:41:24 AM] Found System.dll (00:00:00.0000024 since last.)
2>[12/16/2020 5:41:24 AM] Found Mono.Security.dll (00:00:00.0000022 since last.)
2>[12/16/2020 5:41:24 AM] Found System.Configuration.dll (00:00:00.0000022 since last.)
2>[12/16/2020 5:41:24 AM] Found System.Xml.dll (00:00:00.0000025 since last.)
2>[12/16/2020 5:41:24 AM] Found System.Security.dll (00:00:00.0000022 since last.)
2>[12/16/2020 5:41:24 AM] Found System.Core.dll (00:00:00.0000021 since last.)
2>[12/16/2020 5:41:24 AM] Found System.Numerics.dll (00:00:00.0000076 since last.)
2>[12/16/2020 5:41:24 AM] Found Meadow.Foundation.dll (00:00:00.0000027 since last.)
2>[12/16/2020 5:41:24 AM] Writing App.exe (00:00:00.0668967 since last.)
2>[12/16/2020 5:41:28 AM] Deployment Duration: 00:00:20.9404833 (00:00:03.4371874 since last.)
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========

Launching application…

…Nothing happens on the board

When I close VS2019 for Windows and open PuTTY on the COM Port this is what is there

!Meadow successfully started MONOMono enabled, will run app.exe

When I open a Command Prompt and List Files, this is the Error I get.

C:\Users\Work>meadow --ListFiles
Opening port ‘COM10’
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.2 (Dec 8 2020 10:09:54), Processor: STM32F777IIK6, Processor Id: 2c-00-37-00-0d-51-38-32-37-35-36-30,Serial Number: 306D356D3238, CoProcessor: ESP32, CoProcessor OS Version: 0.4.2.0
Getting list of files
File List:
/meadow0/App.exe
/meadow0/mscorlib.dll
/meadow0/Meadow.dll
/meadow0/System.dll
/meadow0/Mono.Security.dll
/meadow0/System.Configuration.dll
/meadow0/System.Xml.dll
/meadow0/System.Security.dll
/meadow0/System.Core.dll
/meadow0/System.Numerics.dll
/meadow0/Meadow.Foundation.dll
A total of 11 files found

Any thoughts on what I’m missing?

Thanks, Paul

Hi,
I am also new but here a few things you can try.
From the command line:

  • meadow --SetTraceLevel --TraceLevel 3 sets the debug output level to output everything
  • meadow --TraceEnable enable the debug output
  • meadow --MonoEnable run the application
    The check if you can find when trying to run it.
    For easy reading you can put output here between ``` which makes it easier to read.

Regards,
Daniel

You could also try meadow --MonoEnable --KeepAlive which will keep the connection open after starting.

Thank you so much for your help. I was able to track it down to this Error:

Trace: [ 0.103000] (Note) mono/hcom_mono_control.c@161-Attempting to start mono
Trace: [ 0.103000] (Info) mono/hcom_mono_control.c@175-MONO launched [pid:8, pri:100, stack size:65536]
Trace: [ 0.103000] Mono runtime was not found flashed in external flash.

Solution was:
meadow --MonoUpdateRt

Both boards were missing the Mono Runtime.
Now both boards are running app.exe

Once again, Thank you so much for your help.
Paul

1 Like

Your welcome! Good to hear that you found it.

Regards,
Daniel

I had exactly this situation, where the HelloMeadow application would build and deploy to the device seemingly OK, but do nothing.

In my too-fast read of the instructions, I skipped all the meadow steps described in steps 3 and 4 of the Flash Meadow.OS and Coprocessor Firmware section. I mistook them for being part of the immediately preceding Linux-only steps.

Once I went back and executed these steps, the application worked as it was supposed to.

1 Like

I too am unable to get the HelloWorld app to run… followed all the steps… can see COM5 in Device Mgr, Deploy appears to be working correctly. But after a deploy… nothing.
Every time I issue a meadow cli command, I get the same response: Opening port ‘5’

When I try to list files in Meadow (meadow --ListFiles) same response (Opening port ‘5’). Makes me wonder… am I supposed to get a different response?

Yes, you should get a different response.

When I run meadow --List Files, I get:
“Opening port ‘COM8’
Getting list of files
Data: Meadow successfully started MONO
Data: Mono enabled, will run app.exe
App: Initialize hardware…
App: Cycle colors…
File List:
/meadow0/App.exe
/meadow0/mscorlib.dll
/meadow0/Meadow.dll
/meadow0/System.dll
/meadow0/Mono.Security.dll
/meadow0/System.Configuration.dll
/meadow0/System.Xml.dll
/meadow0/System.Security.dll
/meadow0/System.Core.dll
/meadow0/System.Numerics.dll
/meadow0/Meadow.Foundation.dll
/meadow0/Meadow.OS.Runtime.bin
A total of 12 files found”

So, I don’t think you are communicating with your board.

What tripped me up was missing steps 3 and 4 in section Step 3: Flash Meadow.OS and Coprocessor Firmware. I mistook those as being only for Linux.

Once I successfully completed all the meadow commands in those two steps, I gained control of the board.

1 Like

@robert.chiverton, it sounds like the COM port was not specified correctly, can you try meadow -s COM5 --ListFiles and let me know if that works?

Peter… using -s COM5 fixed it!
May I suggest an update to the “Getting Started” instructions? For Windows Users… update the instructions to use the COM5 name explicitly.

Current Instructions:
meadow --MonoDisable
meadow --MonoUpdateRt
meadow --FlashEsp
meadow --MonoEnable

Updated Instructions:
meadow -s COM5 --MonoDisable
meadow -s COM5 --MonoUpdateRt
meadow -s COM5 --FlashEsp
meadow -s COM5 --MonoEnable

FYI, Don’t get hung up on COM5. I have a Windows 10 machine and 2 meadow boards. One board shows up on COM9 and the other shows up on COM12. Also, once you have run a command like: meadow -s COM9 All further meadow commands will be sent to COM9, you don’t have to keep re-specifying the com port with each command.

Ok… COMx then… It would’ve saved me hours if this was in the instructions:

Note: Once you have run a command like: “meadow -s COM9”, all further meadow commands will be sent to COM9, and you don’t have to keep re-specifying the com port with each command.