-
hey guys.
i like the idea of embd beeing a plattform for hardware guys ;)
but as much as i like the idea, when it comes to i2c i somehow dislike the interface used.
in my opinion https://github.com/d…
-
I wanted to test RAM, Kingston DDR4 2*8GB on a Clevo NV41MZ Laptop,
Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz
```
lspci
00:00.0 Host bridge: Intel Corporation 11th Gen Core Pro…
-
When running `sudo hwinfo --short` the output is:
```
cpu:
11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz, 3850 …
-
Building the classes `driver::i2c` and `driver::uart`.
-
Add Lisp operations for interfacing with various defined I2C devices as well generic I2C read and write operations.
-
Building with the default configuration works fine. That said, when changing the pinout in CubeMX (e.g., enabling I2C1) regenerating the code throws several errors as shown below regarding lora_app_ve…
-
I'm not sure which hardware is on the device beyond the accelerometer, but we should decide how we want app writers to interface with it - I know it's fairly well documented for hexpansions, but onboa…
-
During initial development many devices had constants and datatypes exposed in the public interface that are only needed internally. These should be moved to the private section of the spec or to the…
-
Hi, was trying out the QTPY ESP32-S2 and reading the components examples/code and it only supports one i2c interface currently. The spec takes an array, but no idea if the website will let me scan two…
tyeth updated
10 months ago
-
As discussion on Discord revealed, we are using to different types of I2C port expanders on shield and interface.
Currently, we are only supporting the MCP23008 type properly.
They are somewhat comp…