cancel
Showing results for 
Search instead for 
Did you mean: 

NeoChrom/GPU2D registers documentation

robvos
Associate

Will this peripheral ever be documented in detail? i.e. registers, interrupts, etc.

Or even a lightweight/low level library would be acceptable.

We may choose STM32U5 for a product but not if we are forced to use TouchGFX for good performance.

 

55 REPLIES 55

Just some demos on a STM32U5G9J-DK2 discovery kit with STM32U5G9ZJ MCU, using NemaGFX, without TouchGFX or LVGL used.

The buttons, gauge, and VU meter doesn't use any bitmaps, they are rendered by the GPU2D.

The only bitmaps in the demo are the icons. The gauge now uses such an icon in it.

The uploaded video is not as smooth and sharp as the display, somehow. There's lots of compression in it.

My phone's camera isn't very good as well.

The breakoutboard on the left is an RTC (RV-8803)

Here are the linkd to it, enjoy!

https://www.youtube.com/watch?v=6FTJtO-PlJ0

https://www.youtube.com/watch?v=xZ7B-uTisew

chrome_EKAUKkxneQ.png

Text rotation and gradiation

chrome_C2hNM1ghTQ.png

No bitmaps, except the white icons:

chrome_ZNHgOfDJ0e.png

Smoothly animating graph

chrome_me5lFnslf3.png

 

I created a per-pixel scalable font and text library. This text took 1ms to display on the screen.
The text is also 360-degree rotatable (float).

Scalable_Font.jpg

I just received the STM32H7S78-DK discovery kit with STM32H7S7L8 MCU.

Artur Laskowski
Associate II

As I see, the NeoChrom SDK is still not available from the ST webpage, right? What a shame.

Amazing, thank you for sharing.

I do not think ST will ever release it publicly. My assumption is simply that negotiations around publication rights or licensing permission did not conclude successfully.

Nothing to worry about — it appears that ST’s partnership with Think Silicon, the Greek company behind the NEMA GPU, has run its course. If this is the case, I do not blame ST. It is fair to say that negotiations with companies operating within the Greek business and legal framework can be more complex and time-consuming than expected, even for arrangements that might otherwise seem straightforward.

Notably, ST’s latest announced “game changer”, the STM32V8, seems not to include a modern GPU at all. The prior flagship STM32N6 only excluded vector graphics support. Of course, there is no free lunch — a vector graphics requires an additional dedicated SDRAM framebuffer. Realistically 4MB would be a more practical minimum for fully utilizing a vector GPU at resolutions like 1024×768. With 3MB, the headroom is tight if the goal is to run more complex graphics or unlock the vector graphics GPU’s full potential.

In my view, a much bigger concern is that STM32N6 have launched without MIPI-DSI support. This trend is disappointing, as reliable driving of a 1024×768 LCD over LTDC (or even 800x600) is not feasible — bandwidth, pin count, and signal integrity all become limiting factors. The interface also demands too many pins, making high-resolution display designs unnecessarily difficult.

If this trend continues and the STM32V8 also launches without MIPI-DSI (which I do not know), the STM32U5G9 may become the last STM32 microcontroller that even partially meets my design requirements (with the note that its FDCAN implementation has been functionally constrained). It currently appears to be the final device in the portfolio to offer native MIPI-DSI support. Without this interface, the feasibility of reliably driving 1024×768 displays in future STM32-based embedded designs becomes highly uncertain.


@TDJ wrote:

I do not think ST will ever release it publicly. My assumption is simply that negotiations around publication rights or licensing permission did not conclude successfully.

Nothing to worry about — it appears that ST’s partnership with Think Silicon, the Greek company behind the NEMA GPU, has run its course. If this is the case, I do not blame ST. It is fair to say that negotiations with companies operating within the Greek business and legal framework can be more complex and time-consuming than expected, even for arrangements that might otherwise seem straightforward.

That would be a great shame. An ideal situation for me is that a low-level API/ABI for the GPU is provided, like for ARM cores. I could handle the rest without bloated or closed frameworks like TouchGFX.


@TDJ wrote:

Notably, ST’s latest announced “game changer,” the STM32V8, seems not to include a modern GPU at all. The prior flagship STM32N6 only did not include vector graphics support. Of course, there is no free lunch — a vector graphics requires a dedicated SDRAM framebuffer. Realistically 4MB would be a more practical minimum for fully utilizing a vector GPU at resolutions like 1024×768. With 3MB, the headroom is tight if the goal is to run more complex graphics or unlock the vector graphics GPU’s full potential.

In my view, a much bigger concern is that STM32N6 have launched without MIPI-DSI support. This trend is disappointing, as reliable driving of a 1024×768 LCD over LTDC (or even 800x600) is not feasible — bandwidth, pin count, and signal integrity all become limiting factors. The interface also demands too many pins, making high-resolution display designs unnecessarily difficult.

If this trend continues and the STM32V8 also launches without MIPI-DSI (which I do not know), the STM32U5G9 may become the last STM32 microcontroller that even partially meets my design requirements (with the note that its FDCAN implementation has been functionally constrained). It currently appears to be the final device in the portfolio to offer native MIPI-DSI support. Without this interface, the feasibility of reliably driving 1024×768 displays in future STM32-based embedded designs becomes highly uncertain.


True, I have also seen that the STM32V8 lacks some more advanced graphics peripherals, such as a GPU and MIPI DSI, which is quite disappointing. I thought I could use it in some of my projects, but the lack of those peripherals halted me from considering this. I've got some projects with untypical ultra-wide displays that use only MIPI DSI, and I'm not going to use an external chip to convert LTDC to MIPI DSI–I'd rather choose a solution from the other company.

Another thing is that the MIPI DSI is just a hardware wrapper around LTDC interface and is only available on chips with a large number of mostly unused pins, making the board unnecessarily large.

 

@Artur Laskowski Cześć, Very true - the smallest package with MIPI-DSI is 100-pin, even though a much smaller 64-pin option would be entirely feasible.
What disappoints me the most is that ST is finally going to release the STM32V8 with 4 MB of SDRAM, yet at the same time they're removing MIPI-DSI (probably) and the GPU - the very features that benefit most from that extra 1 MB, especially for driving higher-resolution graphics like 800×600 or 1024×768. This strategy just doesn't make sense to me. It almost feels like ST is trying to replace solid graphics capabilities with AI instead. I have to admit - I'm puzzled.