2023-07-18 01:04 AM - edited 2024-05-14 07:40 AM
When forum regulars look at your question, they're looking for a few things:
1. They want to quickly figure out what you're actually asking, so they can decide whether to try and help or move on.
2. They need to know what you're trying to achieve, not just what you tried to do that isn't working out.
3. Once they decide to help, they need as much relevant information as possible. If you include that information it to begin with, you save everyone the trouble of going back and forth asking for further information.
Some general tips here on How To Debug your problem:
https://www.avrfreaks.net/s/topic/a5C3l000000UaFXEA0/t153137?comment=P-1212908
Earlier in that thread, some tips specifically on Debugging Serial Comms:
https://www.avrfreaks.net/s/topic/a5C3l000000UaFXEA0/t153137?comment=P-1212903
Expanded explanation: https://www.avrfreaks.net/s/topic/a5C3l000000UaFXEA0/t153137?comment=P-1212905
#HowToDebug #DebugSerialComms
When your problem is solved, remember to mark the solution:
https://community.st.com/t5/community-guidelines/help-others-to-solve-their-issues/ta-p/575256
Some general resources on debugging Cortex-M Hard Faults:
https://community.arm.com/support-forums/f/embedded-forum/3257/debugging-a-cortex-m0-hard-fault
Specifically for STM32 and the CubeIDE:
https://community.st.com/t5/stm32-mcus/how-to-debug-a-hardfault-on-an-arm-cortex-m-stm32/ta-p/672235
Hi @Andrew Neil and @BarryWhit , great inputs, thanks a lot for sharing them!