cancel
Showing results for 
Search instead for 
Did you mean: 

NUCLEO-F072RB with the X-NUCLEO-GFX01M2

Rupert
Associate II

Hey everyone, I'm new to the whole STM32 world so bear with me.

I saw that the NUCLEO-F072RB worked with the X-NUCLEO-GFX01M2, but I can't make it work. The touchGFX is grey in the CubeMX and there are no examples in the touchGFX designer with the F series.

I was trying to work with the IDE instead of CubeMX but the result is the same.

I've seen some answers here about porting and making 2 exact setups and transfering the difference from one to the other but I'm really confused on how to solve this problem.

Can anyone help me out?

Regards,

Rupert

1 ACCEPTED SOLUTION

Accepted Solutions

Exactly M0 isnt supported in MX wizard as showed in list MCU TGFX docu ... min is M0+

But maybe manual test Why touchgfx doesn't support stm32f1series mcu's? ... - STMicroelectronics Community

But based on prices is waste time try it... switch to G0

View solution in original post

15 REPLIES 15
MM..1
Chief III

F0 is on edge , but can work . Inspire in

MM1_0-1733240129474.png

 

Thanks for your reply!

What do you mean is on "edge"?

Can work? How?

Do you mean that I should do a project in those templates and wait for its release?

Regards

Edge of power and resources. F071 16k SRAM vs G072 36k SRAM ... speed 48MHZ vs 64Mhz   M0 vs M0+

GFX01 realy work here only in partial framebuffer mode.

Work normal way, create in IDE new project and add TGFX software package to it.

Rupert_0-1733303679317.png

It doesn't work

Only warning and i dont use latest versions , simply click on graphics next level open

MM1_0-1733326033423.png

First install compatible version

MM1_1-1733326556305.png

 

Rupert_1-1733329982451.png

 

Rupert_0-1733329851556.png

I have all the latest versions.

Every version appears like this and I cannot click on it, it's greyed out.

Is the F0 series supported? It's a VERY old platform, and all the resources are focused on newer parts with more memory and capabilities.

The GFX01M1/M2 shields might well fit, and be accessible by other code supporting the display and it's controller, TouchGFX might NOT, being a large resource hog vs something lightweight and tailored to low resource MCU's

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..

Rupert_0-1733331677127.png

Hi, thanks for your input!

I based my choice on this list (display datasheet). So even if only one picture and a button, it should work, right?

My application is simple and should be cheap, maybe I chose too cheap?

Maybe it is as you say, it has x-cube-display and not x-touch gfx? 

I'll try these new things and see if it works, Thanks!

Regards.