1 Answer

0 votes
by

Hello.

It seems that your question is not complete - there are just a few pictures.

Please try to follow the Getting Started with STM32F469 Discovery Board and describe what you have done and what does not work. The more details you provide the better help you can expect.

Best regards,

Manfred.

by
hello thank you for your answer. please see this link it is what I am doing , but keil do not compiling project:https: //youtu.be/X19Tl113mkQ

also when I writin hex file from folder: STM32F469-Discovery\MasterDemo

with FlashMasterDemo.bat double clicking, writes ok but touch do not working, automaticaly showing demo examples In sequence, but touch do not have any sense
by
Hello,

if the touch does not work with the provided binary - maybe your board has some hardware issues. Can you try another one?

Your linked video cannot be accessed - it is a private video. But maybe you can just post the first error messages you get within the KEIL IDE.

Best regards,

Manfred.
by

hello. thank you.

when i compiling my test GUI with TouchGFX 4.13.0 Designer and run it all is ok and touch working perfect. but with embedded wizard do not working.

I change permission

please see: https://www.youtube.com/watch?v=X19Tl113mkQ

 

 

compiling ew_bsp_event.c...
..\..\..\ThirdParty\STM32Cube_FW_F4\MiddleWares\Third_Party\FreeRTOS\Source\portable\GCC\ARM_CM4F\portmacro.h(134): error:  #18: expected a ")"
          __asm volatile ( "clz %0, %1" : "=r" ( ucReturn ) : "r" ( ulBitmap ) : "memory" );
..\..\..\ThirdParty\STM32Cube_FW_F4\MiddleWares\Third_Party\FreeRTOS\Source\portable\GCC\ARM_CM4F\portmacro.h(175): error:  #18: expected a ")"
      __asm volatile( "mrs %0, ipsr" : "=r"( ulCurrentInterrupt ) :: "memory" );
..\..\..\ThirdParty\STM32Cube_FW_F4\MiddleWares\Third_Party\FreeRTOS\Source\portable\GCC\ARM_CM4F\portmacro.h(201): error:  #18: expected a ")"
          :"=r" (ulNewBASEPRI) : "i" ( configMAX_SYSCALL_INTERRUPT_PRIORITY ) : "memory"
..\..\..\ThirdParty\STM32Cube_FW_F4\MiddleWares\Third_Party\FreeRTOS\Source\portable\GCC\ARM_CM4F\portmacro.h(193): warning:  #177-D: variable "ulNewBASEPRI" was declared but never referenced
  uint32_t ulNewBASEPRI;
..\..\..\ThirdParty\STM32Cube_FW_F4\MiddleWares\Third_Party\FreeRTOS\Source\portable\GCC\ARM_CM4F\portmacro.h(218): error:  #18: expected a ")"
          :"=r" (ulOriginalBASEPRI), "=r" (ulNewBASEPRI) : "i" ( configMAX_SYSCALL_INTERRUPT_PRIORITY ) : "memory"
..\..\..\ThirdParty\STM32Cube_FW_F4\MiddleWares\Third_Party\FreeRTOS\Source\portable\GCC\ARM_CM4F\portmacro.h(209): warning:  #177-D: variable "ulNewBASEPRI" was declared but never referenced
  uint32_t ulOriginalBASEPRI, ulNewBASEPRI;
..\..\..\ThirdParty\STM32Cube_FW_F4\MiddleWares\Third_Party\FreeRTOS\Source\portable\GCC\ARM_CM4F\portmacro.h(231): error:  #18: expected a ")"
          "    msr basepri, %0    " :: "r" ( ulNewMaskValue ) : "memory"
..\..\..\TargetSpecific\ew_bsp_event.c: 2 warnings, 5 errors

 

firs error linked here into sources file ew_bsp_event.c:

 

    /* Generic helper function. */
    __attribute__( ( always_inline ) ) static inline uint8_t ucPortCountLeadingZeros( uint32_t ulBitmap )
    {
    uint8_t ucReturn;

        __asm volatile ( "clz %0, %1" : "=r" ( ucReturn ) : "r" ( ulBitmap ) : "memory" );
        return ucReturn;
    }

by
Hello and thanks for the provided information.

Concerning the touch driver: Does the Hello World application run, when you create it with GCC?

Concerning the Keil compiler: We tested it with the following version: Keil MDK-ARM Professional Version 5.29.0.0, ARM Compiler 6.13.1 (armclang) - are you using same or similar version?

Best regards,

Manfred.
by
when I compiling with GCC all example aplication runs Including Hello World, but touch do not working In neither case.

 

 I using keil this version:

