Closed theadib closed 2 years ago
ALABSTM
commented
2 years ago Hi @theadib,
Thank you for this report. We will get back to you with a feedback as soon as possible. Please excuse the delay it may take us sometimes to reply. Thank you for your comprehension.
With regards,
RKOUSTM
commented
2 years ago Hi @theadib,
Thank you for your report. Actually, the point you reported is not directly related to the firmware published in this repository and is out of the scope of STMicroelectronics' activity. They are rather treated at ST Community level. Please allow me to redirect you to address your request in this discussion section where the same issue is addressed.
Thank you again for your report. We are looking forward to reading from you again.
With regards,
theadib
commented
2 years ago Hello RKOUSTM,
it is quite easy to ignore that issue. Of course the TSM32F4 libs per se does not have this issue.
The issue is the generated project files by STM32CubeMX application. So it is definitely NOT an STCommunity issue.
Please follow up this issue in a more professional manner. And assign that issue to the STM32CubeMX team.
In the last time I am more and more disappointed by the way how ST treat his customers.
In the hope the words are heard ....
Regards,
On Fri, Mar 4, 2022 at 2:16 PM RKOUSTM @.***> wrote:
Hi @theadib https://github.com/theadib,
Thank you for your report. Actually, the point you reported is not directly related to the firmware published in this repository and is out of the scope of STMicroelectronics' activity. They are rather treated at ST Community https://community.st.com/s/group/0F90X000000AXsASAW/stm32-mcus level. Please allow me to redirect you to address your request in this https://community.st.com/s/question/0D50X00009XkYmMSAV/stm32f407-2-ram-banks discussion section where the same issue is addressed.
Thank you again for your report. We are looking forward to reading from you again.
With regards,
— Reply to this email directly, view it on GitHub https://github.com/STMicroelectronics/STM32CubeF4/issues/107#issuecomment-1059153629, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFMAKRVCYETYTGCAE74FXGLU6IELZANCNFSM5K6IAD5A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
RKOUSTM
commented
2 years ago Hi @theadib,
I hope you are fine. The issue you reported has been logged into an internal bug tracker. The fix will be made available in the frame of a future CubeMX release.
However, as it is related to the ecosystem (namely the Cube MX tool) rather than the firmware published within this repository (CMSIS, HAL, BSP, etc.), please allow me to keep this thread closed.
In case you have other CubeMX-related issues to share, please submit them in the ST Community in the CubeMX related section. There you shall find people who will address your request and whom you will hopefully find a solution with.
Thank you for your comprehension and thank you again for having reported.
With regards,
RKOUSTM
commented
2 years ago ST Internal Reference: 124011
theadib
commented
2 years ago Merci. Adib.
On Tue, Mar 8, 2022 at 12:51 PM RKOUSTM @.***> wrote:
ST Internal Reference: 124011
— Reply to this email directly, view it on GitHub https://github.com/STMicroelectronics/STM32CubeF4/issues/107#issuecomment-1061696923, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFMAKRQEW6R6553BUH7ZZEDU645LHANCNFSM5K6IAD5A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
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 most recent versions I use as of 2021-12-29
Describe the bug The STM32F437VG has several RAM sections that can be attributed by the IDE tools 1) 3 blocks SRAM @2000.0000h: 112kB, 16kB, 64kB, in total 196kB 2) 1 block CCM RAM @1000.0000h, 64kB
The first 3 blocks are in consecutive order with no gaps in between. For those 3 blocks the IDE has only 1(one) entry in the graphical representation.
this is the problem: If I have a large memory block reserved as DMA buffer. And that buffer spans over the boundries of 1(one) of these blocks. Then DMA will fail/stop.
in my case I used a large buffer as DMA buffer for the lwip stack
uint32_t dmabuffer[90kByte/4];But as there where other variables declared before that, the 90kByte block spanned from the first over to the second RAM block. The DMA failed under this memory layout because the DMA has problems when accessing several RAM modules.As the number of RAM blocks addresseable in the GUI is very limited an other method should be chosen to define MEMORY layout. Keil has the ability to create special scatter linker files. probably that should be the method to address this issue.
How To Reproduce
Indicate the global behavior of your application project.
The modules that you suspect to be the cause of the problem (Driver, BSP, MW ...).
The use case that generates the problem.
How we can reproduce the problem.
Additional context If you have a first analysis or patch correction, thank you to share your proposal.
Screenshots If applicable, add screenshots to help explain your problem.
