We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Others
Custom
Custom STM32H7A3 based device build.
When CFG_TUD_MEM_DCACHE_ENABLE is set, dwc2_dcache_clean() function is missing.
Build a project using TinyUSB for STM32H7xx with CFG_TUD_MEM_DCACHE_ENABLE set.
N/A
No response
The text was updated successfully, but these errors were encountered:
Please post your build log.
Sorry, something went wrong.
I cannot :(
It's pretty clear though. It seems the data cache handling functions were added for the esp32 target, but were not for the stm32.
A quick fix for the problem is adding the following to the end of dwc2_stm32.h
TU_ATTR_ALWAYS_INLINE static inline bool dwc2_dcache_clean(const void* addr, uint32_t data_size) { data_size = round_up_to_cache_line_size(data_size); SCB_CleanDCache_by_Addr((uint32_t*)addr, data_size); return true; } TU_ATTR_ALWAYS_INLINE static inline bool dwc2_dcache_invalidate(const void* addr, uint32_t data_size) { data_size = round_up_to_cache_line_size(data_size); SCB_InvalidateDCache_by_Addr((uint32_t*)addr, data_size); return true; } TU_ATTR_ALWAYS_INLINE static inline bool dwc2_dcache_clean_invalidate(const void* addr, uint32_t data_size) { SCB_CleanInvalidateDCache_by_Addr((uint32_t*)addr, data_size); return true; }
No branches or pull requests
Operating System
Others
Board
Custom
Firmware
Custom STM32H7A3 based device build.
What happened ?
When CFG_TUD_MEM_DCACHE_ENABLE is set, dwc2_dcache_clean() function is missing.
How to reproduce ?
Build a project using TinyUSB for STM32H7xx with CFG_TUD_MEM_DCACHE_ENABLE set.
Debug Log as txt file (LOG/CFG_TUSB_DEBUG=2)
N/A
Screenshots
No response
I have checked existing issues, dicussion and documentation
The text was updated successfully, but these errors were encountered: