Detecting JLINK with nrfjprog

RE: Detecting JLINK with nrfjprog

dejans — Mon, 27 Jun 2022 07:36:15 GMT

Hi Eric,

Unfortunately, I do not have this information. For questions related to timeline, please contact regional sales manager.

Best regards,
Dejan

RE: Detecting JLINK with nrfjprog

Eric Wiebols — Mon, 27 Jun 2022 06:25:06 GMT

Ok, great. Do you know when it is scheduled to be released ?

\Eric

RE: Detecting JLINK with nrfjprog

dejans — Thu, 23 Jun 2022 16:25:23 GMT

Hi Eric,

The issue is expected to be fix with nRF Command Line Tools v10.17.0.

Best regards,
Dejan

RE: Detecting JLINK with nrfjprog

dejans — Wed, 15 Jun 2022 08:41:12 GMT

Hi Eric,

Thank you for the log.

I'll get back to you when new information is available, possibly till the end of this week.

Best regards,
Dejan

RE: Detecting JLINK with nrfjprog

Eric Wiebols — Wed, 15 Jun 2022 07:51:14 GMT

devzone.nordicsemi.com/.../fail-with-10.16.txt

Log attached

RE: Detecting JLINK with nrfjprog

dejans — Tue, 14 Jun 2022 12:23:35 GMT

Hi,

[quote user="EricHDS"]Was this supposed to have been fixed ? There is, at least, nothing about it in the 10.16.0 release log.[/quote]

As far as I know, it should have been fixed with nRF Command Line Tools 10.16.0.

Could you provide log using nRF Command Line Tools v10.16.0?

Best regards,
Dejan

RE: Detecting JLINK with nrfjprog

Eric Wiebols — Tue, 14 Jun 2022 11:16:58 GMT

Hi Dejan,

I have tested upgrading to 10.16.0 but the problem persists, i.e. the JLINK still responds with "0" if its serial number is read while it is NOT connected to a target MCU.

Was this supposed to have been fixed ? There is, at least, nothing about it in the 10.16.0 release log.

\Eric

RE: Detecting JLINK with nrfjprog

dejans — Mon, 13 Jun 2022 14:34:12 GMT

Hi,

There is an update for nRF Command Line Tools. Please update your nRF Command Line Tools to the version 10.16.0.

Best regards,
Dejan

RE: Detecting JLINK with nrfjprog

Eric Wiebols — Mon, 13 Jun 2022 13:24:06 GMT

Hi,

Any information regarding this issue yet ? I have a workaround for now but it, sort of, messes up the logic of my flow.

\Eric

RE: Detecting JLINK with nrfjprog

dejans — Tue, 26 Apr 2022 13:11:10 GMT

Hi,

Thank you for the logs.

I have reported the issue internally. I will get back to you when I get more information related to this issue.

Best regards,
Dejan

RE: Detecting JLINK with nrfjprog

Eric Wiebols — Tue, 26 Apr 2022 10:18:32 GMT

Ok, so one "success log" and one "fail log" attached. It seems the correct SNR is read also in the fail log but that something goes wrong due to the (obviously) "low target voltage".

\Eric

devzone.nordicsemi.com/.../Success.txt devzone.nordicsemi.com/.../3716.Fail.txt

RE: Detecting JLINK with nrfjprog

dejans — Tue, 26 Apr 2022 09:04:54 GMT

Hi,

Could you provide a log either by providing a callback to the cb parameter or by setting jlink to log the output to a file (J-Link log file)?

Best regards,
Dejan

RE: Detecting JLINK with nrfjprog

Eric Wiebols — Tue, 26 Apr 2022 08:03:35 GMT

Like I said it is "0", i.e. a valid null terminated string with one character.

\Eric

RE: Detecting JLINK with nrfjprog

dejans — Tue, 26 Apr 2022 07:54:34 GMT

Hi,

Could you please provide the return value of the NRFJPROG_read_connected_emu_snr() in the failing case?

Best regards,
Dejan

RE: Detecting JLINK with nrfjprog

Eric Wiebols — Mon, 25 Apr 2022 13:26:32 GMT

Yes, but I'm doing that. Here is the complete code:

static string JLinkPath = "C:\\Program Files\\SEGGER\\JLink\\JLink_x64.dll";

[DllImport("nrfjprog.dll", CallingConvention = CallingConvention.Cdecl)]
private static extern int NRFJPROG_open_dll(string jlink_path, System.IntPtr cb, int family);

[DllImport("nrfjprog.dll", CallingConvention = CallingConvention.Cdecl)]
private static extern void NRFJPROG_close_dll();

[DllImport("nrfjprog.dll", CallingConvention = CallingConvention.Cdecl)]
private static extern int NRFJPROG_connect_to_emu_without_snr(int clock_speed_in_khz);

