Advance display flickers/corrupted on refresh

2»

Comments

  • Dear Phil,

    Hope you are doing well. Thank you for the support to us.

    Sorry for the bad experience caused.

    In response to your previous feedback, here is the reply: (For other issues, please wait a little longer. We are still analyzing them and will reply to you as soon as possible.)

    ”1) In the tutorial under the text “Choose the correct resolution based on the different sizes you are using” there is a picture of the different screen resolutions and information on associated screen and touchscreen drivers. However no information is given on the required color depth. The images above this show 32-bit the image below 16-bit – which is correct? (I chose 16-bit as it was the last one shown).“

    ---Reply: 1) Please use the 32-bit color depth image for this. We have included this in the tutorial/examples program for Arduino IDE. In fact, PlatformIO has already generated the ready-made file directly.

    ”2) The link for files to download is https://drive.google.com/drive/folders/1Qw7hdW862upBigarI11btgl4cQkr0vpe?usp=sharing, this contains a folder for v1.2, and in there I find a zip file for the 7” screen (7.0_PlatfromIO.zip). The zip is for a platform IO project and does not contain the PNG images you refer to, so instead I chose a simple PNG file of my own.“

    ---Reply: 2) The pictures have just been uploaded to the folder.

    Thanks!
    Warm regards,

  • I had the problem fixed and then something happened between builds, without changing any code. SPIClass had vanished according to the compiler.
    After some searching of the internet, in vain, I downgraded the board to v3.0.0 and reinstalled v3.0.2. The fixed the lost SPIClass but things have returned to flickering screen changes and fuzzy vertical edges. It used to work at a frequency of 21000000. The flicking change disappears with 15000000 but the fuzzy edges remain. :(

  • Dear Phil,

    Hope you are doing well. Thank you for the support to us.
    I just wanted to follow up that has the technical probleom been solved ? Is there anything else we can help ?

    Warm regards,

  • edited October 21

    Hello Jennie,
    Nothing really has changed on my side, still waiting for you to answer the main question - why did you specify that branch for the platform in the platformio.ini file?
    I'm currently in a state where I have to maintain 2 development environments, one for your screen, using the tasmota dev branch, and a second for all my other projects using the default platformio setup.
    I've done a lot of reading, and it seems that the arduino framework supplied by espressif was updated and has multiple breaking changes vs the older release - i.e. version 2.x 3.0. To make things more difficult, the platformio project does not support the newer framework, and has no plan to (some disagreement between espressif and platformio , check issue 1225 on github project platformio/platform-espressif32). There is a forked project (pioarduino) which does support the newer libraries, but does not support the bluetooth BLE libraries (like I posted earlier).

    I assume your screen requires some change/fix in the v3 arduino framework/ v5.3 espressif libraries - but again you have not made that clear. If true you need to update your documentation, either to adopt pioarduino (and make clear of it's restrictions), or to state that users cannot use platformio/vscode and instead have to revert to the (frankly useless for any reasonably complex project) arduino IDE.

    In the meantime I'm trying to build my own version of the arduino framework to include both the v3 libraries and BLE support, which is proving rather challenging, and I don't have enough time at the moment to get that to work.

    With best regards

    Phil.

Sign In or Register to comment.