[SOLVED] J-Link and Windows 10 issues

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

  • [SOLVED] J-Link and Windows 10 issues

    Hello,
    we have been using J-Link to debug MCIMX6G1 since it's support was introduced without any issues. We have been running Win 7, but unfortunately, we're forced to move to Win 10. We have already found two issues.

    The first issue is with fw upgrade. When firmware upgrade attempt occurs, it fails almost immediately (see attached image ). Luckily unplugging and plugging J-link again solves the issue, as the fw upgrade from "recovery mode" works.

    Second issue is that new versions (6.21d, 6.22, 6.22a) couldn't attach to cpu any more. Log follows. The result is same for any fw version we tried.

    C Source Code

    1. C:\Program Files (x86)\SEGGER\JLink_V622a>jlink
    2. SEGGER J-Link Commander V6.22a (Compiled Nov 28 2017 17:56:48)
    3. DLL version V6.22a, compiled Nov 28 2017 17:56:10
    4. Connecting to J-Link via USB...O.K.
    5. Firmware: J-Link Pro V4 compiled Nov 28 2017 11:47:28
    6. Hardware version: V4.00
    7. S/N: 174xxxxxx
    8. License(s): RDI, FlashBP, FlashDL, JFlash, GDB
    9. IP-Addr: DHCP (no addr. received yet)
    10. VTref = 1.089V
    11. Type "connect" to establish a target connection, '?' for help
    12. J-Link>connect
    13. Please specify device / core. <Default>: MCIMX6G1
    14. Type '?' for selection dialog
    15. Device>
    16. Please specify target interface:
    17. J) JTAG (Default)
    18. S) SWD
    19. TIF>
    20. Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
    21. JTAGConf>
    22. Specify target interface speed [kHz]. <Default>: 4000 kHz
    23. Speed>
    24. Device "MCIMX6G1" selected.
    25. Connecting to target via JTAG
    26. TotalIRLen = 13, IRPrint = 0x0101
    27. **************************
    28. WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)
    29. **************************
    30. JTAG chain detection found 3 devices:
    31. #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
    32. #1 Id: 0x00000001, IRLen: 05, Unknown device
    33. #2 Id: 0x1891D01D, IRLen: 04, JTAG-DP
    34. Scanning AP map to find all available APs
    35. AP[2]: Stopped AP scan as end of AP map seems to be reached
    36. AP[0]: AHB-AP (IDR: 0x74770001)
    37. AP[1]: APB-AP (IDR: 0x44770002)
    38. Iterating through AP map to find AHB-AP to use
    39. AP[0]: Skipped. Not an APB-AP
    40. AP[1]: APB-AP found
    41. Invalid ROM table component ID 0x2F0F0F02 @ 0x20001EF0 (expected 0xB105100D). Trying again at alternative offset.
    42. Invalid ROM table component ID 0x2F0F0F02 @ 0x60000FF0 (expected 0xB105100D). Trying again at alternative offset.
    43. TotalIRLen = 13, IRPrint = 0x0101
    44. **************************
    45. WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)
    46. **************************
    47. JTAG chain detection found 3 devices:
    48. #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
    49. #1 Id: 0x00000001, IRLen: 05, Unknown device
    50. #2 Id: 0x1891D01D, IRLen: 04, JTAG-DP
    51. ****** Error: Cortex-A/R-JTAG (connect): Could not determine address of core debug registers. Incorrect CoreSight ROM table in device?
    52. TotalIRLen = 13, IRPrint = 0x0101
    53. **************************
    54. WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)
    55. **************************
    56. JTAG chain detection found 3 devices:
    57. #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
    58. #1 Id: 0x00000001, IRLen: 05, Unknown device
    59. #2 Id: 0x1891D01D, IRLen: 04, JTAG-DP
    60. TotalIRLen = 13, IRPrint = 0x0101
    61. **************************
    62. WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)
    63. **************************
    64. JTAG chain detection found 3 devices:
    65. #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
    66. #1 Id: 0x00000001, IRLen: 05, Unknown device
    67. #2 Id: 0x1891D01D, IRLen: 04, JTAG-DP
    68. Cannot connect to target.
    Display All


    But, if we use older J-Link version (6.15f), it works as expected even with newest firmware:

    C Source Code

    1. J-Link>connect
    2. Please specify device / core. <Default>: MCIMX6G1
    3. Type '?' for selection dialog
    4. Device>
    5. Please specify target interface:
    6. J) JTAG (Default)
    7. S) SWD
    8. TIF>
    9. Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
    10. JTAGConf>
    11. Specify target interface speed [kHz]. <Default>: 4000 kHz
    12. Speed>
    13. Device "MCIMX6G1" selected.
    14. TotalIRLen = 13, IRPrint = 0x0101
    15. **************************
    16. WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)
    17. **************************
    18. JTAG chain detection found 3 devices:
    19. #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
    20. #1 Id: 0x00000001, IRLen: ?, Unknown device
    21. #2 Id: 0x1891D01D, IRLen: ?, Unknown device
    22. ARM AP[0]: 0x74770001, AHB-AP
    23. ARM AP[1]: 0x44770002, APB-AP
    24. ROMTbl[0][0]: CompAddr: 80001000 CID: B105900D, PID:04-001BB961 TMC
    25. ROMTbl[0][1]: CompAddr: 80002000 CID: B105900D, PID:04-004BB906 ECT / CTI
    26. ROMTbl[0][2]: CompAddr: 80003000 CID: B105900D, PID:04-004BB912 TPIU
    27. ROMTbl[0][3]: CompAddr: 80004000 CID: B105F00D, PID:04-001BB101
    28. ROMTbl[0][4]: CompAddr: 80020000 CID: B105100D, PID:04-000BB4A7 ROM Table
    29. ROMTbl[1][0]: CompAddr: 80030000 CID: B105900D, PID:04-005BBC07 Cortex-A7
    30. Found Cortex-A7 r0p5
    31. 6 code breakpoints, 4 data breakpoints
    32. Debug architecture ARMv7.1
    33. Data endian: little
    34. Main ID register: 0x410FC075
    35. I-Cache L1: 32 KB, 512 Sets, 32 Bytes/Line, 2-Way
    36. D-Cache L1: 32 KB, 128 Sets, 64 Bytes/Line, 4-Way
    37. Unified-Cache L2: 128 KB, 256 Sets, 64 Bytes/Line, 8-Way
    38. System control register:
    39. Instruction endian: little
    40. Level-1 instruction cache enabled
    41. Level-1 data cache enabled
    42. MMU enabled
    43. Branch prediction enabled
    44. Cortex-A7 identified.
    45. J-Link>
    Display All


    Although we eventualy got working configuration, it doesn't somehow feel good, to ignore these issues.

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

  • Hello,

    Thank you for your inquiry.
    Such an issue is not known to us.
    We will try to reproduce the issue and come back to you.

    What VTref value do you get with V6.15f?
    In V6.22a it is at about ~1 V. Is that voltage expected at your target?

    Best regards,
    Nino
    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,

    To clarify, VTref shows ~3.3 V for J-Link version V6.15f and 6.22a?
    Because in the logs you posted earlier for V6.22a it shows: VTref = 1.089V

    Did that change?
    Could you post a screenshot of the J-Link commander output in both cases?

    Best regards,
    Nino
    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,
    I rerun connect for both versions.

    Before running JLink.exe, the board is connected to power, then the boot is stoped at u-boot prompt.

    6.22a

    C Source Code

    1. C:\Program Files (x86)\SEGGER\JLink_V622a>jlink
    2. SEGGER J-Link Commander V6.22a (Compiled Nov 28 2017 17:56:48)
    3. DLL version V6.22a, compiled Nov 28 2017 17:56:10
    4. Connecting to J-Link via USB...O.K.
    5. Firmware: J-Link Pro V4 compiled Nov 28 2017 11:47:28
    6. Hardware version: V4.00
    7. S/N: 174xxxxxx
    8. License(s): RDI, FlashBP, FlashDL, JFlash, GDB
    9. IP-Addr: DHCP (no addr. received yet)
    10. VTref = 3.349V
    11. Type "connect" to establish a target connection, '?' for help
    12. J-Link>connect
    13. Please specify device / core. <Default>: MCIMX6G1
    14. Type '?' for selection dialog
    15. Device>
    16. Please specify target interface:
    17. J) JTAG (Default)
    18. S) SWD
    19. TIF>
    20. Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
    21. JTAGConf>
    22. Specify target interface speed [kHz]. <Default>: 4000 kHz
    23. Speed>
    24. Device "MCIMX6G1" selected.
    25. Connecting to target via JTAG
    26. TotalIRLen = 13, IRPrint = 0x0101
    27. **************************
    28. WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)
    29. **************************
    30. JTAG chain detection found 3 devices:
    31. #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
    32. #1 Id: 0x00000001, IRLen: 05, Unknown device
    33. #2 Id: 0x1891D01D, IRLen: 04, JTAG-DP
    34. Scanning AP map to find all available APs
    35. AP[2]: Stopped AP scan as end of AP map seems to be reached
    36. AP[0]: AHB-AP (IDR: 0x74770001)
    37. AP[1]: APB-AP (IDR: 0x44770002)
    38. Iterating through AP map to find AHB-AP to use
    39. AP[0]: Skipped. Not an APB-AP
    40. AP[1]: APB-AP found
    41. Invalid ROM table component ID 0x2F0F0F02 @ 0x20001EF0 (expected 0xB105100D). Trying again at alternative offset.
    42. Invalid ROM table component ID 0x2F0F0F02 @ 0x60000FF0 (expected 0xB105100D). Trying again at alternative offset.
    43. TotalIRLen = 13, IRPrint = 0x0101
    44. **************************
    45. WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)
    46. **************************
    47. JTAG chain detection found 3 devices:
    48. #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
    49. #1 Id: 0x00000001, IRLen: 05, Unknown device
    50. #2 Id: 0x1891D01D, IRLen: 04, JTAG-DP
    51. ****** Error: Cortex-A/R-JTAG (connect): Could not determine address of core debug registers. Incorrect CoreSight ROM table in device?
    52. TotalIRLen = 13, IRPrint = 0x0101
    53. **************************
    54. WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)
    55. **************************
    56. JTAG chain detection found 3 devices:
    57. #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
    58. #1 Id: 0x00000001, IRLen: 05, Unknown device
    59. #2 Id: 0x1891D01D, IRLen: 04, JTAG-DP
    60. TotalIRLen = 13, IRPrint = 0x0101
    61. **************************
    62. WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)
    63. **************************
    64. JTAG chain detection found 3 devices:
    65. #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
    66. #1 Id: 0x00000001, IRLen: 05, Unknown device
    67. #2 Id: 0x1891D01D, IRLen: 04, JTAG-DP
    68. Cannot connect to target.
    Display All


    6.15f

    C Source Code

    1. SEGGER J-Link Commander V6.15f (Compiled May 22 2017 18:57:01)
    2. DLL version V6.15f, compiled May 22 2017 18:56:28
    3. Connecting to J-Link via USB...O.K.
    4. Firmware: J-Link Pro V4 compiled Nov 28 2017 11:47:28
    5. Hardware version: V4.00
    6. S/N: 174xxxxxx
    7. License(s): RDI, FlashBP, FlashDL, JFlash, GDB
    8. IP-Addr: DHCP (no addr. received yet)
    9. VTref = 3.349V
    10. Type "connect" to establish a target connection, '?' for help
    11. J-Link>connect
    12. Please specify device / core. <Default>: MCIMX6G1
    13. Type '?' for selection dialog
    14. Device>
    15. Please specify target interface:
    16. J) JTAG (Default)
    17. S) SWD
    18. TIF>
    19. Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
    20. JTAGConf>
    21. Specify target interface speed [kHz]. <Default>: 4000 kHz
    22. Speed>
    23. Device "MCIMX6G1" selected.
    24. TotalIRLen = 13, IRPrint = 0x0101
    25. **************************
    26. WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)
    27. **************************
    28. JTAG chain detection found 3 devices:
    29. #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
    30. #1 Id: 0x00000001, IRLen: ?, Unknown device
    31. #2 Id: 0x1891D01D, IRLen: ?, Unknown device
    32. ARM AP[0]: 0x74770001, AHB-AP
    33. ARM AP[1]: 0x44770002, APB-AP
    34. ROMTbl[0][0]: CompAddr: 80001000 CID: B105900D, PID:04-001BB961 TMC
    35. ROMTbl[0][1]: CompAddr: 80002000 CID: B105900D, PID:04-004BB906 ECT / CTI
    36. ROMTbl[0][2]: CompAddr: 80003000 CID: B105900D, PID:04-004BB912 TPIU
    37. ROMTbl[0][3]: CompAddr: 80004000 CID: B105F00D, PID:04-001BB101
    38. ROMTbl[0][4]: CompAddr: 80020000 CID: B105100D, PID:04-000BB4A7 ROM Table
    39. ROMTbl[1][0]: CompAddr: 80030000 CID: B105900D, PID:04-005BBC07 Cortex-A7
    40. Found Cortex-A7 r0p5
    41. 6 code breakpoints, 4 data breakpoints
    42. Debug architecture ARMv7.1
    43. Data endian: little
    44. Main ID register: 0x410FC075
    45. I-Cache L1: 32 KB, 512 Sets, 32 Bytes/Line, 2-Way
    46. D-Cache L1: 32 KB, 128 Sets, 64 Bytes/Line, 4-Way
    47. Unified-Cache L2: 128 KB, 256 Sets, 64 Bytes/Line, 8-Way
    48. System control register:
    49. Instruction endian: little
    50. Level-1 instruction cache enabled
    51. Level-1 data cache enabled
    52. MMU enabled
    53. Branch prediction enabled
    54. Cortex-A7 identified.
    Display All
  • Hello,

    Thank you for providing additional information.
    We found another issue in V6.22a that might be related to this case.
    Could you try out V6.22 in comparison?
    You can get it herewhen you click on older versions.

    Does that version work for you?

    Best regards,
    Nino
    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,

    We were able to reproduce the issue and are currently working for a fix.
    For now stay with V6.20i for a working setup.

    Sorry for any inconveniences caused.

    Best regards,
    Nino
    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,

    Quick update on the iMX6 connection issue.
    This issue has been resolved and will be available with the next release version V6.22e.

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