Skip to main content
Visitor II
January 27, 2025
Question

Usb host with touch gfx

  • January 27, 2025
  • 2 replies
  • 587 views

Hi everyone..

I am using USB host for communication CDC along with touch GFX for grafix which will use RTOS, The usb is not getting ready after the start state of usb what will be the issue, but when I configure only USB CDC HOST with out touch GFX it is getting ready and communication is happing. After the touch GFX even though for same usb configuration it is not working 

My clock configuration is set to 48mhz ans other clocks are maintained with in the limit, stack size is also increased, priority is also included 

Please suggest some reasons and solution why it is not getting ready

    This topic has been closed for replies.

    2 replies

    Super User
    January 27, 2025

    So you have a working case (without TouchGFX) and a non-working case (with TouchGFX) for the same USB code - yes?

    So compare & contrast the operation of the two.

    See where they differ:

    • what is happening in the working case, that's not happening in the non-working case?
    • what is not happening in the working case, that is happening in the non-working case?

    Instrument your code to give visibility of what's going on ...

    Visitor II
    January 31, 2025

    when we enable rtos it will internally enable the rtos in usb platform and make usb operation depends on RTOS may be this makes usb to not becoming usb ready state, even though stack size is more (1024) and high priority for usb rtos task, i can't disable the usb rtos enable which is given by default when rtos is enabled.

    again the usb_host _request is sending and after that usb_abort will come but with out using rtos it will not go to usb_abort and it will become USB_READY   please help me to solve this issue 

    Technical Moderator
    January 27, 2025

    Hi @Abhishek_nr 

    It seems like the same issue is described here: TouchGFX with USB cdc Host - STMicroelectronics Community

    I suggest you double check if there are any IOs conflicts or any overlapping memory regions.