2024-12-09 12:09 AM - edited 2024-12-09 07:08 AM
Hi,
I am posting this question, same as I have posted on the stackoverflow to find some clues into my problem.
I had been programming my STM32F407 MCU for almost 6 years using OpenOCD's GPIO Bit bang driver over Raspberry-pi for Serial Wire Debug for almost all kinds of projects. Yesterday, I started developing for the USB device driver on my MCU and after the first flash, I am no longer able to connect to it via OpenOCD GPIO Bit Bang driver.
I am successfully able to do everything using OpenOCD with STLink; however, I am not able to connect to DP, using bit band SWD driver of openocd, even if I mass erase the flash and reset everything using stm32cube programmer first. All the option bytes show that everything is as it should be to allow connecting and writing to flash memory.
Does USB development cause any side effects which I am not aware of ? Did anyone face a similar issue before? My physical connections are not a problem. Sometimes I see messages like Wrong Parity Error. I am not sure why that would appear.
I will be looking forward to some relevant guidelines or pointers to understand this problem.
Regards,
Junaid
2024-12-09 06:37 AM
@Neolithic wrote:I am posting this question here along with stack overflow
Please give a link to the other thread - so that all contributors can see the whole story.
2024-12-09 06:39 AM
I have put the exact same question there. This is just in case if someone is not available on this forum and has the knowledge.
2024-12-09 06:56 AM
So please give a link to that post - so people here don't end up repeating here what's already been said there.
And vice-versa.
2024-12-09 07:08 AM
Original Message edited to contain link of stackoverflow post.
2024-12-09 07:19 AM
Thanks.
And don't forget to post a link on Stackoverflow back to here.