07:55 <re_irc> <barafael> olaoni: you can also check what the utils do, and imitate that

08:51 <re_irc> <ryan-summers> olaoni: You can also build + flash the example project directly from the stm32h7xx-hal repository. If you want it all in a standalone bin, you're going to have to pull in any associated code for the project

08:52 <re_irc> <ryan-summers> And by no means would I say it should be simple to build without the utilities folder. The compiler needs to resolve all the symbols when you compile. If you have a header file in C declaring some "my_function()", you have to compile said function into your code as well

08:53 <re_irc> <ryan-summers> And by no means would I say it should be simple to build without the utilities folder. The compiler needs to resolve all the symbols when you compile. If you have a header file in C declaring some "my_function()", you have to compile said function into your code as well. This is identical to what the "utilities" module is in the example - it's extra code that has to get compiled into the blinky example. You can...

08:53 <re_irc> ... modify the example to not need it, but you can't just leave it out without modifying the example code

09:26 <re_irc> <olaoni> barafael: Thanks the issue with removing the utilities folder in standalone project has not been resolved

09:31 <re_irc> <olaoni> ryan-summers: Yes I am now aware of that now. I have been able to build standalone and from the stm32h7xx-hal reposistory. Going forward I will opt for the latter as I am now slowing beginning to understand the whole structure.

09:31 <re_irc> I have managed to run the blinky on the stm32h743 nucleo board both in repo and standalone.

09:41 <re_irc> <olaoni> * slowly

13:06 <re_irc> <olaoni> ryan-summers: I am trying to use cargo-embed for debugging code. You sent me this link yesterday https://crates.io/crates/cargo-embed however when I add

13:06 <re_irc> cargo-embed = "0.12.0" to my Config.toml file it breaks the build. I am building from stm32h7xx-hal repository.

13:06 <re_irc> I am getting the following error when cargo-embed is added

13:06 <re_irc> stm32h7xx-hal (master) $ cargo build --features=stm32h743v,rt

13:06 <re_irc> ... long message truncated: https://psion.agg.io/_matrix/media/r0/download/psion.agg.io/f31a680fef8fc49159d5ddf3814a9684535bf82bccf6863b94addb399aa671d8 (15 lines)

13:07 <re_irc> <ryan-summers> cargo-embed is a standalone binary, not a library dependency. You install it by running "cargo install cargo-embed", and then you use it by using "cargo embed <args>"

13:07 <re_irc> <olaoni> I have installed it

13:08 <re_irc> <ryan-summers> You don't put it in Cargo.toml

13:08 <re_irc> <olaoni> ah okay

13:09 <re_irc> <olaoni> one more question about <args> in the instruction. This is going to be --chip STM32H743ZITx right?

13:16 <re_irc> <burrbull> yes. in command line or in Embed.toml

13:17 <re_irc> <olaoni> burrbull: Thanks

13:43 <re_irc> <olaoni> I am running the following command from stm32h7xx-hal repo base directory but getting error. I have added added to the same directory a .embed.toml file which I have edited to contain both stlink vid and pid number.

13:43 <re_irc> > > Compiling stm32h7 v0.14.0

13:43 <re_irc> ... long message truncated: https://psion.agg.io/_matrix/media/r0/download/psion.agg.io/aa8a0fb8f998e33841bdba6520fef37f233269a556e313d6f1f04cb65b6638ed (14 lines)

13:43 <re_irc> > > (master) $ **cargo embed --chip STM32H743ZITx**

13:43 <re_irc> > > error: failed to run custom build command for `stm32h7 v0.14.0`

13:44 <re_irc> <olaoni> * cargo embed --chip STM32H743ZITx

13:58 <re_irc> <9names (@9names:matrix.org)> you still need to have --features=stm32h743v,rt

14:00 <re_irc> <Noah> Has anyone here used TFTP or similar to upgrade their devices over ETH (in Rudt ofc) or would be willing to code this on a contract basis?

14:00 <re_irc> <Noah> * Rust

14:03 <re_irc> <ryan-summers> Man, a generic TFTP bootloader in Rust would actually be super nice. I did that exact thing a few years back in C++ and it was a nice mechanism to bootload

14:04 <re_irc> <ryan-summers> Maybe it could be added onto "blethrs"? Don't know how widely the project is still used though, I just remember some chatter about it a while ago

14:10 <re_irc> <olaoni> 9names: Yes I did issue the following command first _*cargo build --features=stm32h743v,rt*_ once it built successfully I then issued the _*cargo embed --chip STM32H743ZITx*_

14:11 <re_irc> <ryan-summers> cargo-embed runs "cargo-build" before flasing, so features supplied in the first build call are completely ignored and overwritten with the new build

14:12 <re_irc> <olaoni> ryan-summers: okay thanks

15:19 <re_irc> <Mehmet Ali> Hi all! Is there a clever way to define registers in a device driver, but in different banks?

15:19 <re_irc> <Mehmet Ali> I mean a register in bank A is different of a register in a bank B

15:19 <re_irc> <Mehmet Ali> Generally, I put all registers in an enum, and implement all methods there

15:21 <re_irc> <Mehmet Ali> Now, I can define an enum for each bank, but I think there should be a way to get that information there somehow and treat them all as equals.

15:22 <re_irc> <Mehmet Ali> I guess this might work:

15:22 <re_irc> DRIVE_CONFIG =(0x13,0x00),

15:22 <re_irc> <Mehmet Ali> DEVICE_CONFIG =(0x11,0x00),

15:22 <re_irc> DRIVE_CONFIG =(0x13,0x00),

15:22 <re_irc> DEVICE_CONFIG =(0x11,0x00),

15:22 <re_irc> <Mehmet Ali> pub enum Register_0 {

15:22 <re_irc> <Mehmet Ali> pub enum Register_0 {

15:22 <re_irc> DRIVE_CONFIG =(0x13,0x00),

15:22 <re_irc> DEVICE_CONFIG =(0x11,0x00),

15:23 <re_irc> <burrbull> olaoni: add "--release" to build optimized version

15:24 <re_irc> <ryan-summers> Mehmet Ali: Check out diondoktor's device-driver: https://github.com/diondokter/device-driver - I think there's a proc-macro in the works to improve it as well

15:24 <re_irc> <ryan-summers> * diondokter's

15:25 <re_irc> <Mehmet Ali> Yep that might be handy

15:27 <re_irc> <olaoni> burrbull: what should I add --release build option to? is this to *cargo embed --chip STM32H743ZITx --release*

15:28 <re_irc> <burrbull> cargo embed --features .. --chip .. --release

15:30 <re_irc> <olaoni> burrbull: thanks let me give that a go

15:38 <re_irc> <olaoni> burrbull: the build completed with error message.

15:38 <re_irc> Compiling stm32h7xx-hal v0.11.0 (/home/onio/workspace/stm32h7xx-hal)

15:38 <re_irc> Error No binary artifacts were found.

15:38 <re_irc> Finished release [optimized + debuginfo] target(s) in 50.24s

15:40 <re_irc> <ryan-summers> Are you building in the HAL repository? If so, you have to specify the --example

15:41 <re_irc> <olaoni> ryan-summers: yes, I am. Sorry I forgot about --example

15:41 <re_irc> <ryan-summers> Also, there's no need to <name> in every message, and it can be quite distracting for me personally 😅

15:42 <re_irc> <olaoni> okay sorry about that

15:44 <re_irc> <dalepsmith> IRC habits

15:44 <re_irc> <olaoni> cool learning fast

15:52 <re_irc> <ryan-summers> Glad to hear it :) Rust's got a lot of stuff to take in early on for sure

16:10 <re_irc> <mutantbob> Ugh. I just ran into a problem with bindgen. It seems to calculate the "__bindgen_padding" wrong when a base class lives in a "blocklist_file()" .

16:10 <re_irc> <mutantbob> It works fine on stable x86_64, but not for AVR

17:57 <re_irc> <mutantbob> I managed to turn it into a tiny reproducible example: https://github.com/rust-lang/rust-bindgen/issues/2175