This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Acconeer XM122 doesn't show up as a J-Link device in Segger Embedded Studio

Hello,

I have got the Acconeer XM122 module (v2.4) and the Acconeer XB122 module (v1.3). The XM122 is connected to the XB122 which is like a breakout board for the XM122. The XB122 is connected to my PC by an USB cable.

I want to program and flash the XM122 by using Segger Embedded Studio for ARM. I want to use Segger's J-Link function via the USB connection. In Segger, I press thus "Target" --> "Connect J-Link" to establish the connection between the PC and the XB122 or XM122, respectively. But, this doesn't work. I don't have an external J-Link flasher, but I was able to flash the development kit nRF52-DK via Segger in this way, i. e., I pressed "Target" --> "Connect J-Link" to establish the connection between the nRF52-DK and the PC in Segger.

The Acconeer module isn't recognized by Segger. The following message appears: "No emulators connected via USB. Do you want to connect to a J-Link via TCP/IP instead?". I know what TCP/IP is, but this is probably the indication that Segger doesn't recognize the module.

Which steps are necessary that the Acconner Module is connectable to Segger as a J-Link device via USB? I used Google and Youtube before, but I wasn't able to find a solution to this problem. The USB cable is able to transmit data. It isn't a "charge-only-one".

My PC uses Linux Mint 19.3 as an operation system. The module doesn't show up in the file explorer, too. Using the command line, I found out that the module is "stored" in /dev/ttyUSB0. The shell's command "lsusb" lists the module as the following:
Bus 001 Device 008: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)

If I don't connect the device to the PC, this name doesn't show up using "lsusb".

I also installed the J-Link Software V7.64d, Segger Embedded Studio V6.22a, the Nordic SDK 15.3, the nRF5 Command Line Tools, the Python package nrfutil, the Acconeer SDK and the XM122's Module Software.

Nordic's SDK is stored in the folder "/home/username/nRF5_SDK_15.3.0_59ac345/". Acconeer's SDK is in "/home/username/nRF5_SDK_15.3.0_59ac345/xm122" and Acconeer's Module Software in "/home/username/nRF5_SDK_15.3.0_59ac345/xm122_module_software".

I added the following path to the Nordic SDK in Segger Studio, i. e., I go to "Tools" --> "Options..." --> "Building" --> "Global Macros" and set "NRF_SDK_ROOT=/home/username/nRF5_SDK_15.3.0_59ac345/" there. Then, I open the solution
"home/username/nRF5_SDK_15.3.0_59ac345/xm122/segger_embedded_studio.emProject" and built the project. No errors occur thereby.

I am thankful for every advice.
Best regards.

Parents
  • Hi,

    From what I can see from the Acconeer XM122-XB122 Getting Started Guide, none of these boards contains a Segger J-Link debugger chip.

    In order to program/debug the board through J-Link, you need to connect a J-Link device to the SWD interface of the nRF52840 chip. According to the guide, there is a 10-pin Serial Wire Debug header on the XB122 board. If you do not have a standalone J-Link device, you can use the debug out port of one of our DKs. If you do not have a J-Link device or DK, the board can be programmed over serial DFU using nrfutil, as described in the guide.

    Best regards,
    Jørgen

Reply
  • Hi,

    From what I can see from the Acconeer XM122-XB122 Getting Started Guide, none of these boards contains a Segger J-Link debugger chip.

    In order to program/debug the board through J-Link, you need to connect a J-Link device to the SWD interface of the nRF52840 chip. According to the guide, there is a 10-pin Serial Wire Debug header on the XB122 board. If you do not have a standalone J-Link device, you can use the debug out port of one of our DKs. If you do not have a J-Link device or DK, the board can be programmed over serial DFU using nrfutil, as described in the guide.

    Best regards,
    Jørgen

Children
Related