About AGaun.1

AGaun.1 · 2022-01-26

I have built a simple gui using TouchGFX 4.18.0 for my H747I-DISCO. I also need to use I2C to read some sensors, so I have used CubeMX 6.4.0 to enable I2C4 (and also the NVIC interrupts), and generated the code.When I try to compile this in CubeIDE 1...

AGaun.1 · 2022-05-04

I'm glad you found a fix for it, even if it required renaming a function.I was using an I2C thermocouple board on I2C4, which worked absolutely fine when I wrote a test program with no touchscreen and the touchscreen worked fine when I used it on its...

AGaun.1 · 2022-05-03

As far as I can tell, the touchscreen requires the same pins that I2C4 use. If you use CubeMX with touchGFX, and also enable I2C4, it will not show as an error or a conflict, and will generate code for both which results in code which conflicts. With...

AGaun.1 · 2022-02-23

I realised that I never posted about what I found out.After much testing, and trying things out between two different H747 disco boards, I also came to the conclusion that it was probably a conflict between the touchscreen/TouchGFX and I2C4. It would...

User statistics

User Activity

How can I resolve a conflicting type error from automatically generated TouchGFX/cubeMX code?

Re: How can I resolve a conflicting type error from automatically generated TouchGFX/cubeMX code?

Re: How can I resolve a conflicting type error from automatically generated TouchGFX/cubeMX code?

Re: How can I resolve a conflicting type error from automatically generated TouchGFX/cubeMX code?