Cart New Account Login

HomeAbout usProductsSupportForumsBlogCustomer Service

search inside this forum
search inside all forums
Program received signal SIGTRAP, Trace/breakpoint trap.
Evgeny E. Oct 3, 2016 at 10:40 AM (10:40 hours)
Staff: Edison T.

  • Hello,

    I am using Multilink Universal FX revB. The hardware is MK50DX256CMC10 and the IDE is Atollic TrueStudio 5.5.2. The problem is when i try to debug the application, it first breaks at main, as expected, but if i let it run, it immidiatly break with "Program received signal SIGTRAP, Trace/breakpoint trap." message. I verified that no breakpoints are set, used the Firmware update utility to get the latest firmware.

    When i used the same environment but with J-Link debugger everything works fine.

    This is the console output:

    Temporary breakpoint 1, main () at ..\src\main.c:1960
    1960   {

    Program received signal SIGTRAP, Trace/breakpoint trap.
    Reset_Handler () at ..\src\k53_startup.c:73
    73    asm("ldr sp,=_estack\n\t");

    This is the GDB output:

    P&E GDB Server for Arm(R) devices, Version
    Copyright 2015, P&E Microcomputer Systems Inc, All rights reserved

    Loading library C:\PEMicro\gdb_server_kinetis\PEGDB\gdi\unit_ngs_arm_internal.dll ...

    Server 1 running on
    All Servers Running
    Full License Activated.
    Connection from "" via
    P&E Interface detected - Flash Version 9.72

    Forcing mass erase...

    Device is NXP_K5x_K50DX256M10.

    Mode is In-Circuit Debug.

    'Kinetis' is a registered trademark of Freescale.

    (C)opyright 2012, P&E Microcomputer Systems, Inc. (
    API version is 101

    Attempted to connect target while target was not initialized.
    Copyright 2012 P&E Microcomputer Systems,Inc.
    Command Line :C:\PEMicro\gdb_server_kinetis\PEGDB\pe_gdb_server.exe /crp


    Target has been RESET and is active.
    CMD>CM C:\PEMicro\gdb_server_kinetis\PEGDB\gdi\P&E\supportFiles_ARM\NXP\K5x\freescale_k50dx256m10_pflash_dflash_eeprom.arp


    ;version 1.14, 06/02/2014, Copyright 2014 P&E Microcomputer Systems, Inc. All rights reserved. [mk_256k_x_pflash_dflash_eeprom]

    ;device freescale, k50dx256m10, pflash_dflash_eeprom

    ;begin_cs device=$00000000, length=$14001000, ram=$20000000

    Loading programming algorithm ...

    Module has been erased.
    Reloading programming algorithm ...

    Processing Object File Data ...

    Verifying object file CRC-16 to device ranges ...
    block 00000000-00006657 ...

    Checksum Verification Successful. (Cumulative CRC-16=$5CC6)


    Target has been RESET and is active.
    Preset breakpoint encountered.

    Any suggestions why might this be happening?



  • I forgot to mention that i am using FreeRTOS V7.1.1

  • -Have you updated your Eclipse plugin to the latest version?
    -What settings do you have configured in your debug sessions?

    • I was able to find how to update the P&E plugin in Atollic TrueStudio without updating the TrueStudio itself. Seems like they dont want people to mess around with plugins that they provide. 

      The settings for the P&E GDB Server are as suggeted in the manual:

      Interface: ...USB Multilink FX ...
      Port: USB1: Multilink....
      Debug Shift Speed: (4) MULTILINK = 0.20 MHZ .....
      Delay after reset.... : 500ms
      Enable Flash Programming Dialog
      Always mass....
      Trace buffer size 128KB

      Device Name K50DX256M10

  • Hello, are you still having trouble with this?

  • Yes, i still have this problem

  • Do you know if this problem still occurs if you use the default project? What if you used an EVB such as a TWR board? You can also try updating the firmware of your Multilink device.

  • I already tried updating the firmware on the Multilink, it actually gets updated as a part of debug session start by the TrueStudio. I switched using J-Link debugger.

  • Just following up on this - I seem to be getting unexpected SIGTRAP breakpoints in KDS using a PEMicro Multilink Universal now. I'm not sure whether this is caused by the Multilink, KDS or pegdbserver. 

    About 6 months ago I never saw this type of exception/breakpoint. It seems to have started after updating my development toolchain.

    I'm using:

    KDS 3.2.0
    GNU ARM PEMicro Interface Debugging Support
    Win10 running as guest under MacOS Parallels 13

Add comment

   Want to comment? Please login or create a new PEMicro account.

© 2018 P&E Microcomputer Systems Inc.
Website Terms of Use and Sales Agreement