Toolchain:        MDK-ARM Professional  Version: 5.21a
Toolchain Path:    C:\Keil_v5\ARM\ARMCC\Bin
C Compiler:         Armcc.exe        V5.06 update 3 (build 300)
Assembler:          Armasm.exe        V5.06 update 3 (build 300)
Linker/Locator:     ArmLink.exe        V5.06 update 3 (build 300)
Library Manager:    ArmAr.exe        V5.06 update 3 (build 300)
Hex Converter:      FromElf.exe        V5.06 update 3 (build 300)
CPU DLL:               SARMCM3.DLL          V5.21a
Dialog DLL:         DCM.DLL              V1.13.8.0
Target DLL:             STLink\ST-LINKIII-KEIL_SWO.dll      V2.0.18.0
Dialog DLL:         TCM.DLL              V1.14.14.0
by
Can you post a photo from the back side of the Discovery board - just to compare it with the hardware that we are using for test.

Thanks,

Manfred.
by

I bought from digikey

by

Hi mixo3891,

I just downloaded STM32F469-Discovery.zip (V9.30) again from https://get.embedded-wizard.de/ and I rebuild the HelloWorld project in the same way as shown in you first video.
On  my side build and flash programming with MDK-ARM (V5.29) works correctly and also the touch screen works. I'm using the board STM32F469I-DISCO (MB1189 B-01).

In you video, I noticed, that compiler V5.06 update 3 build 300 is used, although in the keil project file 'Project.uvprojx' '<pCCUsed>6100001::V6.10.1::.\ARMCLANG</pCCUsed>' is set. So, I do not understand, how this can happen. Have you already tried to change the compiler version in the Keil project settings manually?

Regards,
Martin

by
Hi again,

now it seems to be clear what is going wrong with the touch driver: The MB1189 B-01 (old revision) is using FT6206 touch controller (which is supported within the Embedded Wizard Build Environment for STM32F469-Discovery) and the MB1189 B-02 (new revision) seems to use FT6336 touch controller.

So we have to adapt the Build Environment accordingly. First I need to order a B-02 board.

Thanks for reporting the error!

Best regards,

Manfred.
by
I update keil but there is same problem :(

IDE-Version:
&micro;Vision V5.29.0.0
Copyright (C) 2019 ARM Ltd and ARM Germany GmbH. All rights reserved.

Tool Version Numbers:
Toolchain:        MDK-ARM Professional  Version: 5.29.0.0
Toolchain Path:    C:\Keil_v5\ARM\ARMCC\Bin
C Compiler:         Armcc.exe        V5.06 update 6 (build 750)
Assembler:          Armasm.exe        V5.06 update 6 (build 750)
Linker/Locator:     ArmLink.exe        V5.06 update 6 (build 750)
Library Manager:    ArmAr.exe        V5.06 update 6 (build 750)
Hex Converter:      FromElf.exe        V5.06 update 6 (build 750)
CPU DLL:               SARMCM3.DLL          V5.29.0.0
Dialog DLL:         TCM.DLL              V1.36.5.0
Target DLL:             STLink\ST-LINKIII-KEIL_SWO.dll      V3.0.7.0
Dialog DLL:         TCM.DLL              V1.36.5.0
by
keil kompiling problem solved, I clear all output files all cash and with  MDK-ARM Professional  Version: 5.29.0.0 it compiled good and flashed.

but touch still not working. I think there is driver problem, you have MB1189 B-01 version. I have MB1189 B-02 and need other driver
by
please contac me when you fix this error. thank you
by
Hi. I have same problem to STM32F769I-DISCOVERY that has MB1166 A-03 is using FT6X06 touch controller. Is there any adapt problem to Build Environment? Help me please. Thank you.
by
Hi

I have the same problem with the B02. Could you post the information about a solution in this thread?

Thank you

Regards Michi
by
Hello @all,

the board with FT6336 touch controller is already on the way - I will inform you about the workaround/solution as soon as possible. Stay tuned....

Best regards,

Manfred.
by
hello, do you received board with FT6336 controller?
by

Hello @all,

meanwhile I have received a STM32F469-Discovery board with FT6336 and the support for that touch controller is now added to the following Build Environments (version 9.30.01):

STM32F469 Discovery

STM32F469 Evalboard

STM32F769 Discovery

STM32F769 Evalboard

Please download once again the Build Environment for your target - then you should be able to get the touch running...

Thanks to everybody for the feedback!

Best regards,

Manfred.

by

Hello.

I test on STM32F469 Discovery and it works fine thank you!

by
Hello after few testing I found calibration problem, when I touching it touchs on different area on display,

how I can solve this? need calibration.
by
Hello,

you can try the example "ScreenOrientation" to test the touch coordinates. Please note, that the touch coordinates are used as they are provided by the touch driver.

(I have seen that within the driver ft6x06 there is an auto calibration which can be activated by setting TS_AUTO_CALIBRATION_SUPPORTED=1 and which runs for half a minute. Maybe this helps on your board).
by

Hello.

I test on STM32F769I-Discovery and it works fine thank you!

Embedded Wizard Website | Privacy Policy | Imprint

...