search

ARMmbed / mbed-ls

MOVED: https://github.com/ARMmbed/mbed-os-tools (mbedls detects Mbed Enabled devices connected to your computer)
22 stars 89 forks source link

JLink Windows device detection no longer works properly #385

Closed cmonr closed 5 years ago

cmonr commented 6 years ago

Since https://github.com/ARMmbed/mbed-ls/commit/758394e915c3d6bf7e116e57385987468295cf81, 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         |
+---------------+----------------------+-------------+-------------+--------------+-----------------+
bridadan commented 6 years ago

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]

bridadan commented 5 years ago

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

cmonr commented 5 years ago

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

cmonr commented 5 years ago

Works with 1.6.0!

bridadan commented 5 years ago

Thanks for checking!

srikav commented 5 years ago

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.

charlottewai commented 4 years ago

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

isdsi commented 3 years ago

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