drone-os / drone-stm32-map Goto Github PK

Hi, when trying to build this, it says:

error[E0599]: no method named set_pllsrc found for mutable reference &mut drone_stm32_map::reg::rcc::cfgr::Hold<'_, drone_core::reg::prelude::Srt> in the current scope
--> src/tasks/root.rs:77:11
|
77 | r.set_pllsrc() // HSE oscillator clock selected as PLL input clock
| ^^^^^^^^^^ help: there is an associated function with a similar name: set_i2ssrc

Sorry, I'm new to drone and I'm not sure if it's an issue with this repo or the book repo.

Hi!

Just curiosity; Why wasn't svd2rust chosen to generate Rust code out of svd files?

Hi, I saw that in the peripheral subcrates, in the macros, documentation is written for the components of those peripherals.
However, I can't find the documentation in the resulting just doc anywhere..

Hi,

I am trying to create a register map for the nrf9160, however in their SVD files, they use clusters in the peripheral registers.
I'll see if I can write up a solution to this.

I want to contribute an SPI driver leveraging drone_stm32_map_periph_spi::SpiPeriph. Code organization wise, does that belong in this group of crates, or should a new drone-stm32 crate be created for that purpose?

Hi,

I would like to create a nRF9160 map.
One thing that's unclear to me is what the 12 different pieces are for.
Could you explain that?

Hi there, thanks so much for this amazing project!

I ran drone new --device stm32l4x6 --flash-size 1024k --ram-size 96k hello-world, and when running just build, it returns an error:

error: failed to select a version for `drone-stm32-map`.
    ... required by package `hello-world v0.1.0`
versions that meet the requirements `^0.10.0` are: 0.10.1, 0.10.0

the package `hello-world` depends on `drone-stm32-map`, with features: `fpu` but `drone-stm32-map` does not have these features.


failed to select a version for `drone-stm32-map` which could resolve this conflict

Hi,
Considering switching to Rust for microcontrollers in this project:

http://mbari.org/esp

What would be involved in adding support for the STM32L1xx series of microcontrollers?
(The STM32L152 in particular)

Would this just involve creating the required peripheral bindings, or do the STML1xxx chips lack some features critical for Drone core?

Here's an detailed comparison of the L1 and L4 chips:
http://web.eece.maine.edu/~zhu/book/STM32L4/STM32L1%20vs%20STM32L4.pdf