Conflict from UART and STLINK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-08-20 11:23 AM
Hi there!
i start to work at one project with STM32G031J. Soo my i have this problem one of the pin is use for reset when i download the program at the same time is configurate a single wire half duplex , and
- i can't simulate
- and it's look like every time i send out data they reset the CPU
Some one can help me
Thank you
Sergio
Solved! Go to Solution.
- Labels:
-
STM32Cube MCU Packages
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-08-20 3:20 PM - edited ‎2024-09-06 6:12 PM
Interesting issue. From the datasheet:
possibly being the most opaque and least helpful footnote imaginable. "Particular care", wtf does that mean? (sigh middle-school typos in technical writing from multi-billion $$$ multi-national. can't they afford a spell-checker?)
As DeLorean foretold, the RM documents the option bytes:
So it's not enough to assign an AF to the pin in CubeMX, you also have to set the option byte to incapacitate the nRST logic.
- Please post an update with details once you've solved your issue. Your experience may help others.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-08-20 11:53 AM
Then you're going to have to make some hard choices..
Test/Debug with a different variant of the part with more pins and dead-bug that into the circuit.
Learn to write code where you don't have to single step it all the time to understand how it executes.
Use serial output to provide telemetry and dynamic analysis of function and flow.
Perhaps you can use a NUCLEO board as a proxy until you have 95% functionality so you aren't fighting the low pin count issue beginning to end.
Up vote any posts that you find helpful, it shows what's working..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-08-20 12:29 PM
Try harder to explain your question clearly.
- Please post an update with details once you've solved your issue. Your experience may help others.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-08-20 2:38 PM
I suppose there's a way to change to utilization of the NRST (Pin 4), either on-the-fly, or via the Option Bytes. Cube might not do it for you, but probably coved in the Reference Manual, etc
Up vote any posts that you find helpful, it shows what's working..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-08-20 3:20 PM - edited ‎2024-09-06 6:12 PM
Interesting issue. From the datasheet:
possibly being the most opaque and least helpful footnote imaginable. "Particular care", wtf does that mean? (sigh middle-school typos in technical writing from multi-billion $$$ multi-national. can't they afford a spell-checker?)
As DeLorean foretold, the RM documents the option bytes:
So it's not enough to assign an AF to the pin in CubeMX, you also have to set the option byte to incapacitate the nRST logic.
- Please post an update with details once you've solved your issue. Your experience may help others.
