Skip to main content
This topic has been closed for replies.

2 replies

K.Ata15
Associate II
April 28, 2021

Hey,

Probably your implementation. The FMC is on the 64 bit AXI switch, if you run your code on the M7 core and use the MDMA should be very fast. The 747 unfortunately requires planning and optimisations according to the system architechture (routing, DMA domains, etc.)

K.

HNguy.21
HNguy.21Author
Associate II
April 28, 2021

Thank you for your response, I need to searching more in MDMA as you said.

Tesla DeLorean
Guru
April 28, 2021

The details in the post are a bit superficial.

I'd expect the external interface to actually be clocking slower than 168 MHz, and further slowed by cycle timings.

Why do they even need to be running at 168 MHz, wouldn't the H747 provide for more optimal speeds/settings. A toggling GPIO might be more instructive measurement of relative timing, and data transfer speed.

What controller does the display have? What exactly are you moving across the interface, and from where?

Tips, Buy me a coffee, or three.. PayPal VenmoUp vote any posts that you find helpful, it shows what's working..
HNguy.21
HNguy.21Author
Associate II
April 28, 2021

I config to the same speed in order to see the diff of the LCD rate. Actually, H7 can configure more optimal and I just need it run stable as F4.

My controller is FMC for SRAM, in 8080 series MCU interface.

Tesla DeLorean
Guru
April 28, 2021

>>My controller is FMC for SRAM, in 8080 series MCU interface.

Figured as much, but what controller specifically are we talking about? And what are the timings?

Which memory on the H7 side is the source for the data being moved to the FMC/LCD? How exactly is that transfer occurring? MPU settings? Caching, etc?

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