This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Stop mode issues

Hello, I'm trying to use stop mode on my MCBSTM32E eval board (MCU STM32F103ZE). I've found examples in Keil installation folders. It seems to work til I enable the Systick timer. Indeed, in this case the stop mode is ignored and the systick interrupt happens as usual without any effect. In the example, the Systick is disabled before entering stop mode and re-enable after. Why do we need to do so because in the Reference Manual (RM0008) page 52 (table10) it is said that the instruction is ignored if flags are not reset, but it is not the case here. I thought that by activating stop mode it would stop clocks and so the systick timer. Does anyone have this kind of trouble ?
Thanks in advance.

Parents
  • One more question about the stop mode. I realized my code and tested it by simulation. I now want to test it on the MCU. But the Ulink2 Jtag adapter seems not to like sleep mode. Once I launch the program the ulink "cannot access memory" and "the target dll has been cancelled - Debugger aborted". I dont know what to do. I've faced the same problem with the simple __WFI().
    After that I cannot download another program into my memory without changing boot mode...
    Thanks for any advice about debugging code with WFI/stop mode.

Reply
  • One more question about the stop mode. I realized my code and tested it by simulation. I now want to test it on the MCU. But the Ulink2 Jtag adapter seems not to like sleep mode. Once I launch the program the ulink "cannot access memory" and "the target dll has been cancelled - Debugger aborted". I dont know what to do. I've faced the same problem with the simple __WFI().
    After that I cannot download another program into my memory without changing boot mode...
    Thanks for any advice about debugging code with WFI/stop mode.

Children
No data