Check if updates are necessary after Hardware GDB API changes

[ilg-ul]

In CDT 10 there were several changes that affected the Hardware GDB API:

From: Marc-Andre Laperle malaperle@gmail.com
Subject: Re: [embed-cdt-dev] maven build
Date: 8 November 2020 at 01:01:40 EET
To: embed-cdt developer discussions embed-cdt-dev@eclipse.org
Reply-To: embed-cdt developer discussions embed-cdt-dev@eclipse.org

This might help https://htmlpreview.github.io/?https://raw.githubusercontent.com/eclipse-cdt/cdt/blob/master/doc/org.eclipse.cdt.doc.isv/guide/deprecated_API_removals.html#deprecatedRemovals

IGDBJtagConstants.ATTR_JTAG_DEVICE has been removed. Use IGDBJtagConstants.ATTR_JTAG_DEVICE_ID to persist device ID rather than device name. See Bug 566462.

and

From: Marc-Andre Laperle malaperle@gmail.com
Subject: Re: [embed-cdt-dev] maven build
Date: 8 November 2020 at 02:57:13 EET
To: Liviu Ionescu ilg@livius.net

I just tested the “perform apply” in the Debug config tabs after changing the device name. This was only to check what would happen when code would run through the missing IGDBJtagConstants.ATTR_JTAG_DEVICE

and

From: John Dallaway john@dallaway.org.uk
Subject: Re: [embed-cdt-dev] maven build
Date: 8 November 2020 at 14:20:36 EET
To: embed-cdt-dev@eclipse.org
Reply-To: embed-cdt developer discussions embed-cdt-dev@eclipse.org

Hi Liviu

Please refer to:

https://git.eclipse.org/c/cdt/org.eclipse.cdt.git/tree/jtag/org.eclipse.cdt.debug.gdbjtag.ui/src/org/eclipse/cdt/debug/gdbjtag/ui/GDBJtagDSFDebuggerTab.java

for details of how we migrate legacy debug configurations from ATTR_JTAG_DEVICE to ATTR_JTAG_DEVICE_ID in the CDT repository.