ESP32 Compile errors

[vvvhydr]

Good afternoon. You solved the problem with flovcode 10, but what about those who bought flovcode 9, but don’t have money for flovcode 10, I’m from Ukraine - there’s a war here and there’s no money for an update.
When reinstalling the flowcode and installing esp-idf-tools-setup-2.3, there is no choice of version 4.1, the minimum version is 5.0. What should I do? Maybe you can fix the problem in flowcode 9?
When I had the opportunity, I bought both Flowcode 7 and then Flowcode 9, but now because of the war I can’t buy it. The job is gone...
Help please.

[chipfryer27]

HI

Whilst your chip, a TTGO isn't included in the free chip pack, other ESP32 devices are, and as v10 is now free for hobbyist's and all components are free in v10, you should be able to use v10 and a ST7789.

Unfortunately Matrix isn't in control of the third-party software required to use ESP devices and the vendors often change things without notice. This has caught me out in the past too, and I have had to search the web for previous versions of idf-tools. I can however confirm that if you follow the install instructions exactly as documented in the latest guide, it does work.

Regards

[vvvhydr]

I installed Flowcode 10 using the method described on the forum. Before this, I installed a clean Windows 10. Errors and no compilation of ESP 32.
Everything was installed according to the method from the forum. But it doesn't work.
The installation files were exactly the same as in the installation procedure.

[mnfisher]

It looks as though it has installed and is compiling okay....

The (first) error is :

FCD_0bd11_WLAN_ESP12S1__GetRxArray' differ in signedness [-Werror=pointer-sign]
2609 | {
| ^
| |
| MX_CHAR * {aka char *}

The function GetRxArray is expecting an array of MX_UINT8 (unsigned bytes) but is getting MX_CHAR (signed bytes) - the esp32 compiler is 'very' picky about types....

You can work around it - or fix the component (as the source is available...) - by coercing the type to what the compiler wants...

Martin

[mnfisher]

Also to get rid of the 'dubious' ownership error.

Open a command prompt and do

git config --global --add safe.directory C:/Espressif/frameworks/esp-idf-v5.0.1

There is also a problem with a (possibly) unitiailised return value in one of the library routines (EndServerConnection)

It is possible to compile your code - by adding the following to YourProg/main/CMakeLists.txt (note that if you've used the latest install version - all programs have the same directory which is ?)

The 'signedness' issue doesn't matter - and the uninitialized RetVal may or may not (and is a bug in the component)...

Code: Select all

target_compile_options(${COMPONENT_LIB} PRIVATE -Wno-cpp)
target_compile_options(${COMPONENT_LIB} PRIVATE -Wno-unused-function)
target_compile_options(${COMPONENT_LIB} PRIVATE -Wno-unused-variable)
target_compile_options(${COMPONENT_LIB} PRIVATE -Wno-unused-but-set-variable)
target_compile_options(${COMPONENT_LIB} PRIVATE -Wno-incompatible-pointer-types)
target_compile_options(${COMPONENT_LIB} PRIVATE -Wno-discarded-qualifiers)
target_compile_options(${COMPONENT_LIB} PRIVATE -Wno-int-conversion)
target_compile_options(${COMPONENT_LIB} PRIVATE -Wno-uninitialized)
target_compile_options(${COMPONENT_LIB} PRIVATE -Wno-pointer-sign)

Which tells the compiler to ignore the offending errors (obviously fixing the errors would be better

Martin

[vvvhydr]

I thought maybe my computer was bad, I installed everything on my wife’s MacBook, a Mac with Windows 10 installed as a second system. Intel i7 processor, 16 GB memory. The system is clean. But the miracle did not happen.
Look carefully at the errors in both cases - everything leads to the fact that the problem is in the flowcode components, and not in the expressive programs.

[vvvhydr]

Good afternoon,
In general, in order to compile the program, I had to replace the ESP12 component with ESP32, the program compiled. But in hardware the ESP32 component is not working (even in Flovcode 9 it did not connect to Wifi, which remains in Flovcode 10). I tried to replace ESP32 with ESP12 and this also did not work due to the fact that both components are not working.
The program shows that I disabled the return of data on the initialization of the ESP32 component - the data is not returned.
I wonder if the developers somehow check the performance of their program? /Or is the main goal to sell the product and let users somehow improve it themselves? But how to improve without source code?
Versions 5 and 7 of Flowcode were still working relatively well, but then it started to get worse and worse.
I'm thinking more and more about switching to the Arduino platform.

[medelec35]

Hello.
Please don't hijack other topics, I have created your own topic.
As for the esp32 errors, we have no control over external compiler like ESP32.
The components worked with an older version of ESO32 and other compilers.
We are looking into fixing the issues, so you will be able to compile with FC10 without requiring additional code.
Thank you to the VC members that have contributed, you have done a great job.

[chipfryer27]

Hi

I don't have much time at present, but a brief look through your chart above, the one in which you complain that the components don't work, show some concern. One of which is that you connect to a server but do allow any time for the server to respond before making a decision as to whether you have connected or not.

If I get a chance later in the week I will try and give you an example, but there are recent posts that illustrate the (very) basic steps to use an ESP32 to communicate with a server. You might want to look at those.

Hope this helps.

[chipfryer27]

Hi

Travel delay so I have a bit of free time, but not much.

In your chart Flowcode1 you are using an ESP12S component but your actual target is an ESP32_WROOM_32 and wish to connect to a MQTT broker. How does it know what to connect to? I can't see any broker documented. I would expect problems when compiling to target with this chart.

In chart Flowcode1_net_ESP12 you are actually using an ESP32_WROOM_32. Your Network Component isn't linked to the ESP32 module though.

Again I do not see any broker documented so how does it know where to connect to?

If these modules are incapable of connecting to SSID/Host as you suggest then many, many issues would be reported. The fact that they are not, and a brief search through posts and the WiKi give examples of connecting to SSIDs, Servers and Brokers suggests that Flowcode does indeed work with these modules.

If you "right-click" on a component you will see a Help option that takes you to the WiKi, in which you will usually find examples and source codes.

Hope this helps.