bobbin-rs / bobbin-sdk Goto Github PK

In Nightly, the panic_fmt lang item has been removed and replaced with #[panic_implementation], causing the following error:

error[E0522]: definition of an unknown language item: `panic_fmt`
  --> /Users/jcsoo/.cargo/registry/src/github.com-1ecc6299db9ec823/panic-abort-0.1.1/src/lib.rs:25:1
   |
25 | #[lang = "panic_fmt"]
   | ^^^^^^^^^^^^^^^^^^^^^ definition of unknown language item `panic_fmt`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0522`.
error: Could not compile `panic-abort`.

https://users.rust-lang.org/t/psa-breaking-change-panic-fmt-language-item-removed-in-favor-of-panic-implementation/17875

The MCU`s have 64KB of CCM SRAM
and 112+16KB = 128KB of SRAM.

@jcsoo we should probably have a "no-heap" feature that gates mention of Heap and defines board initialization methods without passing an instance of Heap to them.

If you don't mind, I have already implemented this since otherwise building was failing with an error that compiler was unable to find a heap-related (_sheap) symbols and can make a PR for this.

Hi!

I am really excited about this project, and wanted to ask, if you can give me some pointers for bootstrapping a new MCU for the project. Specifically a STM32F407VGT6 on a F4-discovery board.

I already found this hardware page, which states, that STM33F4X is a secondary target, but I can`t find anything in the repository for it.

I guess it was removed, because it is not up to date any more.

I would not mind making a fork, and trying to add support for at least the MCU itself, the board can wait.

Programming Manual: http://www.st.com/content/ccc/resource/technical/document/programming_manual/6c/3a/cb/e7/e4/ea/44/9b/DM00046982.pdf/files/DM00046982.pdf/jcr:content/translations/en.DM00046982.pdf

Reference Manual: http://www.st.com/content/ccc/resource/technical/document/reference_manual/3d/6d/5a/66/b4/99/40/d4/DM00031020.pdf/files/DM00031020.pdf/jcr:content/translations/en.DM00031020.pdf

Datasheet: http://www.st.com/resource/en/datasheet/stm32f437vg.pdf

The STM32F4xx chips overlap quite a lot, if there's a way to avoid duplicating a lot of code/effort we should probably do that. Would it be better to start with the most featurefull chip (439?) and have variants that disable stuff, or would it be better to start with the least featureful chip (405? 401?) and build up the more featureful ones?

Is there a mechanism for inheritance / overriding?

Reference Manual: http://www.st.com/content/ccc/resource/technical/document/reference_manual/3d/6d/5a/66/b4/99/40/d4/DM00031020.pdf/files/DM00031020.pdf/jcr:content/translations/en.DM00031020.pdf

Datasheet: http://www.st.com/content/ccc/resource/technical/document/datasheet/03/b4/b2/36/4c/72/49/29/DM00071990.pdf/files/DM00071990.pdf/jcr:content/translations/en.DM00071990.pdf

For now, keeping STM32F42x separate from STM32F40x.

When doing a top-level build of bobbin-sdk and entering the board builds I get the following error for all boards packages I try to build for.

~/Workspaces/Rust/Bobbin/bobbin-sdk
* pascal@tsunami  (master=) [52] > make
...
make -C board/
make[1]: Entering directory '/home/pascal/Workspaces/Rust/Bobbin/bobbin-sdk/board'
make -C arduino-zero
make[2]: Entering directory '/home/pascal/Workspaces/Rust/Bobbin/bobbin-sdk/board/arduino-zero'
error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `rustc - --crate-name ___ --print=file-names -C link-arg=-Tlink.x -C linker=arm-none-eabi-ld -Z linker-flavor=ld --target thumbv6m-none-eabi --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro` (exit code: 1)
--- stderr
error: unknown debugging option: `linker-flavor`

I'm building with the current nightly, 1.35.0-nightly (fbd34efb3 2019-03-26). Doing a 'rustc -Z help' shows there is no currently supported linker-flavor option.

I'm not sure how to overcome this. Any hints?