You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Add M5Stack FIRE
* Adjusting naming
* Adding fire and updating nugets
* adjusting buzzer version and adding gitversioning
* fixing fire nuget again
* nit
* m5core nuspec
* adjusting for sonar cloud
@@ -137,13 +140,13 @@ nanoFramework.Console.Write("This is white on black again and on 9th line");
137
140
138
141
> Note: You can change the default font as well, you need to provide it as a property. The Cursor positions are calculated with the largest possible character.
139
142
140
-
M5Core2 has SPRAM, so you can get a full screen buffer as well. Refer to the [Graphics samples](https://github.com/nanoframework/Samples#graphics-for-screens) to understand all you can do with it.
143
+
M5Core2 and Fire have SPRAM, so you can get a full screen buffer as well. Refer to the [Graphics samples](https://github.com/nanoframework/Samples#graphics-for-screens) to understand all you can do with it.
141
144
142
145
### Buttons
143
146
144
147
The main buttons except the power buttons are exposed.
145
148
146
-
On the M5Stack they are called `ButtonLeft`, `ButtonCenter` and `ButtonRight`. You can get access to the events as well. For example:
149
+
On the M5Stack and Fire they are called `ButtonLeft`, `ButtonCenter` and `ButtonRight`. You can get access to the events as well. For example:
147
150
148
151
```csharp
149
152
M5Stack.ButtonLeft.Press+= (sender, e) =>
@@ -272,7 +275,7 @@ The `TouchEventCategory` enum is a flag and can combine buttons and states. The
272
275
273
276
The M5Core and M5StickC/CPlus are exposing their power management elements. It is not recommended to change any default value except if you know what you are doing.
274
277
275
-
Please refer to the detailed examples for the [AXP192](https://github.com/nanoframework/nanoFramework.IoT.Device/blob/develop/devices/Axp192/README.md) used in the M5StickC/CPlus; M5Core2 and [IP5306](https://github.com/nanoframework/nanoFramework.IoT.Device/blob/develop/devices/Ip5306/README.md) for the M5Core.
278
+
Please refer to the detailed examples for the [AXP192](https://github.com/nanoframework/nanoFramework.IoT.Device/blob/develop/devices/Axp192/README.md) used in the M5StickC/CPlus; M5Core2 and [IP5306](https://github.com/nanoframework/nanoFramework.IoT.Device/blob/develop/devices/Ip5306/README.md) for the M5Core and Fire.
276
279
277
280
### Accelerometer and Gyroscope
278
281
@@ -322,7 +325,7 @@ Refer to the [SerialPort documentation](https://github.com/nanoframework/System.
322
325
323
326
### ADC Channels
324
327
325
-
ADC Channels are pre setup on the M5Core, M5Core2 and Atom Lite/Matrix, access them like this:
328
+
ADC Channels are pre setup on the M5Core, M5Core2, Fire and Atom Lite/Matrix, access them like this:
326
329
327
330
```csharp
328
331
// This will give you the ADC1 channel 7 which is on pin 35 of M5Core
Similar as previously, you can get the `GpioController` on any of the M5Core, M5Core2 and M5StickC/CPlus:
358
+
Similar as previously, you can get the `GpioController` on any of the M5Core, M5Core2, Fire and M5StickC/CPlus:
356
359
357
360
```csharp
358
361
// This will open the GPIO 36 as output
@@ -361,7 +364,7 @@ var pin5 = M5StickC.GpioController.OpenPin(36, PinMode.Output);
361
364
362
365
### DAC
363
366
364
-
The M5Core, M5Core2 and Atom Lite/Matrix exposes 2 DAC and you can access them thru the `Dac1` and `Dac2` properties. Refer to the [DAC documentation](https://github.com/nanoframework/System.Device.Dac) for more information.
367
+
The M5Core, M5Core2, Fire and Atom Lite/Matrix exposes 2 DAC and you can access them thru the `Dac1` and `Dac2` properties. Refer to the [DAC documentation](https://github.com/nanoframework/System.Device.Dac) for more information.
0 commit comments