Hi,
Are CMSIS-DAP debug probes compatible through different vendors (who are chip manufacturers too)?
Are RDI/JLINK debug probes compatible through different vendors (who are chip manufacturers too)?
I am confused, because ususally vendors (except OEM vendors) could restrict the access toward 3th party MCU direction.
These the type of OB (On Board) debuggers are very cheap and I think they are limited for given vendor MCUs.
In theoritycal, every CMSIS-DAP probe should be compatible.
The Segger's RDI solution through JLINK is the other story. It seems much more problematic, because we talk about a licensed protocol in that case.
NXP's only talkes about NXP MCU support here: https://www.nxp.com/design/microcontrollers-developer-resources/lpc-microcontroller-utilities/lpc-link2:OM13054
I would like know more about cross operability. Maybe someone has an feeling in this theme.
Don't forget, I asked you about CMSIS-DAP - CMSIS-DAP debug probes interoperability. And I asked you about others e.g. JLINK.
I don't have knowledgement about ST-LINK protocol. Maybe it is an one more 3th party solution.
e.g. situations are below (yes/no response is enough for me)
1. debuging STM's and Silabs's MCUs via NXP's LPC-LINK2 with CMSIS-DAP firmware (this is the main question)
2. debuging NXP's and Silabs's MCUs via STM's ST-Link v2/V3
3. debuging NXP's and STM's MCUs via Silabs JLINK PRO OD
4. debuging NXP's and Silabs's MCUs via STM's ST-Link v2/V3
5. debuging STM's and Silabs's MCUs via NXP's LPC-LINK2 with JLINK OB firmware
As I know, Segger's JLINK Pro supports a lot of vendors, because Segger is an OEM probe manufacturer, so this direction seems okay. Genuine Segger JLINK PRO could be used in a lof of IDEs with different vendor MCUs.
As I know, ARM's ULINK2 supports a lot of vendors too, because ARM is an OEM probe manufacturer, so this direction seems okay too.
Thank you in advance.
Attila