01:39 <firefrommoonligh> adamgreig: You're tim about disabling the dbug in low power modes to save battery worked. I don't know how much power it was using, but it appears to have been a lot

01:39 <firefrommoonligh> * adamgreig: You're tip about disabling the dbug in low power modes to save battery worked. I don't know how much power it was using, but it appears to have been a lot

01:40 <adamgreig-m> great!

01:49 <firefrommoonligh> Also of note: It appears stop mode without enabling the debug mode puts the device in an un-flashable state unless you connect with boot0=high

01:50 <firefrommoonligh> Ie JTAG errors in probe-run, and uanble-to-detect-device in ST-LINK utility

01:50 <firefrommoonligh> So might be worth always designing a button footprint that pulls boot0 high on devices that use low power modes

01:51 <firefrommoonligh> (for debugging, developing etc)

01:51 <firefrommoonligh> Maybe just not connect the button on production where you only expect to flash it once

01:52 <adamgreig-m> how about if you using --connect-under-reset?

01:52 <firefrommoonligh> Yep

01:52 <adamgreig-m> hmm, that doesn't seem right, wonder if it's a bug in probe-rs or something

01:52 <adamgreig-m> even in st-link?

01:52 <firefrommoonligh> Not sure; Im' figuring this out as I go

01:52 <adamgreig-m> boot0 is a useful get out of jail free card but all it does is change what code it starts running after reset

01:53 <adamgreig-m> but the --connect-under-reset takes effect before that even happens and stops the core before it executes anything, so at least in principle it should work regardless of power-saving mode

01:53 <adamgreig-m> not saying you're wrong, wouldn't be the first weird thing here and I always leave boot0 exposed for this and other reasons

01:53 <firefrommoonligh> It certainly could be something else

01:53 <adamgreig-m> just that it sounds surprising that it would need it

01:53 <adamgreig-m> usually I just leave boot0 pulled to 0V with a 10k resistor

01:53 <adamgreig-m> and then you can short it to 3v3 manually to recover

01:54 <adamgreig-m> rather than a button etc

01:54 <firefrommoonligh> I figured connect-under-reset would solve it too; IIRC that's its purpose

01:54 <adamgreig-m> especially convenient if you position the 10k resistor next to a 3v3 pad (like on a decoupling cap) so it's just a pad-to-pad short with tweezers

01:54 <adamgreig-m> make sure you actually have reset wired from the probe to the target :p

01:54 <firefrommoonligh> I have it pulled down with a 10k resistor; was able to pull high with a loose wire soldered on, then touched to an exposed VCC

01:54 <adamgreig-m> yea, exactly

01:55 <adamgreig-m> if you have metallic tweezers often they're a convenient and solder-free way to do this

01:55 <firefrommoonligh> That sounds like a better idea

01:55 <firefrommoonligh> just need to pull it until power on

01:55 <adamgreig-m> yea, or pulse reset while pulling it, via programmer or a reset button or whatever

01:55 <firefrommoonligh> I'll experiment more - curious why connect-under-reset isn't doing it, and why I need boot0 high