00:18 <re_irc> <@jaxter184:matrix.org> oh wow, they dont already sponsor it? seems like a no-brainer to me

08:43 <re_irc> <@mathy_v:matrix.org> : Thx, I will have a look!

12:41 <re_irc> <@wucke13:matrix.org> Is it possible to build a binary in no_std Rust that has an alloc with a stable toolchain?

12:47 <re_irc> <@ryan-summers:matrix.org> I believe that just got stabilized with the latest toolchain release

12:47 <re_irc> <@ryan-summers:matrix.org> I think the release notes indicate this: https://github.com/rust-lang/rust/blob/1.68.1/RELEASES.md#version-1680-2023-03-09

13:35 <re_irc> <@thejpster:matrix.org> Yes that was in 1.68.0.

21:36 <re_irc> <@taral:matrix.org> Anyone know where I can best track the status of the cortex-m 0.8 work?

21:38 <re_irc> <@jaxter184:matrix.org> does anyone have any good resources for understanding memory.x? I'm trying to flash an stm32h723, and I _think_ i'd be fine just using the one in stm32h7xx-hal (which itself is pretty well commented), but I'd like to take this opportunity to understand the file better

21:39 <re_irc> <@jamesmunns:beeper.com> https://docs.rs/cortex-m-rt/latest/cortex_m_rt/ is a pretty good first step

21:39 <re_irc> <@jaxter184:matrix.org> in particular, what stuff like SRAM and AXISRAM are, and where in the datasheet to find the relevant information

21:39 <re_irc> <@jaxter184:matrix.org> oh wow, rad, thanks

21:40 <re_irc> <@jamesmunns:beeper.com> Ah, for the chip specific stuff, there is usually a section called the "memory map" that explains the different regions, kinds, and mappings of ram/flash

21:40 <re_irc> <@jamesmunns:beeper.com> (in your chip specific datasheet, or "reference manual"

21:40 <re_irc> <@jamesmunns:beeper.com> * manual"_

21:40 <re_irc> <@jamesmunns:beeper.com> * manual")

21:40 <re_irc> <@adamgreig:matrix.org> you want the reference manual, RM0468 for that chip

21:41 <re_irc> <@jaxter184:matrix.org> perfect, thanks so much y'all

21:41 <re_irc> <@adamgreig:matrix.org> then section 2.3-2.5 explains what memory you've got where, but it's a bit less clear why you have different sections and what you might use them for

21:41 <re_irc> <@adamgreig:matrix.org> one thing to bear in mind is that you can generally only have one access to a particular memory section going at a time, so for example if you have a DMA transfer and the cpu also wants to access that memory, they'll contend, i.e. one will have to wait

21:41 <re_irc> <@adamgreig:matrix.org> or two simultaneous dma transfers even

21:42 <re_irc> <@jaxter184:matrix.org> oh, interesting, that makes sense

21:42 <re_irc> <@adamgreig:matrix.org> so one advantage to multiple memory sections is you can arrange some transfers to happen in one and others in another, so they can both happen simultaneously

21:42 <re_irc> <@jamesmunns:beeper.com> Yeah all of the general docs will colloquially be called "the datasheet", but at least for ST, there's usually a datasheet, which is more single-chip feature specific, and covers sw + electrical items, and a "reference manual" doc that goes more into detail and explains how to interact with a lot of things

21:42 <re_irc> <@jamesmunns:beeper.com> : just for clarity, this ISN'T controlled by the linker script/memory.x, and is more chip/hardware specific

21:43 <re_irc> <@adamgreig:matrix.org> the axisram is also a wider 64-bit memory bus, so you can get 2 words per access, while the sram1/2 is on the 32-bit ahb bus, and sram4 and backup sram are on a different bus again, but one that you can keep powered up separately in low-power modes

21:43 <re_irc> <@jamesmunns:beeper.com> but the linker script can help ensure you put certain data items in specific hardware memory sections

21:43 <re_irc> <@adamgreig:matrix.org> ah yea, the linker script is just to tell the compiler what addresses each memory starts at and how long they are

21:44 <re_irc> <@adamgreig:matrix.org> figure 1 on page 107 of RM0468 has a nice diagram that shows all the RAMs, flashes, the CPU core, and the bus interconnects

21:44 <re_irc> <@adamgreig:matrix.org> I say "nice" but they manage to completely butcher the aspect ratio so it's all squished :/

21:45 <re_irc> <@jaxter184:matrix.org> do they? my pdf reader seems to show it fine

21:45 <re_irc> <@jaxter184:matrix.org> its like twice the width of the other pages

21:48 <re_irc> <@adamgreig:matrix.org> huh, yea, I take it back, it's just foxitreader being stupid, weird

22:19 <re_irc> <@sjm42:matrix.org> Sounds like one page is landscape while others are portrait

22:19 <re_irc> <@sjm42:matrix.org> Have seen it often in datasheet pdf files

22:20 <re_irc> <@taral:matrix.org> maybe ?

22:26 <re_irc> <@taral:matrix.org> (for ref: I would contribute, but I don't know what's blocking or needed)