Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

STM32F469I-DISCO display does not work on newer board revision (B-08) #1002

Open
hshose opened this issue Apr 16, 2023 · 1 comment · May be fixed by #1003
Open

STM32F469I-DISCO display does not work on newer board revision (B-08) #1002

hshose opened this issue Apr 16, 2023 · 1 comment · May be fixed by #1003

Comments

@hshose
Copy link
Contributor

hshose commented Apr 16, 2023

I have a new STM32F469-DISCO board with marking DK32F469I$AU1 which is supposedly corresponding to a mainboard revision MB1189-F469NIH6-B08, according to STs UM1932 manual:

image

The Board has a a new touch panel and "severl part references updated":
image

When I try to flashing any of the display examples, the display doesn't show anything.

There is a limited datasheet for the FRD400B25025 display in this thread, but for now I didn't find helpful information in there to get the display to work.

The people in this thread seem to have a similar issue and got the ST TouchGFX Desginer 4.21 as response from ST... not sure how easy it is to extract values from that software. However, the thread says, the new driver might be a NT35510 instead of the old otm8009a.

For the NT35510, there is a pretty long datasheet available...
AND... there is an ST Driver for it on github

I also found CubeMX generated Code that is supposedly running this driver.
The USE_STM32469I_DISCO_REVC seems to select the version B08 on the boards marked DK32F469I$AU1.

@hshose hshose linked a pull request Apr 16, 2023 that will close this issue
2 tasks
@rleh
Copy link
Member

rleh commented Jun 27, 2023

Let's see the other DSI status registers, DSI->GPSR: 0x15

LOL 🤣
grafik

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants