Skip to main content
Development DGOC
Associate
September 11, 2017
Question

STM32L152C- Discovery ''target halted due to breakpoint'' while running

  • September 11, 2017
  • 2 replies
  • 822 views
Posted on September 11, 2017 at 13:45

Hi, I am using the STM32L152C- Discovery.

I am trying to run an example project from STM32CubeL1, however , I get the following error while running.

** Programming Started **

auto erase enabled

Info : Device: STM32L1xx (Cat.1 - Low/Medium Density)

Info : STM32L flash size is 128kb, base address is 0x8000000

STM32L152RCTx.cpu: target state: halted

target halted due to breakpoint, current mode: Thread

xPSR: 0x61000000 pc: 0x2000000e msp: 0x20008000

wrote 8192 bytes from file Debug/STM32L152C-Discovery.elf in 0.614524s (13.018 KiB/s)

** Programming Finished **

** Verify Started **

STM32L152RCTx.cpu: target state: halted

target halted due to breakpoint, current mode: Thread

xPSR: 0x61000000 pc: 0x2000002e msp: 0x20008000

verified 4152 bytes in 0.061745s (65.668 KiB/s)

** Verified OK **

** Resetting Target **

adapter speed: 240 kHz

shutdown command invoked
    This topic has been closed for replies.

    2 replies

    Nesrine M_O
    Associate
    September 11, 2017
    Posted on September 11, 2017 at 14:59

    Hi

    dev.dgoc

    ,

    1- Which

    STM32CubeL1 versionare you using?

    2- Which example did you looked to?

    3-what is your IDE ?

    Could you please provide more explanation on your case, so that it will be easier to understand the issue?

    -Nesrine-

    Development DGOC
    Associate
    September 12, 2017
    Posted on September 12, 2017 at 06:48

    Thank you,

    1- I am using STM32CubeL1_V1.7.0

    2-I am trying to run GPIO_IOToggle example on AC6 (SW4STM32).

    Vangelis Fortounas
    Associate II
    September 11, 2017
    Posted on September 11, 2017 at 16:29

    Hello!

    In System Workbench for STM32 this is not an Error.

    It means that the previous builded and linked image is succesfully loaded , verified  and running.

    Try to load the GPIO_IOToggle example for your discovery board to have visual evidence that the code is running.

    Rgrds

    vf