home.social

#lvgl — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #lvgl, aggregated by home.social.

fetched live
  1. [Перевод] Как загрузить любой шрифт Google Fonts на дисплей ESP32 — без Processing и ручной конвертации

    Встроенных шрифтов TFT_eSPI хватает ровно до того момента, когда интерфейс ESP32 хочется сделать аккуратнее обычного тестового стенда. В статье автор показывает браузерный генератор для Google Fonts и собственных TTF, а заодно объясняет, как устроен формат VLW и что важно учесть при работе со сглаживанием, LittleFS, переносами строк и размером файла. Настроить шрифты

    habr.com/ru/companies/otus/art

    #esp32 #Google_Fonts #TFTдисплей #TFT_eSPI #LVGL #шрифты_для_микроконтроллеров #VLW #LittleFS #встраиваемые_системы #embeddedразработка

  2. [Перевод] Как загрузить любой шрифт Google Fonts на дисплей ESP32 — без Processing и ручной конвертации

    Встроенных шрифтов TFT_eSPI хватает ровно до того момента, когда интерфейс ESP32 хочется сделать аккуратнее обычного тестового стенда. В статье автор показывает браузерный генератор для Google Fonts и собственных TTF, а заодно объясняет, как устроен формат VLW и что важно учесть при работе со сглаживанием, LittleFS, переносами строк и размером файла. Настроить шрифты

    habr.com/ru/companies/otus/art

    #esp32 #Google_Fonts #TFTдисплей #TFT_eSPI #LVGL #шрифты_для_микроконтроллеров #VLW #LittleFS #встраиваемые_системы #embeddedразработка

  3. [Перевод] Как загрузить любой шрифт Google Fonts на дисплей ESP32 — без Processing и ручной конвертации

    Встроенных шрифтов TFT_eSPI хватает ровно до того момента, когда интерфейс ESP32 хочется сделать аккуратнее обычного тестового стенда. В статье автор показывает браузерный генератор для Google Fonts и собственных TTF, а заодно объясняет, как устроен формат VLW и что важно учесть при работе со сглаживанием, LittleFS, переносами строк и размером файла. Настроить шрифты

    habr.com/ru/companies/otus/art

    #esp32 #Google_Fonts #TFTдисплей #TFT_eSPI #LVGL #шрифты_для_микроконтроллеров #VLW #LittleFS #встраиваемые_системы #embeddedразработка

  4. Oddly pairing Microbe C++ with #gtk (gtk4) directly produces far better cross-platform results than either #vala #mono or C++ with #Qt and does so while producing tiny executables. Of course, the idea of doing any desktop applications while #blind is rather amusing, too.

    Something like Microbe might pair very well with #LVGL too, producing an embedded ui environment potentially cleaner than #QtQuick for most use cases while having far less execution overhead.

  5. Stories and reasoning we put to our work is often not that visible. Here is my Link project, which is partly AI implemented communication system to test various transport and security measures. It's built with buildroot and all other details can be found here: codeberg.org/resiliencetheatre
    #opsec #comsec #outofband #opensource #buildroot #embedded #lvgl #prepping #preparedness #nitrokey #fido2 #satcom

  6. Stories and reasoning we put to our work is often not that visible. Here is my Link project, which is partly AI implemented communication system to test various transport and security measures. It's built with buildroot and all other details can be found here: codeberg.org/resiliencetheatre
    #opsec #comsec #outofband #opensource #buildroot #embedded #lvgl #prepping #preparedness #nitrokey #fido2 #satcom

  7. Stories and reasoning we put to our work is often not that visible. Here is my Link project, which is partly AI implemented communication system to test various transport and security measures. It's built with buildroot and all other details can be found here: codeberg.org/resiliencetheatre
    #opsec #comsec #outofband #opensource #buildroot #embedded #lvgl #prepping #preparedness #nitrokey #fido2 #satcom

  8. Learnt about ESP #IDF, #PlatformIO, #FreeRTOS, and took way too long to properly initialize the SPI bus so that I could get #LVGL running.
    Hello, World!

    #Swift #ESP32

  9. Learnt about ESP #IDF, #PlatformIO, #FreeRTOS, and took way too long to properly initialize the SPI bus so that I could get #LVGL running.
    Hello, World!

    #Swift #ESP32

  10. Learnt about ESP #IDF, #PlatformIO, #FreeRTOS, and took way too long to properly initialize the SPI bus so that I could get #LVGL running.
    Hello, World!

    #Swift #ESP32

  11. Learnt about ESP #IDF, #PlatformIO, #FreeRTOS, and took way too long to properly initialize the SPI bus so that I could get #LVGL running.
    Hello, World!

    #Swift #ESP32

  12. Learnt about ESP #IDF, #PlatformIO, #FreeRTOS, and took way too long to properly initialize the SPI bus so that I could get #LVGL running.
    Hello, World!

    #Swift #ESP32

  13. Hello #Smarthome community!
    I finally found the "sweet spot" for displaying data on larger LCDs.

    After testing various layouts (from free-floating icons to strict tables) modern "tiles" are definitely the winner.

    The aesthetics can always be tweaked, but from a functional standpoint, this layout is unbeatable.

    The heart of this project is the #Waveshare ESP32-S3-Touch-LCD-4.3B. It is used as a central dashboard for sensor data and remote control of my other IoT nodes

    #ESPHome #DIY #IoT #LVGL

  14. Hello #Smarthome community!
    I finally found the "sweet spot" for displaying data on larger LCDs.

    After testing various layouts (from free-floating icons to strict tables) modern "tiles" are definitely the winner.

    The aesthetics can always be tweaked, but from a functional standpoint, this layout is unbeatable.

    The heart of this project is the #Waveshare ESP32-S3-Touch-LCD-4.3B. It is used as a central dashboard for sensor data and remote control of my other IoT nodes

    #ESPHome #DIY #IoT #LVGL

  15. Hello #Smarthome community!
    I finally found the "sweet spot" for displaying data on larger LCDs.

    After testing various layouts (from free-floating icons to strict tables) modern "tiles" are definitely the winner.

    The aesthetics can always be tweaked, but from a functional standpoint, this layout is unbeatable.

    The heart of this project is the #Waveshare ESP32-S3-Touch-LCD-4.3B. It is used as a central dashboard for sensor data and remote control of my other IoT nodes

    #ESPHome #DIY #IoT #LVGL

  16. Hello #Smarthome community!
    I finally found the "sweet spot" for displaying data on larger LCDs.

    After testing various layouts (from free-floating icons to strict tables) modern "tiles" are definitely the winner.

    The aesthetics can always be tweaked, but from a functional standpoint, this layout is unbeatable.

    The heart of this project is the #Waveshare ESP32-S3-Touch-LCD-4.3B. It is used as a central dashboard for sensor data and remote control of my other IoT nodes

    #ESPHome #DIY #IoT #LVGL

  17. Hello #Smarthome community!
    I finally found the "sweet spot" for displaying data on larger LCDs.

    After testing various layouts (from free-floating icons to strict tables) modern "tiles" are definitely the winner.

    The aesthetics can always be tweaked, but from a functional standpoint, this layout is unbeatable.

    The heart of this project is the #Waveshare ESP32-S3-Touch-LCD-4.3B. It is used as a central dashboard for sensor data and remote control of my other IoT nodes

    #ESPHome #DIY #IoT #LVGL

  18. After two solid days of wrestling with toolchains, I can now write to the screen. I feel like this is a major accomplishment. Screen refresh is noticeably slow, though.

    I'm using VSCodium, PlatformIO, ESP-IDF, and an ST7789 driver of unknown provenance (probably Waveshare). That's not the first combo I tried, nor the fourth.

    🧵 10/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL #VSCodium #PlatformIO

  19. After two solid days of wrestling with toolchains, I can now write to the screen. I feel like this is a major accomplishment. Screen refresh is noticeably slow, though.

    I'm using VSCodium, PlatformIO, ESP-IDF, and an ST7789 driver of unknown provenance (probably Waveshare). That's not the first combo I tried, nor the fourth.

    🧵 10/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL #VSCodium #PlatformIO

  20. After two solid days of wrestling with toolchains, I can now write to the screen. I feel like this is a major accomplishment. Screen refresh is noticeably slow, though.

    I'm using VSCodium, PlatformIO, ESP-IDF, and an ST7789 driver of unknown provenance (probably Waveshare). That's not the first combo I tried, nor the fourth.

    🧵 10/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL #VSCodium #PlatformIO

  21. After two solid days of wrestling with toolchains, I can now write to the screen. I feel like this is a major accomplishment. Screen refresh is noticeably slow, though.

    I'm using VSCodium, PlatformIO, ESP-IDF, and an ST7789 driver of unknown provenance (probably Waveshare). That's not the first combo I tried, nor the fourth.

    🧵 10/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL #VSCodium #PlatformIO

  22. After two solid days of wrestling with toolchains, I can now write to the screen. I feel like this is a major accomplishment. Screen refresh is noticeably slow, though.

    I'm using VSCodium, PlatformIO, ESP-IDF, and an ST7789 driver of unknown provenance (probably Waveshare). That's not the first combo I tried, nor the fourth.

    🧵 10/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL #VSCodium #PlatformIO

  23. I'm reviving this project.

    This is the ESP32 board I'm using. It has an ESP32S3, 8+16MB PSRAM, touch screen, yada³. Nice little kit.
    waveshare.com/wiki/ESP32-S3-To

    I am trying to decide whether to use a high level toolkit like LVGL or roll my own optimized SPI driver for the display and eke out all the performance I can. I'm leaning toward the latter, because that's what I always do.

    🧵 9/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL

  24. I'm reviving this project.

    This is the ESP32 board I'm using. It has an ESP32S3, 8+16MB PSRAM, touch screen, yada³. Nice little kit.
    waveshare.com/wiki/ESP32-S3-To

    I am trying to decide whether to use a high level toolkit like LVGL or roll my own optimized SPI driver for the display and eke out all the performance I can. I'm leaning toward the latter, because that's what I always do.

    🧵 9/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL

  25. I'm reviving this project.

    This is the ESP32 board I'm using. It has an ESP32S3, 8+16MB PSRAM, touch screen, yada³. Nice little kit.
    waveshare.com/wiki/ESP32-S3-To

    I am trying to decide whether to use a high level toolkit like LVGL or roll my own optimized SPI driver for the display and eke out all the performance I can. I'm leaning toward the latter, because that's what I always do.

    🧵 9/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL

  26. I'm reviving this project.

    This is the ESP32 board I'm using. It has an ESP32S3, 8+16MB PSRAM, touch screen, yada³. Nice little kit.
    waveshare.com/wiki/ESP32-S3-To

    I am trying to decide whether to use a high level toolkit like LVGL or roll my own optimized SPI driver for the display and eke out all the performance I can. I'm leaning toward the latter, because that's what I always do.

    🧵 9/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL

  27. I'm reviving this project.

    This is the ESP32 board I'm using. It has an ESP32S3, 8+16MB PSRAM, touch screen, yada³. Nice little kit.
    waveshare.com/wiki/ESP32-S3-To

    I am trying to decide whether to use a high level toolkit like LVGL or roll my own optimized SPI driver for the display and eke out all the performance I can. I'm leaning toward the latter, because that's what I always do.

    🧵 9/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL

  28. Часть 3: Создание пользовательского интерфейса на дисплее Guition с ESPHome и библиотекой LVGL

    Привет Habr! Продолжаем серию статей о LVGL в ESPHome. В третьей части статьи речь пойдет о создании своего пользовательского виджета, который может быть подключен к проекту. И не только к данному проекту, а вообще даст небольшое представление как делать виджеты в ESPHome. Итак, Создавать будем виджет умной розетки с индикацией мощности, напряжения и силы тока. Поехали...

    habr.com/ru/articles/935528/

    #esp32s3 #esp32 #esphome #homeassistant #iot #guition #lvgl #diy #display #firmware

  29. Часть 3: Создание пользовательского интерфейса на дисплее Guition с ESPHome и библиотекой LVGL

    Привет Habr! Продолжаем серию статей о LVGL в ESPHome. В третьей части статьи речь пойдет о создании своего пользовательского виджета, который может быть подключен к проекту. И не только к данному проекту, а вообще даст небольшое представление как делать виджеты в ESPHome. Итак, Создавать будем виджет умной розетки с индикацией мощности, напряжения и силы тока. Поехали...

    habr.com/ru/articles/935528/

    #esp32s3 #esp32 #esphome #homeassistant #iot #guition #lvgl #diy #display #firmware

  30. Часть 3: Создание пользовательского интерфейса на дисплее Guition с ESPHome и библиотекой LVGL

    Привет Habr! Продолжаем серию статей о LVGL в ESPHome. В третьей части статьи речь пойдет о создании своего пользовательского виджета, который может быть подключен к проекту. И не только к данному проекту, а вообще даст небольшое представление как делать виджеты в ESPHome. Итак, Создавать будем виджет умной розетки с индикацией мощности, напряжения и силы тока. Поехали...

    habr.com/ru/articles/935528/

    #esp32s3 #esp32 #esphome #homeassistant #iot #guition #lvgl #diy #display #firmware

  31. Усовершенствование интерфейса дисплея Guition на ESPHome (LVGL)

    Продолжаем развивать интерфейс дисплея Guition на ESPHome с использованием LVGL. Изначально планировалось просто добавить пару виджетов, но в процессе работы появилась идея кардинально изменить структуру проекта: сделать виджеты подключаемыми, вынести сущности в переменные для шаблонизации и максимально упростить использование прошивки для конечного пользователя.

    habr.com/ru/articles/925228/

    #esp32 #esphome #homeassistant #lvgl #guition #iot #diy_умный_дом #diy_или_сделай_сам #display #firmware

  32. Усовершенствование интерфейса дисплея Guition на ESPHome (LVGL)

    Продолжаем развивать интерфейс дисплея Guition на ESPHome с использованием LVGL. Изначально планировалось просто добавить пару виджетов, но в процессе работы появилась идея кардинально изменить структуру проекта: сделать виджеты подключаемыми, вынести сущности в переменные для шаблонизации и максимально упростить использование прошивки для конечного пользователя.

    habr.com/ru/articles/925228/

    #esp32 #esphome #homeassistant #lvgl #guition #iot #diy_умный_дом #diy_или_сделай_сам #display #firmware

  33. Усовершенствование интерфейса дисплея Guition на ESPHome (LVGL)

    Продолжаем развивать интерфейс дисплея Guition на ESPHome с использованием LVGL. Изначально планировалось просто добавить пару виджетов, но в процессе работы появилась идея кардинально изменить структуру проекта: сделать виджеты подключаемыми, вынести сущности в переменные для шаблонизации и максимально упростить использование прошивки для конечного пользователя.

    habr.com/ru/articles/925228/

    #esp32 #esphome #homeassistant #lvgl #guition #iot #diy_умный_дом #diy_или_сделай_сам #display #firmware

  34. @xavi
    You will always need bus and display drivers for this; either loaded as part of your project, or a #MicroPython firmware with a drivers built-in.

    #QSPI is 'Quad SPI', a very fast display bus. The #ESP32 micropython port does not support this natively, so you need a driver for that.
    It may get added in the future, See discussion here, etc:
    github.com/orgs/micropython/di

    You also need a driver for the SH8601 itself (this will use the QSPI bus).

    Have a look at this page; which has a pre-compiled, non-lvgl firmware supporting your board + display.
    github.com/dobodu/Lilygo-Amole

    Personally; I think you want to go the #LVGL route anyway; It's more of an ecosystem than just a set of display drivers. You get the tools and libraries to use the display effectively, as well as the hardware support.

    Micropython itself does not build in any drivers or features for this sort of display. It has basic framebuffer support but this is intended for tiny OLED's etc. Not large color displays. Indeed, a framebuffer for this display would be 688K in size.. larger than the system RAM.

  35. @xavi
    You will always need bus and display drivers for this; either loaded as part of your project, or a #MicroPython firmware with a drivers built-in.

    #QSPI is 'Quad SPI', a very fast display bus. The #ESP32 micropython port does not support this natively, so you need a driver for that.
    It may get added in the future, See discussion here, etc:
    github.com/orgs/micropython/di

    You also need a driver for the SH8601 itself (this will use the QSPI bus).

    Have a look at this page; which has a pre-compiled, non-lvgl firmware supporting your board + display.
    github.com/dobodu/Lilygo-Amole

    Personally; I think you want to go the #LVGL route anyway; It's more of an ecosystem than just a set of display drivers. You get the tools and libraries to use the display effectively, as well as the hardware support.

    Micropython itself does not build in any drivers or features for this sort of display. It has basic framebuffer support but this is intended for tiny OLED's etc. Not large color displays. Indeed, a framebuffer for this display would be 688K in size.. larger than the system RAM.

  36. @xavi
    You will always need bus and display drivers for this; either loaded as part of your project, or a #MicroPython firmware with a drivers built-in.

    #QSPI is 'Quad SPI', a very fast display bus. The #ESP32 micropython port does not support this natively, so you need a driver for that.
    It may get added in the future, See discussion here, etc:
    github.com/orgs/micropython/di

    You also need a driver for the SH8601 itself (this will use the QSPI bus).

    Have a look at this page; which has a pre-compiled, non-lvgl firmware supporting your board + display.
    github.com/dobodu/Lilygo-Amole

    Personally; I think you want to go the #LVGL route anyway; It's more of an ecosystem than just a set of display drivers. You get the tools and libraries to use the display effectively, as well as the hardware support.

    Micropython itself does not build in any drivers or features for this sort of display. It has basic framebuffer support but this is intended for tiny OLED's etc. Not large color displays. Indeed, a framebuffer for this display would be 688K in size.. larger than the system RAM.

  37. @xavi
    You will always need bus and display drivers for this; either loaded as part of your project, or a #MicroPython firmware with a drivers built-in.

    #QSPI is 'Quad SPI', a very fast display bus. The #ESP32 micropython port does not support this natively, so you need a driver for that.
    It may get added in the future, See discussion here, etc:
    github.com/orgs/micropython/di

    You also need a driver for the SH8601 itself (this will use the QSPI bus).

    Have a look at this page; which has a pre-compiled, non-lvgl firmware supporting your board + display.
    github.com/dobodu/Lilygo-Amole

    Personally; I think you want to go the #LVGL route anyway; It's more of an ecosystem than just a set of display drivers. You get the tools and libraries to use the display effectively, as well as the hardware support.

    Micropython itself does not build in any drivers or features for this sort of display. It has basic framebuffer support but this is intended for tiny OLED's etc. Not large color displays. Indeed, a framebuffer for this display would be 688K in size.. larger than the system RAM.

  38. @xavi
    You will always need bus and display drivers for this; either loaded as part of your project, or a #MicroPython firmware with a drivers built-in.

    #QSPI is 'Quad SPI', a very fast display bus. The #ESP32 micropython port does not support this natively, so you need a driver for that.
    It may get added in the future, See discussion here, etc:
    github.com/orgs/micropython/di

    You also need a driver for the SH8601 itself (this will use the QSPI bus).

    Have a look at this page; which has a pre-compiled, non-lvgl firmware supporting your board + display.
    github.com/dobodu/Lilygo-Amole

    Personally; I think you want to go the #LVGL route anyway; It's more of an ecosystem than just a set of display drivers. You get the tools and libraries to use the display effectively, as well as the hardware support.

    Micropython itself does not build in any drivers or features for this sort of display. It has basic framebuffer support but this is intended for tiny OLED's etc. Not large color displays. Indeed, a framebuffer for this display would be 688K in size.. larger than the system RAM.

  39. Is there anyone in the room with knowledge about #ESP32 microcontrollers?

    I am playing with a #Waveshare development board that has an #AMOLED and a touchscreen, and it says it has built-in #SH8601 display driver and #FT3168 capacitive touch chip, using #QSPI and #I2C communication respectively.

    waveshare.com/product/arduino/

    It directly works in #Arduino with #C, but I am trying to make it work with #MicroPython.

    Before I spend effort trying to compile it with #LVGL, 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.

    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.

    Re-posts are appreciated.

    Thank in advance 😊