1a60c1d944
Merge pull request #84 from rubberduck203/update-vscode-docs
...
Update vscode docs to reflect fixes from PR #83
2020-03-05 12:10:50 +00:00
888ddb7e0d
Update vscode docs to reflect fixes from PR #83
...
9977613eac6c26219611https://github.com/rust-embedded/cortex-m-quickstart/pull/83
2020-03-05 07:02:29 -05:00
23a74e9add
Merge pull request #83 from david-boles/patch-1
...
Corrected default VSCode build task.
2020-03-05 11:29:07 +00:00
9977613eac
Corrected default VSCode clean task.
2020-03-04 19:02:05 -05:00
6c26219611
Corrected default VSCode build task.
2020-03-04 14:07:32 -05:00
cda24a671d
Merge pull request #82 from rubberduck203/vscode
...
VS Code build tasks
2020-02-27 22:03:30 +00:00
ee3eca20d3
Add vscode build tasks for examples and release
2020-02-07 19:22:11 -05:00
e7025922f8
Merge pull request #79 from rubberduck203/track-debug-conf
...
Track launch.json, tasks.json, md & svd files
2020-01-01 16:36:34 +01:00
55bc69690a
Add recommended extensions file
2020-01-01 08:02:15 -05:00
b741ef37f5
Track launch.json, tasks.json, md & svd files
...
Ignoring the .vscode/ directory is good default behavior,
but it's probably best to track the files that define build tasks, debug
configs, documentation, and any system view description files.
The gitignore.io sample takes the same approach.
https://www.gitignore.io/api/visualstudiocode
> We in the VS Code team share debug and task specific settings as well because we want our team to have the same set of debug targets and task targets for VS Code.
https://stackoverflow.com/a/32979933/3198973
Even people who vehemently argue that .vscode shouldn't be track, agree
that complex debug configs should be tracked and shared.
> The only .vscode that makes sense to include are complex launch configs for debugging.
https://stackoverflow.com/a/47668283/3198973
2020-01-01 07:43:32 -05:00
a546d1b00c
Merge pull request #78 from rubberduck203/vscode
...
VS Code Support
2019-12-27 17:49:21 +00:00
57de818726
Add VS Code support
...
Adds basic configuration for VS Code for QEMU and STM32F3DISCOVERY.
2019-12-25 06:46:43 -05:00
3ca2bb9a46
Merge pull request #75 from rust-embedded/cortex-m-rt_fix
...
Update of cortex-m-rt for coming stable breakage
2019-08-13 20:17:27 +02:00
ac5d1fcb10
Update of cortex-m-rt for coming stable breakage
2019-08-13 20:13:09 +02:00
f5a8721006
Merge pull request #74 from rust-embedded/fix-73
...
Update instructions for device example, closes #73
2019-08-06 20:17:58 +02:00
d018974c6f
Update instructions for device example, closes #73
2019-07-23 20:59:12 -06:00
77e60809b5
Merge pull request #72 from ssendev/print-panic
...
add openocd.gdb hint how to print panic immediatly
2019-07-23 23:26:20 +02:00
97788b8215
add openocd.gdb hint how to print panic immediatly
2019-07-22 17:35:15 +02:00
08e6ba02f1
Merge pull request #71 from josephpenafiel/patch-1
...
added missing import
2019-07-10 00:09:51 +02:00
eae0512459
added missing import
...
NVIC wasn't imported from the stm32f30x crate
2019-07-09 10:08:51 -05:00
9610e04635
Merge pull request #69 from rust-embedded/bump-everything
...
Bump dependency versions
2019-06-04 19:14:19 -06:00
cc52aef020
Bump dependency versions
2019-06-04 21:35:21 +02:00
6919488412
Merge pull request #68 from rust-embedded/bt_limit
...
Added backtrace limit to mitigate infinite backtraces
2019-02-05 21:56:28 +00:00
73bae533c4
Added backtrace limit to mitigate infinite backtraces
2019-02-05 20:17:20 +01:00
ac344b967f
Merge pull request #66 from jacobrosenthal/patch-1
...
update interrupt usage
2019-01-30 19:54:09 +01:00
c6599f3686
update interrupt usage
2019-01-29 15:12:07 -07:00
3aa5ea9fd3
Merge pull request #64 from sstelfox/fix_breakpoint
...
Adjust the default breakpoint name to match cortex-m-rt pull #144
2019-01-22 08:38:49 +00:00
26baac1bf3
Adjust the default breakpoint name to match cortex-m-rt pull #144
2019-01-21 23:39:45 -05:00
2d7405fc04
Merge pull request #61 from rubberduck203/tests
...
Add example of writing tests that run on host machine
2019-01-01 11:34:22 +01:00
e58549b2ec
Add more documentation for testing on host
2018-12-31 07:01:16 -05:00
9ee8b84217
Merge pull request #62 from rubberduck203/coc
...
Fixes code of conduct link.
2018-12-31 11:35:55 +01:00
0e2aadf8f2
Make sure we can actually test prod code
2018-12-30 19:55:24 -05:00
e7138e0e2a
Fixes code of conduct link.
...
Closes #60
2018-12-30 19:24:24 -05:00
c142db6e23
Add example of writing tests that run on host machine
2018-12-30 19:17:58 -05:00
207bca35f4
Merge pull request #59 from rust-embedded/loop_crash_fix
...
Workaround for loop {} until it is fixed
2018-11-20 15:33:23 +01:00
f9570c7c65
Workaround for loop {} until it is fixed
2018-11-20 07:58:38 +01:00
f47d1633af
Merge pull request #57 from rust-embedded/sh
...
use hprint macros and NVIC::pend; fix allocator example
2018-11-10 00:10:46 +00:00
55e61c3291
bump dependencies
2018-11-10 00:04:28 +01:00
e64e690512
use NVIC::pend
...
instead of the deprecated NVIC.set_pending
2018-11-10 00:02:00 +01:00
f7a943f480
fix the allocator example
...
importing alloc is a bit weird
2018-11-10 00:01:25 +01:00
9c6b290e12
use hprint macros
2018-11-10 00:00:57 +01:00
7e2bec66b7
Merge pull request #54 from Nicoretti/toml
...
Add additional meta data to improve crate experience
2018-10-28 23:48:50 +01:00
4295bccf0e
Merge pull request #51 from rust-embedded/therealprof-extended-remote
...
Default to extended-remote instead of remote mode
2018-10-28 23:48:32 +01:00
8f292e0f07
Add additional meta data to improve crate experience
...
* Add readme setting, so README.md is shown on https://crates.io/
2018-10-26 15:54:27 +02:00
76d2e947a5
Merge pull request #53 from birkenfeld/patch-1
...
Add example moving .bss data into custom memory
2018-10-22 19:18:17 -07:00
76cdd6a95b
fix example
2018-10-21 17:27:47 +02:00
314e48537c
Add example moving .bss data into custom memory
...
We're using a STM32F429 and wanted to move stuff around in memory, notably put stack+data into CPU coupled memory, and put framebuffers for the integrated LCD controller into the normal SRAM.
Getting this right while not completely overriding the default `link.x` was quite tricky (especially finding the `INSERT AFTER` life-saver...) so I thought an example would not hurt here.
It should probably also be mentioned in other places (book/...)?
2018-10-21 13:04:40 +02:00
d5abcf6d2a
Merge pull request #52 from jannic/patch-1
...
Update rust version requirements in README.md
2018-10-13 21:40:23 +02:00
b02a67b5f9
Update rust version requirements in README.md
...
As Cargo.toml now includes edition = "2018", it won't build with rust 1.30-stable. 1.31-stable will be the first stable version to have the edition feature enabled. (See https://internals.rust-lang.org/t/rust-2018-release-schedule-and-extended-beta/8076 for details.)
At the same time, remove the remark about 1.30-beta not being out yet, as it's out by now.
2018-10-13 21:37:17 +02:00
d7c22926f4
Default to extended-remote instead of remote mode
...
Extended remote allows a lot more features like attaching and detaching and much more fine-grained execution options. If a gdbserver implementation supports it (and OpenOCD sure does) it should be preferred over `remote`.
2018-10-13 02:17:35 +02:00
Adam Greig