Closed Kheavenin closed 2 years ago
RKOUSTM
commented
3 years ago Hi @WojciechBernat,
First we would like to thank you for your report.
In order to allow a better analysis of your problem, could you please confirm when using the latest CubeMX version v6.3.0 that the issue is systematically reproducible on your side ? Could you please give us the .ioc file that you are used to reproduce this issue, so that we can give you an answer.
Thank you again for your report.
With regards,
Kheavenin
commented
3 years ago Hi
I am attaching a .ioc file. It was generated in STM32CubeIDE Version: 1.7.0 Build: 10852_20210715_0634 (UTC).
STM32CubeMX - STM32 Device Configuration Tool Version: 6.3.0-RC5 Build: 20210714-1111 (UTC) STM32CubeIDE - C/C++ Embedded Development Tools for MCU Version: 2.0.0.202105061353
I checked this in few projects base on F411. Also checked on two F411 boards. In my request I wrote abote CubeIDE ver. 1.6.1, it's not true. I have ver. 1.7.0 - sorry my mistake.
Best regards, Wojciech
wt., 5 paź 2021 o 10:37 RKOUSTM @.***> napisał(a):
Hi @WojciechBernat https://github.com/WojciechBernat,
First we would like to thank you for your report.
In order to allow a better analysis of your problem, could you please confirm when using the latest CubeMX version v6.3.0 that the issue is systematically reproducible on your side ? Could you please give us the .ioc file that you are used to reproduce this issue, so that we can give you an answer.
Thank you again for your report.
With regards,
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/STMicroelectronics/stm32f4xx_hal_driver/issues/6#issuecomment-934191684, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMDNUFZMJNLCKUFRYM4Z2IDUFK2LDANCNFSM5FGN3EEA . 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.
RKOUSTM
commented
3 years ago Hi @WojciechBernat,
Thank you for your reply. However, I don't see the .ioc file in your reply, so it seems there is a problem.
With regards,
Kheavenin
commented
3 years ago Hi
I attached again file.
With regards, Wojciech
śr., 6 paź 2021 o 20:16 RKOUSTM @.***> napisał(a):
Hi @WojciechBernat https://github.com/WojciechBernat,
Thank you for your reply. However, I don't see your .ioc file in your reply, so it seems there is a problem.
With regards,
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/STMicroelectronics/stm32f4xx_hal_driver/issues/6#issuecomment-936831951, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMDNUF6B7RDQM6PICKBF47DUFSG7FANCNFSM5FGN3EEA . 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.
RKOUSTM
commented
3 years ago Hi @WojciechBernat,
Thank you for your feedback. Indeed, I didn't receive any .ioc file from you. Please see the screenshot below of your comment box:
To attach the .ioc file to your issue, please drag-and-drop it into the comment box or you can click on the bar at the bottom of the comment box to add it from your computer and then wait for the upload process to finish.
With regards,
Kheavenin
commented
3 years ago RKOUSTM
commented
2 years ago Hi @WojciechBernat,
Thank you for your contribution. The point you reported is related to the CubeMX generation problem and not directly related to the firmware published in this repository. Unfortunately we don't treat aspect related to CubeMX tool in our GitHub repositories.
Now, as this issue is not directly related to some software component published within this repository (CMSIS, HAL, BSP, etc.) but rather to our ecosystem (namely the Cube MX tool), please allow me to close it.
Thank you for your contribution. We are looking forward to reading from you again.
With regards,
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 your report to the ST Community in the STM32 MCUs dedicated page.
Describe the set-up STM32F411E-Disco STM32CubeIDE 1.6.1 FW: 1.26.2 MCU package
Describe the bug (skip if none) Issue with MX_GPIO_Init() which works for this information: 'Target is not responding, retrying...' - You can see this in Debuge mode. Connection with board broken. Few month age this code work pretty good, so I think that problems is in new firmware.
I checked MX_GPIO_Init() and found after which line this problem occurred. MX_GPIO_Init() -> HAL_GPIO_Init(GPIOA, &GPIO_InitStruct) ( in my code it's line 74) -> GPIOx->MODER = temp; ///In this line issue occu ( line: 232)
When I turned off 'Set all free pins as analog ( to optimize the power consumption)' error didn't occur and program went straight to while().
A clear and concise description of what the bug is.
How to reproduce the bug (skip if none) Try simple configuration for STM32F411 stock board. Set some GPIO and in 'Project manager' tab set 'Set all free pins as analog'.
If you want some additional information, please write to me: wojciechbernat95@gmail.com
Your sincerely, Wojciech