I plan to do some firmware development on the OpenMV platform and I’d like to know if it’s possible to use an st-link debugger.
I can see that SWCLK, SWDIO adn nRST are available on the headers, but not SWO (PB3).
Yes, Ibrahim used it previously to find the source of a serious bug on the platform. That said, I have no idea how he did this. He can respond with details.
I’ve used both the embedded debugger and “official” st-link (and a debugger found on ebay). You’ll need to connect the two wires data/clock, GND (don’t forget it!) and target VDD (that’s 3.3vout from the cam to the board) see the discovery pinout.
Hi,
Can you please help me to connect (ST-link v2) debugger > https://www.st.com/en/development-tools/st-link-v2.html > to the OpenMV M7 board please? Is there any image/video/document to explain this? Thanks in advance.
It’s very straightforward, you just need to connect SWC->SWC, SWD->SWD, TRST->RST, Target VCC->3.3v and GND->GND to the debugging header on the OpenMV camera. See the stlink datasheet for the pinout.
I have connected the stlink to my openmv camera but when I type st-info --probe continuously, the memory keeps on changing. Is this correct? I am using the latest version stlink from texane, and have updated the st-link firmware using st utility tool. I have also tried the stm32 utility in Windows to connect to the device but failed.
I’m not sure, but I don’t think the st-util stlink sw supports the H7, at least last time I checked it didn’t, note this post is really old probably was targeted at the F7 cams…FWIW I moved on to JLinks they work great.