[SOLVED] J-Link EDU Mini

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

  • [SOLVED] J-Link EDU Mini

    Hi,

    We have 2 J-Link EDU Mini in our lab, and we're using it for a while flashing LPC804 and LPC845.

    Last week both stopped working, probably after an update.

    I tried downgrading using another PC with older version, trougth J-Link Configurator, but haven't worked anyway.

    I asked a home office reasearcher with another EDU mini to return to the lab for tests, and it was working fine with the PC with the older version, and i'm not confortably trying to plug in the other PCs with the newer software. I'll probably do after unninstalling the newer versions.

    In the log, it says "Set MTB base address as it is missing from ROM table". I don't know why those new version aren't recognizing the MTB, and don't know why downgrading hasn't worked.

    Have you seem something similar with the new J-link EDU updates? I could buy new ones, but i'm not confortably with it as we don't fully understand what happened.

    Is there any other tests I could do for debugging this?

  • Hi,
    Thank you for your inquiry.

    Before we can discuss this issue:
    Your description highly indicates that you are using the J-Link EDU models (J-Link EDU and J-Link EDU Mini) in a commercial context.
    We would like to point out that the J-Link EDU models are for non-profit use only.
    Using them in a commercial context is against the the Terms of Service you agreed to and is illegal:
    segger.com/products/debug-prob…/j-link-edu/#terms-of-use

    Could you please clarify in which context you are using these J-Links?

    Best regards,
    Fabian
    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'm sorry i wasn't clear about that, that's an university laboratory.

    There are several mini robots developed my a master degree student, 2 years ago, controlled by LPC845 and LPC804, that we are continuously using since then.

    I'll try to change my mail to the intitutional one.

  • Hi,

    Thanks for explaining.
    Back to the initial post:
    We do not fully understand what problem you are actually seeing.
    You wrote that you are using the EDU Minis for flashing but then you wrote something about MTB not being recognized. MTB is not required for flashing but for tracing.

    So we would like to understand what problem you are actually seeing.
    Can you please let us know:
    1) What software / utility you are using for flashing?
    2) What is the exact error message / problem you are seeing?
    3) Do you have a 2nd setup on another PC etc. that is still working?

    Can you please get us 2 log files?
    1 of a working setup, 1 of a non-working one?
    If you do not have a working setup, 1 log file of the failing setup would be fine.

    wiki.segger.com/Enable_J-Link_log_file
    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,

    i tried with JFlashLite, JFlash and by command line, the main message is just a failed to connect.

    I'll paste here the log of non-working one, i could get a working one if necessary.

    Thanks for the help.

    T3EDC 772:666.337 SEGGER J-Link V6.86 Log File
    T3EDC 772:666.395 DLL Compiled: Sep 24 2020 17:31:31
    T3EDC 772:666.402 Logging started @ 2021-03-09 18:47
    T3EDC 772:666.408 - 20531.264ms
    T3EDC 772:666.421 JLINK_SelectUSB(Port = 0)
    T3EDC 772:667.239 - 0.824ms returns 0
    T3EDC 772:667.274 JLINK_OpenEx(...)
    T3EDC 772:678.856 Firmware: J-Link EDU Mini V1 compiled Jul 17 2020 16:25:21
    T3EDC 772:679.031 Decompressing FW timestamp took 142 us
    T3EDC 772:694.152 Hardware: V1.00
    T3EDC 772:694.176 S/N: 801018075
    T3EDC 772:694.184 OEM: SEGGER
    T3EDC 772:694.192 Feature(s): FlashBP, GDB
    T3EDC 772:696.170 TELNET listener socket opened on port 19021
    T3EDC 772:696.580 WEBSRV Starting webserver
    T3EDC 772:696.629 WEBSRV Failed to put socket into listener state (port 19080)
    T3EDC 772:696.691 WEBSRV Webserver running on local port 19081
    T3EDC 772:696.702 - 29.431ms returns "O.K."
    T3EDC 772:696.730 JLINK_GetFirmwareString(...)
    T3EDC 772:696.738 - 0.010ms
    T3EDC 772:697.117 JLINK_TIF_Select(JLINKARM_TIF_SWD)
    T3EDC 772:697.707 - 0.596ms returns 0x00
    T3EDC 772:697.763 JLINK_CORE_Select(100663551)
    T3EDC 772:697.771 - 0.010ms
    T3EDC 772:697.779 JLINK_ExecCommand("Device = LPC845M301", ...).
    T3EDC 772:700.963 Device "LPC845M301" selected.
    T3EDC 772:703.135 - 5.357ms returns 0x00
    T3EDC 772:703.150 JLINK_ExecCommand("ExcludeFlashCacheRange 0x0-0xFFFFFFFF", ...).
    T3EDC 772:703.159 - 0.003ms returns 0x00
    T3EDC 772:703.166 JLINK_GetAvailableLicense()
    T3EDC 772:710.771 - 7.613ms returns 0x02
    T3EDC 772:710.793 JLINK_SetEndian(ARM_ENDIAN_LITTLE)
    T3EDC 772:710.799 - 0.008ms returns 0
    T3EDC 772:710.806 JLINK_SetSpeed(4000)
    T3EDC 772:710.990 - 0.192ms
    T3EDC 772:711.021 JLINK_GetSpeed()
    T3EDC 772:711.028 - 0.009ms returns 4000
    T3EDC 772:711.052 JLINK_GetHWStatus(...)
    T3EDC 772:711.270 - 0.224ms returns 0
    T3EDC 772:711.308 JLINK_Connect()
    T3EDC 772:711.515 ConfigTargetSettings() start
    T3EDC 772:711.526 J-Link Script File: Executing ConfigTargetSettings()
    T3EDC 772:711.535 Set MTB base address as it is missing from ROM table.
    T3EDC 772:711.549 ConfigTargetSettings() end
    T3EDC 773:412.733 ConfigTargetSettings() start
    T3EDC 773:412.809 J-Link Script File: Executing ConfigTargetSettings()
    T3EDC 773:412.848 Set MTB base address as it is missing from ROM table.
    T3EDC 773:413.096 ConfigTargetSettings() end
    T3EDC 773:518.716 - 807.458ms returns 0xFFFFFFFF
    T3EDC 773:535.232 JLINK_Close()
    T3EDC 773:537.794 - 2.601ms
    T3EDC 773:537.848
    T3EDC 773:537.873 Closed

  • We manage to find the problem in one of the j-link. The DIO resistor was opened, and the module worked after changing the resistor.

    We couldn't find any problems in the second one, but some burnt pin on the uC side could be the problem.

    Didn't find any shorted pin do GND.

    I don't know what could have caused those problems.

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

  • Hi,
    Good to hear that you found the source of the issue.

    I will check internally what could have cause the described damage.

    Best regards,
    Fabian
    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,
    Sorry for the delay in response.

    Somehow this slipped under the table.

    If we understand you correctly the SWDIO GPIO lane was damaged/destroyed.
    This should not be possible by simply connecting it to ground.
    Possible causes could be:
    - 5V+ current connected to the pin
    - negative current connected to the pin
    - ESD

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