Flowcode Support Board

Hi !

Hopefully some can tell me what´s wrong. I have been working on a projeject for long time. Everytime I have made some small change I compile to the chip, done it many time now. Today I start up my project again and the first I do is to compile chip without perform any change, suddently I get erroe 01. It look like something is wrong with a string, but where.
Please advice.
br

jorgen

Hi Jorgen,

The error is at:

C:\ProgramData\MatrixTSL\FlowcodeV9\CAL\ESP\ESP_CAL_I2C.c: In function 'FC_CAL_I2C_Transaction_Init_1':
C:\ProgramData\MatrixTSL\FlowcodeV9\CAL\ESP\ESP_CAL_I2C.c:385:1: error: control reaches end of non-void function [-Werror=return-type]

- so in the CAL_I2C code... Have you just done an update? It compiles AOK for me - so maybe try checking all is up to date?

Martin

As an aside - it would be great if the esp32 output could be filtered a bit - there are 1794 lines of output I see a couple of radio buttons (hide warnings / hide building/linking) to just show 'errors' if the user requires this.

I tried using the latest esp-idf tools and output is colour-coded to a terminal which helps a bit.. I didn't manage to get it to work with Flowcode though (at least not when using any background code such as the CAL_SPI - seems lots of registers have 'new' names). I did mange to compile some code for an esp32-c3

I open the msg.txt file in an editor and 'find' error....

Martin

Hi Martin!

Thank´s for reply. Yes my FC is update 100 %. You said it compile for you, strange. After you said that, I tryed to compile on my other labtop, but still same error. As far I can se in the compiler message it look like some "some string" problem, but I don´t know what it mean´s.?
Well, pity I used many hours on the program and suddently it will not compile anymore.

I think I will export all the macros and then delete them in my program and then try again step by step import angain, otherwice I will try to create some similar same program using an Arduino and a keypad and LCD display. But I like these ILI9488 disply

Thank´s

Jorgen

Hi Jorgen.
Sorry to hear about the issue you have with compiling.
Can you please try the following as a temporary solution?
Select Help>Library Updates...
Leave the dropdown to Files in-use.
Select Show up-to-date files tick box.
Select ESP\ESP_CAL_I2C.c tick box
Change New Revision for ESP\ESP_CAL_I2C.c from 10 to 9 Select Download, then reload your project and compile it again.

Thanks Martin - looks like I'm not up to date

Hi Martin!

I try your suggest, but Iam not able to get 9 when I press the download nothing happen, the Download buttom is also "ghostet". not active.?

Jorgen

Hi Martin!

I have to tick on "filename" too, then I could downgrade to 9. And yes, I can Compile again, but the XPT2046 doesn´t work now, before this work I cant tell you of the BH1750 working, can´t go to next screen?

So far thank´s Martin Hope you can solve the rest too

EDIT ******** My fault, it´s working Martin *******

I can compile and all seem to work. Does it mean everytime I have made an update I have to go back to 9 ?

You just saved many hours work, thank´s

Jorgen

Hi Jorgen.
I'm glad it's all working for you now.

jgu1 wrote: ↑

Sun Jan 22, 2023 2:34 pm

I can compile and all seem to work. Does it mean everytime I have made an update I have to go back to 9 ?

No, this will be sorted during working hours as soon as possible.

jgu1 wrote: ↑

Sun Jan 22, 2023 2:34 pm

You just saved many hours work, thank´s

mnfisher wrote: ↑

Sun Jan 22, 2023 1:15 pm

Thanks Martin - looks like I'm not up to date

You're both welcome.

Hello,

Many thanks for letting us know, the latest change was to allow the I2C transaction to be re-initialised without reinstalling the I2C driver. Some components use this to flick between several sub devices and it was a little inefficient.

I've hopefully solved the compilation problem for you now in the latest version (v11) on the library update system.

The fix was applied to all devices but the ESP32 compiler is very strict and so this is the only one that complained.

It is possible to reduce the number of warnings the compiler generates but it means editing one of the files within the IPE folder. I'll see if I can dig out the information.