[LPC11U68] Added UART1-4 support #341
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
+ code cleanup
Link to FRDM-K64F page, add Nucleo-F302R8, LPC800-MAX, DipCortex-M0, DipCortex-M3, BlueBoard-LPC11U24, link to mbed Platforms page at top of "Supported Microcontrollers and Boards" section.
…espectively. Names must be divided by comma.
|
Please rebase your pull request on top of our master and resubmit. |
bridadan
pushed a commit
that referenced
this pull request
Jun 21, 2016
Increase callback test time to fix timeout
ccli8
added a commit
to ccli8/mbed-os
that referenced
this pull request
Oct 16, 2024
…d image (ARMmbed#341) * Upload: PyOCD: Halt device after UPLOAD_LAUNCH_COMMANDS For pyocd debug, it appears the device under debug must be halted after UPLOAD_LAUNCH_COMMANDS, or debugger will become abnormal. * Convert output to Intel HEX format unconditionally in post-build This converts output to Intel HEX format unconditionally but to BIN format just on demand for the following reasons: 1. Most flash programming tools support Intel HEX format, e.g. GDB load command. 2. Output can have large holes in addresses which BIN format cannot handle and can generate very large file. * Upload: Support adjustment of debug commands for debug launch This gives chance to adjust GDB commands MBED_UPLOAD_LAUNCH_COMMANDS or MBED_UPLOAD_RESTART_COMMANDS for debug launch by implementing mbed_adjust_upload_debug_commands cmake function. * Upload: Change GDB load command to flash post-build processed image With this adjustment, GDB load command changes to "load <app>.hex" from just "load": 1. "Load" will load <app>.elf and is inappropriate for targets like bootloader or TF-M enabled which need to post-build process images. 2. "load <app>.bin" is not considered because GDB load command doesn't support binary format. * Upload: Generate GDB command line gdbinit for multiple application This enables generating GDB command line gdbinit file for single project multiple application scenario. The gdbinit file name would be <app>.gdbinit for distinct among multiple applications.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.