Adapt mbed-cmake's automatic uploading and debugging system #14010

multiplemonomials · 2020-12-08T02:13:38Z

Summary of changes

This PR ports over one of the best features of mbed-cmake (in my opinion at least): automatic uploading and debugging from the command line. In short, it provides two useful features: the ability to automatically flash code after building with a special make target (flash-<executable name>), and the ability to automatically start a debug server with the gdbserver make target. It supports a number of different upload tools (not just pyOCD or the USB drive interface), including OpenOCD and J-Link, so it's friendly to custom board users.

A more complete description of how to use it is available on the doc page.

I've refactored the original mbed-cmake implementation to clean it up and split out each upload method into its own file. This makes the upload methods easier to edit and even lets users add their own upload methods that can be called via our tool.

Possible future enhancements include additional upload methods (does the LPC-Link have a specific upload tool or GDB server?) and the ability to auto detect the correct USB drive of attached Mbed devices (can mbed-tools do this?). It also might be neat to create a preexisting config file for each Mbed board that is automatically used, though this will take a fair bit of work and testing.

Impact of changes

CMake build scripts will need to be updated to add the upload method config file as described in the documentation. If the config file isn't added, a notice will be printed and the new functionality will be disabled by the cmake scripts (UPLOAD_METHOD will be set to NONE).

Migration actions required

Documentation

I created a doc page here as part of the code. Eventually we should add this to the actual docs, but since there's no cmake stuff in there yet I held off on adding it.

Pull request type

[] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[X] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

Test results

[X] No Tests required for this change (E.g docs only update)
[] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

Reviewers

@0xc0170
@hugueskamba

ciarmcom · 2020-12-08T02:30:19Z

@multiplemonomials, thank you for your changes.
@0xc0170 @hugueskamba @ARMmbed/mbed-os-tools @ARMmbed/mbed-os-maintainers please review.

ghost · 2020-12-08T12:34:57Z

Ah, I've been wanting a way to do this for nrfproj and the thing adafruit uses for their uf2 based bootloaders.

Although it seems like few of these clearly support dfu.

multiplemonomials · 2020-12-09T08:13:13Z

@jrobeson Do you want to help me test an nrfjprog upload method? I'd definitely like to add support for it, and if you've got hardware that you can test with I'd appreciate your help. If so, can you send me the command you're using to flash your device as a starting point?

ghost · 2020-12-09T22:12:03Z

I think i just followed the nrfproject commnad in the documentation. I've mostly been playing with adafruit's somewhat mbed equivalent like so

adafruit-nrfutil dfu genpkg --dev-type 0x0052 --application /path/to/app_name_application.hex dfu-package.zip
dafruit-nrfutil --verbose dfu serial --package dfu-package.zip -p /dev/ttyACM0 -b 115200 --singlebank --touch 1200

I've mostly been playing with stuff that will hopefully/eventually give me/us FOTA.

@AGlass0fMilk and others have finally gotten support for mbed os applications merged into https://github.com/mcu-tools/mcuboot as per https://github.com/AGlass0fMilk/mbed-mcuboot-demo so that's what i'll be trying next.

AGlass0fMilk · 2020-12-10T04:36:01Z

I've mostly been playing with stuff that will hopefully/eventually give me/us FOTA.

@AGlass0fMilk and others have finally gotten support for mbed os applications merged into https://github.com/mcu-tools/mcuboot as per https://github.com/AGlass0fMilk/mbed-mcuboot-demo so that's what i'll be trying next.

If you're interested in FOTA you will want to check this out if you haven't already: ARMmbed/mbed-os-experimental-ble-services#13

I have a demo of FOTA working but I have yet to push up some changes/documentation... maybe tomorrow.

ghost · 2020-12-10T12:27:14Z

wow @AGlass0fMilk. I really appreciate you pointing that out, and the repository generally.

adbridge · 2021-01-07T12:08:09Z

@0xc0170 @hugueskamba please review

multiplemonomials · 2021-01-18T00:40:01Z

