Hi guys,who knows what the best to connect STM32H743 to a computer for debugging?

You'll need two things

• the hardware interface JTAG or ST-Link
• the software that runs on the computer. An "integrated debugging environment"

Best?

Are we talking about a hobbyist student who is willing to put time and effort into sifting through documentation/youtube/web-searches but can only afford something relatively cheap.

Or a major institution with unlimited budget looking to equip a major research laboratory.

You can't go far wrong starting with the stm32cube software, and an stm32 nucleo/discovery board that has built-in USB-to-jtag/st-link

But when you're designing your own boards you'll want a separate JTAG/ST-Link. ST sell some. I happen to use one by Rowley*. As far as I know there are more expensive ones by Segger (maybe others) that add trace capability.

*I use their commercial Crossworks IDE. I started before stm32cube was around, and I prefer it. But other offerings also exist.

Hope this helps,

Danish

I've order online they made it ! Never had the chance to make it work properly! I was wondering from the software ST there s a method to connect to it through bluetooth or wifi , from ST thisone https://www.st.com/en/development-tools/st-link-v2.html

https://www.st.com/en/evaluation-tools/stm32-nucleo-boards.html even this you mentioned ,my aim is to debug in real time while the device is playing so I'd rather do it even through bluethooth maybe wifi

well is to make the code working fine

1. Normal debugging uses low cost STLink (Debug by Breakpoints, memory view, etc.). You'll want that first for programming and to debug any wireless or other connections you create.
2. UART or USB VCP debugging, where you output diagnostics using your own code, i.e. printf(). With an appropriate IC these could be redirected over wireless, though there will likely be bandwidth limits. I suggest creating ring buffers so your code dumps diag to the ring buffers, and the ring buffers are sent over UART/VCP/wireless as the bandwidth allows. Ring buffers maybe 10K~100K depending on how verbose you are. Include code to handle ringbuffer overflow when you get too verbose :)
3. Full speed real time debugging can use Trace Interface (JTracePro for Cortex M $$$). Be very careful to keep traces from STM32 to connector short, balanced, equal length, etc. See the appropriate app notes. Any issues will limit the MHz the STM32H743 can be traced at. This is way faster than anything wireless can handle, but even with this done perfectly you can probably only run the H743 at half speed before diag info overloads the trace link. You can configure the RCC to slow down the H743 when using Trace, then when debugged recompile with the RCC back to full speed (with appropriate timing corrections in your code). You can use regular STLink functions with H743 at full speed.

Paul

That does look like an impressive board.

We do not need to know what the board is intended to do, but please tell us more about the timing or other requirements for debugging.

For example, if the board controls a high-power motor, where momentarily freezing execution could lead to burned-out windings, then conventional JTAG / ST-Link debugging is difficult. This is because the way JTAG works is that it momentarily freezes the stm32 and instead reads/writes debug information from the internal processor buses. That freezing is extremely quick on a "human" timescale, but could be thousands of processor-clock-cycles.

And your desire for wireless debugging e.g. Bluetooth suggests there might be high voltages present and that you want electrical isolation to protect your PC. If this is the only worry, I seem to remember that ST had an opto-isolated ST-Link.

Years back, people would do "burn-and-crash" debugging - burning fresh code into an eprom, then letting it run - observing the execution and outputs on an oscilloscope or logic-analyser. Then trying to guess where the outputs did not match what was intended and from that deducing what might be wrong with the code. Not easy, but it was all we had.

Things are much easier if you can send debugging information out, but all interfaces (other than direct-writes to LEDs) are also very slow compared with the stm32. Even with a handy JTAG for getting the exact processor state, memory-contents etc at a breakpoint, I like to have a UART for logging near-real-time diagnostics at various points in my code without having to freeze execution. But UARTs are slow, so I have to code a FIFO for my UART.

Hope this helps,

Danish

What connector is on your board?

We have STM32H743 boards with tiny MIPI 10,14,20pin, and we use:

• STLINK-V3MINI STMicroelectronics | Mouser Canada
• I like to use clear heatshrink to cover these
• They are light weight so they don't stress the ribbon cable.

You can also get the STLINK-V3SET, bigger and different connector but same functionality.

Don't get STLINK-V3MODS, it doesn't have a connector.

Segger parts also work (and may also do non-ST ARM MCUs).

If you have an ST demo board you may be able to use its onboard STLINK, see the docs for the board you have.

I wouldn't buy anything except ST or Segger, I've heard some of the knockoffs are flakey, and the STLINK-V3MINI is just so low cost why not get real thing.

Paul

Hmm, I've missed this newsletter )

https://blog.st.com/tapnlink-nfc-st25dv/

sure,I mean presferences and configuration file has to be set better,

so to work on the projects,It has being created meticoulosly well ,

design ether software still to make confidence with it,but I can do it !