search

STMicroelectronics / STM32CubeF4

STM32Cube MCU Full Package for the STM32F4 series - (HAL + LL Drivers, CMSIS Core, CMSIS Device, MW libraries plus a set of Projects running on all boards provided by ST (Nucleo, Evaluation and Discovery Kits))
Other
897 stars 424 forks source link

CubeMX does not handle custom PHY anymore #176

Closed theadib closed 4 months ago

theadib commented 5 months ago

Caution The Issues are strictly limited for the reporting of problem encountered with the software provided in this project. For any other problem related to the STM32 product, the performance, the hardware characteristics and boards, the tools the environment in general, please post a topic in the ST Community/STM32 MCUs forum.

Describe the set-up

Describe the bug A clear and concise description of what the bug is. CubeMX does not handle custom PHY anymore. on older CubeMX, up to version 6.4, CubeMX could handle customization of PHY registers by providing some address and pattern. That can be adapted regarding the used PHY. Now, with CubeMX > 6.4, a BSP is needed. Only 2(two) PHY BSP are provided. There is no documentation howto integrate own custom driver. The generated code makes it very hard for a good customization. The generated lwip.c should call using abstract function name (like phy->isLink()) rather than insert the name of that choosen driver in "dp83...._link()"

How To Reproduce

  1. Indicate the global behavior of your application project.

  2. The modules that you suspect to be the cause of the problem (Driver, BSP, MW ...).

  3. The use case that generates the problem. please provide:

    • a documentation howto create a custom PHY driver that is selecteable in the CubeMX
    • a selecteable "custom" driver that can be extended by the user by placng the known USER sections in the source code

  4. How we can reproduce the problem.

Additional context If you have a first analysis or patch correction, thank you to share your proposal.

I also put something in the forum, but since month there is no response from ST nor it is changed in the CubeMX For me this is rather frustrating.

Screenshots If applicable, add screenshots to help explain your problem.

theadib commented 5 months ago

Hi ALABSTM, I saw you assigned and added labels ... it is related to Ethernet not USB. please change labels of the ticket from USB to Ethernet THanks, Adib.

ALABSTM commented 5 months ago

Hi @theadib,

Thank you for the heads-up. Label updated. Your request has been logged internally. I will keep you informed.

With regards,

ALABSTM commented 5 months ago

ST Internal Reference: 183949

ALABSTM commented 4 months ago

Hi @theadib,

Our development teams acknowledged your point. An update should be available in the frame of version 6.13.0 of STM32CubeMX.

As this issue is not directly related to the firmware published within this repository, please allow me to close it. Thank you for your comprehension and thank you again for having reported.

With regards,