[SOLVED] iMX535 GDB halting issue.

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

  • [SOLVED] iMX535 GDB halting issue.

    Hello.

    I'm trying to initiate a GDB session with a Digi CC-WMX53-LX board which has a ConnectCore Wi-i.MX53 module on it.
    Connection seems to work but programming does not. Anyone know anything about halting issues? At the same time jlink commander seems able to halt the target.

    Source Code

    1. SEGGER J-Link GDB Server V6.00e GUI Version
    3. JLinkARM.dll V6.00e (DLL compiled Aug 4 2016 09:37:38)
    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: off
    14. Silent mode: off
    15. Single run mode: off
    16. Target connection timeout: 5000 ms
    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: iMX535
    23. Target interface: JTAG
    24. Target interface speed: auto
    25. Target endian: little
    27. Connecting to J-Link...
    28. J-Link is connected.
    29. Firmware: J-Link Pro V4 compiled Aug 3 2016 18:51:26
    30. Hardware: V4.00
    31. S/N: 174301086
    32. Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
    33. Checking target voltage...
    34. Target voltage: 1.80 V
    35. Listening on TCP/IP port 2331
    36. Connecting to target...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)
    38. 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)
    41. J-Link found 3 JTAG devices, Total IRLen = 13
    42. JTAG ID: 0x1BA00477 (Cortex-A8)
    43. Connected to target
    44. Waiting for GDB connection...Connected to 127.0.0.1
    45. Reading all registers
    46. Read 4 bytes @ address 0x77817148 (Data = 0xE3110020)
    47. Read 4 bytes @ address 0x77851209 (Data = 0x4D574343)
    48. Read 4 bytes @ address 0x4D57433A (Data = 0x00000000)
    49. WARNING: CPU not halted after Reset, halting using Halt request
    50. WARNING: CPU could not be halted
    51. ERROR: Bad JTAG communication: Write to IR: Expected 0x1, got 0xF (TAP Command : 10) @ Off 0x5.
    53. Resetting target
    54. Downloading 4096 bytes @ address 0x70000000WARNING: CPU could not be halted
    55. WARNING: CPU could not be halted
    56. - Verify failed
    57. Downloading 4096 bytes @ address 0x70001000WARNING: CPU could not be halted
    58. WARNING: CPU could not be halted
    59. - Verify failed
    60. Downloading 4096 bytes @ address 0x70002000WARNING: CPU could not be halted
    61. WARNING: CPU could not be halted
    62. - Verify failed
    63. Downloading 4096 bytes @ address 0x70003000WARNING: CPU could not be halted
    64. WARNING: CPU could not be halted
    65. - Verify failed
    66. Downloading 4096 bytes @ address 0x70004000WARNING: CPU could not be halted
    67. WARNING: CPU could not be halted
    68. - Verify failed
    69. Downloading 4096 bytes @ address 0x70005000WARNING: CPU could not be halted
    70. WARNING: CPU could not be halted
    71. - Verify failed
    72. Downloading 4096 bytes @ address 0x70006000WARNING: CPU could not be halted
    73. WARNING: CPU could not be halted
    74. - Verify failed
    75. Downloading 4096 bytes @ address 0x70007000WARNING: CPU could not be halted
    76. WARNING: CPU could not be halted
    77. - Verify failed
    78. Downloading 4096 bytes @ address 0x70008000WARNING: CPU could not be halted
    79. WARNING: CPU could not be halted
    80. - Verify failed
    81. Downloading 4096 bytes @ address 0x70009000WARNING: CPU could not be halted
    82. WARNING: CPU could not be halted
    83. - Verify failed
    84. Downloading 4096 bytes @ address 0x7000A000WARNING: CPU could not be halted
    85. WARNING: CPU could not be halted
    86. - Verify failed
    87. Downloading 4096 bytes @ address 0x7000B000WARNING: CPU could not be halted
    Display All


    Source Code

    1. SEGGER J-Link Commander V6.00e (Compiled Aug 4 2016 09:38:11)
    2. DLL version V6.00e, compiled Aug 4 2016 09:37:38
    4. Connecting to J-Link via USB...O.K.
    5. Firmware: J-Link Pro V4 compiled Aug 3 2016 18:51:26
    6. Hardware version: V4.00
    7. S/N: 174301086
    8. License(s): RDI, FlashBP, FlashDL, JFlash, GDB
    9. IP-Addr: DHCP (no addr. received yet)
    10. VTref = 1.804V
    13. Type "connect" to establish a target connection, '?' for help
    14. J-Link>device imx535
    15. J-Link>connect
    16. Please specify target interface:
    17. J) JTAG (Default)
    18. S) SWD
    19. TIF>J
    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>1000
    24. Device "IMX535" selected.
    27. TotalIRLen = 13, IRPrint = 0x0101
    29. **************************
    30. WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1
    31. 149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)
    33. **************************
    35. ARM AP[0]: 0x44770001, AHB-AP
    36. ARM AP[1]: 0x24770002, APB-AP
    37. ROMTbl 0 [0]: 00001003, CID: B105900D, PID:04-000BB907 ETB
    38. ROMTbl 0 [1]: 00002003, CID: B105900D, PID:04-104BB921
    39. ROMTbl 0 [2]: 00003003, CID: B105900D, PID:04-004BB912 TPIU
    40. ROMTbl 0 [3]: 00004003, CID: B105900D, PID:04-104BB922
    41. ROMTbl 0 [4]: 00005003, CID: B105900D, PID:04-000BB906 ECT / CTI
    42. ROMTbl 0 [5]: 00006003, CID: B105900D, PID:04-003BB906 ECT / CTI
    43. ROMTbl 0 [6]: 00007003, CID: B105900D, PID:04-003BB906 ECT / CTI
    44. ROMTbl 0 [7]: 00008003, CID: B105900D, PID:04-104BBC08 Cortex-A8
    45. Found Cortex-A8 r2p5
    46. 6 code breakpoints, 2 data breakpoints
    47. Debug architecture ARMv7.0
    48. Data endian: little
    49. Main ID register: 0x412FC085
    50. I-Cache L1: 32 KB, 128 Sets, 64 Bytes/Line, 4-Way
    51. D-Cache L1: 32 KB, 128 Sets, 64 Bytes/Line, 4-Way
    52. Unified-Cache L2: 256 KB, 512 Sets, 64 Bytes/Line, 8-Way
    53. System control register:
    54. Instruction endian: little
    55. Level-1 instruction cache enabled
    56. Level-1 data cache enabled
    57. MMU enabled
    58. Branch prediction enabled
    59. Found 3 JTAG devices, Total IRLen = 13:
    60. #0 Id: 0x1BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)
    61. #1 Id: 0x00000001
    62. #2 Id: 0x1190D01D
    63. Cortex-A8 identified.
    64. J-Link>h
    65. PC: (R15) = 77817148, CPSR = 200001D3 (SVC mode, ARM FIQ dis. IRQ dis.)
    66. Current:
    67. R0 =00000000, R1 =00000060, R2 =53FBC0B4, R3 =53FBC000
    68. R4 =77861BE4, R5 =00000000, R6 =77860784, R7 =7785B53C
    69. R8 =77817150, R9 =77817150, R10=7740061C, R11=00000000, R12=00000001
    70. R13=77851209, R14=53FBC0B4, SPSR=773FFE70
    71. USR: R8 =7740061C, R9 =00000000, R10=00000001, R11=77851209, R12=53FBC0B4
    72. R13=7C9B7FE6, R14=5D8D5C97
    73. FIQ: R8 =A4BD3EEC, R9 =BC268EB7, R10=F925BB74, R11=7C75B317, R12=34F73FDE
    74. R13=9FBFCFAF, R14=6D7B9865, SPSR=00000000
    75. IRQ: R13=C04B9076, R14=C40F16B7, SPSR=00000000
    76. SVC: R13=773FFE70, R14=77826FA0, SPSR=00000000
    77. ABT: R13=AC1763BE, R14=AFAFCCDF, SPSR=00000000
    78. UND: R13=BC67FFF6, R14=9C37F67A, SPSR=00000000
    79. J-Link>loadfile test.hex
    80. Downloading file [test.hex]...
    81. O.K.
    82. J-Link>setpc 0x70000000
    83. J-Link>s
    84. 70000000: 18 F0 9F E5 LDR PC, [PC, #+0x18] ; 0x70000020
    85. J-Link>s
    86. 700001C0: 70 10 9F E5 LDR R1, [PC, #+0x70] ; 0x70000238
    87. J-Link>s
    88. 700001C4: 10 1F 0C EE MCR p15, 0, R1, c12, c0, 0
    89. J-Link>h
    90. PC: (R15) = 700001C8, CPSR = 200001D3 (SVC mode, ARM FIQ dis. IRQ dis.)
    91. Current:
    92. R0 =00000000, R1 =70000000, R2 =53FBC0B4, R3 =53FBC000
    93. R4 =77861BE4, R5 =00000000, R6 =77860784, R7 =7785B53C
    94. R8 =700001D0, R9 =700001D0, R10=7740061C, R11=00000000, R12=00000001
    95. R13=77851209, R14=53FBC0B4, SPSR=773FFE70
    96. USR: R8 =7740061C, R9 =00000000, R10=00000001, R11=77851209, R12=53FBC0B4
    97. R13=7C9B7FE6, R14=5D8D5C97
    98. FIQ: R8 =A4BD3EEC, R9 =BC268EB7, R10=F925BB74, R11=7C75B317, R12=34F73FDE
    99. R13=9FBFCFAF, R14=6D7B9865, SPSR=00000000
    100. IRQ: R13=C04B9076, R14=C40F16B7, SPSR=00000000
    101. SVC: R13=773FFE70, R14=77826FA0, SPSR=00000000
    102. ABT: R13=AC1763BE, R14=AFAFCCDF, SPSR=00000000
    103. UND: R13=BC67FFF6, R14=9C37F67A, SPSR=00000000
    104. J-Link>
    Display All

  • Hi,

    Anyone know anything about halting issues?
    Seems like in GDB Server you perform a reset instead of a halt. Most probably, the reset command will not work in J-Link Commander as well. Why? For iMX53, a special reset is required which is not implemented yet and can not easily implemented because it may differ from setup to setup because it depends on the boot source. Therefore, we recommend to the reset on your own using a J-Link Script file so it fits your requirements. Further information regarding J-Link Script Files can be found in the J-Link User Manual (UM08001).


    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.