02:31 <Noah[m]> I probably should have paid attention on the last few meetings but is there any plans to update embedded-hal in cortex-m?

05:39 <DavidBrown[m]> Yes, but then the API becomes pretty much unusable.

05:39 <DavidBrown[m]> The goal is to keep it safe, but also make the interface usable.

09:51 <thejpster[m]> Just wanted to ping https://github.com/rust-embedded/wg/pull/818 again. I think there’s consensus but we’re stuck on procedure.

10:36 <AlexandrosLiarok> What's a good way to prevent the M4 core from running when using a dual core bootloader running from M7 ?

10:36 <AlexandrosLiarok> (stm32h745)

10:37 <AlexandrosLiarok> Because the m7 core will be overwriting the m4 flash region.

11:33 <thejpster[m]> That should be explained in the chips data sheet

11:34 <AlexandrosLiarok> I guess I can keep the M4 option byte to off and enable on bootloader jump.

11:35 <AlexandrosLiarok> * and enable the SYSCFG boot bit on bootloader

11:59 <RobinMueller[m]> Hey, does anyone know an elegant way to initialize very large arrays? I have to define a L1 table with 4096 u32 entries, but all the values are known at compile time. This was solved with assembler... (full message at <https://catircservices.org/_irc/v1/media/download/AU976XQteaWqBBOX1hmmBgwI9HnOYtIOuyR23646WGVdokCiE24mhr7fJfltwDHCKTbXyOK7AVG02sGcJ3VNXU-_8AAAAAAAAGNhdGlyY3NlcnZpY2VzLm9yZy9KY3BjTGV1RGtIWXdLc3VOZ2ZSVURpaW4>)

11:59 <RobinMueller[m]> Ah, the code is not public yet..

14:44 <rmsyn[m]> <RobinMueller[m]> "Hey, does anyone know an elegant..." <- there's a couple ways to achieve what you're trying to do.... (full message at <https://catircservices.org/_irc/v1/media/download/AdmmeQR5cehVVrKgL3OjBBp93IPDPhynIM4ZP0n4MYJ20hinuzpw0DokHBjl5V3OUHFvGLCvxISHWMHyuf2gDBa_8AAAAAAAAGNhdGlyY3NlcnZpY2VzLm9yZy9URkhQaFJJZURTaVVpTGNzbllJRmVyU3I>)

14:45 <rmsyn[m]> s/`/`./, s/for//, s/you.//

14:49 <thejpster[m]> I’d make a static slice of slices and flatten the iterator to set them all at run time

14:50 <rmsyn[m]> right, but they were asking about how to achieve a compile-time solution ...

14:56 <thejpster[m]> Compile time what though? You can’t get data into the MMU at compile time.

14:57 <thejpster[m]> And it’s unlikely that MMU set up is performance critical.

14:58 <thejpster[m]> So to me it’s just a question of “code size” vs “data size”.

14:59 <rmsyn[m]> alright, yeah I guess that's answering a different question of "why do you want a compile-time solution".

15:09 <rmsyn[m]> I think the general case is still interesting, though. like there are entire crates dedicated to how to const-initialize an array programmatically using macros that take function arguments for how to initialize the elements

15:13 <thejpster[m]> Yeah but we have const blocks now so initialising a bunch of slices is now fairly easy

15:14 <rmsyn[m]> sure, I guess you also move the initiializer into a `const fn do_init<const N: usize>(..args) -> [T; N]` type function

15:20 <rmsyn[m]> ah, the `const` block is new to me. you're talking about doing something like:... (full message at <https://catircservices.org/_irc/v1/media/download/AX7jvsrlvX5d_J41lrectz7YUGnc_ZRIE1URFnoXqeq0g9oNOeJKsKx50RjMRccHgcZzFa298QC-vtLHQjt1WjW_8AAAAAAAAGNhdGlyY3NlcnZpY2VzLm9yZy9TdkhGV2xtZ1d4cHFyYVhiVW1jWkF4eHQ>)

15:21 <rmsyn[m]> * ah, the `const` block is new to me. you're talking about doing something like:... (full message at <https://catircservices.org/_irc/v1/media/download/Af8ij3eEe-FKu8jV0gm2p2sgGhzIB50qHSjuqxV1NXnezwg4anFPAMI3WQmrfm8urG6iTbx8tsRQM68YJ37-v2m_8AAAAAAAAGNhdGlyY3NlcnZpY2VzLm9yZy9QWE1CRkZUTlJOWVJ1aXFtdFlWUk1Td2U>)