Meadow core

Did you know that since Meadow.OS v1.6, you can use the Direct Memory Access (DMA) feature on the F7 to do Analog to Digital Conversions (ADC) at an incredibly high sampling rate? While the AnalogInputPort provides a powerful way to do analog port reads…

As modern .NET developers, we’re gotten used to seeing and using Tasks in our code. They do a great job of abstracting away the complexity and dangers of old school multi-threaded code. If you’ve got experience creating complex threaded applications using Threads you definitely…

In an earlier blog I talked about why Meadow apps on the F7 (i.e. our Feather and Core Compute based products) are always named “App.dll”, but if you’re running Meadow on Linux or Windows, that explanation makes things a bit muddy. In this deep…

Simply running your application is usually the primary focus of an IoT solution, but how do you know if it’s running well? How do you track if the app is crashing and the device is rebooting? How do you know what devices in the…

It wasn’t too long ago that the release process for the Meadow stack was…let’s just call it horribly inefficient. From when we decided “time to ship a build” to when NuGets were available was literally measured in days. It was a process that we…

If you work directly with a Meadow F7 Feather or a Meadow Core Compute Module, accessing the hardware signals from your application is pretty simple and straightforward. The Meadow.Core stack exposes the Device.Pins collection so creating something as simple as an IDigitalOutputPort is pretty…

The Meadow Core stack has a hard-coded requirement for Meadow Apps on the F7 platform to be named either “App.dll” or “App.exe”. This requirement is actually a bit of a legacy carryover from the beta days. Originally, when the Meadow stack only targeted the…