cortex-m
Here are 205 public repositories matching this topic...
The ADC driver for the nRF52 chip only supports single samples. The continuous sampling function needs to be implemented:
-
Updated
May 28, 2020 - Python
optimization notes
- reshape function should optimize for inference dimension of output
- quantizev2 function dimension inference should be optimized
there are just work around for now
When adding a comment to the app macro as such:
/// Some text <- this causes the error
#[app(device = stm32f4xx_hal::stm32, peripherals = true)]
const APP: () = {
#[init]
fn init(cx: init::Context) {}
};Gives the error:
error: expected `const`
error: aborting due to previous error
Target: Nucleo L073RZ
OS: MacOS 10.14.5
Mbed OS: 5.13.1
Binary: mbed-os-blinky (built with GCC or AC6)
Flashing the above target using a specified CMSIS pack sometimes works, but more often claims No cores were discovered!.
Using the pack from here
./pyocd flash --frequency 1800000 --uid 066DFF5556547251870951
-
Updated
May 27, 2020 - Python
-
Updated
May 17, 2020 - C++
It looks like the documentation instructs users to create something called a "Virtual manifest" by omitting the [package] directive at https://docs.rs/svd2rust/0.16.1/svd2rust/#target--cortex-m-1
[dependencies]
bare-metal = "0.1.0"
msp430 = "0.1.0"
vcell = "0.1.0"
[dependencies.msp430-rt]
optional = true
version = "0.1.0"
[features]
rt = ["msp430-rt"]However, whe
uint16_t readChannel(Channel channel)
According to docs.modm.io
typedef uint8_t Channel
// this type may also be an enum or enum class
the call readChannel(1) should be legal, but: error: cannot convert 'int' to 'modm::platform::Adc1::Channel'.
We should up
NVIC::enable() was deprecated with the following warning.
WARNING This method is a soundness hole in the API; it should actually be an unsafe function. Use NVIC::unmask which has the right unsafety.
https://docs.rs/stm32f3xx-hal/0.3.0/stm32f3xx_hal/stm32/struct.NVIC.html#method.enable
NVIC::unmask() has the following documentation.
This function is unsafe because it can break m
-
Updated
Apr 17, 2020 - GDB
In current patch, we already implemented a futex-liked mutex. It didn't support PI. In order to achieve better real-time capability, the higher priority task should execute as soon as possible. It also makes sense on synchronization. So we could apply PI to enhance our real-time capability.
By the way, this's feature would be released soon. Furthermore, folks should not work on this feature
-
Updated
May 27, 2020 - C++
-
Updated
Sep 17, 2019 - Forth
@jamesmunns and I had a discussion on Matrix about the current defaults that leave HardFault_ and DefaultHander_ implemented as infinite loops.
This should most likely be replaced with panic in the default case to help the implementors detect issues and if nothing is done the panic crate takes care of the default course of action.
This might increase code size a bit, but for those that do
-
Updated
Jan 3, 2019 - C
-
Updated
Sep 7, 2018 - C++
-
Updated
Apr 29, 2020 - C++
-
Updated
Jul 5, 2019 - CMake
-
Updated
May 29, 2020 - C
-
Updated
Mar 15, 2020 - Rust
-
Updated
Nov 11, 2019 - C
-
Updated
Mar 9, 2020 - Rust
-
Updated
Sep 27, 2018 - C++
Improve this page
Add a description, image, and links to the cortex-m topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the cortex-m topic, visit your repo's landing page and select "manage topics."


因为要使用rtt+emwin,在emwin532版本里,GUI_X_OS.c是和os的接口,在rtconfig.h里打开#define RT_USING_CMSIS_OS后,编译出了几条错误,如下
cmsis_rtthread.c
Error[Pe167]: argument of type "os_pthread" is incompatible with parameter of type "void (*)(void *)" \RTThread\rt-thread-v2.1.x\components\CMSIS\RTOS\cmsis_rtthread.c 33
Warning[Pe188]: enumerated type mixed with another type \RTThread\rt-thread-v2.1.x\components\CMSIS\RTOS\cm