Page 8 of 11

Re: ST7789 display

Posted: Sat Mar 11, 2023 4:40 pm
by WingNut
The compiler output message file is in the same folder as the hex file and is 'yourfilename'.msg.txt

Re: ST7789 display

Posted: Sat Mar 11, 2023 6:03 pm
by medelec35
After compiling, if you have an issue and have not already done so, can you post your .fcfx project file, please?
Also posting your .c file can help.

Re: ST7789 display

Posted: Fri May 05, 2023 8:54 am
by jandidden
One of those Fridays again.
The previous versions of my ESP32 Flowcode programs no longer compile.
I did an upgrade to the latest version of FC9 some time ago, that worked on some PIC applications without issues, but no longer on the ESP32 programs.
I got the same problem as I had earlier, which I fixed by completely reinstalling the ESP32 toolchain.
Did that again, no joy.
Question: in the user guide to install the toolchain, version 4.0 of the ESP-IDF is shown in the selection screen.
But currently there are later version from which you can choose, 4.1, 4.2, up to 5.0.
Should I re-install with V4.0?

Code: Select all

Done! You can now compile ESP-IDF projects.
Go to the project directory and run:

  idf.py build

Please use idf.py only in an ESP-IDF shell environment.

Build Failed

C:\ProgramData\MatrixTSL\FlowcodeV9\FCD\ESP\Batch\esp32_build.bat reported error code 0x1

Autoclose turned off

Jan

Re: ST7789 display

Posted: Sat May 06, 2023 2:32 pm
by jandidden
Please look this output:

Code: Select all

C:\Users\jandi\OneDrive - Linear Audio\2a - AR xt>REM DIR: FCD\ESP\Batch\esp32_build.bat 
Building ESP32 wroom log scale test ...
Setting IDF_PATH: C:\Users\jandi\esp-idf

Adding ESP-IDF tools to PATH...
    C:\Users\jandi\esp-idf-tools\tools\xtensa-esp32-elf\esp-2020r3-8.4.0\xtensa-esp32-elf\bin
    C:\Users\jandi\esp-idf-tools\tools\xtensa-esp32s2-elf\esp-2020r3-8.4.0\xtensa-esp32s2-elf\bin
    C:\Users\jandi\esp-idf-tools\tools\esp32ulp-elf\2.28.51-esp-20191205\esp32ulp-elf-binutils\bin
    C:\Users\jandi\esp-idf-tools\tools\esp32s2ulp-elf\2.28.51-esp-20191205\esp32s2ulp-elf-binutils\bin
    C:\Users\jandi\esp-idf-tools\tools\cmake\3.16.4\bin
    C:\Users\jandi\esp-idf-tools\tools\openocd-esp32\v0.11.0-esp32-20211220\openocd-esp32\bin
    C:\Users\jandi\esp-idf-tools\tools\ninja\1.10.0\
    C:\Users\jandi\esp-idf-tools\tools\idf-exe\1.0.1\
    C:\Users\jandi\esp-idf-tools\tools\ccache\3.7\
    C:\Users\jandi\esp-idf-tools\tools\dfu-util\0.9\dfu-util-0.9-win64
    C:\Users\jandi\esp-idf-tools\python_env\idf4.2_py3.7_env\Scripts
    C:\Users\jandi\esp-idf\tools
Checking if Python packages are up to date...
Python requirements from C:\Users\jandi\esp-idf\requirements.txt are satisfied.

Done! You can now compile ESP-IDF projects.
Go to the project directory and run:

  idf.py build

[0/1] Re-running CMake...
FAILED: build.ninja 
C:\esp-idf-tools\tools\cmake\3.13.4\bin\cmake.exe -SC:\Users\jandi\OneDrive_-_Linear_Audio\2a_-_AR_xt\ESP32_wroom_log_scale_test -BC:\Users\jandi\OneDrive_-_Linear_Audio\2a_-_AR_xt\ESP32_wroom_log_scale_test\build
CreateProcess failed: The system cannot find the file specified.
ninja: error: rebuilding 'build.ninja': subcommand failed
Executing action: all (aliases: build)
Running ninja in directory c:\users\jandi\onedrive_-_linear_audio\2a_-_ar_xt\esp32_wroom_log_scale_test\build
Executing "ninja all"...
ninja failed with exit code 1

Build Failed
At the top: Setting IDF_PATH: C:\Users\jandi\esp-idf - which is correct, that's where I installed stuff.

But then later, it complains it can find stuff in C:\esp-idf-tools\tools\cmake\3.13.4\bin
Why does it look there?? The location is correctly set to C:\Users\jandi\....

I will uninstall all and re-install to C:\esp_idf etc. See if that works.

Jan

Re: ST7789 display

Posted: Sat May 06, 2023 2:54 pm
by jandidden
Its a mess. Uninstalled and deleted everything related.
Re-installed from scratch to C:\esp-idf and C:\esp-idf-tools
Now I get this:

Code: Select all

  C:/esp-idf/tools/cmake/project.cmake:371 (idf_build_process)
  CMakeLists.txt:13 (project)
-- Configuring incomplete, errors occurred!
See also "C:/Users/jandi/OneDrive_-_Linear_Audio/2a_-_AR_xt/ESP32_wroom_log_scale_test-2/build/CMakeFiles/CMakeOutput.log".
Executing action: all (aliases: build)
Running cmake in directory c:\users\jandi\onedrive_-_linear_audio\2a_-_ar_xt\esp32_wroom_log_scale_test-2\build
Executing "cmake -G Ninja -DPYTHON_DEPS_CHECKED=1 -DESP_PLATFORM=1 -DIDF_TARGET=esp32 -DCCACHE_ENABLE=1 c:\users\jandi\onedrive_-_linear_audio\2a_-_ar_xt\esp32_wroom_log_scale_test-2"...
cmake failed with exit code 1

As to: See also "C:/Users/jandi/OneDrive_-_Linear_Audio/2a_-_AR_xt/ESP32_wroom_log_scale_test-2/build/CMakeFiles/CMakeOutput.log". - there is no such directory or file.
I give up. It's Saturday.

Jan

Re: ST7789 display

Posted: Sat May 06, 2023 7:57 pm
by jandidden
Did a clean install on another computer where that toolchain was never installed before. Same problem.
The installation guide says to install version 4.0, but at this time the only selections available are 4.2 and up to 5.0.
Could it be that the install script assumes 4.0 is used and gets mixed up when you install another version, which is different/incompatible?

Jan

Re: ST7789 display

Posted: Sat May 06, 2023 8:00 pm
by mnfisher
Hi Jan,

Might be worth making the jump to v5?
See viewtopic.php?f=3&t=1879&p=11284#p11284

Martin

Re: ST7789 display

Posted: Sat May 06, 2023 8:31 pm
by jgu1
Hi Martin!

Dare to brake in ;)

I have the ESP-IDF installed, what is the benefit to upgrade to IDF V.5, please ?

Br Jorgen

Re: ST7789 display

Posted: Sat May 06, 2023 9:08 pm
by mnfisher
If v4.1 is installed and working - then probably none....

If you want to use newer variants of the esp32 (S2 or C3 for example) - then you might need to change.
I'd messed up my install (I will try things - that don't always (ever?) go to plan) - so reinstalled using the latest version (having seen Ben's posts). It seems to need a few changes to my code :-(

Martin

Re: ST7789 display

Posted: Sun May 07, 2023 7:45 am
by jgu1
Ok thanks for reply Martin. no I stick to the version I have now and it works on my esp32dev. don't risk anything :lol:

Jorgen