Segger j-link target device list doesn't have nrf9151_xxAA

[dm1]

Segger j-link target device list doesn't have nrf9151_xxAA

This means I have to manually select  nrf9151_xxCA every time as a work around. 

Is there any way it can be added

[helsing]

Hi,

Thank you for reporting your findings. We will look into this and get back to you.

[helsing]

Exactly where do you need to select this every time? Would you be able to provide some more context regarding the tool and setup? Would you be able to share a screenshot? We will then try to make sure that tool is updated.

[dm1]

It occurs when you are using vs code with the nRF connect sdk tools version 3.0 and sdk version 3.2. It is when you are using the nrf9151 dk and want to connect to the rtt terminal. Segger jlink I think v8.54 is used in the background and pops up a dialog saying the chipset version xxAA isn’t supported. I guess it’s because the 9151 is new. 

[helsing]

Our developers replied that nrf9151_xxCA is the correct name to use. nrfutil(version 2.8.8, I assume) has been using the wrong name (nrf9151_xxAA) which has then been used by VS Code to select the device in the J-Link. This is fixed in the new version of nrfutil that will be released soon (in a few days).