nRF91 DK / nRF53 DK support

[simtind]

Description

Mbed-ls does not correctly list newest-generation nRF dev kits. This is probably related to them having more than one com port. At least on windows, the script stops parsing composite device functions before all parts of the probe has been discovered, since the max number of components is hardcoded to 5.

mbed-os-tools version: 0.0.15
mbed-ls version: 1.7.12
Targets: nRF5340-DK and nRF9160-DK

Steps to reproduce:

• Connect an nRF9160-DK or nRF5340-DK to computer with mbed-ls installed.
• Excecute mbedls -u

Output looks like the following

platform_name	platform_name_unique	mount_point	serial_port	target_id	interface_version
unknown	None[0]	unknown	COM22	000960012849	unknown

If -u is not passed to mbedls, the following warning appears.
WARNING:mbedls.lstools_base:MBED with target id '000960012849' is connected, but not mounted. Use the '-u' flag to include it in the list.

The expected behavior is for mbedls to detect and recognize the nRF devkit:

platform_name	platform_name_unique	mount_point	serial_port	target_id	interface_version
nRF5340_DK	None[0]	E:	COM22	000960112849	unknown

Ideally, the serial_port value would be a list for devkits with more than one COM port.

platform_name	platform_name_unique	mount_point	serial_port	target_id	interface_version
nRF5340_DK	None[0]	E:	['COM12', 'COM11', 'COM22']	000960112849	unknown

Issue request type

[ ] Question
[X] Enhancement
[ ] Bug