@0xc0170 @hugueskamba Have you had a chance to look at this yet? Any comments?

0xc0170 · 2021-01-18T10:12:36Z

@multiplemonomials sorry for the delay reviewing this one. We should review this week.

ladislas

First review, just for typos. A lot of double spaces everywhere that need fixing :)

I've spotted the first ones, but you'll be better using grep and fixing this locally.

ladislas · 2021-01-19T10:50:56Z

tools/cmake/UploadMethods.md

+|Name|CMake Argument|Supports Uploading|Supports Debugging|Upload Speed|Supported On
+|---|---|---|---|---|---|
+|No upload method|`-DUPLOAD_METHOD=NONE`|❌|❌|N/A|N/A
+|MBed USB|`-DUPLOAD_METHOD=MBED`|✔️|❌|Fast|All Mbed Boards
+|J-Link|`-DUPLOAD_METHOD=JLINK`|✔️|✔️|Fast|Mbed boards with J-Link On-Board.  Custom boards with a J-Link probe.
+|pyOCD|`-DUPLOAD_METHOD=PYOCD`|✔️|✔️|Medium|Almost all Mbed boards.  Custom boards with an ST-Link or DAPLink probe.
+|OpenOCD|`-DUPLOAD_METHOD=OPENOCD`|✔️|✔️|(Varies)|A number of different debug probes, but requires configuration.
+|NXP Bootloader|`-DUPLOAD_METHOD=NXPPROG`|✔️|❌|Slow|LPC1768 and LPC1114 on custom boards.
+|STM32Cube|`-DUPLOAD_METHOD=STM32CUBE`|✔️|✔️|Fast|All STMicroelectronics Mbed boards, custom boards with ST_Link probes.


better rendering of the table

Suggested change

|Name|CMake Argument|Supports Uploading|Supports Debugging|Upload Speed|Supported On

|---|---|---|---|---|---|

|No upload method|`-DUPLOAD_METHOD=NONE`|❌|❌|N/A|N/A

|MBed USB|`-DUPLOAD_METHOD=MBED`|✔️|❌|Fast|All Mbed Boards

|J-Link|`-DUPLOAD_METHOD=JLINK`|✔️|✔️|Fast|Mbed boards with J-Link On-Board. Custom boards with a J-Link probe.

|pyOCD|`-DUPLOAD_METHOD=PYOCD`|✔️|✔️|Medium|Almost all Mbed boards. Custom boards with an ST-Link or DAPLink probe.

|OpenOCD|`-DUPLOAD_METHOD=OPENOCD`|✔️|✔️|(Varies)|A number of different debug probes, but requires configuration.

|NXP Bootloader|`-DUPLOAD_METHOD=NXPPROG`|✔️|❌|Slow|LPC1768 and LPC1114 on custom boards.

|STM32Cube|`-DUPLOAD_METHOD=STM32CUBE`|✔️|✔️|Fast|All STMicroelectronics Mbed boards, custom boards with ST_Link probes.

| Name | CMake Argument | Supports Uploading | Supports Debugging | Upload Speed | Supported On |

|------------------ |----------------------------- |-------------------- |-------------------- |-------------- |-------------------------------------------------------------------------- |

| No upload method | `-DUPLOAD_METHOD=NONE` | ❌ | ❌ | N/A | N/A |

| MBed USB | `-DUPLOAD_METHOD=MBED` | ✔️ | ❌ | Fast | All Mbed Boards |

| J-Link | `-DUPLOAD_METHOD=JLINK` | ✔️ | ✔️ | Fast | Mbed boards with J-Link On-Board. Custom boards with a J-Link probe. |

| pyOCD | `-DUPLOAD_METHOD=PYOCD` | ✔️ | ✔️ | Medium | Almost all Mbed boards. Custom boards with an ST-Link or DAPLink probe. |

| OpenOCD | `-DUPLOAD_METHOD=OPENOCD` | ✔️ | ✔️ | (Varies) | A number of different debug probes, but requires configuration. |

