Flaky connections with J-Link and STM32H747 on Crossworks 5.1?

Follow

Ray Rischpater

• November 04, 2024 20:39

Subject pretty much says it all. We've been chalking this up to being on older versions of Crossworks, and recently renewed our licenses and upgraded for lots of reasons, and switched from ST-Link to J-Link Ultra+ JTAG interfaces.

We're debugging on two cores, with two instances of Crossworks open -- one for the CM7 core and one for the CM4 core. When it works, it's the bee's knees.

Intermittently -- it usually happens once every thirty or so debug sessions, sometimes a little more often --- one or the other core will fail after flashing with a target processor mismatch error. Typically quitting Crossworks in both instances and restarting seems to fix it; occasionally we don't even have to do that, but do the Target -> Reconnect option and we're off and running again.

Has anyone else seen this? Any suggestions?

Thanks!

 

 

0

• 

  Michael Johnson

  • November 05, 2024 08:22

  The project property "Debug | Target Control | Connect With Reset" may help.

  0

  Comment actions Permalink
• 

  Ray Rischpater

  • November 05, 2024 20:39

  Thanks! I'll give that a go.

  0

  Comment actions Permalink

Please sign in to leave a comment.