This channel is about working with mostly STM32CubeIDE, TouchGFX and ST's development kits.
But I've been using other companies development kits lately. Due to my work I've been using dev kits from TI, Xilinx and Atmel ATtiny. So one day when I get a chance, I'll try and make a video on those kits.
Kits that I have * ST * B-L475E-IOT01A B-U585I-IO02A SensorTile.box STEVAL-PROTEUS1 STM32F072B-DISCO STM32L0538-DISCO STM32F407G-DISCO amzn.to/404rich STM32F429I-DISCO STM32F429I-DISC1 amzn.to/3Qg74Ia STM32F746G-DISCO STM32F769I-DISCO STM32H747I-DISCO STM32H750B-DK STM32MP157C-DK2 NUCLEO-C031C6 NUCLEO-F072RB NUCLEO-F302R8 amzn.to/3s22hli NUCLEO-F334R8 NUCLEO-G431KB NUCLEO-G431RB NUCLEO-L432KC amzn.to/3Q9ioWh NUCLEO-H563ZI NUCLEO-H723ZG P-NUCLEO-LRWAN3
* Microchip * Explorer 16/32 dsPIC33CH512MP508 PIM
Hello, thank you for this tuto but i want to know if it´s possible to interface a SmartEmbedded screen with an toshiba inverter and read out the inverter frequency on the screen by using RS485 wire with Stm32cubeIde and TouchGFX ?
Used this to test Smart Riverdi Display 50STM32U5A9 RS232 - Arduino RS232 shield to expansion port P4-USART1_TX-D1- PG9 -P4-25 AND USART1_RX-D0- PG10 -P4-27 Used TouchGFX v4.23.2, STMCubeMX v6.11.0, X-CUBE-FREERTOS STM32H5/U5/WBA/C0 v1.2.0 and STMCubeIDE v1.5.0 The code had to be updated to use "cmsis_os2.h" and of course all the other STM update improvements? Works with some work! The basic Path “Simple” explanation of what it takes to use TouchGFX is good best I have seen so far.
Hi, great video, by the way, in TouchGFX Designer, there are 3 buttons. Generate code, build (window pops up to test) and build & run. When you finish designing, you just need to click the build & run, and the code is automatically flashed to the board. No need for this complicated stuff. If I understanded this right, this is the same you did. Regards.
Yes i know you can program the development directly from TouchGFX. But then how do you set up UART, PWM, ADC, I2C from TouchGFX? How do you run the debugger from TouchGFX?
Hello. I would like to ask a question. How is that LCD fixed to the pcb? I checked the PCB file provided by STM, but I have no idea how it is fixed. I would appreciate it if you could tell me in detail how it is fixed to the PCB.
Hey, in terms of osSemaphoreRelease(...Handle) function, I understand that this functionality lock/unlock code access of the exectuted thread so that other threads do not have a potential acess to the updating value (of the ADC in this case). So this works like mutexes in terms of lock/unlock for pthread_create() in RTOS, am I understanding the use of osSemaphoreRelease in this sense, correctly?
Dear Mr. Karl First of all, congratulations for you tutorial and to share with us. Dear Karl in my project if I enable freeRTOS, the programs stops working and the display turn off.How can I send data from touchGFX (GUI) to main task (MCU) wthouy freeertos.Could you please send an example. Thanks best regards.
please help, i want to go back to the factory condition on this board. After i debug it with stm32cube i can only see a white screen. I used a binary factory but the touch screen not responsive ther was a game in factory condition and now nothing work. Please help
Hi Karl, I am using STM32F469I-DISCO (DK32F469I$AU1), TouchGFX is version 4.21.1. My app is just a box with a button on it. Code generation and flashing onto the board show no error in TouchGFX, so is building app in STM32CubeIDE (with firmware version FW_F4 V1.27.1) but it just gives blank screen. Tried a few examples and demos on the board too, none worked. I have another made in China board, i can created TouchGFX app and runs fine, but this STMF469I-DISCO just drives me nuts, just could not get it run even a simple app. Any clue ?
Hi i am getting error like this when i debug the project....Drivers/BSP/STM32746G-Discovery/stm32746g_discovery_sd.c:459:35: error: unknown type name 'SD_HandleTypeDef'; did you mean 'TIM_HandleTypeDef'? can you please help me with this
@@Red_Fang. well instead of debouncing for 20ms you can do 2000ms which is 2 seconds which will call your shut down function TimerCallbackTimerStart(&timerCallback, ShutDownFunction, 2000, TIMER_NO_REPEAT);// one shot
Hi, thanks for sharing touchGFX tutorial , I am new to touchgfx, and trying to display float value on TextArea , using following code is working w/o problem. Unicode::snprintf(textArea2Buffer, TEXTAREA1_SIZE, "%d", gTvalue); textArea2.invalidate(); But if I change with floating Unicode::snprintf(textArea4Buffer, TEXTAREA4_SIZE, "%3.1f", gTvalue); I get text -- %3.1f is there anything setting I missing? please advics, thank you.
I ran across a note in the STM community "rename STM32CubeIDE project". It seems the process is much simplified. All that needs be done is to open the .project file and on the first line correct the default name supplied by touchgfx designer (which is the board name). Then when importing the project into the STM32Cube-IDE it will be named appropriately AND there won't be a conflict with the board name attached to the ioc file.
You're partly correct that you only need to rename the one line. But you can't add the IOC file to the project tree without renaming it to the same name as the project. CubeIDE won't open it because it's not the same name as the project. But I did stumble on an easier way to add the IOC file to the project tree and to rename it. Then I realized that it fixes the issue with TouchGFX not finding the board name unless you rename the text as the project name in the .gfx files. But with your insight it helped me find an easier solution😀. I will have to replace this video soon.
@@EEbyKarl Love your videos! For such a noob as myself, they are very useful and informative. As to the naming of the *.ioc file, yep, after posting my original comment I ran across that. It seems ST's product dev teams, as good as they obviously are, could do a bit better job of communicating how the various apps should communicate and interact. It feels like they are SOOO close to having a fairly seamless integration between the gfx design and the Cube-IDE code & compile aspects of development. Distantly related to all the preceeding: I ran across a new channel (STM32 Research) with only a single video so far (posted about 4 months ago). What I found very, very useful was his approach to using the F429i disc1 board and adding a new (2nd) OLED ssd1306 display by hand. First starting the project as if it's a bare mcu (not a board version), configuring the pins for spi, then adding touchgfx to the project and showing the manual edits to get the display up. I found his workflow very straightforward. I need to try his approach to see if it finally gets me to a nice, orderly and repeatable approach to developing some apps for my own use. Please keep publishing! Your information is so very useful!!!🤩
Thx Karl ! It works good. I am using TouchGFX 4.20.0 and STM32CubeIDE 1.10.1. But ioc file doesnt create or linked. So i added link code to .project file then when i created project, it linked a ioc file.
Nice video.I followed your video for stm32f469i disco but it doesn't work.I tried many times but the screen remain black.can you make a video for stm32f469i disco.thanks in advance
The video is titled STM32F469I-DISCO but you go on to do everything on a STM32F429I-DISCO. Is this on purpose and the advise universal for the DISCO boards or an error?
I am using the STM32F429I In some of the files that you have modified, in addition to having 'STM32F429I-DISCO' I also have the following: "STM32F429I_DISCO_REV_E01" Should I replace this as well?
I compiled the github project with errors such as /Middlewares/ST/touchgfx_backup/framework/source/platform/hal/simulator/sdl2/HALSDL2.cpp:18:10: fatal error: SDL2/SDL.h: No such file or directory. Please advise
Is it same process on STM32F469I-DISCO Board...Can i follow that steps on my DISCO board. please reply me...If any video you have then link send me please...
Karl, as many pointed out, the content is great but the background music is annoying and it's even louder than your voice. Great job explaining the hardware GUI interface.