How to use the LCD in the f429i discovery board with CubeIDE? In the old cubemx examples there are rich libraries to draw, write, etc on LCD, but they're not updated to the CubeIDE Hal drivers.

[MAles.1]

You can import demo projects from the Cube package downloaded by the IDE, but you cannot integrate the libraries in a CubeIDE project, because they use different drivers. All you're left with in the new IDE is low-level functions. Is there a software package suitable for that? It's sad that even much of official ST documentation for boards still refer to pre-cubeIDE era.

[TDK]

It seems like TouchGFX is the supported graphics solution from ST. There are a number of hits for "f429 discovery touchgfx" if you search.

[MAles.1]

Thank you, it was not very clear from the package name and description it it was suitable.

Anyway, I find it a little "overkilled" just to use a peripheral, if you don't want to design a full GUI application.

I created the project from "Software packs" in the ioc and I'm getting a link error, from what I read you have to create a C++ project, and that's another problem, I think it's an unneeded overhead for common applications.

I don't know what's the vision for the future of embedded development, but what would be needed in my opinion are simple software libraries (headers, c code and/or binary libraries) that can be easily integrated in your project, not the other way around.

[MM..1]

Maybe you missunderstand HAL. Abstraction layer for hardware inside MCU , not outside. LCD draw, write cant be part of HAL...

And LCD is Nxbigger amount of combination as one HAL peripheral driver...

[TDK]

Okay, well the solution is out there. If you don't want to use it or think it's bad or would design it differently, that's fine.

Old code still works. If you liked what was done in the past, just keep using that.

[waclawek.jan]

https://github.com/STMicroelectronics/STM32CubeF4/blob/master/Drivers/BSP/STM32F429I-Discovery/stm32f429i_discovery_lcd.c /.h ?

JW

[MAles.1]

I think that's the same as the cube package that's downloaded by the IDE.

[waclawek.jan]

Yes, and what's the problem with it?

JW

[MAles.1]

I'll try to explain the problem better: does ST want us to use the new IDE or not? Because before you had examples, demos and convenient libraries, while there's nothing similar now.

You can import a project from the cube package, that's a sort of work around, you import one of the projects that are eclipse-based and it works, but then you have no device configurator, initialization of pripherals is different, etc.

The various documents still refer to the projects in cube-style, I still have not seen cubeIDE mentioned in documents regarding software development. ​

[waclawek.jan]

> does ST want us to use the new IDE or not? 

ST's business are chips, not software. They provide software only as a vehicle to sell chips. Chips are sold to managers, not engineers, so Cubes are provided for managers who want to hear that it is easy to make firmware by relatively unskilled workforce by clicking, here are the tools for free.

Cube as a library predated CubeMX and CubeIDE and there was a huge effort to convert most the existing SPL-based examples to Cube. The investment to convert it again into CubeMX/CubeIDE simply won't pay off.

JW