EFM32GG STK3700 Has anyone succeeded in debugging Jlink?

isdsi · January 11, 2021, 7:40am

I have installed Mbed Studio.

github.com/ARMmbed/mbed-ls

JLink Windows device detection no longer works properly

opened 03:21PM - 10 Aug 18 UTC

closed 09:45PM - 09 Oct 18 UTC

cmonr

mirrored Jira status: OPEN

Since https://github.com/ARMmbed/mbed-ls/commit/758394e915c3d6bf7e116e5738598746…8295cf81, 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 | +---------------+----------------------+-------------+-------------+--------------+-----------------+ ```

Updated mbed cli package as below.

mbed-cli = 1.8.3
mbed-greentea = 1.7.4
mbed-ls = 1.8.3
mbed-host-tests = 1.5.10
pyocd = 0.28.3

I tried to build and debug ‘mbed-os-example-blinky’. But it doesn’t work.

It came out like the picture below.

What should I do?

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

platform_name	platform_name_unique	mount_point	serial_port	target_id	interface_version
EFM32GG_STK3700	EFM32GG_STK3700[0]	D:	COM5	2015009F0000E19CD6C6D253	0.14.3

Topic		Replies	Views
Mbed-tools cannot detect target Bugs mbed_os	7	2125	April 9, 2021
Mbed Studio Debug Erasing Mbed Studio	23	1792	May 27, 2021
Can't debug code in other IDEs after use an STM32-F411RE with arm Mbed OS Bugs	0	1002	April 3, 2020
NUCLEO-G431KB Port Boards stmicroelectronics	6	1476	November 3, 2020
Which boards will `mbed-tools detect` work for? Mbed CLI	1	458	May 25, 2021

EFM32GG STK3700 Has anyone succeeded in debugging Jlink?

Related topics