<re_irc>
<@firefrommoonlight:matrix.org> Does not work on F1 though, which it seems you're using
<re_irc>
<@lkostka:matrix.org> firefrommoonlight:matrix.org: ooooo totaly different approach without those awful macros and template meta programming. MUCH MUCH readable.
<re_irc>
<@lkostka:matrix.org> thx for the link
cr1901 has quit [Remote host closed the connection]
<re_irc>
<@w00tspeaks:matrix.org> All the the val24 enumeratedValues are garbage and not useful.
<re_irc>
<@w00tspeaks:matrix.org> For whatever reason, the file is generated with values of 0x18-0x1f that aren't actually useful, and they all get val24 as their names.
<re_irc>
<@burrbull:matrix.org> we have similar issue with new stm32 g0 SVDs
<re_irc>
<@burrbull:matrix.org> As I can see it is better to clear all enumeratedValues
<re_irc>
<@burrbull:matrix.org> If it's hard to do manually you could wtite script witch parse svd with `svd-parser`, iterate over all fields to clear them and resave with `svd-encoder`
<re_irc>
<@burrbull:matrix.org> And then use `svdtools` to add right values
<re_irc>
<@burrbull:matrix.org> Or use `svdtools` `clear` if you need clear only exact fields
<re_irc>
<@w00tspeaks:matrix.org> In this case, it would be good enough to delete all the val24 enumerated values in this peripheral (and a few others with different names, like val25) and keep the others.
<re_irc>
<@w00tspeaks:matrix.org> I'm wondering if svd2rust should just ignore dupes
<re_irc>
<@burrbull:matrix.org> You can use `.fields().filter(|f| f.name == "foo")` when iterate
<re_irc>
<@w00tspeaks:matrix.org> val24 is sometimes okay
<re_irc>
<@w00tspeaks:matrix.org> it's only in this peripheral
<re_irc>
<@w00tspeaks:matrix.org> Really, I just want anything with description == None to be gone
<re_irc>
<@w00tspeaks:matrix.org> I think that might work across teh board on this one.
<re_irc>
<@w00tspeaks:matrix.org> BTW, this svd is from the cmsis pack
<re_irc>
<@w00tspeaks:matrix.org> FWIW, I have tried to write something to use svdtools to patch the svd, but I haven't been successful.
starblue has quit [Ping timeout: 240 seconds]
tokomak has joined #rust-embedded
rardiol has quit [Ping timeout: 256 seconds]
<re_irc>
<@w00tspeaks:matrix.org> Wow. The svd for this board is just garbage. Especially the enumeratedValues.
<re_irc>
<@w00tspeaks:matrix.org> burrbull Do you manually remove all the enum values and add reasonable ones?
tokomak has quit [Read error: Connection reset by peer]
tokomak has joined #rust-embedded
<re_irc>
<@burrbull:matrix.org> w00tspeaks:matrix.org: If all values same as in example part, definetly yes
cr1901 has quit [Remote host closed the connection]
cr1901 has joined #rust-embedded
<re_irc>
<@monacoprinsen:matrix.org> Does anyone know how itm-decode works?
<re_irc>
<@monacoprinsen:matrix.org> When I run the flag and file in the /tmp folder it does not stay open to log anything.
<re_irc>
<@dirbaio:matrix.org> since it'll never return rustc doesn't bother to fully set up the stack frame or something..? Not sure if it's a probe-run bug or rustc bug
<re_irc>
<@dirbaio:matrix.org> now that you mention it, mine is unwinding into garbage lol
<re_irc>
<@mehmet:grusbv.com> dirbaio:matrix.org: This didn't change much
<re_irc>
<@mehmet:grusbv.com> Is there a code that I must have for the backtrace?
<re_irc>
<@mehmet:grusbv.com> Sth like defining a panic! macro
<re_irc>
<@mehmet:grusbv.com> or similiar
<re_irc>
<@dirbaio:matrix.org> no, it's all done by probe-run
<re_irc>
<@mehmet:grusbv.com> dirbaio:matrix.org: Oh that is odd.
<re_irc>
<@dirbaio:matrix.org> like, the firmware doesn't have the code for printing the stacktrace, it's probe-run that's reading the target's RAM to reconstruct the stack trace and printing it
<re_irc>
<@mehmet:grusbv.com> James Munns: I froze the toolchain to:
<re_irc>
<@mehmet:grusbv.com> Well, not dealbreaker I guess, since it is only main in most cases, right
<re_irc>
<@mehmet:grusbv.com> 👍️
<re_irc>
<@mehmet:grusbv.com> mehmet:grusbv.com: This happens only if I don't use --release now
<re_irc>
<@mehmet:grusbv.com> Should I make debug=1 explicit?
<re_irc>
<@mehmet:grusbv.com> If I don't state anything, is it default bench?
<re_irc>
<@dirbaio:matrix.org> I have no idea, Cargo docs will probably tell
<re_irc>
<@mehmet:grusbv.com> >The profile is automatically chosen based on which command is being run if a profile is not specified on the command-line.
<re_irc>
<@mehmet:grusbv.com> could be --dev though
<re_irc>
<@mehmet:grusbv.com> It sort of makes sense
<re_irc>
<@mehmet:grusbv.com> Now this is interesting, when my code is not optimized, and compiled to be 204 KiB, the code does not run (I get no defmt:info traces) And when I exit with Ctrl-C, I get the ERROR:
<re_irc>
<@mehmet:grusbv.com> Finished dev [unoptimized + debuginfo] target(s) in 0.62s
<re_irc>
<@adamgreig:matrix.org> thanks, published
rardiol has joined #rust-embedded
richardeoin has quit [Quit: WeeChat 2.8]
richardeoin has joined #rust-embedded
smach has quit [Ping timeout: 256 seconds]
<re_irc>
<@dbrgn:matrix.coredump.ch> Quick hardware question from a software guy... If I replace a 32.768 kHz LSE crystal with 50 kO ESR and 6 pF load capacitance (the Nucleo reference crystal) with another model that has 90 kO ESR and 12.5 pF load capacitance (thanks chip shortage...) , what will be the effect? Do I simply have to replace the two capacitors with different values and it will be OK? I assume the tradeoffs are accuracy and...
<re_irc>
... power consumption?
<re_irc>
<@dbrgn:matrix.coredump.ch> (NDK NX3215SA-32.768KHZ-EXS00A-MU00529 vs NX3215SA-32.768K-EXS00A-MU00003)
<re_irc>
<@dbrgn:matrix.coredump.ch> Also, is there some magic trick to get hold of some STM32L071s? 😅
<re_irc>
<@adamgreig:matrix.org> Yea, just change the load capacitors appropriately, there's not necessarily any tradeoff in accuracy
<re_irc>
<@adamgreig:matrix.org> Note the crystal's capacitance is not the number you need to buy capacitors in, but rather the combination of your two load caps and the trace/pin and stm32 internal caps
<re_irc>
<@dbrgn:matrix.coredump.ch> Thanks! Yes, currently I simply re-used the values from the reference design.
<re_irc>
<@josfemova:matrix.org> So, for the two and a half EOS-S3 owners around here: I've been working on writing the SVD for the thing. Very-Super-Ultra-Duper WIP, but fortunately there's an excel sheet with all the registers. I already got some of those transcribed, blinky already tested but there's a lot more left to test. Dunno if there's enough people to have a separate organization, right now i'm just working on a personal repo ...
<re_irc>
<@josfemova:matrix.org> Ofc I'm a n00b so help and counsel are deeply appreciated. I will keep working on getting all the remaining registers transcribed in the meantime
<re_irc>
<@josfemova:matrix.org> Special thanks to the people behind svdtools because xml is a god forsaken language and transcribing everything to yaml is way more comfy
<re_irc>
<@jamesmunns:beeper.com> Hey adamgreig, I think we're up to ~20 languages for the translation tweet, do you think this would merit a quick one-off blog post? I'm actually super happy at the level of response
<re_irc>
<@adamgreig:matrix.org> Yea, it's been a great response! Blog post sounds good to me
<re_irc>
<@jamesmunns:beeper.com> K, will add to the list for this week!