1 ACCEPTED SOLUTION
Accepted Solutions
Ohh boy zero info... Try this
run simultor and press A key on keyboard Work transition ?
Interaction1 in my example is add on main screen (FYI your screen marked to start) and transition go to Screen1...
When this works ok you can step to physical button code ...
Hi,
I already have a different hardware button implemented for a separate function so I believe this is working correctly.
Sorry if I haven't provided enough info, I'll drop some code in below that i have tried so far.
Button setup in TouchGFX:
This is the cpp file as created in the youtube video provided by STM.
#include <newButtonController.hpp>
#include <main.h>
#include <touchgfx/hal/HAL.hpp>
extern "C" uint8_t User_ButtonState;
void newButtonController::init()
{
previousState = 0xFF;
}
bool newButtonController::sample(uint8_t& key)
{
if(HAL_GPIO_ReadPin(GPIOD, GPIO_PIN_2) == GPIO_PIN_RESET && previousState == 0x00)
{
previousState = 0xFF;
key = 1; // here key determines which key will be trigger in TouchGFX
return true;
}
previousState = 0x00;
return false;
}And this the header file:
#ifndef NEWBUTTONCONTROLLER_HPP_
#define NEWBUTTONCONTROLLER_HPP_
#include <platform/driver/button/ButtonController.hpp>
class newButtonController : public touchgfx::ButtonController
{
virtual void init();
virtual bool sample(uint8_t& key);
private:
uint8_t previousState;
};
#endif /* NEWBUTTONCONTROLLER_HPP_ */Finally the modified TouchGFXHAL.cpp file:
#include <TouchGFXHAL.hpp>
/* USER CODE BEGIN TouchGFXHAL.cpp */
#include "main.h"
#include <newButtonController.hpp>
newButtonController bc;
using namespace touchgfx;
extern "C" uint8_t framebuffer[800 * 480];
void TouchGFXHAL::initialize()
{
// Calling parent implementation of initialize().
//
// To overwrite the generated implementation, omit the call to the parent function
// and implement the needed functionality here.
// Please note, HAL::initialize() must be called to initialize the framework.
/*
*/
TouchGFXGeneratedHAL::initialize();
// Set the framebuffer start address
HAL::getInstance()->setFrameBufferStartAddresses(
framebuffer, // Framebuffer for the first layer (internal memory)
nullptr, // Framebuffer for the second layer (if unused, set to nullptr)
nullptr // Framebuffer for the third layer (if unused, set to nullptr)
);
setButtonController(&bc);
}And here is how the button is configured in the ioc file:
Thanks again,
Josh
Hello @Josh_W020 ,
From what I understood, you are sure that the button itself works and you are sure that you are able to do a screen transition.
So the issue must be between connecting these 2 actions.
We provide examples of boards and UI using hardware buttons with the GFX01M2 display extension.
One of the GUI using hardware button is the "Aircon remote demo":
Instead of adding a hardware button to TouchGFX Designer (which is possible), we mapped it to a keyboard key.
This way, we can execute an interaction from pressing a key on the keyboard (when simulating for instance) and we are also able to map our physical button to execute the interaction.
Here you can see that the interaction is executed when pressing the key '8' :
And here you can see how we mapped the hardware button to a key in MB1642ButtonController.cpp :
I hope this example is helpful to you!
Regards,
