[SOLVED] Cannot Connect JLinkGDBServer to CC3200 on OS X

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

  • [SOLVED] Cannot Connect JLinkGDBServer to CC3200 on OS X

    Hi,
    I am having trouble connecting JLinkGDBServer to my CC3200 chip on OS X.
    Setup:
    OS X v10.12.3
    J-Link GDB Server Command Line v6.14b

    This is my output:


    $ JLinkGDBServer -device CC3200 -if JTAG
    SEGGER J-Link GDB Server V6.14b Command Line Version

    JLinkARM.dll V6.14b (DLL compiled Mar 9 2017 08:48:31)

    -----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: off
    Silent mode: off
    Single run mode: off
    Target connection timeout: 0 ms
    ------J-Link related settings------
    J-Link Host interface: USB
    J-Link script: none
    J-Link settings file: none
    ------Target related settings------
    Target device: CC3200
    Target interface: JTAG
    Target interface speed: 1000kHz
    Target endian: little

    Connecting to J-Link...
    J-Link is connected.
    Failed to set device (CC3200). Unknown device selected?ERROR : Failed to set device.

    Firmware: J-Link V10 compiled Jan 9 2017 17:48:51
    Hardware: V10.10
    S/N: 260100867
    OEM: SEGGER-EDU
    Feature(s): FlashBP, GDB
    Checking target voltage...
    Target voltage: 3.28 V
    Listening on TCP/IP port 2331
    Connecting to target...ERROR: No CPU core or target device has been selected. Please make sure at least the core J-Link shall connect to, is selected.
    ERROR: Could not connect to target.
    Target connection failed. GDBServer will be closed...Restoring target state and closing J-Link connection...
    Shutting down...
    Could not connect to target.



    However, when I run the same command on a Windows 10 VM(also with 6.14b installed) using Parallels on the same Mac it works:



    C:\Program Files (x86)\SEGGER\JLink_V614b>JLinkGDBServerCL.exe -device CC3200 -if JTAG
    SEGGER J-Link GDB Server V6.14b Command Line Version

    JLinkARM.dll V6.14b (DLL compiled Mar 9 2017 08:46:04)

    -----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: off
    Init regs on start: off
    Silent mode: off
    Single run mode: off
    Target connection timeout: 0 ms
    ------J-Link related settings------
    J-Link Host interface: USB
    J-Link script: none
    J-Link settings file: none
    ------Target related settings------
    Target device: CC3200
    Target interface: JTAG
    Target interface speed: 1000kHz
    Target endian: little

    Connecting to J-Link...
    J-Link is connected.
    Firmware: J-Link V10 compiled Jan 9 2017 17:48:51
    Hardware: V10.10
    S/N: 260100867
    OEM: SEGGER-EDU
    Feature(s): FlashBP, GDB
    Checking target voltage...
    Target voltage: 3.28 V
    Listening on TCP/IP port 2331
    Connecting to target...
    J-Link found 2 JTAG devices, Total IRLen = 10
    JTAG ID: 0x4BA00477 (Cortex-M4)
    Connected to target
    Waiting for GDB connection...


    Is CC3200 not supported in the OS X release for v6.14b? If not, will it be supported soon?

    As an aside I can get JLinkGDBServer v6.14b running on my Mac with the NRF52840 chip, so I have had success running it on the Mac side. Thanks!

    best,
    Akbar
  • Hi Akbar,


    sorry for the delay in response.
    This issue is fixed in version 6.14c of the J-Link software & documentation pack.

    Best regards,
    Niklas
    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 Akbar,


    you are correct, 6.14c only fixed the issue for the Linux .rpm and .deb packages.
    6.14d, which will be released later today or tomorrow, will fix the issue for the macOS .pkg package.

    Sorry for any inconveniences caused.


    Best regards,
    Niklas
    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.