This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Eclipse debugger hangs up with "Starting target CPU..."

Hi!

I have been following this process to develop using armgcc and Eclipse: https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/development-with-gcc-and-eclipse

So far, I have successfully run the blinky code. However, when I am trying to run the code in "examples\ble_central_and_peripheral\experimental\ble_app_att_mtu_throughput" directory the debugger hangs up with "Starting target CPU..." (image attached). 

I am using nrf52840 DK, SDK version 14.0.0, GCC Toolchain 4.9 and JLink 6.40. 

I have followed the solution stated here: https://devzone.nordicsemi.com/f/nordic-q-a/15253/debugging-problem-with-gnu-arm-eclipse-toolchain-nrf52-blink, but the problem has not resolved. Any comment would be appreciated. Thanks!

Parents
  • Hi Rabbi,

    It is a little bit hard to say what the issue is. 
    It could be that you have set a breakpoint in main(), if you could show the CPU registers it could be easier to see if the code is running normally.

    However, I would highly recommend that you upgrade to SDK version 14.2 or newer since there it is introduced SES IDE support for free which in my opinion works a lot better than Eclipse.

    Also, the support is much better with using SES with nRF52x products.

    Best Regards,

    Martin L.

Reply
  • Hi Rabbi,

    It is a little bit hard to say what the issue is. 
    It could be that you have set a breakpoint in main(), if you could show the CPU registers it could be easier to see if the code is running normally.

    However, I would highly recommend that you upgrade to SDK version 14.2 or newer since there it is introduced SES IDE support for free which in my opinion works a lot better than Eclipse.

    Also, the support is much better with using SES with nRF52x products.

    Best Regards,

    Martin L.

Children
No Data
Related