It is important to remember that not all USB cables are created equal. When programming, Meadow uses a USB cable supplying both power and data. It is important to use a good quality USB cable to connect your Meadow device to your computer.
Some USB cables are only suitable for charging as they do not contain the D+ and / or D- data lines.
It is important to ensure that you have a USB cable capable of providing data transfer capability and that it is a good quality cable.
Unpowered USB Hub
If you’re having issues communicating with Meadow that is connected via an unpowered USB-Hub, try connecting Meadow directly to a USB port in your machine to ensure the USB-Hub is the issue.
As there are a large variety USB-hubs out there, we cant guarantee Meadow will work properly for all of them.
It is important to ensure that Windows computers have the correct driver installed.
Scott Hanselman has written a good blog post about how to check this and ensure that the correct driver is installed.
Error when flashing Meadow (Windows)
If you’re getting the
Could not find a connected Meadow with the serial number #########, the board might not have the correct Window drivers. To solve this, follow these steps:
- Open Device Manager.
- Under USB Devices right click Meadow F7 Micro.
- Uninstall Devices and click the check box.
- Unplug your Meadow.
- Restart your PC.
- Once PC is restarted, plug in Meadow in bootloader mode.
- Run command
meadow flash os.
- Wait until the line: “Having trouble putting Meadow in DFU Mode, please press RST button on Meadow and press enter to try again” appears.
- Open Zadig and replace the driver.
- Wait for the flash to finish.
Error while updating Meadow after successful DFU Meadow.OS install
While updating the Meadow.OS, you may encounter an error after successfully flashing the OS when your Meadow is rebooted.
Meadow.CLI.Core.Exceptions.DeviceNotFoundException: Could not find a connected Meadow with the serial number
This means that something during the reboot didn’t work correctly. You can work around this by doing another Meadow OS flash but skipping the DFU portion that worked previously.
meadow flash os -d
Deploying from a Virtual Machine
Some users have reported issues deploying to Meadow using a development environment installed on a VM.
At the moment we do not have a solution with this and would welcome any contribution / assistance with this problem.
My Application.exe Does Not Run
At the moment, the default application executed by Meadow is App.exe.
If your application does not execute, please check your project settings and if necessary change your assembly name to App.exe and redeploy your application.
Diagnosing Issues Using Meadow CLI
The Meadow CLI tool can be used to diagnose and fix a number of issues that can appear during the beta phase.
A list of command can be found in the Meadow CLI documentation.
Check Files Deployed to Meadow
meadow file list command to verify that all of the required files have been deployed to Meadow. The list of expected files can be found at the end of the Meadow CLI documentation page.
As noted above, the main application assembly should be App.exe.
Disable Application Execution
meadow mono disable command to stop Meadow from executing the deployed application.
Try to deploy your application using Visual Studio or Visual Studio for Mac.
Delete one or more required files (start with App.exe) using the
meadow file delete -f [Filename] command and try to redeploy your application.
meadow flash erase command will remove all of the files deployed to the flash storage and recreate the file system. It is recommended that you first do a Mono Disable so we ensure a Meadow app is not running.
Deploy Your Application Manually
Firstly, ensure that Mono has automatic execution of the application disabled (see
meadow mono disable).
meadow file write -f [Filename] command to deploy each of the required files to Meadow.
Follow this by checking that the files have been deployed using the
meadow file list command and if everything looks good then re-enable execution of the application using the
meadow mono enable command.
Advanced OS Deployment Troubleshooting
An Advanced OS Deployment Troubleshooting Guide is also available should the above steps not resolve your issue.