<re_irc>
<James Munns> So, question for all the Cortex-M/ASM folks:
<re_irc>
Does anyone know offhand what I need to in Cortex-M in an interrupt handler to basically totally context-switch-on-handler-exit? I have thread mode set up with it's own process stack, but if I wanted to "boot the app like new", I think I need to:
<re_irc>
- Wipe everything in the process address space, reset the stack pointer back to the top of the new (clear) stack
<re_irc>
- Put something (???) on the stack, to be restored on exit of the interrupt
<re_irc>
<James Munns> Basically in my tiny OS, I want some way to "exit"/"context switch"/"load new app". So app A would make a syscall, and when the syscall exits, I want to be back at the top of app B.
<re_irc>
<James Munns> (right now I "cheat" by just rebooting)
<re_irc>
<yruama_lairba> i just realize i don't understand some details about Alternate function
<re_irc>
<yruama_lairba> is there a special thing to do with alternate pin depending the alternate function read or write the pin ?
<re_irc>
<yruama_lairba> sorry, stm32 chip
<re_irc>
<yruama_lairba> ooops wasn't looking the right figure in datasheet. Apparantly alternate function manage automatically if the input schmitt trigger or output buffer should be enabled
<re_irc>
<Lachlan> I can't seem to get my stm32f1 to acknowledge CAN frames
<re_irc>
<Lachlan> It can send them, but can't receive them
<re_irc>
<Lachlan> Same with the raspi with an mcp2515 on the other side
<re_irc>
<Lachlan> I have them both hooked up to an oscilloscope, and the levels are pretty much the same. It's possible the bauds aren't the same. The can controller on the stm32f1 doesn't seem to do the bitrate that http://www.bittiming.can-wiki.info/ says it should.
<re_irc>
<James Munns> dumb question - do they have a common ground?
<re_irc>
<James Munns> I guess at least through the common oscilloscope ground, if you have them both connected.
<re_irc>
<aholtzma> has anyone used cargo-call-stack on stm32?