[ABANDONED] Is the J-Link able to communicate with 88MZ100?

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

  • [ABANDONED] Is the J-Link able to communicate with 88MZ100?

    Hi,

    I'm trying to connect to a 88MZ100.
    Unfortunately there is no public datasheet and the chip is not officially in the list of supported devices of the J-Link.
    Nonetheless, people on the internet say that this chip can be connected to as "it is just a Cortex-M3" and there exist even developement boards with a J-Link clone (i suppose?).

    Now my question is how to connect to that chip?
    I wired everything up (on the SWD pads) and chose in the Commander the device "Cortex-M3" @ 4000 kHz.
    The-Jlink is flashing orange and green and outputs after 1-2 seconds "Cannot connect to target.".
    Is there some way to know why it failed? Can the commander get more verbose on its output?

    Thanks!
  • Hello,

    Thank you for your inquiry.

    Niob wrote:

    Unfortunately there is no public datasheet and the chip is not officially in the list of supported devices of the J-Link.
    Unfortunately we do not have any information about that chip either.
    How to add device support yourself is described here: wiki.segger.com/Adding_Support_for_New_Devices

    Niob wrote:

    Nonetheless, people on the internet say that this chip can be connected to as "it is just a Cortex-M3" and there exist even developement boards with a J-Link clone (i suppose?).
    Probably possible, hard to tell without any manuals. The J-Link in that link is definitely a clone and it is illegal to be used with SEGGER software.

    Niob wrote:

    I wired everything up (on the SWD pads) and chose in the Commander the device "Cortex-M3" @ 4000 kHz.
    The-Jlink is flashing orange and green and outputs after 1-2 seconds "Cannot connect to target.".
    Is there some way to know why it failed? Can the commander get more verbose on its output?
    For more detailed information you can look into the J-Link log file: wiki.segger.com/Enable_J-Link_log_file
    But without any device information we can't comment on what needs to be done to work with the chip successfully.
    However for the 88MC200 device series which we do support there was special reset handling required as the chip was able to boot from different boot media.

    Maybe that is a hint that could help.


    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.
  • Thank you for your answer.
    I logged the output but was not able to find information on how to read the logfile.

    Source Code

    1. TAB0D3740 000:000 SEGGER J-Link V6.40 Log File (0001ms, 0001ms total)
    2. TAB0D3740 000:000 DLL Compiled: Oct 26 2018 15:08:28 (0001ms, 0001ms total)
    3. TAB0D3740 000:000 Logging started @ 2018-11-28 09:43 (0001ms, 0001ms total)
    4. TAB0D3740 000:001 JLINK_SelectUSB(Port = 0) returns 0x00 (0106ms, 0107ms total)
    5. TAB0D3740 000:107 JLINK_SetWarnOutHandler(...) (0000ms, 0107ms total)
    6. TAB0D3740 000:107 JLINK_OpenEx(...)
    7. Firmware: J-Link V10 compiled Oct 26 2018 12:04:17
    8. Hardware: V10.10
    9. S/N: XXXXXXXXXX
    10. OEM: SEGGER-EDU
    11. Feature(s): FlashBP, GDB
    12. TELNET listener socket opened on port 19021WEBSRV
    13. Starting webserver (0016ms, 0123ms total)
    14. TAB0D3740 000:107 WEBSRV Webserver running on local port 19080 (0016ms, 0123ms total)
    15. TAB0D3740 000:107 returns O.K. (0016ms, 0123ms total)
    16. TAB0D3740 000:123 JLINK_GetFirmwareString(...) (0000ms, 0123ms total)
    17. TAB0D3740 000:123 JLINK_GetHardwareVersion() returns 0x18A88 (0000ms, 0123ms total)
    18. TAB0D3740 000:123 JLINK_EMU_HasCapEx(0x00000026) returns 0x00 (0000ms, 0123ms total)
    19. TAB0D3740 000:123 JLINK_EMU_GetProductId() (0000ms, 0123ms total)
    20. TAB0D3740 000:123 JLINK_GetHardwareVersion() returns 0x18A88 (0000ms, 0123ms total)
    21. TAB0D3740 000:123 JLINK_GetFirmwareString(...) (0000ms, 0123ms total)
    22. TAB0D3740 000:123 JLINK_GetEmuCaps() returns 0xB9FF7BBF (0000ms, 0123ms total)
    23. TAB0D3740 000:123 JLINK_GetEmuCaps() returns 0xB9FF7BBF (0000ms, 0123ms total)
    24. TAB0D3740 000:123 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 0123ms total)
    25. TAB0D3740 000:123 JLINK_EMU_HasCapEx(0x00000044) returns 0x01 (0000ms, 0123ms total)
    26. TAB0D3740 000:123 JLINK_ReadEmuConfigMem(..., Off = 0x9A, NumBytes = 0x01) returns 0x00 (0000ms, 0123ms total)
    27. TAB0D3740 003:307 JLINK_Api_MRU_GetList()JLINK_DEVICE_GetIndex(sDeviceName = CORTEX-M3)XML file found at: /opt/SEGGER/JLink_V640/JLinkDevices.xml (0000ms, 0123ms total)
    28. TAB0D3740 004:236 /opt/SEGGER/JLink_V640/JLinkDevices.xml evaluated successfully. returns 15 (0035ms, 0158ms total)
    29. TAB0D3740 004:271 JLINK_DEVICE_GetInfo(DeviceIndex = 15) returns 0 (0000ms, 0158ms total)
    30. TAB0D3740 006:400 JLINK_ExecCommand("device=CORTEX-M3", ...). Device "CORTEX-M3" selected. returns 0x00 (0000ms, 0158ms total)
    31. TAB0D3740 006:400 JLINK_EnableLog(...) (0000ms, 0158ms total)
    32. TAB0D3740 006:400 JLINK_GetEmuCaps() returns 0xB9FF7BBF (0000ms, 0158ms total)
    33. TAB0D3740 006:400 JLINK_TIF_GetAvailable(...) (0000ms, 0158ms total)
    34. TAB0D3740 006:400 JLINK_TIF_Select(JLINKARM_TIF_SWD) returns 0x00 (0001ms, 0159ms total)
    35. TAB0D3740 006:401 JLINK_SetSpeed(4000) (0000ms, 0159ms total)
    36. TAB0D3740 006:401 JLINK_Connect() >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> returns 0xFFFFFFFF (0792ms, 0951ms total)
    37. TAB0D3740 007:194 JLINK_GetIdData(...) >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> (0281ms, 1232ms total)
    38. TAB0D3740 070:549 JLINK_ExecCommand("device=88MC200", ...). Device "88MC200" selected. returns 0x00 (0001ms, 1233ms total)
    39. TAB0D3740 070:550 JLINK_EnableLog(...) (0000ms, 1233ms total)
    40. TAB0D3740 070:550 JLINK_GetEmuCaps() returns 0xB9FF7BBF (0000ms, 1233ms total)
    41. TAB0D3740 070:550 JLINK_TIF_GetAvailable(...) (0001ms, 1234ms total)
    42. TAB0D3740 070:551 JLINK_TIF_Select(JLINKARM_TIF_SWD) returns 0x00 (0000ms, 1234ms total)
    43. TAB0D3740 070:551 JLINK_SetSpeed(4000) (0000ms, 1234ms total)
    44. TAB0D3740 070:551 JLINK_Connect() >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> returns 0xFFFFFFFF (0794ms, 2028ms total)
    45. TAB0D3740 071:345 JLINK_GetIdData(...) >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> >0x10B TIF> >0x10F TIF> (0282ms, 2310ms total)
    46. TAB0D3740 456:530 JLINK_IsOpen() returns 0x01 (0000ms, 2310ms total)
    47. TAB0D3740 456:537 JLINK_Close() (0005ms, 2315ms total)
    48. TAB0D3740 456:537 (0005ms, 2315ms total)
    49. TAB0D3740 456:537 Closed (0005ms, 2315ms total)
    Display All
    What does this log mean? Did I wire something wrong?
    Thanks.

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

  • Hello,

    What kind of application are you using to connect to your target device?
    Could you try it with J-Link Commander and post a screenshot of your results?
    wiki.segger.com/J-Link_cannot_connect_to_the_CPU
    Could you also attach the log file of such a session?

    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,

    I used the J-Link Commander on Linux.
    This was a log of a Commander session (I edited the post to contain the full log (except the S/N)).
    The session looks like that:

    Source Code

    1. T540p:~$ JLinkExe
    2. SEGGER J-Link Commander V6.40 (Compiled Oct 26 2018 15:08:38)
    3. DLL version V6.40, compiled Oct 26 2018 15:08:28
    4. Connecting to J-Link via USB...O.K.
    5. Firmware: J-Link V10 compiled Oct 26 2018 12:04:17
    6. Hardware version: V10.10
    7. S/N: XXXXXXXXX
    8. License(s): FlashBP, GDB
    9. OEM: SEGGER-EDU
    10. VTref=3.296V
    11. Type "connect" to establish a target connection, '?' for help
    12. J-Link>connect
    13. Please specify device / core. <Default>: CORTEX-M3
    14. Type '?' for selection dialog
    15. Device>
    16. Please specify target interface:
    17. J) JTAG (Default)
    18. S) SWD
    19. T) cJTAG
    20. TIF>S
    21. Specify target interface speed [kHz]. <Default>: 4000 kHz
    22. Speed>
    23. Device "CORTEX-M3" selected.
    24. Connecting to target via SWD
    25. Cannot connect to target.
    26. J-Link>device 88MC200
    27. J-Link>connect
    28. Device "88MC200" selected.
    29. Connecting to target via SWD
    30. Cannot connect to target.
    31. J-Link>exit
    Display All
    Thanks again!