• State Accepted Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 22 subscribers
  • Views 1734 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

strange problem to debug stm32f20x board based via ULINKpro emulator?

DavideG

hi all.

i normally connect to a stm32f20x based board via ULINK2, and it works fine.

i tried with ULINKpro emulator and the it does't work at all. This message is displayed: No ULINK2/ME Device Found.

even if the debug "Use"configuratione has been changed correctly (i think :)) in ULINK Pro Cortex Debugger.

On the other hand, i normally use the ULINKpro emulator (just the same emulator) with board based on stm32h743xx micro, and it works fine.

It seems that in the first case, mdk looks for ULINK2/ME the same also when you declare and use ULINKpro. 

what's the matter? anybody could help?

thanks a lot.

davide gandolfi

Parents
  • +1 Arm Employee Badge in reply to DavideG

    This is very strange... we can see from the Settings view that the adapter is (correctly) identified as a ulinkPro. However the error says that the tool is looking for ulink2.

    I've never seen this occur before... but I suspect something is corrupted in the project file... if you create a new project, does the issue continue?

    If your project is complex, you should be able to export (Project > Export > Save Project to CPRJ Format), and then re-import (Project > Import > Import project from CPRJ format), to retain the build structure, and can then configure debug settings again.

    Hope this helps?

    Ronan

Reply
  • +1 Arm Employee Badge in reply to DavideG

    This is very strange... we can see from the Settings view that the adapter is (correctly) identified as a ulinkPro. However the error says that the tool is looking for ulink2.

    I've never seen this occur before... but I suspect something is corrupted in the project file... if you create a new project, does the issue continue?

    If your project is complex, you should be able to export (Project > Export > Save Project to CPRJ Format), and then re-import (Project > Import > Import project from CPRJ format), to retain the build structure, and can then configure debug settings again.

    Hope this helps?

    Ronan

Children