[SOLVED] micro:bit segger jlink failed

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

  • [SOLVED] micro:bit segger jlink failed

    I am using segger embedded studio for nordic board nrf52 board had no problem.
    However, when I testing with the micro:bit segger jlink, it failed.
    -----------------------------------------------
    Connecting ‘J-Link’ using ‘USB’
    Connecting to target using SWD
    Loaded C:/Program Files/SEGGER/SEGGER Embedded Studio for ARM 3.40/bin/JLink_x64.dll
    Firmware Version: J-Link OB-BBC-microbit compiled Mar 24 2017 09:33:30
    DLL Version: 6.32c
    Hardware Version: V1.00
    Target Voltage: 3.300
    Device "NRF51822_XXAA" selected.
    Found SW-DP with ID 0x0BB11477
    Scanning AP map to find all available APs
    AP[1]: Stopped AP scan as end of AP map has been reached
    AP[0]: AHB-AP (IDR: 0x04770021)
    Iterating through AP map to find AHB-AP to use
    AP[0]: Core found
    AP[0]: AHB-AP ROM base: 0xF0000000
    CPUID register: 0x410CC200. Implementer code: 0x41 (ARM)
    Found Cortex-M0 r0p0, Little endian.
    The connected J-Link (S/N 788039736) is low on memory. Target connection cannot be established
    connect failed
    Failed to connect to target.
    No idcode detected.
    Please check connection and Target Interface Type
    -----------------------------------------------------------------
    I also used Keil 5 for the setup and the micor:bit board gave me the error:
    No Cortex-M SW Device found.
    The message copied as follow:
    JLink info:
    ------------
    DLL: V6.32g, compiled Jun 15 2018 17:26:15
    Firmware: J-Link OB-BBC-microbit compiled Mar 24 2017 09:33:30
    Hardware: V1.00
    S/N : 788039736
    * JLink Info: Found SW-DP with ID 0x0BB11477
    * JLink Info: Scanning AP map to find all available APs
    * JLink Info: AP[1]: Stopped AP scan as end of AP map has been reached
    * JLink Info: AP[0]: AHB-AP (IDR: 0x04770021)
    * JLink Info: Iterating through AP map to find AHB-AP to use
    * JLink Info: AP[0]: Core found
    * JLink Info: AP[0]: AHB-AP ROM base: 0xF0000000
    * JLink Info: CPUID register: 0x410CC200. Implementer code: 0x41 (ARM)
    * JLink Info: Found Cortex-M0 r0p0, Little endian.
    ***JLink Error: The connected J-Link (S/N 788039736) is low on memory. Target connection cannot be established
    Error: Flash Download failed - Target DLL has been cancelled
    Flash Load finished at 22:01:44
    ----------------------------------------------
    Please help if there is any setting wrong.
    Thanks,

    Kan.
  • Hello Kan,

    Thank you for your inquiry.
    Such an issue is not known to us.
    Attached is a successful connect using the BBC microbit.
    Could you post the J-Link Commander output of your connection attempt? wiki.segger.com/J-Link_cannot_…ty_using_J-Link_Commander
    You get the error that memory is low on J-Link.
    Are you using some third party software with J-Link that might not close connection to J-Link properly before or while you try to connect to the device?

    Best regards,
    Nino
    Images
    • Capture.PNG

      33.31 kB, 677×594, viewed 52 times
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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 contact us per e-mail.
    Alternatively our support system can be used as well: segger.com/ticket/
  • Hi Nino,
    Thanks for your prompt and helpful reply.
    I followed the wiki and here is the output:
    I am using both segger embedded studio and keil with no other third party software.
    The same cable and setup using official Nordic board with no issues.
    However, micro:bit is my target platform.
    Good to know that it works with micro:bit but I still have no luck.
    Please help.
    Thanks,

    Kan.
    Images
    • Capture segger.JPG

      80.7 kB, 672×628, viewed 41 times
  • Hello Kan,

    On our side the issue was not reproducible on the micro:bit board. So from J-Link perspective everything is working as expected.
    Please understand that we can't put much time into this matter as from our side everything is working.
    When setting up your device did you follow this guide? segger.com/products/debug-prob…-microbit-j-link-upgrade/
    Could you provide a J-Link log of the failing sequence? wiki.segger.com/Enable_J-Link_log_file

    Did the micro:bit work at any point?

    Is some application already running in the target device?


    Best regards,

    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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 contact us per e-mail.
    Alternatively our support system can be used as well: segger.com/ticket/
  • Hi Nino,
    Some progress but not really solve the issues.
    I am using my friend's desktop running win 7 ultimate and the micro:bit jlink works ok.
    My own development environment is win 10 laptop and probably need to get myself a win 7 desktop.
    This is not the best solution but at least it works.
    I hope to continue working on the win 10 laptop and can Segger look into this direction?
    Thanks,

    Kan
  • Hi Kan,

    Thank you for the additional information.
    As you reported the issue is reproducible under Win 10. We will investigate this further.
    Sorry for any inconveniences caused.

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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 contact us per e-mail.
    Alternatively our support system can be used as well: segger.com/ticket/
  • Hello Kan,

    as written before the issue was reproducible for us on Win 10 and has already been fixed internally. The fixed version is expected to be available with our next J-Link software release expected this week.

    To stay up-to-date with J-Link software releases you can subscribe here: segger.com/notification/subscribe.php?prodid=7,94

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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 contact us per e-mail.
    Alternatively our support system can be used as well: segger.com/ticket/