<re_irc>
<James Munns> I'm guessing you're debugging now
<re_irc>
<James Munns> but usually that means:
<re_irc>
- not fencing everything that needs to be fenced
<re_irc>
- (since it's the H7) no clearing dcache/icache as recommended in the datasheet
<re_irc>
- not checking all of the appropriate "done" flags, meaning sometimes you race the completion
<re_irc>
<James Munns> Lachlan ^ in case that checklist helps :p
<re_irc>
<Lachlan> Oh those are useful, thank you
<re_irc>
<Lachlan> I don't believe dcache is being cleared
<re_irc>
<Lachlan> I patched the hal to output what bank errors are occurring and it appears that the programming sequence is bad
<re_irc>
<James Munns> that smells like one of the first two things to me
<re_irc>
<James Munns> but that's a wild guess.
<re_irc>
<Lachlan> Yeah, hmm
<re_irc>
<James Munns> if nothing is immediately apparent, check the errata for that chip
<re_irc>
<Lachlan> I believe the flag is getting raised once the flash is locked again after writing
<re_irc>
<James Munns> sometimes they'll be like "lol you have to read this twice to actually clear the flag" or "you must wait 4 clock cycles before the state is actually correct"
<re_irc>
<Lachlan> Yeah, I don't see anything in erata
<re_irc>
<dirbaio> wasnt there a discussion about h7xx-hal flash bugs recently?
<re_irc>
<dirbaio> ah it was you 😂
<re_irc>
<Lachlan> It was yep lol
<re_irc>
<Lachlan> I thought I solved it but I'm not sure if I ended up running in release or not
<re_irc>
<Chris [pwnOrbitals]> Hi everyone, I’m having a DeviceError(timout) while writing to SD card through embedded-sdmmc on stm32h7 with the HAL. Reading from the SD card goes fine. Any idea how this could be ? Thanks
<re_irc>
<bugadani> wait, deprecating GATs is a real option? 😱
<re_irc>
<bugadani> my whole firmware is built around GATs, let's hope it's not what's going to happen
<re_irc>
<bugadani> +🤣
<re_irc>
<James Munns> "nightly means nightly"
<re_irc>
<bugadani> I know, but still
<re_irc>
<bugadani> One can hope
<re_irc>
<adamgreig> t-lang have to keep the nightly users on their toes somehow :P
<re_irc>
<jessebraham> They don't want us to be happy
<re_irc>
<jessebraham> (Joking of course)
<re_irc>
<James Munns> I think boats' comments are pretty level headed and ring true
<re_irc>
<James Munns> it's a splash of cold water, but "get shit done right" is more important than "get shit done", honestly.
dc740 has quit [Remote host closed the connection]
<re_irc>
<James Munns> "A good game is only late until it ships, a bad game is bad forever"
<Shell>
v much agreeing with boats here tbh.
dc740 has joined #rust-embedded
<re_irc>
<adamgreig> yea, I'm not sure I completely agree with "In general, it's better to offer an incomplete solution than no solution at all."
<re_irc>
<adamgreig> anyway, room meeting time again! agenda is https://hackmd.io/hcdyOdpFS_iO-IHm2yJXhg, please add anything you'd like to discuss or announce and we'll start in a few mins
<re_irc>
... compile rather than do the wrong thing
<re_irc>
<Chris [pwnOrbitals]> Not really an announcement, but I’ve been using Rust to develop the embedded software for a solar sail spacecraft (my company is a french start-up called GAMA) and it’s been going great ! Thank you everyone here for the support, I’ve been asking a lot of questions here :D and overall the ecosystem and community looks very active and healthy :)
<re_irc>
<adamgreig> one brief point from me, it's now 2 years since I joined the core team, and since then we haven't had any change in core team membership, maybe something for people to think over: should we rotate core team members? does anyone else want to be involved?
<re_irc>
<adamgreig> other than that I'm out of topics for this week, though we haven't quite resolved some of the embedded-hal questions like what to do with nb
<re_irc>
<James Munns> (as the only person who has rotated off the core team, I strongly support keeping new faces regularly on the team)
<re_irc>
<James Munns> Especially with N=3 core team members, rotating one at a time means there's always a fresh view and historical context.
<re_irc>
<Chris [pwnOrbitals]> What does it involve exactly ?
<re_irc>
<adamgreig> in practice it's 99% "run the weekly meeting"
<cr1901>
>as the only person who has rotated off the core team <-- japaric?
<re_irc>
<James Munns> He's still on there, AFAIK.
<cr1901>
ahhh
<re_irc>
<burrbull> there is also interesting PR by luojia65 https://github.com/rust-embedded/svd2rust/pull/627 . But it have some questions. Should we rename all field-related types (enums, readers and writers) or only enums?
<re_irc>
<adamgreig> oh, that is interesting and a nice idea
<re_irc>
<adamgreig> usually the PAC user does not interact with the enum, reader, or writer type names, right? except... in the documentation, where the current names can be quite confusing
<re_irc>
<burrbull> enums sometimes we are use
<re_irc>
<Chris [pwnOrbitals]> I just read about the weekly driver initiative, is this still going ?
<re_irc>
<therealprof> Chris [pwnOrbitals]: In theory, yes. In practise it's more <insert time window here> rather than weekly. 😅
<re_irc>
<burrbull> adamgreig: I don't have strict opinion. PR renames all of them
<re_irc>
<adamgreig> seems ok to me
<re_irc>
<adamgreig> ok, anyone have anything else to discuss or shall we close the meeting here?
<re_irc>
<Hmvp> I was wondering something
<re_irc>
<Hmvp> There is embedded time which sounds somewhat official, and there is fugit
<re_irc>
<Hmvp> Is there any consensus about whats best
<re_irc>
<Hmvp> Based on the usage numbers I'd say fugit is the place to be... Is it?
<re_irc>
<adamgreig> neither are "official" as such, but yea, I've used fugit a bunch recently and it's quite popular
<re_irc>
<adamgreig> they are slightly different and maybe one or the other will end up being more suitable - some libraries define a trait that either embedded-time or fugit could fulfil, e.g. rtic, so the user can pick which one to use
<re_irc>
<Hmvp> There are two hals that use e-time but at least one has a PR to switch
<re_irc>
<jessebraham> We decided on using "fugit" in "esp-hal" for what it's worth
<re_irc>
<therealprof> Slightly different focus but both are very useful.
<re_irc>
<therealprof> fugit is newer and more modern in its approach and use of Rust features.
<re_irc>
<therealprof> The creators of both hang out here, BTW.
<re_irc>
<Hmvp> I do encounter some friction with using drivers implement with one while the Hal uses something else...
<re_irc>
<therealprof> Indeed, that's not ideal.
<re_irc>
<adamgreig> there's occasionally talk of having some shared traits that both could implement, a la embedded-hal, but it's surprisingly tricky
<re_irc>
<Hmvp> For some reason I was under the impression that both libraries try to fullfil that role with some extra utility functions...
<re_irc>
<adamgreig> well, they both provide types rather than traits
<re_irc>
<adamgreig> thanks everyone, let's close the meeting here! I have to run, have a good evening 👋
<re_irc>
<Chris [pwnOrbitals]> Thanks for the organization adamgreig, good evening everyone