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.
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?
thanks for quick answer.
i tried your suggestion but it is not possible:
"Export to CPRJ project file" is grayed and not operative.
i'm investigating a little cause the project is complex enough (that is : it makes part of a multiproject and it is quite a little old fashioned.
the only active option in Export menu is "Save Project to uVison3 format". do you think i can try this kind of exporting?
sorry for boring you again: you were right: something corrupted somewhere in the project files.i tried to rebuild "manually" the project and i yet never seen again the no consistent message about ulink emulator missing status.
i also try to change the emulator to ulinkm2 and to ulinkpro again and uvison run fine in every case.
sorry again. sometimes the simplest things matter a lot.
Glad to hear you have been able to resolve the issue, sorry that you had to do it manually.
thanks a lot!