[DllImport("nrfjprog.dll", CallingConvention = CallingConvention.Cdecl)]
private static extern int NRFJPROG_read_connected_emu_snr(out int serial_number);

private void btnJlink_Click(object sender, RoutedEventArgs e)
{

int snr,clock_speed_in_khz = 4000;
IntPtr cb = new IntPtr();

NRFJPROG_close_dll();

NRFJPROG_open_dll(JLinkPath, cb, 1);

NRFJPROG_connect_to_emu_without_snr(clock_speed_in_khz);

NRFJPROG_read_connected_emu_snr(out snr);

}

And as previously stated, snr will have the correct serial number IF the emulator is (physically) connected to a target but "0" if it is not.

\Eric

RE: Detecting JLINK with nrfjprog

dejans — Mon, 25 Apr 2022 13:18:43 GMT

Hi,

The function NRFJPROG_read_connected_emu_snr() returns the serial number of the emulator to which it is connected, but before that it is necessary to establish the connection to the emulator, which is done by using the functions NRFJPROG_connect_to_emu_with_snr() or NRFJPROG_connect_to_emu_without_snr().
In other words, the function NRFJPROG_read_connected_emu_snr() requires as a precondition a live connection to the debug probe.

Best regards,
Dejan

RE: Detecting JLINK with nrfjprog

Eric Wiebols — Mon, 25 Apr 2022 11:16:35 GMT

Hi,

Please note that I'm not asking about NRFJPROG_enum_emu_snr() anymore. What I'm trying (since 220420) is to use NRFJPROG_read_connected_emu_snr(). Since it does not use serial_numbers_length I don't understand your question.

\Eric

RE: Detecting JLINK with nrfjprog

dejans — Mon, 25 Apr 2022 10:13:47 GMT

Hi,

Could you please confirm that serial_numbers_length in your code is not zero?

Best regards,
Dejan

RE: Detecting JLINK with nrfjprog

Eric Wiebols — Fri, 22 Apr 2022 12:54:57 GMT

I have a JLink+ with a custom board.

Yes, with nrfjprog --ids I get the id from the emulator regardless if it is connected to a target or not. So, either the NRFJPROG_read_connected_emu_snr (out snr) function has an issue when called from C# or the nrfprog application uses another function in the .dll API. Maybe you can investigate internally what it uses ?

\Eric

RE: Detecting JLINK with nrfjprog

dejans — Fri, 22 Apr 2022 12:11:36 GMT

Hi,

I could get serial number if there is a connection to the debugger on nRF52840-DK. As long as the debugger is powered on, I could read its serial number with "nrfjprog --ids".

Are you using external debugger? Are you using development kit or custom board? In case you are using development kit, how are you cutting power to the nrf52 chip?

Can you get serial number by running the command "nrfjprog --ids" from the command line?

Best regards,
Dejan

RE: Detecting JLINK with nrfjprog

Eric Wiebols — Fri, 22 Apr 2022 06:15:03 GMT

Sorry, but you misinterpret my question;

Yes, I establish the connection with the debugger/emulator and can read out the serial number, but, ONLY, if the debugger/emulator is connected to a powered target system (e.g. nRF52). If it is not the serial number returned is "0". Have you tested this on your end ?

\Eric

RE: Detecting JLINK with nrfjprog

dejans — Thu, 21 Apr 2022 15:03:02 GMT

Hi,

[quote user="EricHDS"]Connection established with what ?[/quote]

The connection is established to the emulator/debugger. Proper steps for establishing the connection are given in the header file I mentioned before.

[quote user="EricHDS"]Why does the emulator need to be connected to a target in order for its (the emulator's) serial number to be read ?[/quote]

This is the way how it is done - first establish the connection and then read the serial number.

Best regards,
Dejan

RE: Detecting JLINK with nrfjprog

Eric Wiebols — Thu, 21 Apr 2022 14:17:53 GMT

Dejan,

Connection established with what ? Why does the emulator need to be connected to a target in order for its (the emulator's) serial number to be read ?

\Eric

RE: Detecting JLINK with nrfjprog

dejans — Thu, 21 Apr 2022 14:13:03 GMT

Hi,

As it is described in nrfjprog header file for specific family (for example jlinkarm_nrf52_nrfjprogdll.h for 52 family), NRFJPROG_read_connected_emu_snr() can be used to check emulator's serial number after connection is established. Before the execution of the function DLL must be opened and connection to the emulator must be established.

Best regards,
Dejan

RE: Detecting JLINK with nrfjprog

Eric Wiebols — Wed, 20 Apr 2022 13:27:01 GMT

Hi again,

Came across a similar problem with the NRFJPROG_read_connected_emu_snr (out snr) function. If I call it when the JLink is connected to a nRF52 it returns the correct serial number of the JLink. If it is NOT connected to a nRF52 it will simply return "0" as the serial number.

This does not make any sense, Any there way around it ?

\Eric