Community

Stalled on "Loading Application..."

I am attempting to run the HelloMeadow project (right from the Template) on a new Meadow device, but the first Deployment I get the following error, then following deployments get stuck on “Loading Application…”. I can’t find any errors or logs. All the latest versions of everything used (VS, Meadow, Nuget, etc) have been loaded.

2>------ Deploy started: Project: HelloMeadow, Configuration: Release Any CPU ------
2>[12/22/2020 4:26:00 PM] Deploying to Meadow on COM4…
2>[12/22/2020 4:26:08 PM] Checking files on device (may take several seconds) (00:00:07.9610759 since last.)
2>[12/22/2020 4:26:18 PM] Found App.exe (00:00:09.6365277 since last.)
2>[12/22/2020 4:26:18 PM] Found mscorlib.dll (00:00:00.0000501 since last.)
2>[12/22/2020 4:26:18 PM] Found Meadow.dll (00:00:00.0000370 since last.)
2>[12/22/2020 4:26:18 PM] Found System.dll (00:00:00.0000197 since last.)
2>[12/22/2020 4:26:18 PM] Found Mono.Security.dll (00:00:00.0000347 since last.)
2>[12/22/2020 4:26:18 PM] Found System.Configuration.dll (00:00:00.0000275 since last.)
2>[12/22/2020 4:26:18 PM] Found System.Xml.dll (00:00:00.0000230 since last.)
2>[12/22/2020 4:26:18 PM] Found System.Security.dll (00:00:00.0000202 since last.)
2>[12/22/2020 4:26:18 PM] Found System.Core.dll (00:00:00.0000154 since last.)
2>[12/22/2020 4:26:18 PM] Found System.Numerics.dll (00:00:00.0000197 since last.)
2>[12/22/2020 4:26:18 PM] Found Meadow.Foundation.dll (00:00:00.0000192 since last.)
2>Exception of type ‘MeadowCLI.DeviceManagement.MeadowDeviceManagerException’ was thrown.

I followed the Trace steps in another thread and here is the output for MonoEnable

C:\WINDOWS\system32>meadow --MonoEnable
Opening port ‘COM4’
ID: Meadow by Wilderness Labs, Model: F7Micro, MeadowOS Version: 0.4.2 (Dec 8 2020 10:09:54), Processor: STM32F777IIK6, Processor Id: 19-00-2a-00-0d-51-38-32-37-35-36-30,Serial Number: 3060355A3238, CoProcessor: ESP32, CoProcessor OS Version: 0.4.2.0
Trace: [ 272.504000] (Debug) comms/hcom_host_parse.c@127-15 bytes added to cir buf
Trace: [ 272.504000] (Debug) comms/hcom_host_parse.c@228-Non-data seq:0, len:12
Trace: [ 272.504000] (Debug) -->Received non-data cmd. 0 bytes in header. RqstType:0x0112
Data: Mono has been enabled. Restarting F7 Micro
Trace: [ 0.082000] hcom_nx/create_fs/hcom_nx_fs.c@233-Mounted partition 0 as ‘/dev/little0p0’ to ‘/meadow0’ for type ‘littlefs’
Data: Meadow successfully started MONO
Trace: [ 0.083000] F/S creation complete
Trace: [ 0.083000] +hcom_nx_upd_initialize
Trace: [ 0.085000] (Debug) inicfg/meadow_inicfg.c@304-Config file:/meadow0/meadow.cfg could not be opened
Data: Mono enabled, will run app.exe
Trace: [ 0.085000] (Error) inicfg/meadow_inicfg.c@164-‘Config file:/meadow0/meadow.cfg could not be opened’-file:(null), section:startup, key:tracelevel, errno:2
Trace: [ 0.087000] (Debug) inicfg/meadow_inicfg.c@304-Config file:/meadow0/meadow.cfg could not be opened
Trace: [ 0.087000] (Error) inicfg/meadow_inicfg.c@136-‘Config file:/meadow0/meadow.cfg could not be opened’-file:(null), section:startup, key:monorun, errno:2
Trace: [ 0.088000] (Note) Meadow 0.4.2 (Dec 8 2020@10:09:51) rebooted, Mono:Enabled, Trace level:0xff, to:Host, type:ramlog
Trace: [ 0.090000] (Debug) inicfg/meadow_inicfg.c@304-Config file:/meadow0/meadow.cfg could not be opened
Trace: [ 0.090000] (Error) inicfg/meadow_inicfg.c@136-‘Config file:/meadow0/meadow.cfg could not be opened’-file:(null), section:startup, key:uart1, errno:2
Trace: [ 0.093000] (Debug) comms/hcom_host_receive.c@243-usb open read /dev/ttyACM0
Trace: [ 0.095000] (Debug) inicfg/meadow_inicfg.c@304-Config file:/meadow0/meadow.cfg could not be opened
Trace: [ 0.096000] (Error) inicfg/meadow_inicfg.c@136-‘Config file:/meadow0/meadow.cfg could not be opened’-file:(null), section:startup, key:monorun, errno:2
Trace: [ 0.105000] (Debug) inicfg/meadow_inicfg.c@304-Config file:/meadow0/meadow.cfg could not be opened
Trace: [ 0.105000] (Error) inicfg/meadow_inicfg.c@164-‘Config file:/meadow0/meadow.cfg could not be opened’-file:(null), section:startup, key:ResetEsp32AtStartup, errno:2
Trace: [ 0.106000] espcp/espcp_thread.c@154 Waiting for ESP initialisation to complete.
Trace: [ 0.108000] (Note) mono/hcom_mono_control.c@161-Attempting to start mono
Trace: [ 0.108000] (Info) mono/hcom_mono_control.c@175-MONO launched [pid:8, pri:100, stack size:65536]
Trace: [ 0.108000] Mono runtime was not found flashed in external flash.
Trace: [ 0.345000] (Debug) comms/hcom_host_receive.c@268-/dev/ttyACM0 ready for host comms
Trace: [ 0.444000] (Debug) inicfg/meadow_inicfg.c@304-Config file:/meadow0/meadow.cfg could not be opened
Trace: [ 0.444000] (Error) inicfg/meadow_inicfg.c@136-‘Config file:/meadow0/meadow.cfg could not be opened’-file:(null), section:startup, key:monorun, errno:16
Trace: [ 0.601000] (Debug) comms/hcom_host_receive.c@279-Waiting for ‘/dev/ttyACM0’ message
Trace: [ 272.572000] (Debug) comms/hcom_host_parse.c@127-15 bytes added to cir buf
Trace: [ 272.572000] (Debug) comms/hcom_host_parse.c@228-Non-data seq:0, len:12
Trace: [ 272.572000] (Debug) -->Received non-data cmd. 0 bytes in header. RqstType:0x0110

Guessing it has something to do with the missing config file. Any clues or insight would help.

I was told that it goes back to default settings if no config is found. Can you do one more run with meadow --MonoEnable --KeepAlive?

I tried, but the same result. I ended up flashing everything and running the Step 4 in the Max directions:

meadow --MonoUpdateRt
meadow --FlashEsp
meadow --MonoEnable

And I was able to get it deployed. Cheers for reaching out.