| NXP Bootloader | `-DUPLOAD_METHOD=NXPPROG` | ✔️ | ❌ | Slow | LPC1768 and LPC1114 on custom boards. |

| STM32Cube | `-DUPLOAD_METHOD=STM32CUBE` | ✔️ | ✔️ | Fast | All STMicroelectronics Mbed boards, custom boards with ST_Link probes. |

ladislas · 2021-01-19T10:51:22Z

tools/cmake/UploadMethodManager.cmake

+# Load the upload method that the user selects
+
+if(NOT DEFINED UPLOAD_METHOD_DEFAULT)
+	message(STATUS "Note: UPLOAD_METHOD_DEFAULT not found.  Please create an upload method config file if you wish to use CMake's auto uploading and debugging support.")


double space

Suggested change

message(STATUS "Note: UPLOAD_METHOD_DEFAULT not found. Please create an upload method config file if you wish to use CMake's auto uploading and debugging support.")

message(STATUS "Note: UPLOAD_METHOD_DEFAULT not found. Please create an upload method config file if you wish to use CMake's auto uploading and debugging support.")

ladislas · 2021-01-19T10:51:37Z

tools/cmake/UploadMethods.md

@@ -0,0 +1,214 @@
+Mbed OS's CMake build system supports a number of upload methods to help get code onto your device.  Some uploaders also support debugging, and for these CMake will help you by automatically running the needed commands to start a debugging session.


double space

Suggested change

Mbed OS's CMake build system supports a number of upload methods to help get code onto your device. Some uploaders also support debugging, and for these CMake will help you by automatically running the needed commands to start a debugging session.

Mbed OS's CMake build system supports a number of upload methods to help get code onto your device. Some uploaders also support debugging, and for these CMake will help you by automatically running the needed commands to start a debugging session.

ladislas · 2021-01-19T10:51:52Z

tools/cmake/UploadMethods.md

@@ -0,0 +1,214 @@
+Mbed OS's CMake build system supports a number of upload methods to help get code onto your device.  Some uploaders also support debugging, and for these CMake will help you by automatically running the needed commands to start a debugging session.
+
+In order to enable uploading, you'll need to configure which upload methods your project supports.  To do this, you'll need to create an UploadMethodConfig.cmake file and include it in your top-level CMakeLists.txt.  You can start by using the template UploadMethodConfig-Sample.cmake (which is for Nucleo F429ZI) in this folder.  You'll then edit it to control the upload methods that are available for your target, and set the parameters that they need to operate.  THe different parameters and their values are explained in this document.


double spaces

Suggested change

In order to enable uploading, you'll need to configure which upload methods your project supports. To do this, you'll need to create an UploadMethodConfig.cmake file and include it in your top-level CMakeLists.txt. You can start by using the template UploadMethodConfig-Sample.cmake (which is for Nucleo F429ZI) in this folder. You'll then edit it to control the upload methods that are available for your target, and set the parameters that they need to operate. THe different parameters and their values are explained in this document.

In order to enable uploading, you'll need to configure which upload methods your project supports. To do this, you'll need to create an UploadMethodConfig.cmake file and include it in your top-level CMakeLists.txt. You can start by using the template UploadMethodConfig-Sample.cmake (which is for Nucleo F429ZI) in this folder. You'll then edit it to control the upload methods that are available for your target, and set the parameters that they need to operate. THe different parameters and their values are explained in this document.

ladislas · 2021-01-19T10:52:05Z

tools/cmake/UploadMethods.md

+
+In order to enable uploading, you'll need to configure which upload methods your project supports.  To do this, you'll need to create an UploadMethodConfig.cmake file and include it in your top-level CMakeLists.txt.  You can start by using the template UploadMethodConfig-Sample.cmake (which is for Nucleo F429ZI) in this folder.  You'll then edit it to control the upload methods that are available for your target, and set the parameters that they need to operate.  THe different parameters and their values are explained in this document.
+
+This page lists each upload method, its _parameters_ (variables that will have a fixed value) and its _options_ (variables that are different for different people and should be set on the command line when you run cmake).  Since this config is set by standard CMake code, it's very easy to add your own additional logic (including command line options) to adjust these variables!


