[SOLVED] DOA J-link edu ?

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

  • [SOLVED] DOA J-link edu ?

    We ordered a J-Link edu (Version 9.3
    Production date 14-44.) from farnell but we are unable to get it in a
    working state. Our main platform is Linux so we tried it first on Linux.
    We installed the software. When we run JLinkExe we get the error:

    Source Code

    1. $ JLinkExe
    2. SEGGER J-Link Commander V5.00f ('?' for help)
    3. Compiled Jun 30 2015 19:06:09
    4. Can not connect to J-Link via USB.
    5. J-Link>


    ShowEmuList finds a device but is unable to detect the serial number:

    Source Code

    1. J-Link> ShowEmuList
    2. J-Link[0]: Connection: USB, Serial number: 0, ProductName: J-Link


    firmware info also doesn't seem to work:

    Source Code

    1. J-Link>f
    2. Unable to retrieve firmware info !


    Show hardware status and Show hardware info return some information:

    Source Code

    1. J-Link> st
    2. VTarget=0.000V
    3. ITarget=0mA
    4. TCK=0 TDI=0 TDO=0 TMS=0 TRES=0 TRST=0
    6. Supported target interface speeds:
    7. - 16 MHz/n, (n>=4). => 4000kHz, 3200kHz, 2666kHz, ...
    9. J-Link>hwinfo
    10. HWInfo[00] = Target power is disabled
    11. HWInfo[02] = 0mA (ITarget)
    12. HWInfo[03] = 0mA (ITargetPeak)
    13. HWInfo[04] = 0mA (ITargetPeakOperation)
    14. HWInfo[05] = 0x00000000
    15. HWInfo[06] = 0x00000000
    16. HWInfo[07] = 0x00000000
    17. HWInfo[08] = 0x00000000
    18. HWInfo[09] = 0x00000000
    19. HWInfo[10] = 0ms (ITargetMaxTime0)
    20. HWInfo[11] = 0ms (ITargetMaxTime1)
    21. HWInfo[12] = 0ms (ITargetMaxTime2)
    22. HWInfo[13] = 0x00000000
    23. HWInfo[14] = 0x00000000
    24. HWInfo[15] = 0x00000000
    25. HWInfo[16] = 0x00000000
    26. HWInfo[17] = 0x00000000
    27. HWInfo[18] = 0x00000000
    28. HWInfo[19] = 0x00000000
    29. HWInfo[20] = 0x00000000
    30. HWInfo[21] = 0x00000000
    31. HWInfo[22] = 0x00000000
    32. HWInfo[23] = 0x00000000
    33. HWInfo[24] = 0x00000000
    34. HWInfo[25] = 0x00000000
    35. HWInfo[26] = 0x00000000
    36. HWInfo[27] = 0x00000000
    37. HWInfo[28] = 0x00000000
    38. HWInfo[29] = 0x00000000
    39. HWInfo[30] = 0x00000000
    40. HWInfo[31] = 0x00000000
    Display All


    License show also doesn't work:

    Source Code

    1. J-Link>license show
    2. Could not determine available licenses.



    On Windows, the results are the same. It detects the J-Link but is
    unable to get the serial number, licenses or do anything useful.

    Is there anything else we can try to get this debugger working or is it DOA?

  • Hi Bram,


    can you please describe the output of the status LED of your J-Link EDU?
    Could you also please try it with a different USB-Cable ?
    On Windows, the results are the same. It detects the J-Link[...]
    Does the J-Link show up in the Windows device manger ?


    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 Niklas,
    thanks for your response.

    The LED is green, on, and blinks (turns off for a fraction of a seocnd) ~2 times per second.

    Yes, the J-Link shows up in the Windows device manager. Driver version 2.6.8.1. In Linux it is also listed in lsusb.

    I tried a different USB cable but the results are the same.

    Kind regards,
    Bram.

  • Hi Bram,

    How did you install the Linux version?
    Did you use one of the deb / rpm installers?
    If not: Did you follow the instructions in the tar.gz archive regarding making J-Link accessible as a regular user?
    The problems you are seeing sound a bit like a permission problem.
    Did you try to start J-Link Commander as root? (sudo ./JLinkExe)

    The J-Link itself seems to be fine.
    The "heartbeat" you are seeing is indicating that J-Link did boot and now is waiting to receive commands.


    Best regards
    Alex - Product Manager J-Link
    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 Alex,
    we are using Fedora 21 and used the rpm installer. Permissions seems to be fine and there is no difference if I run it as root or as a normal user. (we also see the same problem on windows)

    This is the output of usbmon. Capture starts when I start JLinkExe till the line "Can not connect to J-Link via USB" pops up. Perhaps it's helps in solving the problem.

    ec2c3c00 0.967491 S Ci:1:002:0 s 80 00 0000 0000 0002 2 <
    ec2c3c00 0.967562 C Ci:1:002:0 0 2 =
    ec2c33c0 0.967683 S Bo:1:002:1 - 1 =
    ec2c33c0 1.967488 C Bo:1:002:1 -2 0
    ec2c33c0 1.967520 S Co:1:002:0 s 02 01 0000 0081 0000 0
    ec2c33c0 1.967583 C Co:1:002:0 0 0
    d5277c00 1.967595 S Co:1:002:0 s 02 01 0000 0001 0000 0
    d5277c00 1.967651 C Co:1:002:0 0 0
    d5277c00 1.967661 S Bo:1:002:1 - 1 =
    d5277c00 2.967482 C Bo:1:002:1 -2 0
    ec2c39c0 2.967514 S Co:1:002:0 s 02 01 0000 0081 0000 0
    ec2c39c0 2.967569 C Co:1:002:0 0 0
    ec2c39c0 2.967672 S Co:1:002:0 s 02 01 0000 0001 0000 0
    ec2c39c0 2.967730 C Co:1:002:0 0 0
    ec2c39c0 2.967763 S Bo:1:002:1 - 1 =
    ec2c39c0 3.967506 C Bo:1:002:1 -2 0
    ec2c39c0 3.967523 S Co:1:002:0 s 02 01 0000 0081 0000 0
    ec2c39c0 3.967581 C Co:1:002:0 0 0
    ec2c39c0 3.967593 S Co:1:002:0 s 02 01 0000 0001 0000 0
    ec2c39c0 3.967648 C Co:1:002:0 0 0
    c486b6c0 3.967727 S Bo:1:002:1 - 1 =
    c486b6c0 4.967478 C Bo:1:002:1 -2 0
    d5277e40 4.967518 S Co:1:002:0 s 02 01 0000 0081 0000 0
    d5277e40 4.967581 C Co:1:002:0 0 0
    ec2c3300 4.967597 S Co:1:002:0 s 02 01 0000 0001 0000 0
    ec2c3300 4.967658 C Co:1:002:0 0 0
    ec2c3300 4.967671 S Bo:1:002:1 - 1 =
    ec2c3300 5.967497 C Bo:1:002:1 -2 0
    ec2c3300 5.967543 S Co:1:002:0 s 02 01 0000 0081 0000 0
    ec2c3300 5.967605 C Co:1:002:0 0 0
    ec2c3300 5.967652 S Co:1:002:0 s 02 01 0000 0001 0000 0
    ec2c3300 5.967708 C Co:1:002:0 0 0
    ec2c3300 5.967740 S Bo:1:002:1 - 1 =
    ec2c3300 6.967487 C Bo:1:002:1 -2 0
    ec2c3300 6.967510 S Co:1:002:0 s 02 01 0000 0081 0000 0
    ec2c3300 6.967570 C Co:1:002:0 0 0
    ec2c3300 6.967582 S Co:1:002:0 s 02 01 0000 0001 0000 0
    ec2c3300 6.967636 C Co:1:002:0 0 0
    d5277e40 7.136019 S Bo:1:002:1 - 1 =
    d5277e40 8.135479 C Bo:1:002:1 -2 0
    c486b300 8.135496 S Co:1:002:0 s 02 01 0000 0081 0000 0
    c486b300 8.135553 C Co:1:002:0 0 0
    c486b300 8.135582 S Co:1:002:0 s 02 01 0000 0001 0000 0
    c486b300 8.135641 C Co:1:002:0 0 0
    c486b300 8.135669 S Bo:1:002:1 - 1 =
    c486b300 9.135463 C Bo:1:002:1 -2 0
    d52773c0 9.135491 S Co:1:002:0 s 02 01 0000 0081 0000 0
    d52773c0 9.135546 C Co:1:002:0 0 0
    d52773c0 9.135581 S Co:1:002:0 s 02 01 0000 0001 0000 0
    d52773c0 9.135635 C Co:1:002:0 0 0
    ec2c33c0 9.135675 S Bo:1:002:1 - 1 =
    ec2c33c0 10.135543 C Bo:1:002:1 -2 0
    ec2c33c0 10.135566 S Co:1:002:0 s 02 01 0000 0081 0000 0
    ec2c33c0 10.135630 C Co:1:002:0 0 0
    ec2c33c0 10.135663 S Co:1:002:0 s 02 01 0000 0001 0000 0
    ec2c33c0 10.135723 C Co:1:002:0 0 0


    Thanks!
    Bram

  • Hi bram,

    it seems that the commands to the J-Link is somehow rejected. What I can see is, that that any USB transactions to the normal pipes of the J-Link fail with errno -2 which means file not found.
    Would it be possible to perform a detailed lsusb dump of you J-Link?
    This can be done doing the following:
    • Open a console and type[quote]lsusb[/quote]
    • You should get a output similar to the below one:

      Source Code

      1. Bus 001 Device 002: ID 1366:0101 SEGGER J-Link ARM
      2. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
      3. Bus 002 Device 004: ID 0e0f:0008 VMware, Inc.
      4. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
      5. Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
      6. Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    • With that output check which bus no. and device no. your J-Link has - In our case this is Bus 001 Device 002.
      This is necessary in order to retrieve the detail information of the J-Link:
      Type: [quote]sudo lsusb -D lsusb -D /dev/bus/usb/<Bus no>/<Device no>[/quote]
      In our case we type: sudo lsusb -D /dev/bus/usb/001/002
      Output of lsusb -D:

      Source Code

      1. Device: ID 1366:0101 SEGGER J-Link ARM
      2. Device Descriptor:
      3. bLength 18
      4. bDescriptorType 1
      5. bcdUSB 2.00
      6. bDeviceClass 0 (Defined at Interface level)
      7. bDeviceSubClass 0
      8. bDeviceProtocol 0
      9. bMaxPacketSize0 64
      10. idVendor 0x1366 SEGGER
      11. idProduct 0x0101 J-Link ARM
      12. bcdDevice 1.00
      13. iManufacturer 1 SEGGER
      14. iProduct 2 J-Link
      15. iSerial 3 000059200001
      16. bNumConfigurations 1
      17. Configuration Descriptor:
      18. bLength 9
      19. bDescriptorType 2
      20. wTotalLength 32
      21. bNumInterfaces 1
      22. bConfigurationValue 1
      23. iConfiguration 4 Configuration
      24. bmAttributes 0x80
      25. (Bus Powered)
      26. MaxPower 100mA
      27. Interface Descriptor:
      28. bLength 9
      29. bDescriptorType 4
      30. bInterfaceNumber 0
      31. bAlternateSetting 0
      32. bNumEndpoints 2
      33. bInterfaceClass 255 Vendor Specific Class
      34. bInterfaceSubClass 255 Vendor Specific Subclass
      35. bInterfaceProtocol 255 Vendor Specific Protocol
      36. iInterface 5 J-Link
      37. Endpoint Descriptor:
      38. bLength 7
      39. bDescriptorType 5
      40. bEndpointAddress 0x81 EP 1 IN
      41. bmAttributes 2
      42. Transfer Type Bulk
      43. Synch Type None
      44. Usage Type Data
      45. wMaxPacketSize 0x0040 1x 64 bytes
      46. bInterval 1
      47. Endpoint Descriptor:
      48. bLength 7
      49. bDescriptorType 5
      50. bEndpointAddress 0x01 EP 1 OUT
      51. bmAttributes 2
      52. Transfer Type Bulk
      53. Synch Type None
      54. Usage Type Data
      55. wMaxPacketSize 0x0040 1x 64 bytes
      56. bInterval 1
      57. Device Status: 0x0000
      58. (Bus Powered)
      Display All
    Best regards,
    Souhail
    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.

  • Hello Souhail,
    this is the requested information:


    Device: ID 1366:0101 SEGGER J-Link PLUS
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 2.00
    bDeviceClass 0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 64
    idVendor 0x1366 SEGGER
    idProduct 0x0101 J-Link PLUS
    bcdDevice 1.00
    iManufacturer 1 SEGGER
    iProduct 2 J-Link
    iSerial 3 000269302824
    bNumConfigurations 1
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 32
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0x80
    (Bus Powered)
    MaxPower 100mA
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 2
    bInterfaceClass 255 Vendor Specific Class
    bInterfaceSubClass 255 Vendor Specific Subclass
    bInterfaceProtocol 255 Vendor Specific Protocol
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x81 EP 1 IN
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0040 1x 64 bytes
    bInterval 1
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x01 EP 1 OUT
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0040 1x 64 bytes
    bInterval 1
    Device Status: 0x0000
    (Bus Powered)


    Thanks!

  • It's working! I attached the device to a Mac (5.00i). It immediately detected the device and performed the firmware upgrade. After that it also worked fine on Linux. Seems to be a compatibility problem with the firmware/software and Windows and Linux unable to perform the upgrade.

  • Thank you for the feedback.
    I have marked this case as solved.

    Anyhow, we will check if we can reproduce such an behavior here as the firmware / software should be compatible anyway.


    Best regards
    Erik
    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.