Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
EBlink Install Fail
#11
As with Chris, can confirm v2.40 installs. And also with Chris, I do not use ST-Link, but use J-Link.

Wandering through v2.40 I am unable to see how J-Link can be chosen.

With Embitz v1.11 (where J-Link is available) I have build code for MCUs other than ST Microelectronics.

My attraction to Embitz is its lack of clutter and its effort to be purposeful. Embitz v2.40 is a rejuvenation.

Workalot
Reply
#12
It's a big misunderstanding that you can only debug STmicro with STlinkV2.
I use STlinkV2 for all my devices, STmicro, Atmel, Silabs and NXP. I never use the Jlinks I have here.

If you don't use EBlink then you throw a lot of useful functionality away.

If you need a different probe then you should use the GDB server for that probe and configure it as a remote interface in EmBitz. You can setup EmBitz in such way that it will launch the external GDB server automatically.
Reply
#13
Ah, did not realize that. Makes sense to me now, Eblink & St-Link for use on many MCU manufacturers, yery good!

And as you say, all at a price that can't be bettered.

Thank you very much.

Workalot
Reply
#14
(17-03-2022, 12:00 AM)Workalot Wrote: Ah, did not realize that. Makes sense to me now, Eblink & St-Link for use on many MCU manufacturers, yery good!

And as you say, all at a price that can't be bettered.

Thank you very much.

Workalot

Only STlink-V2!
The STlink-V3 is locked to STmicro only.
Reply
#15
Clarity, and still more clarity, all around me clarity has appeared. I've got it!

Shows how important this forum is.

Workalot
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)