double space

Suggested change

This page lists each upload method, its _parameters_ (variables that will have a fixed value) and its _options_ (variables that are different for different people and should be set on the command line when you run cmake). Since this config is set by standard CMake code, it's very easy to add your own additional logic (including command line options) to adjust these variables!

This page lists each upload method, its _parameters_ (variables that will have a fixed value) and its _options_ (variables that are different for different people and should be set on the command line when you run cmake). Since this config is set by standard CMake code, it's very easy to add your own additional logic (including command line options) to adjust these variables!

ladislas · 2021-01-19T10:53:09Z

tools/cmake/UploadMethods.md

+
+**Type:** Integer
+
+This controls the port that GDB servers will be run on when debugging.  A value higher than 1024 is recommended to allow debugging without root on Linux/Mac.


double space

Suggested change

This controls the port that GDB servers will be run on when debugging. A value higher than 1024 is recommended to allow debugging without root on Linux/Mac.

This controls the port that GDB servers will be run on when debugging. A value higher than 1024 is recommended to allow debugging without root on Linux/Mac.

ladislas · 2021-01-19T10:53:17Z

tools/cmake/UploadMethods.md

+
+## MBed USB Upload Method
+
+This upload method interfaces with standard MBed boards which present themselves as USB drives.  Given the folder where the USB drive is mounted, it first removes any other .bin files from the folder, then automatically copies the compiled program on. 


double space

Suggested change

This upload method interfaces with standard MBed boards which present themselves as USB drives. Given the folder where the USB drive is mounted, it first removes any other .bin files from the folder, then automatically copies the compiled program on.

This upload method interfaces with standard MBed boards which present themselves as USB drives. Given the folder where the USB drive is mounted, it first removes any other .bin files from the folder, then automatically copies the compiled program on.

ladislas · 2021-01-19T10:53:25Z

tools/cmake/UploadMethods.md

+
+**Type:** Folder Path
+
+Path that the MBed device is mounted to on your machine.  On Windows, this is usually a drive letter, such as `D:/`.


double space

Suggested change

Path that the MBed device is mounted to on your machine. On Windows, this is usually a drive letter, such as `D:/`.

Path that the MBed device is mounted to on your machine. On Windows, this is usually a drive letter, such as `D:/`.

ladislas · 2021-01-19T10:53:45Z

tools/cmake/UploadMethods.md

+
+## J-Link Upload Method
+
+This upload method connects to your processor via a J-Link JTAG box and the J-Link command line tools.  It supports both flashing and debugging.  CMake will automatically locate the J-Link tools in their standard install locations on Windows, Mac, and Linux.


double space

Suggested change

This upload method connects to your processor via a J-Link JTAG box and the J-Link command line tools. It supports both flashing and debugging. CMake will automatically locate the J-Link tools in their standard install locations on Windows, Mac, and Linux.

This upload method connects to your processor via a J-Link JTAG box and the J-Link command line tools. It supports both flashing and debugging. CMake will automatically locate the J-Link tools in their standard install locations on Windows, Mac, and Linux.

ladislas · 2021-01-19T10:54:02Z

tools/cmake/UploadMethods.md

