[SOLVED] Unable to connect to Atmel SAM4S Xplained Pro

  • [SOLVED] Unable to connect to Atmel SAM4S Xplained Pro

    Hi - first time poster...

    I do most of my embedded development using OSX, gcc (GNU ARM Eclipse), and JLink (with NXP processors). It works great so I want to keep using it that way.

    I recently got an Atmel SAM4S Xplained Pro dev board and saw the press release about reprogramming it so that the EDBG chip works as a JLink. I reprogrammed it following the steps here (using a Win VM) but can't get it to connect on OSX or Win. Using JLinkExe and JLink.exe doesn't work either: JLinkExe (OSX) can't connect, and JLink.exe says something about unable to synchronize and fails.


    I don't know if this has anything to do with it: I notice that the picture on the link page referenced above shows JLink 5.11e but I could only find 5.11d (beta) release online.


    Any suggestions to try?

    Thanks
    -Kevin

  • Hello Kevin,


    i could reproduce this issue.
    The "EDBG -J-Link OB" works with Windows, but does not work with OSX 10.11 or VMs running on a OSX 10.11 host.
    We will fix this issue in a future release of the J-Link software & documentation pack.
    I will update this thread once a fixed version is released.

    Best regards,
    Niklas
    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 Kevin,

    The firmware for J-Link EDBG was not O.K. for OS X.
    We have uploaded a fixed firmware here:
    segger.com/jlink-edbg.html

    This one now also works flawlessly with OS X.
    Could you please give it a try?

    Short feedback would be appreciated.

    To update the EDBG on the xplained board once it is running a J-Link firmware is a bit tricky, because the firmware update utility from Atmel can no longer put the device into boot mode automatically.
    For now, you need to shorten the Boot pad with the GND pad when plugging in USB.
    EDBG will then stay in the bootloader and you can follow the steps again to update the FW.
    We will probably also provide a utility to put EDBG into boot mode once it is running a J-Link firmware, so you do not need to manually do anything on the board.
    However, this utility is not available yet.


    Best regards
    Alex
    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.

  • Alex, many thanks for the prompt response.

    I successfully updated the EDBG fw (via VM again).

    It now works on Win (via VM, and when checking using JLink.exe, and when debugging using Atmel Studio 7) but still not on OSX. However, there's some movement: on OSX, JLinkExe (v5.11d) says "Connecting to J-Link via USB...FAILED: Can not connect to J-Link via USB". However, now at the J-Link prompt, if I type 'f' it says "J-Link connection not established yet but required for command.\n Connecting to J-Link via USB...O.K.\n Firmware: J-Link EDBG compiled Mar 2 2016 ..." etc. So, it actually sorta sees the JLink EDBG. GNU ARM Eclipse still doesn't see it though. However, one additional data point; if I successfully make a debug connection/session via Atmel Studio 7 (running on VM; running then stopping Atmel debugger), then virtually disconnect the JLink EDBG from the Win VM back to OSX, GNU ARM Eclipse successfully establishes a debug connection/session. If the EDBG is reset (i.e. usb unplug/replug, or reset button) then GNU ARM Eclipse can no longer make a successful connection.

    You might ask, "well why not just use the VM since it works?" The reason is that it is insanely slow and a memory hog on my system, making it unusable for development. So, I very much appreciate your help. Hope this info helps. :)
    -Kevin

  • Hi Kevin and Forum,

    I cannot reproduce any issue with the current J-Link software (6.12d, J-Link EDBG firmware 160503), a SAM4S Xplained Pro board and macOS 10.12.2 .
    Please open a new thread if the issue still persists.

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