lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Server stats:

64
active users

#i2c

1 post1 participant0 posts today
Xavi<p>Is there anyone in the room with knowledge about <a href="https://talamanca.social/tags/ESP32" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ESP32</span></a> microcontrollers?</p><p>I am playing with a <a href="https://talamanca.social/tags/Waveshare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Waveshare</span></a> development board that has an <a href="https://talamanca.social/tags/AMOLED" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AMOLED</span></a> and a touchscreen, and it says it has built-in <a href="https://talamanca.social/tags/SH8601" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SH8601</span></a> display driver and <a href="https://talamanca.social/tags/FT3168" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FT3168</span></a> capacitive touch chip, using <a href="https://talamanca.social/tags/QSPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>QSPI</span></a> and <a href="https://talamanca.social/tags/I2C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>I2C</span></a> communication respectively.</p><p><a href="https://www.waveshare.com/product/arduino/boards-kits/esp32-s3-touch-amoled-1.8.htm" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">waveshare.com/product/arduino/</span><span class="invisible">boards-kits/esp32-s3-touch-amoled-1.8.htm</span></a></p><p>It directly works in <a href="https://talamanca.social/tags/Arduino" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Arduino</span></a> with <a href="https://talamanca.social/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>C</span></a>, but I am trying to make it work with <a href="https://talamanca.social/tags/MicroPython" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MicroPython</span></a>. </p><p>Before I spend effort trying to compile it with <a href="https://talamanca.social/tags/LVGL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LVGL</span></a>, I want to know if I could print a "Hello World" to the screen as is, and while my mind tells me that I need a driver, the sentence "built-in display driver using QSPI" makes me think that I could eventually use the display without code drivers, but I don't know how.</p><p>I'd love to see an example, if it's possible, or to be pointed to any resources that I can read in this regard. I am complete newbie.</p><p>Re-posts are appreciated.</p><p>Thank in advance 😊</p>
Daniele Verducci 🧉That should do.<br>Using <a class="hashtag" href="https://social.ichibi.eu/tag/i2c" rel="nofollow noopener noreferrer" target="_blank">#i2c</a> to connect the <a class="hashtag" href="https://social.ichibi.eu/tag/bme280" rel="nofollow noopener noreferrer" target="_blank">#bme280</a> to the <a class="hashtag" href="https://social.ichibi.eu/tag/esp8266" rel="nofollow noopener noreferrer" target="_blank">#esp8266</a> microcontroller on the default pins. It defaults to SCL on GPIO5 and SDA on GPIO4. I checked the pinout and they are the ones labeled as D1 and D2.<br>Now let's write a <a class="hashtag" href="https://social.ichibi.eu/tag/yaml" rel="nofollow noopener noreferrer" target="_blank">#yaml</a> config for <a class="hashtag" href="https://social.ichibi.eu/tag/esphome" rel="nofollow noopener noreferrer" target="_blank">#esphome</a> ...
Espen Andersen<p>For anyone interested in connecting an <a href="https://techhub.social/tags/esp32" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>esp32</span></a> to an <a href="https://techhub.social/tags/ublox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ublox</span></a> <a href="https://techhub.social/tags/GNSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GNSS</span></a> module, i just published a brief outline on how I got it to work over the <a href="https://techhub.social/tags/i2c" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>i2c</span></a> bus.</p><p>It's part of my crazy <a href="https://techhub.social/tags/DIY" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DIY</span></a> broadcast clock <a href="https://techhub.social/tags/electronics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>electronics</span></a> project (all <a href="https://techhub.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opensource</span></a> <a href="https://techhub.social/tags/oss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>oss</span></a>)...</p><p>Personal page:<br><a href="https://espenandersen.no/u-blox-module-with-esp32/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">espenandersen.no/u-blox-module</span><span class="invisible">-with-esp32/</span></a></p><p>GitHub:<br><a href="https://github.com/espena/broadcast-clock" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/espena/broadcast-cl</span><span class="invisible">ock</span></a></p>
GeekProjects News<p>Tiny Trackpad Fits On Ergonomic Keyboard <a href="https://hackaday.com/2024/08/06/tiny-trackpad-fits-on-ergonomic-keyboard/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">hackaday.com/2024/08/06/tiny-t</span><span class="invisible">rackpad-fits-on-ergonomic-keyboard/</span></a> <a href="https://geekprojects.com/tags/PeripheralsHacks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PeripheralsHacks</span></a> <a href="https://geekprojects.com/tags/splitkeyboard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>splitkeyboard</span></a> <a href="https://geekprojects.com/tags/zsavoyager" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>zsavoyager</span></a> <a href="https://geekprojects.com/tags/ergonomic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ergonomic</span></a> <a href="https://geekprojects.com/tags/keyboard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>keyboard</span></a> <a href="https://geekprojects.com/tags/trackpad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>trackpad</span></a> <a href="https://geekprojects.com/tags/Pogopin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Pogopin</span></a> <a href="https://geekprojects.com/tags/mouse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mouse</span></a> <a href="https://geekprojects.com/tags/trrs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>trrs</span></a> <a href="https://geekprojects.com/tags/i2c" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>i2c</span></a></p>
Florian 'floe' Echtler<p>I suspect that one of the battery's <a href="https://hci.social/tags/I2C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>I2C</span></a> lines is still floating, but I haven't been able to find a second test point to connect to. I've even checked another undamaged tablet to confirm the wiring, and 3 out of 4 support signals are definitely connected again.</p><p>Question is: does the battery usually have its own I2C bus connected to the battery controller, or is it actually the system bus? Because in the second case, I could in theory just put in another I2C bridge...? (2/2)</p>
Wintermute_BBS<p>A small demonstration of my I2C serial UART driver code being used by a small "server-side application" that remotely smells of BBS. </p><p>"FORTH isn't for complex applications" some say. Well, I beg to differ ... </p><p><a href="https://oldbytes.space/tags/BBS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BBS</span></a><br><a href="https://oldbytes.space/tags/UART" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>UART</span></a><br><a href="https://oldbytes.space/tags/SC16IS750" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SC16IS750</span></a><br><a href="https://oldbytes.space/tags/I2C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>I2C</span></a> <br><a href="https://oldbytes.space/tags/Forth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Forth</span></a> <br><a href="https://oldbytes.space/tags/RetroComputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RetroComputing</span></a> <br><a href="https://oldbytes.space/tags/RetroCoding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RetroCoding</span></a> <br><a href="https://oldbytes.space/tags/ForthDeck" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ForthDeck</span></a> <br><a href="https://oldbytes.space/tags/My4TH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>My4TH</span></a> <br><a href="https://oldbytes.space/tags/Mynor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Mynor</span></a></p>
Wintermute_BBS<p>Testing my custom <a href="https://oldbytes.space/tags/I2C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>I2C</span></a> <a href="https://oldbytes.space/tags/driver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>driver</span></a> code I've written for the <a href="https://oldbytes.space/tags/rc2014" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rc2014</span></a> using <a href="https://oldbytes.space/tags/DXForth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DXForth</span></a> for CP/M. I decided to try to run my *unmodifed* <a href="https://oldbytes.space/tags/sc16is750" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>sc16is750</span></a> driver code I wrote for the <a href="https://oldbytes.space/tags/Mynor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Mynor</span></a> <a href="https://oldbytes.space/tags/My4TH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>My4TH</span></a> <a href="https://oldbytes.space/tags/ForthDeck" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ForthDeck</span></a> keeping all fingers crossed ...</p><p>... and yay, it works! 🥳​</p><p>So now I can use the RC2014 <a href="https://oldbytes.space/tags/I2CBusMasterModule" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>I2CBusMasterModule</span></a> from within DX Forth and recycle most of the code I've written on another machine (the Mynor My4TH). Even the <a href="https://oldbytes.space/tags/hd44780" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>hd44780</span></a> driver I wrote works like a charm, only my Thermometer app seems to have some issues (and I have a vague idea what causes these).</p><p>It may take some time until I make the code available (still need to comment / document everything, clean up screens etc.) but if you're in a hurry and can't wait - drop me a personal message.</p><p><a href="https://oldbytes.space/tags/cpm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cpm</span></a> <br><a href="https://oldbytes.space/tags/forth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>forth</span></a> <br><a href="https://oldbytes.space/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>retrocomputing</span></a> <br><a href="https://oldbytes.space/tags/z80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>z80</span></a></p>
LeoDJ<p>After a lengthy bring-up debug session, I noticed the <a href="https://chaos.social/tags/SSD1303" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SSD1303</span></a> not quite behaving as I expected.<br>Pin D2 (SDA_out, which "should be left open" in <a href="https://chaos.social/tags/SPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPI</span></a> mode) was not staying high all the time, like I had measured previously.<br>Rather it was shifting out some kind of gibberish data.<br>This was not compatible with my tested idea of "just putting a diode between SDA_out and SDA_in (D1)", to still allow I2C-lows through in <a href="https://chaos.social/tags/I2C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>I2C</span></a> mode, but block the constant* high signal in SPI mode.</p><p>* formerly believed as</p>
maexchen1<p><span class="h-card"><a href="https://mstdn.ca/@CleoQc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>CleoQc</span></a></span> </p><p>Mhh Pullup Resistor on the Line enable?</p><p>Wenn 2 <a href="https://nrw.social/tags/I2C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>I2C</span></a>, 2 I2C Controler put 5 V on the Line. The Line is alway high.</p>
Shufei 👩🏽‍🌾<p><span class="h-card"><a href="https://merveilles.town/@neauoire" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>neauoire</span></a></span> What does one need to DIY core memory weave and have it addressable by smolputer <a href="https://social.sdf.org/tags/GPIO" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GPIO</span></a> with <a href="https://social.sdf.org/tags/I2C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>I2C</span></a> or whatever? Just hook it to usb and zap at it? Any notions offhand?</p><p>This is to say I have some notion of how to make the core weave from junk, but little grok of a platform which can talk to it readily.</p>
dooraim :linux: :asahi:<p><a href="https://fosstodon.org/tags/introduction" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>introduction</span></a> <a href="https://fosstodon.org/tags/whoami" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>whoami</span></a> </p><p>Hey i'm dooraim. </p><p>I'm a <a href="https://fosstodon.org/tags/softwaredeveloper" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>softwaredeveloper</span></a> in a company that creates <a href="https://fosstodon.org/tags/embedded" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>embedded</span></a> <a href="https://fosstodon.org/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>linux</span></a> systems. <br> <br>Before I worked for an <a href="https://fosstodon.org/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opensource</span></a> project (<a href="https://fosstodon.org/tags/pulp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pulp</span></a>) which uses <a href="https://fosstodon.org/tags/riscv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>riscv</span></a>, for which I implemented the <a href="https://fosstodon.org/tags/drivers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>drivers</span></a> for <a href="https://fosstodon.org/tags/I2C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>I2C</span></a> and <a href="https://fosstodon.org/tags/SPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPI</span></a>. </p><p>I know <a href="https://fosstodon.org/tags/c" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>c</span></a> as a programming language and now I'm using <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>python</span></a>. </p><p>Right now I'm working on an interface between gateway and <a href="https://fosstodon.org/tags/cloud" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cloud</span></a>. I like to study <a href="https://fosstodon.org/tags/SoC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SoC</span></a> architecture and core <a href="https://fosstodon.org/tags/ISA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ISA</span></a> (<a href="https://fosstodon.org/tags/ARM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ARM</span></a>).</p>