<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
<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
<adamgreig-m>
great!
<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
<firefrommoonligh>
Ie JTAG errors in probe-run, and uanble-to-detect-device in ST-LINK utility
<firefrommoonligh>
So might be worth always designing a button footprint that pulls boot0 high on devices that use low power modes
<firefrommoonligh>
Maybe just not connect the button on production where you only expect to flash it once
<adamgreig-m>
how about if you using --connect-under-reset?
<firefrommoonligh>
Yep
<adamgreig-m>
hmm, that doesn't seem right, wonder if it's a bug in probe-rs or something
<adamgreig-m>
even in st-link?
<firefrommoonligh>
Not sure; Im' figuring this out as I go
<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
<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
<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
<firefrommoonligh>
It certainly could be something else
<adamgreig-m>
just that it sounds surprising that it would need it
<adamgreig-m>
usually I just leave boot0 pulled to 0V with a 10k resistor
<adamgreig-m>
and then you can short it to 3v3 manually to recover
<adamgreig-m>
rather than a button etc
<firefrommoonligh>
I figured connect-under-reset would solve it too; IIRC that's its purpose
<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
<adamgreig-m>
make sure you actually have reset wired from the probe to the target :p
<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
<adamgreig-m>
yea, exactly
<adamgreig-m>
if you have metallic tweezers often they're a convenient and solder-free way to do this
<firefrommoonligh>
That sounds like a better idea
<firefrommoonligh>
just need to pull it until power on
<adamgreig-m>
yea, or pulse reset while pulling it, via programmer or a reset button or whatever
<firefrommoonligh>
I'll experiment more - curious why connect-under-reset isn't doing it, and why I need boot0 high
oaky has joined ##stm32-rs
oaky has quit [Client Quit]
oaky has joined ##stm32-rs
oaky has quit [Remote host closed the connection]
oaky has joined ##stm32-rs
cyrusmetcalf[m] has quit [Quit: Idle for 30+ days]
oaky_ has joined ##stm32-rs
oaky has quit [Ping timeout: 260 seconds]
oaky_ has quit [Read error: Connection reset by peer]