+
+**Type:** String
+
+The name that your processor is known by to J-link.  These are listed [here](https://www.segger.com/downloads/supported-devices.php).


double space

Suggested change

The name that your processor is known by to J-link. These are listed [here](https://www.segger.com/downloads/supported-devices.php).

The name that your processor is known by to J-link. These are listed [here](https://www.segger.com/downloads/supported-devices.php).

multiplemonomials · 2021-01-19T18:03:48Z

Is it... bad to have double spaces? That's what my grammar school teacher taught me...

ladislas · 2021-01-19T20:53:17Z

Is it... bad to have double spaces? That's what my grammar school teacher taught me...

Well I don't think you'll go to jail for that, but looking more into it, I found this: How Many Spaces Should Be After a Period? which taught me a lot.

Pandoc will remove them when parsing from markdown to CommonMark.

I'll let the mbed os team shine in, but I'd say it's better to stick with how the current documentation is written, and it uses one space.

ciarmcom · 2021-01-23T12:51:02Z

This pull request has automatically been marked as stale because it has had no recent activity. @0xc0170, @hugueskamba, @ARMmbed/mbed-os-maintainers, @ARMmbed/mbed-os-tools, please complete review of the changes to move the PR forward. Thank you for your contributions.

0xc0170

First initial review. It took me a while to get back to this after the longer break.

We used to have something similar (wrappers for flashing) in yotta. I realized after seeing gdb implementation here. What we did back then was to use gdb server by default or export to IDE that has own debug server there. Two options I can think of: simple wrapper to start gdb and load the executable with configured target - the config came from target module. Or export to IDE that has the MCU configured and just flash and start debug session there.

The tricky part is that each of flashing methods need specific configuration that depends various settings either coming from a user (MCU name, speed),

We would like to support --flash argument that old tools provided - we do already , via cp binary to usb so basically copying it. We haven't yet looked at this subject to how it shall be done (CMake/Tools parts). I'll share this with the tools team and trigger a discussion this week.

Looking at this from the old tools perspective, I recall their support for flashing is either via usb mbed drive or jlink or stlink.

Thanks for sharing all this work, impressive set of support for flashing.

Update one day later: I also remembered we got cmsis-pack manager - fetching device data - like MCU type. We used it for exporting or getting flash algo. That could be useful to get some of the required data here like MCU name.

CMakeLists.txt

0xc0170 · 2021-01-25T16:26:38Z

tools/cmake/app.cmake

+
+# set executable suffix (has to be done after enabling languages)
+# Note: This is nice to have, but is also required because STM32Cube will only work on files with a .elf extension
+set(CMAKE_EXECUTABLE_SUFFIX .elf)


I recall other IDE also had this limitation (only able to find executable in their viewer if it has specific extension, it could have been .axf for uvision). However it should work (this shall be tested before we hit the problem like STM32Cube in this case).

tools/cmake/upload_methods/CheckPythonPackage.cmake

0xc0170 · 2021-01-25T16:32:56Z

tools/cmake/UploadMethodConfig-Sample.cmake

+set(JLINK_UPLOAD_ENABLED FALSE)
+
+if(JLINK_UPLOAD_ENABLED)
+    set(JLINK_CPU_NAME STM32F429ZI)


this config contains couple of values that should be stored somewhere. The only place that comes to my mind is targets.json that would have this (MCU_ target there would contain jlink/pyocd or others).

When back then we had project generator in exporters, that one has this in yaml files - debugging configuration for various exporters, each one has specific value and they do not match unfortunately).

How was this used in mbed-cmake repo? This is still the main issue for this flashing bits. Based on your latest reply, would it make sense to simplify the flashing: to initially add support for mbed flashing via copy binaries and extend it with more advanced flashing like this jlink/pyOCD - as they will need further configuration. Or we just figure it out here now (it might take a while to get this configuration for targets).

tools/cmake/UploadMethods.md

multiplemonomials · 2021-01-28T03:54:40Z

Okay, I broke some of the pre-requisite functionality out into other PRs.

And yeah, thinking about what you said, I suppose we can remove the NXPPROG method for now. It's not useful except in a pretty narrow use case (helping people using an LPC1768 on a custom board flash code without a programmer). It will still be available to add but not part of the base code. FWIW, the script is basically being maintained by RPL right now (we forked it), but I don't know if I want to sign up for actually maintaining it going forward.

multiplemonomials · 2021-01-28T06:29:49Z

Update: I looked into what you said about mbed-cli having flash support, and you're right -- it handles the mbed boards a lot better than the CMake implementation does. It can automatically detect where they're mounted, and even filter them by target name and UID.

The only annoying part is that I couldn't find any public script that calls the flashing code, other than mbed compile itself. So, I wrote one: https://github.com/USCRPL/mbed-cmake/blob/mbed-pathless/cmake/upload_methods/install_bin_file.py . This script also improves handling of multiple boards of the same type (it allows selecting one by UID, instead of the mbed-cli behavior of flashing all of them).

Once some people try it out, I'll merge that in here, and then CMake will be able to use (most of) the full power of mbed's upload tools.

Pull request has been modified.

multiplemonomials · 2021-11-01T01:40:15Z

@rwalton-arm sorry for the delay, ready for another look

multiplemonomials · 2022-02-15T15:53:55Z

@0xc0170 @rwalton-arm is this able to be looked at? It it doesn't seem like merging it is in the cards, I might just make it a standalone library.

0xc0170 · 2022-02-16T10:30:56Z

@0xc0170 @rwalton-arm is this able to be looked at? It it doesn't seem like merging it is in the cards, I might just make it a standalone library.

Yes, please, it will be better as standalone library and be referenced from the docs.
It is cool feature and it will be helpful for many users.

0xc0170 · 2022-02-16T12:19:35Z

I'll close this as result.

mergify bot added the needs: work label Dec 8, 2020

ciarmcom added the release-type: feature label Dec 8, 2020

ciarmcom requested review from 0xc0170, hugueskamba and a team December 8, 2020 02:30

ciarmcom added the needs: review label Dec 8, 2020

Patater mentioned this pull request Dec 8, 2020

Add possibility to use external scripts to detect target, flash firmware, reset board and discover serial port for custom boards ARMmbed/mbed-tools#145

Open

2 tasks

adbridge removed the needs: work label Jan 7, 2021

ladislas suggested changes Jan 19, 2021

View reviewed changes

ciarmcom added the stale Stale Pull Request label Jan 23, 2021

0xc0170 reviewed Jan 25, 2021

View reviewed changes

ciarmcom removed the stale Stale Pull Request label Jan 25, 2021

This was referenced Jan 28, 2021

Set executable suffix in CMake #14204

Merged

CMake: better detection of memap dependencies #14205

Merged

ciarmcom added the stale Stale Pull Request label Jan 29, 2021

ciarmcom added stale Stale Pull Request and removed stale Stale Pull Request labels Aug 20, 2021

ciarmcom added stale Stale Pull Request and removed stale Stale Pull Request labels Aug 27, 2021

ciarmcom added stale Stale Pull Request and removed stale Stale Pull Request labels Sep 3, 2021

ciarmcom added stale Stale Pull Request and removed stale Stale Pull Request labels Sep 12, 2021

ciarmcom added stale Stale Pull Request and removed stale Stale Pull Request labels Sep 19, 2021

ciarmcom added the stale Stale Pull Request label Sep 26, 2021

0xc0170 removed the stale Stale Pull Request label Sep 29, 2021

multiplemonomials added 6 commits October 31, 2021 18:35

Adapt mbed-cmake's automatic uploading and debugging system

57b7f07

Remove NXPPROG from provided upload methods (too specialized).

4b99e04

License header added to all new filed

f0d88a5

Update with new MBED install method

0d12892

Add docs for new upload method

9fd7794

Response to comments

b91eab8

multiplemonomials force-pushed the cmake-upload-debug branch from 9e059a6 to b91eab8 Compare November 1, 2021 01:39

Add license to python file

4f4aaf4

0xc0170 closed this Feb 16, 2022

mergify bot removed needs: work release-type: feature labels Feb 16, 2022

multiplemonomials deleted the cmake-upload-debug branch May 17, 2023 06:53

	message(STATUS "Note: UPLOAD_METHOD_DEFAULT not found. Please create an upload method config file if you wish to use CMake's auto uploading and debugging support.")
	message(STATUS "Note: UPLOAD_METHOD_DEFAULT not found. Please create an upload method config file if you wish to use CMake's auto uploading and debugging support.")

		@@ -0,0 +1,214 @@
		Mbed OS's CMake build system supports a number of upload methods to help get code onto your device. Some uploaders also support debugging, and for these CMake will help you by automatically running the needed commands to start a debugging session.

		@@ -0,0 +1,214 @@
		Mbed OS's CMake build system supports a number of upload methods to help get code onto your device. Some uploaders also support debugging, and for these CMake will help you by automatically running the needed commands to start a debugging session.

		In order to enable uploading, you'll need to configure which upload methods your project supports. To do this, you'll need to create an UploadMethodConfig.cmake file and include it in your top-level CMakeLists.txt. You can start by using the template UploadMethodConfig-Sample.cmake (which is for Nucleo F429ZI) in this folder. You'll then edit it to control the upload methods that are available for your target, and set the parameters that they need to operate. THe different parameters and their values are explained in this document.


		In order to enable uploading, you'll need to configure which upload methods your project supports. To do this, you'll need to create an UploadMethodConfig.cmake file and include it in your top-level CMakeLists.txt. You can start by using the template UploadMethodConfig-Sample.cmake (which is for Nucleo F429ZI) in this folder. You'll then edit it to control the upload methods that are available for your target, and set the parameters that they need to operate. THe different parameters and their values are explained in this document.

		This page lists each upload method, its _parameters_ (variables that will have a fixed value) and its _options_ (variables that are different for different people and should be set on the command line when you run cmake). Since this config is set by standard CMake code, it's very easy to add your own additional logic (including command line options) to adjust these variables!


		Type: Integer

		This controls the port that GDB servers will be run on when debugging. A value higher than 1024 is recommended to allow debugging without root on Linux/Mac.


		## MBed USB Upload Method

		This upload method interfaces with standard MBed boards which present themselves as USB drives. Given the folder where the USB drive is mounted, it first removes any other .bin files from the folder, then automatically copies the compiled program on.


		Type: Folder Path

		Path that the MBed device is mounted to on your machine. On Windows, this is usually a drive letter, such as `D:/`.


		## J-Link Upload Method

		This upload method connects to your processor via a J-Link JTAG box and the J-Link command line tools. It supports both flashing and debugging. CMake will automatically locate the J-Link tools in their standard install locations on Windows, Mac, and Linux.


		Type: String

		The name that your processor is known by to J-link. These are listed [here](https://www.segger.com/downloads/supported-devices.php).

Adapt mbed-cmake's automatic uploading and debugging system #14010

Adapt mbed-cmake's automatic uploading and debugging system #14010

Uh oh!

Conversation

multiplemonomials commented Dec 8, 2020

Summary of changes

Impact of changes

Migration actions required

Documentation

Pull request type

Test results

Reviewers

Uh oh!

ciarmcom commented Dec 8, 2020

Uh oh!

ghost commented Dec 8, 2020 • edited by ghost Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

multiplemonomials commented Dec 9, 2020 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ghost commented Dec 9, 2020 • edited by ghost Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

AGlass0fMilk commented Dec 10, 2020

Uh oh!

ghost commented Dec 10, 2020

Uh oh!

adbridge commented Jan 7, 2021

Uh oh!

multiplemonomials commented Jan 18, 2021

Uh oh!

0xc0170 commented Jan 18, 2021

Uh oh!

ladislas left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

multiplemonomials commented Jan 19, 2021

Uh oh!

ladislas commented Jan 19, 2021

Uh oh!

ciarmcom commented Jan 23, 2021

Uh oh!

0xc0170 left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

0xc0170 Feb 2, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

multiplemonomials commented Jan 28, 2021

Uh oh!

ghost commented Dec 8, 2020 •

edited by ghost

Loading

multiplemonomials commented Dec 9, 2020 •

edited

Loading

ghost commented Dec 9, 2020 •

edited by ghost

Loading

0xc0170 left a comment •

edited

Loading

0xc0170 Feb 2, 2021 •

edited

Loading

multiplemonomials commented Feb 15, 2022 •

edited

Loading