J-Link embedded in a Energy Micro STK-3600 on OSX loses communications whenever new code is flashed

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • J-Link embedded in a Energy Micro STK-3600 on OSX loses communications whenever new code is flashed

    Hi,

    I am using OSX and v4.82 of the J-Link drivers and after each time I flash the target processor (I am using the STK-3600 to debug my own design), almost every time I lose communications and have to disconnect the STK-3600 for a minute or two and then reconnect.

    If I plug the same STK-3700 into a Windows machine, I do not have this issue.

    Here is an example where the code downloads, but the fails to start the CPU:

    Source Code

    1. SEGGER J-Link GDB Server V4.82 Command Line Version
    3. JLinkARM.dll V4.82 (DLL compiled Mar 10 2014 19:13:25)
    5. -----GDB Server start settings-----
    6. GDBInit file: none
    7. GDB Server Listening port: 2331
    8. SWO raw output listening port: 2332
    9. Terminal I/O port: 2333
    10. Accept remote connection: localhost only
    11. Generate logfile: off
    12. Verify download: on
    13. Init regs on start: on
    14. Silent mode: off
    15. Single run mode: on
    16. Target connection timeout: 5 sec.
    17. ------J-Link related settings------
    18. J-Link Host interface: USB
    19. J-Link script: none
    20. J-Link settings file: none
    21. ------Target related settings------
    22. Target device: EFM32LG330F128
    23. Target interface: SWD
    24. Target interface speed: 4kHz
    25. Target endian: little
    27. Connecting to J-Link...
    28. J-Link is connected.
    29. Firmware: Energy Micro EFM32 compiled Nov 6 2012 20:02:43
    30. Hardware: V7.00
    31. S/N: 440004343
    32. Feature(s): GDB
    33. Checking target voltage...
    34. Target voltage: 3.34 V
    35. Listening on TCP/IP port 2331
    36. Connecting to target...Connected to target
    37. Waiting for GDB connection...Connected to 127.0.0.1
    38. Reading all registers
    39. Read 4 bytes @ address 0x00000000 (Data = 0x20008000)
    40. Target interface speed set to 30 kHz
    41. Resetting target
    42. Halting target CPU...
    43. ...Target halted (PC = 0x000000DC)
    44. R0 = 40088000, R1 = 00000000, R2 = 00000010, R3 = 00000000
    45. R4 = 100006FC, R5 = 10000754, R6 = 10000754, R7 = 00000000
    46. R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
    47. R12= 10000670, R13= 20008000, MSP= 20008000, PSP= 20001B78
    48. R14(LR) = FFFFFFFF, R15(PC) = 000000DC
    49. XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
    50. CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00
    51. Reading all registers
    52. Select auto target interface speed (2000 kHz)
    53. Flash breakpoints enabled
    54. Semi-hosting enabled (VectorAddr = 0x08)
    55. Semihosting I/O set to TELNET Client
    56. SWO disabled succesfully.
    57. SWO enabled succesfully.
    58. Downloading 16112 bytes @ address 0x00000000 - Verified OK
    59. Downloading 16176 bytes @ address 0x00003EF0 - Verified OK
    60. Downloading 16176 bytes @ address 0x00007E20 - Verified OK
    61. Downloading 16144 bytes @ address 0x0000BD50 - Verified OK
    62. Downloading 16144 bytes @ address 0x0000FC60 - Verified OK
    63. Downloading 16208 bytes @ address 0x00013B70 - Verified OK
    64. Downloading 4428 bytes @ address 0x00017AC0 - Verified OK
    65. Downloading 4 bytes @ address 0x00018C0C - Verified OK
    66. Downloading 8 bytes @ address 0x00018C10 - Verified OK
    67. Downloading 3776 bytes @ address 0x00018C18 - Verified OK
    68. Downloading 1536 bytes @ address 0x00019AD8 - Verified OK
    69. Read 4 bytes @ address 0x000000DC (Data = 0x47804801)
    70. Read 2 bytes @ address 0x00000122 (Data = 0xE7F6)
    71. Read 2 bytes @ address 0x000000E2 (Data = 0x4700)
    72. Read 2 bytes @ address 0x0000014C (Data = 0xF2C0)
    73. Read 2 bytes @ address 0x0000AB18 (Data = 0xF7FE)
    74. Read 2 bytes @ address 0x0000AB24 (Data = 0xF249)
    75. Read 2 bytes @ address 0x0000AB18 (Data = 0xF7FE)
    76. Read 2 bytes @ address 0x0000AB56 (Data = 0xF00A)
    77. Read 2 bytes @ address 0x0000B7D4 (Data = 0xF44F)
    78. Read 2 bytes @ address 0x0000B8CE (Data = 0xF04F)
    79. Read 2 bytes @ address 0x0000AB18 (Data = 0xF7FE)
    80. Read 2 bytes @ address 0x0000AB18 (Data = 0xF7FE)
    81. Read 2 bytes @ address 0x0000B920 (Data = 0xF640)
    82. Read 2 bytes @ address 0x0000B922 (Data = 0x0381)
    83. Read 2 bytes @ address 0x0000B924 (Data = 0xF2C2)
    84. Read 2 bytes @ address 0x0000B926 (Data = 0x0300)
    85. Read 2 bytes @ address 0x0000B920 (Data = 0xF640)
    86. Read 2 bytes @ address 0x0000AB18 (Data = 0xF7FE)
    87. Read 2 bytes @ address 0x0000AB52 (Data = 0xF7FF)
    88. Read 2 bytes @ address 0x0000B95E (Data = 0xF89D)
    89. Read 2 bytes @ address 0x0000B95E (Data = 0xF89D)
    90. Read 2 bytes @ address 0x0000AB18 (Data = 0xF7FE)
    91. Read 2 bytes @ address 0x0000AB18 (Data = 0xF7FE)
    92. Read 2 bytes @ address 0x0000AB18 (Data = 0xF7FE)
    93. Read 2 bytes @ address 0x0000AB56 (Data = 0xF00A)
    94. Read 2 bytes @ address 0x0000AB18 (Data = 0xF7FE)
    95. Read 2 bytes @ address 0x0000AB20 (Data = 0xF000)
    96. Read 2 bytes @ address 0x000000DC (Data = 0x4801)
    97. Read 4 bytes @ address 0x000000E4 (Data = 0x00000379)
    98. Read 2 bytes @ address 0x000000DE (Data = 0x4780)
    99. Read 2 bytes @ address 0x000000DE (Data = 0x4780)
    100. Read 2 bytes @ address 0x00004D16 (Data = 0x2051)
    101. Read 2 bytes @ address 0x00004D16 (Data = 0x2051)
    102. Read 2 bytes @ address 0x0000AB18 (Data = 0xF7FE)
    103. Read 2 bytes @ address 0x0000ABE6 (Data = 0xF249)
    104. Read 2 bytes @ address 0x0000AB18 (Data = 0xF7FE)
    105. Read 2 bytes @ address 0x0000AB56 (Data = 0xF00A)
    106. Read 2 bytes @ address 0x0000AB18 (Data = 0xF7FE)
    107. Read 2 bytes @ address 0x0000AB52 (Data = 0xF7FF)
    108. Read 2 bytes @ address 0x000099B8 (Data = 0x9B01)
    109. Read 2 bytes @ address 0x000099B8 (Data = 0x9B01)
    110. Read 2 bytes @ address 0x000000F0 (Data = 0x4901)
    111. Read 4 bytes @ address 0x000000F8 (Data = 0x20008000)
    112. Read 2 bytes @ address 0x000000F2 (Data = 0x468D)
    113. Read 2 bytes @ address 0x000000F2 (Data = 0x468D)
    114. Read 2 bytes @ address 0x0000AB18 (Data = 0xF7FE)
    115. Read 2 bytes @ address 0x0000AB18 (Data = 0xF7FE)
    116. Read 2 bytes @ address 0x0000AB18 (Data = 0xF7FE)
    117. Resetting target
    118. Halting target CPU...
    119. ...Target halted (PC = 0x000000DC)
    120. R0 = 40088000, R1 = 00000000, R2 = 00000010, R3 = 00000000
    121. R4 = 100006FC, R5 = 10000754, R6 = 10000754, R7 = 00000000
    122. R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
    123. R12= 10000670, R13= 20008000, MSP= 20008000, PSP= 20001B78
    124. R14(LR) = FFFFFFFF, R15(PC) = 000000DC
    125. XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
    126. CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00
    127. Reading all registers
    128. Read 4 bytes @ address 0x000000DC (Data = 0x47804801)
    129. Setting breakpoint @ address 0x000000DE, Size = 2, BPHandle = 0x0002
    130. Setting breakpoint @ address 0x000099B8, Size = 2, BPHandle = 0x0003
    131. Setting breakpoint @ address 0x0000AB18, Size = 2, BPHandle = 0x0004
    132. Setting breakpoint @ address 0x0000AB56, Size = 2, BPHandle = 0x0005
    133. Setting breakpoint @ address 0x0000ABE6, Size = 2, BPHandle = 0x0006
    134. Starting target CPU...
    135. ERROR: Communication timed out: Requested 24 bytes, received 0 bytes !
    136. Could not start CPU core. (ErrorCode: -1)
    137. ...Target halted (PC = 0x00000000)
    138. Reading all registers
    139. Removing breakpoint @ address 0x000000DE, Size = 2
    140. WARNING: Could not remove breakpoint @ address 0x000000DE
    141. Removing breakpoint @ address 0x000099B8, Size = 2
    142. WARNING: Could not remove breakpoint @ address 0x000099B8
    143. Removing breakpoint @ address 0x0000AB18, Size = 2
    144. WARNING: Could not remove breakpoint @ address 0x0000AB18
    145. Removing breakpoint @ address 0x0000AB56, Size = 2
    146. WARNING: Could not remove breakpoint @ address 0x0000AB56
    147. Removing breakpoint @ address 0x0000ABE6, Size = 2
    148. WARNING: Could not remove breakpoint @ address 0x0000ABE6
    149. WARNING: Failed to read memory @ address 0x00000000
    150. Read 4 bytes @ address 0x00000000 (Data = 0x00007FFF)
    151. WARNING: Failed to read memory @ address 0x00000000
    152. Read 4 bytes @ address 0x00000000 (Data = 0x00007FFF)
    153. Reading 140 bytes @ address 0x00000000
    154. WARNING: Failed to read memory @ address 0x00000000
    155. WARNING: Failed to read memory @ address 0x00000000
    156. Read 2 bytes @ address 0x00000000 (Data = 0x7FFF)
    157. Reading 100 bytes @ address 0x00000001
    158. WARNING: Failed to read memory @ address 0x00000001
    159. WARNING: Failed to read memory @ address 0x00000000
    160. Read 2 bytes @ address 0x00000000 (Data = 0x7FFF)
    161. Reading 100 bytes @ address 0x00000002
    162. WARNING: Failed to read memory @ address 0x00000002
    163. WARNING: Failed to read memory @ address 0x00000002
    164. Read 2 bytes @ address 0x00000002 (Data = 0x7FFF)
    165. Reading 100 bytes @ address 0x00000003
    166. WARNING: Failed to read memory @ address 0x00000003
    167. WARNING: Failed to read memory @ address 0x00000002
    168. Read 2 bytes @ address 0x00000002 (Data = 0x7FFF)
    169. Reading 100 bytes @ address 0x00000004
    170. WARNING: Failed to read memory @ address 0x00000004
    171. WARNING: Failed to read memory @ address 0x00000004
    172. Read 2 bytes @ address 0x00000004 (Data = 0x7FFF)
    173. Reading 100 bytes @ address 0x00000005
    174. WARNING: Failed to read memory @ address 0x00000005
    175. WARNING: Failed to read memory @ address 0x00000004
    176. Read 2 bytes @ address 0x00000004 (Data = 0x7FFF)
    Display All


    here is and example where it simple refuses to connect:

    Source Code

    1. SEGGER J-Link GDB Server V4.82 Command Line Version
    3. JLinkARM.dll V4.82 (DLL compiled Mar 10 2014 19:13:25)
    5. -----GDB Server start settings-----
    6. GDBInit file: none
    7. GDB Server Listening port: 2331
    8. SWO raw output listening port: 2332
    9. Terminal I/O port: 2333
    10. Accept remote connection: localhost only
    11. Generate logfile: off
    12. Verify download: on
    13. Init regs on start: on
    14. Silent mode: off
    15. Single run mode: on
    16. Target connection timeout: 5 sec.
    17. ------J-Link related settings------
    18. J-Link Host interface: USB
    19. J-Link script: none
    20. J-Link settings file: none
    21. ------Target related settings------
    22. Target device: EFM32LG330F128
    23. Target interface: SWD
    24. Target interface speed: 4kHz
    25. Target endian: little
    27. Connecting to J-Link...
    28. Connecting to J-Link failed. Connected correctly?
    29. GDBServer will be closed...
    30. Shutting down...
    Display All


    If again unplug and replug after several minutes, it works again.

    I have used Apples "USB Prober" Dev tool and note that I have to wait until the device completely disappears from the "Bus Probe" before it will work again.

    This is extremely frustrating.

    I tried to find the J-Link Commander tool listed on the downloads, but I cannot find it for OSX, does it exist four OSX?

    Cheers
    Douglas

    The post was edited 1 time, last by Douglas ().

  • *** UPDATE ****

    The board is actually a STK-3700 not a STK-3600 from Energy Micro (aka SILabs)

    I have moved the STK-3700 onto a WIn7 machine and am able to remotely debug via JLinkGDBServer on the Win7 machine from Eclipse on OSX with my own boards USB connected back to OSX and using "SerialTools" from the Apple App store as a terminal emulator for the USB CDC serial port my device uses. This works fine (v4.78d of JLink)

    I have also removed Apple's "USB Prober" DevTool for debug and tracing too and tried again fully under OSX, but before every debug session I have to completely power off the STK-3700 and then try to debug and more often than not I have to do that multiple times before it will work.

    The only USB devices I have are the STK-3700 and my own board being debugged.

    This is extremely frustrating.

  • Hi,

    Sorry to hear that you are running into problems.
    We are not aware of such issues.
    Please note that there is no direct support from SEGGER for the Energy Micro on-board debug probe (which is J-Link compatible but maintained by Energy Micro, now SiLabs).
    Can you provide the ELF file you are trying to download and debug under OS X?
    We will then give it a try here.

    PS:
    This is extremely frustrating.

    Just repeating that this frustrating for you, is not productive in any way... We heard you the first time..


    - Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi,

    I tried to find the J-Link Commander tool listed on the downloads, but I cannot find it for OSX, does it exist four OSX?

    Yes, of course:
    JLinkExe


    - Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi,

    Thanks for the feedback :)

    To try and simplify things I have created a smaller application that started to work the first time I download, but when I "Suspend" the application (Using Eclipse) it fails to read the memory and I can never re-flash or restart the debugging unless I unplug the STK3700 for a few minutes and then start all over. Note this is connecting to my own EFM32LG330F256 board.

    The same thing happens using the gdb CLI.

    If I then remove the STK3700 from my OSX machine and plug it into my Windows machine and I can remotely debug using the gdb server box, I can properly debug, change the code, ref lash, suspend, stop, single step, etc.

    When I reconnect back to my OSX machine, around 20% of the time I can initially load the code, it will sometimes run to the first time I suspend the code, then I cannot re-flash or restart the debug session.

    Here is a sample of the messages I get when connected to OSX:

    SEGGER J-Link GDB Server V4.82 Command Line Version

    JLinkARM.dll V4.82 (DLL compiled Mar 10 2014 19:13:25)

    -----GDB Server start settings-----
    GDBInit file: none
    GDB Server Listening port: 2331
    SWO raw output listening port: 2332
    Terminal I/O port: 2333
    Accept remote connection: localhost only
    Generate logfile: off
    Verify download: on
    Init regs on start: on
    Silent mode: off
    Single run mode: on
    Target connection timeout: 5 sec.
    ------J-Link related settings------
    J-Link Host interface: USB
    J-Link script: none
    J-Link settings file: none
    ------Target related settings------
    Target device: EFM32LG330F128
    Target interface: SWD
    Target interface speed: 4kHz
    Target endian: little

    Connecting to J-Link...
    J-Link is connected.
    Firmware: Energy Micro EFM32 compiled Nov 6 2012 20:02:43
    Hardware: V7.00
    S/N: 440004343
    Feature(s): GDB
    Checking target voltage...
    Target voltage: 3.32 V
    Listening on TCP/IP port 2331
    Connecting to target...Connected to target
    Waiting for GDB connection...Connected to 127.0.0.1
    Reading all registers
    Read 4 bytes @ address 0x00000000 (Data = 0x20008000)
    Target interface speed set to 30 kHz
    Resetting target
    Halting target CPU...
    ...Target halted (PC = 0x0000825C)
    R0 = 00000000, R1 = 00006E90, R2 = 00006E90, R3 = 00006E8F
    R4 = 00000000, R5 = 00000000, R6 = 00000000, R7 = 00000000
    R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
    R12= 00000052, R13= 20008000, MSP= 20008000, PSP= 20006488
    R14(LR) = FFFFFFFF, R15(PC) = 0000825C
    XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
    CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00
    Reading all registers
    Select auto target interface speed (2000 kHz)
    Flash breakpoints enabled
    Semi-hosting enabled (VectorAddr = 0x08)
    Semihosting I/O set to TELNET Client
    SWO disabled succesfully.
    SWO enabled succesfully.
    Downloading 12556 bytes @ address 0x00000000 - Verified OK
    Downloading 4 bytes @ address 0x0000310C - Verified OK
    Downloading 8 bytes @ address 0x00003110 - Verified OK
    Downloading 160 bytes @ address 0x00003118 - Verified OK
    Downloading 32 bytes @ address 0x000031B8 - Verified OK
    Writing register (PC = 0x000000dc)
    Read 4 bytes @ address 0x000000DC (Data = 0x47804801)
    Read 2 bytes @ address 0x000012CC (Data = 0x2300)
    Read 2 bytes @ address 0x000012CC (Data = 0x2300)
    Read 2 bytes @ address 0x000012CC (Data = 0x2300)
    Resetting target
    Halting target CPU...
    ...Target halted (PC = 0x000000DC)
    R0 = 00000000, R1 = 00000000, R2 = 00000010, R3 = 669C55EF
    R4 = 100006FC, R5 = 10000754, R6 = 10000754, R7 = 00000000
    R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
    R12= 10000670, R13= 20008000, MSP= 20008000, PSP= 20006488
    R14(LR) = FFFFFFFF, R15(PC) = 000000DC
    XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
    CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00
    Reading all registers
    Read 4 bytes @ address 0x000000DC (Data = 0x47804801)
    Setting breakpoint @ address 0x000012CC, Size = 2, BPHandle = 0x0002
    Starting target CPU...
    ERROR: Communication timed out: Requested 24 bytes, received 0 bytes !
    Could not start CPU core. (ErrorCode: -1)
    ...Target halted (PC = 0x00000000)
    Debugger requested to halt target...
    Reading all registers
    Removing breakpoint @ address 0x000012CC, Size = 2
    WARNING: Could not remove breakpoint @ address 0x000012CC
    WARNING: Failed to read memory @ address 0x00000000
    Read 4 bytes @ address 0x00000000 (Data = 0x00007FFF)
    WARNING: Failed to read memory @ address 0x00000000
    Read 4 bytes @ address 0x00000000 (Data = 0x00007FFF)
    Reading 100 bytes @ address 0x00000000
    WARNING: Failed to read memory @ address 0x00000000
    WARNING: Failed to read memory @ address 0x00000018
    Read 2 bytes @ address 0x00000018 (Data = 0x7FFF)
    Reading 108 bytes @ address 0x00000001
    WARNING: Failed to read memory @ address 0x00000001
    WARNING: Failed to read memory @ address 0x00000018
    Read 2 bytes @ address 0x00000018 (Data = 0x7FFF)
    Reading 108 bytes @ address 0x00000002
    WARNING: Failed to read memory @ address 0x00000002
    WARNING: Failed to read memory @ address 0x00000018
    Read 2 bytes @ address 0x00000018 (Data = 0x7FFF)
    Reading 108 bytes @ address 0x00000003
    WARNING: Failed to read memory @ address 0x00000003
    WARNING: Failed to read memory @ address 0x00000018
    Read 2 bytes @ address 0x00000018 (Data = 0x7FFF)
    Reading 108 bytes @ address 0x00000004
    WARNING: Failed to read memory @ address 0x00000004
    WARNING: Failed to read memory @ address 0x00000018
    Read 2 bytes @ address 0x00000018 (Data = 0x7FFF)
    Reading 108 bytes @ address 0x00000005
    WARNING: Failed to read memory @ address 0x00000005
    WARNING: Failed to read memory @ address 0x00000018
    Read 2 bytes @ address 0x00000018 (Data = 0x7FFF)

    If I then Exit the debug session and close Eclipse down completely and try:

    SEGGER J-Link Commander V4.82 ('?' for help)
    Compiled Mar 10 2014 19:13:30
    Can not connect to J-Link via USB.
    J-Link>

    I then removed the STK3700 from the USB port and replugged it in after about 15 seconds and re-ran JLinkexe:

    SEGGER J-Link Commander V4.82 ('?' for help)
    Compiled Mar 10 2014 19:13:30
    DLL version V4.82, compiled Mar 10 2014 19:13:25
    Firmware: Energy Micro EFM32 compiled Nov 6 2012 20:02:43
    Hardware: V7.00
    S/N: 440004343
    Feature(s): GDB
    VTarget = 1.157V
    No devices found on JTAG chain. Trying to find device on SWD.

    WARNING: RESET (pin 15) high, but should be low. Please check target hardware.

    WARNING: RESET (pin 15) high, but should be low. Please check target hardware.
    No device found on SWD.
    Did not find any core.
    Failed to identify target. Trying again with slow (4 kHz) speed.

    WARNING: RESET (pin 15) high, but should be low. Please check target hardware.
    No devices found on JTAG chain. Trying to find device on SWD.

    WARNING: RESET (pin 15) high, but should be low. Please check target hardware.
    No device found on SWD.
    Did not find any core.
    No device found at all. Selecting JTAG as default target interface.

    *** J-Link V4.82 Error ***
    Debugger tries to select target interface JTAG.
    This interface is not supported by the connected emulator.
    Selection will be ignored by the DLL.
    *** J-Link V4.82 Error ***

    J-Link>

    I then checked my circuit diagram and the reset pin from the debug port on the STK3700 goes directly to the reset pin on the EFM32LG330F256 and has no other components on it.

    I Then unplugged the STK-3700 for a minute, and retried and got:

    SEGGER J-Link Commander V4.82 ('?' for help)
    Compiled Mar 10 2014 19:13:30
    DLL version V4.82, compiled Mar 10 2014 19:13:25
    Firmware: Energy Micro EFM32 compiled Nov 6 2012 20:02:43
    Hardware: V7.00
    S/N: 440004343
    Feature(s): GDB
    VTarget = 3.336V
    Info: Found SWD-DP with ID 0x2BA01477
    Info: Found Cortex-M3 r2p1, Little endian.
    Info: FPUnit: 6 code (BP) slots and 2 literal slots
    Info: TPIU fitted.
    Info: ETM fitted.
    Found 1 JTAG device, Total IRLen = 4:
    Cortex-M3 identified.
    Target interface speed: 100 kHz
    J-Link>f
    Firmware: Energy Micro EFM32 compiled Nov 6 2012 20:02:43
    Hardware: V7.00

    J-Link>


    Cheers
    Douglas
    Files

  • I have tried the V4.83a beta version and from a freshly plugged in device I get:

    Source Code

    1. SEGGER J-Link GDB Server V4.83a (beta) Command Line Version
    3. JLinkARM.dll V4.83a (DLL compiled Mar 25 2014 19:17:44)
    5. -----GDB Server start settings-----
    6. GDBInit file: none
    7. GDB Server Listening port: 2331
    8. SWO raw output listening port: 2332
    9. Terminal I/O port: 2333
    10. Accept remote connection: localhost only
    11. Generate logfile: on
    12. Verify download: on
    13. Init regs on start: on
    14. Silent mode: off
    15. Single run mode: on
    16. Target connection timeout: 5 sec.
    17. ------J-Link related settings------
    18. J-Link Host interface: USB
    19. J-Link script: none
    20. J-Link settings file: none
    21. ------Target related settings------
    22. Target device: EFM32LG330F256
    23. Target interface: SWD
    24. Target interface speed: 1000kHz
    25. Target endian: little
    27. Connecting to J-Link...
    28. J-Link is connected.
    29. Firmware: Energy Micro EFM32 compiled Nov 6 2012 20:02:43
    30. Hardware: V7.00
    31. S/N: 440004343
    32. Feature(s): GDB
    33. Checking target voltage...
    34. Target voltage: 3.32 V
    35. Listening on TCP/IP port 2331
    36. Connecting to target...Connected to target
    37. Waiting for GDB connection...Connected to 127.0.0.1
    38. Reading all registers
    39. Read 4 bytes @ address 0x00000000 (Data = 0x20008000)
    40. Target interface speed set to 2667 kHz
    41. Resetting target
    42. Halting target CPU...
    43. ...Target halted (PC = 0x00008294)
    44. R0 = 200065AC, R1 = 00000000, R2 = 20006740, R3 = 20006740
    45. R4 = 00000000, R5 = 00000000, R6 = 00000000, R7 = 00000000
    46. R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
    47. R12= 00000052, R13= 20008000, MSP= 20008000, PSP= 20006488
    48. R14(LR) = FFFFFFFF, R15(PC) = 00008294
    49. XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
    50. CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00
    51. Reading all registers
    52. Target interface speed set to 2000 kHz
    53. Flash breakpoints enabled
    54. Semi-hosting enabled (VectorAddr = 0x08)
    55. Semihosting I/O set to TELNET and GDB Client
    56. SWO disabled succesfully.
    57. SWO enabled succesfully.
    58. Downloading 16096 bytes @ address 0x00000000 - Verified OK
    59. Downloading 16144 bytes @ address 0x00003EE0 - Verified OK
    60. Downloading 16128 bytes @ address 0x00007DF0 - Verified OK
    61. Downloading 16144 bytes @ address 0x0000BCF0 - Verified OK
    62. Downloading 9820 bytes @ address 0x0000FC00 - Verified OK
    63. Downloading 8 bytes @ address 0x0001225C - Verified OK
    64. Downloading 2276 bytes @ address 0x00012264 - Verified OK
    65. Read 4 bytes @ address 0x00008294 (Data = 0x47804807)
    66. Read 2 bytes @ address 0x00006546 (Data = 0x9B01)
    67. Read 2 bytes @ address 0x00006576 (Data = 0x484A)
    68. Read 2 bytes @ address 0x00007434 (Data = 0xF7FF)
    69. Read 2 bytes @ address 0x00007434 (Data = 0xF7FF)
    70. Read 2 bytes @ address 0x00006B04 (Data = 0x4812)
    71. Read 2 bytes @ address 0x00006B0E (Data = 0x4B12)
    72. Read 2 bytes @ address 0x00007434 (Data = 0xF7FF)
    73. Read 2 bytes @ address 0x00007434 (Data = 0xF7FF)
    74. Read 2 bytes @ address 0x00007434 (Data = 0xF7FF)
    75. Resetting target
    76. Halting target CPU...
    77. ...Target halted (PC = 0x00008294)
    78. R0 = 40088000, R1 = 00000000, R2 = 00000010, R3 = 00000000
    79. R4 = 100006FC, R5 = 10000754, R6 = 10000754, R7 = 00000000
    80. R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
    81. R12= 10000670, R13= 20008000, MSP= 20008000, PSP= 20006488
    82. R14(LR) = FFFFFFFF, R15(PC) = 00008294
    83. XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
    84. CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00
    85. Reading all registers
    86. Read 4 bytes @ address 0x00008294 (Data = 0x47804807)
    87. Setting breakpoint @ address 0x00006576, Size = 2, BPHandle = 0x0002
    88. Setting breakpoint @ address 0x00007434, Size = 2, BPHandle = 0x0003
    89. Starting target CPU...
    90. ERROR: Communication timed out: Requested 24 bytes, received 0 bytes !
    91. Could not start CPU core. (ErrorCode: -1)
    92. ...Target halted (PC = 0x00000000)
    93. Reading all registers
    94. Removing breakpoint @ address 0x00006576, Size = 2
    95. WARNING: Could not remove breakpoint @ address 0x00006576
    96. Removing breakpoint @ address 0x00007434, Size = 2
    97. WARNING: Could not remove breakpoint @ address 0x00007434
    98. WARNING: Failed to read memory @ address 0x00000000
    99. Read 4 bytes @ address 0x00000000 (Data = 0x00007FFF)
    100. WARNING: Failed to read memory @ address 0x00000000
    101. Read 4 bytes @ address 0x00000000 (Data = 0x00007FFF)
    102. Reading 100 bytes @ address 0x00000000
    103. WARNING: Failed to read memory @ address 0x00000000
    104. WARNING: Failed to read memory @ address 0x00000000
    105. Read 2 bytes @ address 0x00000000 (Data = 0x7FFF)
    106. Reading 108 bytes @ address 0x00000001
    107. WARNING: Failed to read memory @ address 0x00000001
    108. WARNING: Failed to read memory @ address 0x00000000
    109. Read 2 bytes @ address 0x00000000 (Data = 0x7FFF)
    110. Reading 108 bytes @ address 0x00000002
    111. WARNING: Failed to read memory @ address 0x00000002
    112. WARNING: Failed to read memory @ address 0x00000002
    113. Read 2 bytes @ address 0x00000002 (Data = 0x7FFF)
    114. Reading 108 bytes @ address 0x00000003
    115. WARNING: Failed to read memory @ address 0x00000003
    116. WARNING: Failed to read memory @ address 0x00000002
    117. Read 2 bytes @ address 0x00000002 (Data = 0x7FFF)
    118. Reading 108 bytes @ address 0x00000004
    119. WARNING: Failed to read memory @ address 0x00000004
    120. WARNING: Failed to read memory @ address 0x00000004
    121. Read 2 bytes @ address 0x00000004 (Data = 0x7FFF)
    122. Reading 108 bytes @ address 0x00000005
    123. WARNING: Failed to read memory @ address 0x00000005
    124. WARNING: Failed to read memory @ address 0x00000004
    125. Read 2 bytes @ address 0x00000004 (Data = 0x7FFF)
    Display All


    Any thoughts?

    Cheers
    Douglas

  • I have just upgraded to v4.84 and my MAC rebooted after detecting a memory leak, possibly in the JLinkGDBServer:

    Here is the log that was generated and sent to Apple:

    Source Code

    1. Sat Mar 29 16:20:09 2014
    2. panic(cpu 2 caller 0xffffff8017c5220d): "zalloc: zone map exhausted while allocating from zone socache zone, likely due to memory leak in zone socache zone (2609041248 total bytes, 1289052 elements allocated)"@/SourceCache/xnu/xnu-2422.90.20/osfmk/kern/zalloc.c:2494
    3. Backtrace (CPU 2), Frame : Return Address
    4. 0xffffff8025efbc80 : 0xffffff8017c22fa9
    5. 0xffffff8025efbd00 : 0xffffff8017c5220d
    6. 0xffffff8025efbe00 : 0xffffff8018011533
    7. 0xffffff8025efbe20 : 0xffffff8018011642
    8. 0xffffff8025efbe70 : 0xffffff8018011a7d
    9. 0xffffff8025efbeb0 : 0xffffff801801e4a0
    10. 0xffffff8025efbf10 : 0xffffff801801e380
    11. 0xffffff8025efbf50 : 0xffffff801803e363
    12. 0xffffff8025efbfb0 : 0xffffff8017cf3b26
    14. BSD process name corresponding to current thread: JLinkGDBServer
    16. Mac OS version:
    17. 13C64
    19. Kernel version:
    20. Darwin Kernel Version 13.1.0: Thu Jan 16 19:40:37 PST 2014; root:xnu-2422.90.20~2/RELEASE_X86_64
    21. Kernel UUID: 9FEA8EDC-B629-3ED2-A1A3-6521A1885953
    22. Kernel slide: 0x0000000017a00000
    23. Kernel text base: 0xffffff8017c00000
    24. System model name: iMac14,2 (Mac-27ADBB7B4CEE8E61)
    26. System uptime in nanoseconds: 602607367901984
    27. vm objects:29536864
    28. vm object hash entri:4120800
    29. VM map entries:4946400
    30. Reserved VM map entr:2015680
    31. pv_list:19894272
    32. vm pages:146889432
    33. kalloc.32:1604736
    34. kalloc.64:102517632
    35. kalloc.128:174862336
    36. kalloc.256:10067968
    37. kalloc.512:13991936
    38. kalloc.1024:5935104
    39. kalloc.2048:2027520
    40. kalloc.4096:2732032
    41. kalloc.8192:8708096
    42. mem_obj_control:1651584
    43. wait queue links:1370880
    44. ipc ports:6401440
    45. threads:1436304
    46. vnodes:31713840
    47. namecache:10958880
    48. HFS node:42766608
    49. HFS fork:13008896
    50. cluster_write:9857752
    51. decmpfs_cnode:1939392
    52. buf.8192:38903808
    53. ubc_info zone:8714992
    54. socache zone:2609041248
    55. vnode pager structur:3595600
    56. Kernel Stacks:2392064
    57. PageTables:83845120
    58. Kalloc.Large:25791964
    60. Backtrace suspected of leaking: (outstanding bytes: 2534048)
    61. 0xffffff8017c51d13
    62. 0xffffff8018011533
    63. 0xffffff8018011642
    64. 0xffffff8018011a7d
    65. 0xffffff801801e4a0
    66. 0xffffff801801e380
    67. 0xffffff801803e363
    69. last loaded kext at 602511689809096: com.apple.driver.AppleUSBCDCECMData 4.2.1b5 (addr 0xffffff7f9a2e3000, size 28672)
    70. last unloaded kext at 602468921991897: com.apple.driver.AppleUSBCDC 4.2.1b5 (addr 0xffffff7f9a2d4000, size 16384)
    71. loaded kexts:
    72. com.apple.driver.AppleUSBCDCECMData 4.2.1b5
    73. com.apple.driver.AppleUSBCDCACMData 4.2.1b5
    74. com.apple.driver.AppleUSBCDC 4.2.1b5
    75. com.apple.filesystems.afpfs 11.1
    76. com.apple.nke.asp-tcp 8.0.1
    77. com.apple.filesystems.smbfs 2.0.1
    78. com.apple.driver.AudioAUUC 1.60
    79. com.apple.driver.AppleHWSensor 1.9.5d0
    80. com.apple.driver.AppleBluetoothMultitouch 80.14
    81. com.apple.driver.ApplePlatformEnabler 2.0.9d1
    82. com.apple.driver.AGPM 100.14.15
    83. com.apple.driver.X86PlatformShim 1.0.0
    84. com.apple.filesystems.autofs 3.0
    85. com.apple.iokit.IOBluetoothSerialManager 4.2.3f10
    86. com.apple.driver.AppleMikeyHIDDriver 124
    87. com.apple.driver.AppleMikeyDriver 2.6.0f1
    88. com.apple.driver.AppleHDA 2.6.0f1
    89. com.apple.iokit.IOUserEthernet 1.0.0d1
    90. com.apple.Dont_Steal_Mac_OS_X 7.0.0
    91. com.apple.driver.AppleHWAccess 1
    92. com.apple.driver.AppleUpstreamUserClient 3.5.13
    93. com.apple.GeForce 8.2.4
    94. com.apple.driver.AppleBacklight 170.3.5
    95. com.apple.driver.AppleMCCSControl 1.1.12
    96. com.apple.driver.AppleThunderboltIP 1.1.2
    97. com.apple.driver.AppleIntelHD5000Graphics 8.2.4
    98. com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.3f10
    99. com.apple.driver.AppleLPC 1.7.0
    100. com.apple.driver.AppleSMCLMU 2.0.4d1
    101. com.apple.driver.AppleIntelFramebufferAzul 8.2.4
    102. com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
    103. com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
    104. com.apple.BootCache 35
    105. com.apple.driver.AppleUSBHub 666.4.0
    106. com.apple.driver.XsanFilter 404
    107. com.apple.iokit.IOAHCIBlockStorage 2.5.1
    108. com.apple.driver.AppleSDXC 1.5.2
    109. com.apple.driver.AirPort.Brcm4360 831.21.63
    110. com.apple.iokit.AppleBCM5701Ethernet 3.8.1b2
    111. com.apple.driver.AppleAHCIPort 3.0.0
    112. com.apple.driver.AppleUSBXHCI 670.4.0
    113. com.apple.driver.AppleRTC 2.0
    114. com.apple.driver.AppleACPIButtons 2.0
    115. com.apple.driver.AppleHPET 1.8
    116. com.apple.driver.AppleSMBIOS 2.1
    117. com.apple.driver.AppleACPIEC 2.0
    118. com.apple.driver.AppleAPIC 1.7
    119. com.apple.nke.applicationfirewall 153
    120. com.apple.security.quarantine 3
    121. com.apple.driver.AppleUSBCDCACMControl 4.2.1b5
    122. com.apple.security.SecureRemotePassword 1.0
    123. com.apple.driver.AppleBluetoothHIDKeyboard 170.15
    124. com.apple.driver.AppleHIDKeyboard 170.15
    125. com.apple.driver.IOBluetoothHIDDriver 4.2.3f10
    126. com.apple.driver.AppleMultitouchDriver 245.13
    127. com.apple.kext.triggers 1.0
    128. com.apple.iokit.IOSerialFamily 10.0.7
    129. com.apple.driver.DspFuncLib 2.6.0f1
    130. com.apple.vecLib.kext 1.0.0
    131. com.apple.iokit.IOAudioFamily 1.9.5fc2
    132. com.apple.kext.OSvKernDSPLib 1.14
    133. com.apple.iokit.KLog 650.4.0
    134. com.apple.iokit.IOBluetoothFamily 4.2.3f10
    135. com.apple.nvidia.driver.NVDAGK100Hal 8.2.4
    136. com.apple.nvidia.driver.NVDAResman 8.2.4
    137. com.apple.iokit.IOAcceleratorFamily 98.14
    138. com.apple.driver.AppleSMBusPCI 1.0.12d1
    139. com.apple.driver.AppleBacklightExpert 1.0.4
    140. com.apple.driver.AppleSMBusController 1.0.11d1
    141. com.apple.driver.X86PlatformPlugin 1.0.0
    142. com.apple.driver.AppleThunderboltEDMSink 2.1.3
    143. com.apple.iokit.IOSurface 91
    144. com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.3f10
    145. com.apple.driver.IOPlatformPluginFamily 5.7.0d10
    146. com.apple.iokit.IONDRVSupport 2.4.1
    147. com.apple.driver.AppleSMC 3.1.8
    148. com.apple.driver.AppleHDAController 2.6.0f1
    149. com.apple.iokit.IOHDAFamily 2.6.0f1
    150. com.apple.AppleGraphicsDeviceControl 3.4.35
    151. com.apple.iokit.IOAcceleratorFamily2 98.14
    152. com.apple.iokit.IOGraphicsFamily 2.4.1
    153. com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.6
    154. com.apple.driver.AppleUSBMergeNub 650.4.0
    155. com.apple.driver.AppleUSBComposite 656.4.1
    156. com.apple.driver.AppleThunderboltDPOutAdapter 3.1.7
    157. com.apple.driver.AppleThunderboltDPInAdapter 3.1.7
    158. com.apple.driver.AppleThunderboltDPAdapterFamily 3.1.7
    159. com.apple.driver.AppleThunderboltPCIDownAdapter 1.4.5
    160. com.apple.iokit.IOUSBUserClient 660.4.2
    161. com.apple.driver.AppleThunderboltNHI 2.0.1
    162. com.apple.iokit.IOThunderboltFamily 3.2.7
    163. com.apple.iokit.IO80211Family 630.35
    164. com.apple.iokit.IOEthernetAVBController 1.0.3b4
    165. com.apple.driver.mDNSOffloadUserClient 1.0.1b5
    166. com.apple.iokit.IONetworkingFamily 3.2
    167. com.apple.iokit.IOAHCIFamily 2.6.5
    168. com.apple.iokit.IOUSBFamily 675.4.0
    169. com.apple.driver.AppleEFINVRAM 2.0
    170. com.apple.driver.AppleEFIRuntime 2.0
    171. com.apple.iokit.IOHIDFamily 2.0.0
    172. com.apple.iokit.IOSMBusFamily 1.1
    173. com.apple.security.sandbox 278.11
    174. com.apple.kext.AppleMatch 1.0.0d1
    175. com.apple.security.TMSafetyNet 7
    176. com.apple.driver.AppleKeyStore 2
    177. com.apple.driver.DiskImages 371.1
    178. com.apple.iokit.IOStorageFamily 1.9
    179. com.apple.iokit.IOReportFamily 23
    180. com.apple.driver.AppleFDEKeyStore 28.30
    181. com.apple.driver.AppleACPIPlatform 2.0
    182. com.apple.iokit.IOPCIFamily 2.9
    183. com.apple.iokit.IOACPIFamily 1.4
    184. com.apple.kec.pthread 1
    185. com.apple.kec.corecrypto 1.0
    186. Model: iMac14,2, BootROM IM142.0118.B00, 4 processors, Intel Core i5, 3.4 GHz, 8 GB, SMC 2.15f2
    187. Graphics: NVIDIA GeForce GTX 775M, NVIDIA GeForce GTX 775M, PCIe, 2048 MB
    188. Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3430554738454655352D474E4C2D46
    189. Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3430554738454655352D474E4C2D46
    190. AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x111), Broadcom BCM43xx 1.0 (6.30.223.154.63)
    191. Bluetooth: Version 4.2.3f10 13477, 3 services, 23 devices, 1 incoming serial ports
    192. Network Service: Wi-Fi, AirPort, en1
    193. Serial ATA Device: APPLE HDD WD10EZES-40UFAA0, 1 TB
    194. USB Device: EFM32 USB CDC serial port device
    195. USB Device: FaceTime HD Camera (Built-in)
    196. USB Device: BRCM20702 Hub
    197. USB Device: Bluetooth USB Host Controller
    198. USB Device: EFM32
    199. Thunderbolt Bus: iMac, Apple Inc., 23.10
    Display All

    Cheers
    Douglas

  • Hi Douglas,

    We possibly found the issue. Cannot guarantee it, but the behavior looks quite the same but under other circumstances.
    Note: It *only* shows up with the OB on the Energy Micro board (which is not directly maintained & supported by SEGGER).
    It does not show up with any "full" J-Link.
    We are planning to have a new version by the end of this week.


    Best regards
    Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi Douglas,

    Should be fixed in V4.84a: segger.com/jlink-software.html


    Best regards
    Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi Again,

    I have downloaded v4.84a and the very first time I connect to my board it works perfectly and I download into flash and can debug, etc.

    BUT, when I stop, then update my code and re-download, I again get the time out errors.

    I have to then unplug the STK3700, wait a few minutes and plug back in and again, the first download and debug works, but no subsequent download to flash and debugs work.

    More than happy if you want me to test a version that perhaps generates more debug messages if that helps to diagnose the issue.

    Thanks for your help to date.

    Cheers
    Douglas

  • Hi Douglas,

    We need a reproduction scenario which allows us to reproduce the problem here in house on an eval board.
    So far, we are not aware of *any* problems with the current release.


    - Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi,

    I have returned to try 4.86 which I noticed had some OSX fixes that might address my issue.

    However, it now fails every time when the flash has completed and JLink is starting the CPU:

    J-Link found 1 JTAG device, Total IRLen = 4
    JTAG ID: 0x2BA01477 (Cortex-M3)
    Connected to target
    Waiting for GDB connection...Connected to 127.0.0.1
    Reading all registers
    Read 4 bytes @ address 0x00000000 (Data = 0x20008000)
    Target interface speed set to 1000 kHz
    Resetting target
    Halting target CPU...
    ...Target halted (PC = 0x00008B9C)
    R0 = 00000000, R1 = 00000000, R2 = 00000000, R3 = 00000001
    R4 = 00000000, R5 = 00000000, R6 = 00000000, R7 = 00000000
    R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
    R12= 00000000, R13= 20008000, MSP= 20008000, PSP= 20006D00
    R14(LR) = FFFFFFFF, R15(PC) = 00008B9C
    XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
    CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00
    Reading all registers
    Target interface speed set to 2000 kHz
    Flash breakpoints enabled
    Semi-hosting enabled (VectorAddr = 0x08)
    Semihosting I/O set to TELNET and GDB Client
    SWO disabled succesfully.
    SWO enabled succesfully.
    WARNING: Unknown packet received: "qXfer:threads:read::0,fff"
    Downloading 16096 bytes @ address 0x00000000
    Downloading 16112 bytes @ address 0x00003EE0
    Downloading 16160 bytes @ address 0x00007DD0
    Downloading 16192 bytes @ address 0x0000BCF0
    Downloading 3812 bytes @ address 0x0000FC30
    Downloading 8 bytes @ address 0x00010B14
    Downloading 2244 bytes @ address 0x00010B1C
    Read 4 bytes @ address 0x00008B9C (Data = 0x47804807)
    Read 2 bytes @ address 0x00006830 (Data = 0xF01E)
    Read 2 bytes @ address 0x00006830 (Data = 0xF01E)
    Read 2 bytes @ address 0x00007C92 (Data = 0xF7FE)
    Read 2 bytes @ address 0x00007C92 (Data = 0xF7FE)
    Read 2 bytes @ address 0x00006848 (Data = 0x9B01)
    Read 2 bytes @ address 0x00006848 (Data = 0x9B01)
    Read 2 bytes @ address 0x00007C92 (Data = 0xF7FE)
    Read 2 bytes @ address 0x00007C92 (Data = 0xF7FE)
    Read 2 bytes @ address 0x00007C92 (Data = 0xF7FE)
    Resetting target
    Halting target CPU...
    ...Target halted (PC = 0x00008B9C)
    R0 = 00000000, R1 = 00000000, R2 = 00000000, R3 = 00000001
    R4 = 00000000, R5 = 00000000, R6 = 00000000, R7 = 00000000
    R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
    R12= 00000000, R13= 20008000, MSP= 20008000, PSP= 20006D00
    R14(LR) = FFFFFFFF, R15(PC) = 00008B9C
    XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
    CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00
    Reading all registers
    Read 4 bytes @ address 0x00008B9C (Data = 0x47804807)
    Setting breakpoint @ address 0x00006830, Size = 2, BPHandle = 0x0002
    Setting breakpoint @ address 0x00006848, Size = 2, BPHandle = 0x0003
    Setting breakpoint @ address 0x00007C92, Size = 2, BPHandle = 0x0004
    Starting target CPU...
    ...Breakpoint reached @ address 0x00007C92
    Reading all registers
    Removing breakpoint @ address 0x00006830, Size = 2
    Removing breakpoint @ address 0x00006848, Size = 2
    Removing breakpoint @ address 0x00007C92, Size = 2
    Read 4 bytes @ address 0x00007C92 (Data = 0xFE1FF7FE)
    Reading 64 bytes @ address 0x20006D00
    WARNING: Unknown packet received: "qXfer:threads:read::0,fff"
    GDB closed TCP/IP connection

    I notice that the
    WARNING: Unknown packet received: "qXfer:threads:read::0,fff"
    is a new message I have not seem in the previous releases, any ideas?

    If I try the GDBServer again I get:

    SEGGER J-Link GDB Server V4.86 Command Line Version

    JLinkARM.dll V4.86 (DLL compiled Jun 6 2014 19:08:58)

    -----GDB Server start settings-----
    GDBInit file: none
    GDB Server Listening port: 2331
    SWO raw output listening port: 2332
    Terminal I/O port: 2333
    Accept remote connection: yes
    Generate logfile: off
    Verify download: off
    Init regs on start: on
    Silent mode: off
    Single run mode: off
    Target connection timeout: 5 sec.
    ------J-Link related settings------
    J-Link Host interface: USB
    J-Link script: none
    J-Link settings file: none
    ------Target related settings------
    Target device: unspecified
    Target interface: JTAG
    Target interface speed: 1000kHz
    Target endian: little

    Connecting to J-Link...
    Connecting to J-Link failed. Connected correctly?
    GDBServer will be closed...
    Shutting down...

    or JLinkExe

    $ JLinkExe
    SEGGER J-Link Commander V4.86 ('?' for help)
    Compiled Jun 6 2014 19:09:03
    Can not connect to J-Link via USB.
    J-Link>

    If you want me to try and capture any other messages, or if you are able to provide a version for OSX that outputs debug statements, I am more than happy to help diagnose exactly what is not working and I appreciate your help!

    Thanks in advance.

    Cheers
    Douglas

  • Hi,

    I notice that the
    WARNING: Unknown packet received: "qXfer:threads:read::0,fff"
    is a new message I have not seem in the previous releases, any ideas?


    Unfortunately, this has been introduced in V4.86, since support for some new commands, sent by GDB, has been implemented.
    This implementation was faulty.
    Corrected in V4.86a. Sorry for any inconveniences caused.

    V4.86a: segger.com/jlink-software.html


    - Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.