When starting debugging with a launch.json configuration, the debugger would always start on the device that was linked to the active build if nothing else was specified. In cases where the active build is different from the debugged build, this would start debugging on the wrong board. This has been fixed.