JLink Windows device detection no longer works properly

Question

JLink Windows device detection no longer works properly

cmonr opened this issue 6 years ago · 8 comments

Since 758394e, running mbedls in a Windows env does not detect JLink targets properly.

Before the commit:

C:\Users\redacted\tmp\mbed-ls>mbedls
+-----------------+----------------------+-------------+-------------+--------------------------+-----------------+
| platform_name   | platform_name_unique | mount_point | serial_port | target_id                | daplink_version |
+-----------------+----------------------+-------------+-------------+--------------------------+-----------------+
| EFM32GG_STK3700 | EFM32GG_STK3700[0]   | E:          | COM3        | 2015009F00004A2AD6C679E5 | 0.14.3          |
+-----------------+----------------------+-------------+-------------+--------------------------+-----------------+

After the commit:

C:\Users\redacted\tmp\mbed-ls>mbedls
WARNING:mbedls.lstools_base:No valid file found to update JLink device details
+---------------+----------------------+-------------+-------------+--------------+-----------------+
| platform_name | platform_name_unique | mount_point | serial_port | target_id    | daplink_version |
+---------------+----------------------+-------------+-------------+--------------+-----------------+
| LPC2368       | LPC2368[0]           | E:          | COM3        | 000440018986 | unknown         |
+---------------+----------------------+-------------+-------------+--------------+-----------------+

The above output is the same for release-version-1.5.0.

However, the output does change when using release-version-1.5.1:

C:\Users\redacted\tmp\mbed-ls>mbedls
WARNING:mbedls.lstools_base:No valid file found to update JLink device details
+---------------+----------------------+-------------+-------------+--------------+-----------------+
| platform_name | platform_name_unique | mount_point | serial_port | target_id    | daplink_version |
+---------------+----------------------+-------------+-------------+--------------+-----------------+
| unknown       | None[0]              | E:          | COM3        | 000440018986 | unknown         |
+---------------+----------------------+-------------+-------------+--------------+-----------------+

Answer 1 · 2018-08-10T15:24:04.000Z

Ah oops. The Si-Labs boards used to be detected as DAPLink boards. Now that we're using VID and PID to identify them, its trying to find them in the JLink database, which they aren't. Ugg this is annoying, I'll have to look at this more.
[Mirrored to Jira]

Answer 2 · 2018-10-02T14:59:37.000Z

Pretty sure this should be fixed? @cmonr can you check?
[Mirrored to Jira]

Answer 3 · 2018-10-08T23:26:44.000Z

@bridadan Will try again tomorrow when I have access to a board.

Answer 4 · 2018-10-09T21:45:49.000Z

Works with 1.6.0!

Answer 5 · 2018-10-10T15:01:58.000Z

Thanks for checking!

Answer 6 · 2018-12-31T20:56:01.000Z

from what i am seeing the problem still exists

Command-line code management tool for ARM mbed OS - http://www.mbed.com
version 1.8.3

WARNING:mbedls.lstools_base:No valid file found to update JLink device details

platform_name	platform_name_unique	mount_point	serial_port	target_id	daplink_version
TB_SENSE_12	TB_SENSE_12[0]	E:	COM5	2041010A0001EC21D752DFBA	1.3.0

can you please point me in the right direction to fix the issue.

Answer 7 · 2020-03-03T05:39:21.000Z

Hi, any update on this? I am seeing this on version 1.10.2 as well.

Answer 8 · 2021-01-11T06:58:12.000Z

Has this solved the problem? I tried it on pyocd 0.28.3. But It doesn't work.