[SOLVED] YRDKRX62N - Can not connect to J-Link via USB

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

  • [SOLVED] YRDKRX62N - Can not connect to J-Link via USB

    I am running Fedora 22 - x64 and have downloaded and installed the jlink-5.2.1.x86_64.rpm package. My hardware is a Renesas YRDKRX62N development board. The JLinkExe program works the first time that I plug the board in but fails every time after that.

    Here is the output of the "lsusb -vd 1366:0101" before I run the JLinkExe command.

    Source Code

    1. Bus 005 Device 012: ID 1366:0101 SEGGER J-Link PLUS
    2. Device Descriptor:
    3. bLength 18
    4. bDescriptorType 1
    5. bcdUSB 1.10
    6. bDeviceClass 0 (Defined at Interface level)
    7. bDeviceSubClass 0
    8. bDeviceProtocol 0
    9. bMaxPacketSize0 8
    10. idVendor 0x1366 SEGGER
    11. idProduct 0x0101 J-Link PLUS
    12. bcdDevice 0.01
    13. iManufacturer 1 SEGGER
    14. iProduct 2 J-Link
    15. iSerial 3 123456
    16. bNumConfigurations 1
    17. Configuration Descriptor:
    18. bLength 9
    19. bDescriptorType 2
    20. wTotalLength 32
    21. bNumInterfaces 1
    22. bConfigurationValue 1
    23. iConfiguration 0
    24. bmAttributes 0xc0
    25. Self 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 0
    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 0
    47. Endpoint Descriptor:
    48. bLength 7
    49. bDescriptorType 5
    50. bEndpointAddress 0x02 EP 2 OUT
    51. bmAttributes 2
    52. Transfer Type Bulk
    53. Synch Type None
    54. Usage Type Data
    55. wMaxPacketSize 0x0040 1x 64 bytes
    56. bInterval 0
    57. Device Status: 0x0001
    58. Self Powered
    Display All


    This is the output of the JLinkExe command on first run.

    Brainfuck Source Code

    1. SEGGER J-Link Commander V5.02a ('?' for help)
    2. Compiled Sep 4 2015 18:50:52
    3. DLL version V5.02a, compiled Sep 4 2015 18:50:47
    4. Firmware: J-Link ARM-OB SAM7 compiled Jun 1 2012 09:33:42
    5. Hardware: V2.10
    6. S/N: ---------
    7. Emulator has Trace capability
    8. VTarget = 3.300V
    9. Info: TotalIRLen = 8, IRPrint = 0x00C1
    10. Info: Found Renesas RX62N device
    11. Info: Debugger authenticated successfully.
    12. Info: Endian: little
    13. Found 1 JTAG device, Total IRLen = 8:
    14. #0 Id: 0x0D002447, IRLen: 08, IRPrint: 0xC1, RX62N Core (Renesas)
    15. Renesas RX core identified.
    16. Target interface speed: 100 kHz
    Display All


    This is the output of the "lsusb -vd 1366:0101" command after the JLinkExe command has been run.

    Source Code

    1. Bus 005 Device 012: ID 1366:0101 SEGGER J-Link PLUS
    2. Device Descriptor:
    3. bLength 18
    4. bDescriptorType 1
    5. bcdUSB 1.10
    6. bDeviceClass 0 (Defined at Interface level)
    7. bDeviceSubClass 0
    8. bDeviceProtocol 0
    9. bMaxPacketSize0 8
    10. idVendor 0x1366 SEGGER
    11. idProduct 0x0101 J-Link PLUS
    12. bcdDevice 0.01
    13. iManufacturer 1 (error)
    14. iProduct 2 (error)
    15. iSerial 3 (error)
    16. bNumConfigurations 1
    17. Configuration Descriptor:
    18. bLength 9
    19. bDescriptorType 2
    20. wTotalLength 32
    21. bNumInterfaces 1
    22. bConfigurationValue 1
    23. iConfiguration 0
    24. bmAttributes 0xc0
    25. Self 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 0
    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 0
    47. Endpoint Descriptor:
    48. bLength 7
    49. bDescriptorType 5
    50. bEndpointAddress 0x02 EP 2 OUT
    51. bmAttributes 2
    52. Transfer Type Bulk
    53. Synch Type None
    54. Usage Type Data
    55. wMaxPacketSize 0x0040 1x 64 bytes
    56. bInterval 0
    57. Device Status: 0x0001
    58. Self Powered
    Display All


    This is the output for all subsequent runs of the JLinkExe command

    Source Code

    1. SEGGER J-Link Commander V5.02a ('?' for help)
    2. Compiled Sep 4 2015 18:50:52
    3. Can not connect to J-Link via USB.


    This is the relevant bits of a strace of the JLinkExe process.

    Source Code

    1. ioctl(3, USBDEVFS_CLAIMINTERFACE, 0x7ffc1d6d068c) = 0
    2. ioctl(3, USBDEVFS_BULK, 0x7ffc1d6d1790) = 1
    3. ioctl(3, USBDEVFS_BULK, 0x7ffc1d6d1790) = 2
    4. ioctl(3, USBDEVFS_BULK, 0x7ffc1d6d1760) = 112
    5. lseek(3, 0, SEEK_SET) = 0
    6. read(3, "\22\1\20\1\0\0\0\10f\23\1\1\1\0\1\2\3\1", 18) = 18
    7. ioctl(3, USBDEVFS_CONTROL, 0x7ffc1d6d16a0) = -1 ETIMEDOUT (Connection timed out)
    8. close(3) = 0


    In addition, the dmesg log sees this.

    Source Code

    1. usbfs: USBDEVFS_CONTROL failed cmd JLinkExe rqt 128 rq 6 len 255 ret -110

  • Hello Chris,


    thanks for your inquiry.
    Due to your exemplary documentation of this issue, we were able to reproduce and examine the root of it.

    We will fix this in a future release of the J-Link software and documentation pack.

    Would you like to be added to the J-Link software update notification list,
    so you get informed automatically when new versions become available?

    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.

  • Please feel free to add my registration email to the software update notification list.

    Done


    -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.