Difference between NRF52-DK Version v3.0.0 and v2.1.0

RE: Difference between NRF52-DK Version v3.0.0 and v2.1.0

YakaMein — Tue, 01 Nov 2022 01:52:08 GMT

Hi,

Thank you so much for your patience.

" do you also have the same issues when only trying to use the DK by itself and the onboard nRF52 SoC? Also, can you share some information on what voltage the external board is supplied with, and whether it is an nRF device on board or not?"

>The customer still checking use the DK by itself and the onboard nRF52 SoC.

But voltage the external board is supplied with, and whether it is an nRF device on board is 3.00V DC stabilized power supply.

I will get back as soon as checking DK can run and the onboard nRF52 SoC

Thank you so much.

Best Regards,

Takashi

RE: Difference between NRF52-DK Version v3.0.0 and v2.1.0

Simonr — Mon, 31 Oct 2022 12:40:29 GMT

SEGGER Embedded Studio (SES) is still usable with the newer nRF52 DKs, as the new debugger also has J-Link firmware compatible with SES, so there shouldn't be a problem there. Since it seems like you're trying to debug and program an external board, do you also have the same issues when only trying to use the DK by itself and the onboard nRF52 SoC? Also, can you share some information on what voltage the external board is supplied with, and whether it is an nRF device on board or not?

However, it's worth noting that we're now focusing on the nRF Connect Extension for VS Code if your customer is working on the nRF Connect SDK and not the nRF5 SDK.

Best regards,

Simon

RE: Difference between NRF52-DK Version v3.0.0 and v2.1.0

YakaMein — Fri, 28 Oct 2022 06:41:20 GMT

Simonr

*Can you please let us know recommended replaceable software rather than SEEGER Embedded Studio?

I believe you tested with was not SEEGER. I just need to know what software you tested and working fine though.

And can you let us know what was it?

Susheel Nuguru

Speaking about Pin assignment. I agree with Susheel-san.

Because Rev 2.1.0 and Rev. 3.0.0 is same way the customer hooked up as ground.

He just wants to connect to J-Link as correctly.

We have no idea why he can't and he use SEEGER Embedded Studio But MCU is not SEEGER anymore.

So we don't know SEEGER soft is capable or not, though.

Can you give us some advice?

Thank you so much.

Takashi

RE: Difference between NRF52-DK Version v3.0.0 and v2.1.0

Susheel Nuguru — Thu, 27 Oct 2022 10:26:10 GMT

On v3.0.0 both pin 3 and 5 needs to be connected to GND on the external board. Seems not to be the case in your setup.

RE: Difference between NRF52-DK Version v3.0.0 and v2.1.0

YakaMein — Thu, 27 Oct 2022 05:24:14 GMT

Hi Simonr -san

The customer said he use SEGGER Embedded Studio.

Should he use nRF Programmer - nordicsemi.com instead SEGGER one?

Since you said MCU is changed to Original nRF5340 SoCs from SEGGER chip and you may not use SEGGER Embedded Studio either,right?

We want to know how you succeeded to connect J-Link. I think software.

Can you give some advice?

Takashi

RE: Difference between NRF52-DK Version v3.0.0 and v2.1.0

YakaMein — Wed, 26 Oct 2022 05:18:51 GMT

RE: Difference between NRF52-DK Version v3.0.0 and v2.1.0

YakaMein — Tue, 25 Oct 2022 23:37:58 GMT

Hi Simon-san,

Thank you for your support.

The customer found out Pin assign is changed without notice.

Version 2.1.0

Page 6　Debug OUT Connector

/cfs-file/__key/communityserver-discussions-components-files/4/pca10040_5F00_schematic_5F00_11.02.2019.pdf

Enlarge

Version 3.0.0

Page 5 Debug OUT Connector

https://www.nordicsemi.com/Products/Development-hardware/nrf52-dk/download#infotabs

(Needs to download pdf)

enlarge

If he can use same set up as 2.1.0 to 3.0.0, J19 connector harness needs to change, isn't it?

If he needs to change set up from 2.1.0.

Can you let us know how?

The customer simply wants to make it work asap.

Thank you so much.

Kind regards,

Takashi

RE: Difference between NRF52-DK Version v3.0.0 and v2.1.0

Simonr — Tue, 25 Oct 2022 13:19:49 GMT

Sorry, my bad. That is indeed not the correct file to reflash the newer Interface MCUs on v3.0.0. The MCU firmware on these newer DKs should not be easily erased on these newer DKs, so I'm struggling to see what has happened here.

Was this DK not able to connect to J-Link out of the box, or did it work as intended at some point and then stopped working. I've tested some 52-DKs of rev. 3.0.0 on my end and I'm not able to see this issue here.

Can you also ask them to check the following on their DK:

Have they cut the solder bridge SB9 to do current measurement? If so they need to short the P22 pin header.
Is the SW7 set to ON or OFF? It should be set to ON to show up correctly as a VCOM.
Can they try with another USB cable if they haven't already in order to rule a faulty USB cable out of the question?

Best regards,

Simon

RE: Difference between NRF52-DK Version v3.0.0 and v2.1.0

YakaMein — Tue, 25 Oct 2022 04:32:24 GMT

Hi Simon-san,

The customer said it should be working with J-Link as well and I think so too.

He doesn't have mbed But J-link.

And here is the screen shot for this failure.

But he's using SEGGER Embedded Studio.

SEGGER Embedded Studio is not capable for Ver. 3.0.0? or just defective?

I think he needs to use

nRF Connect for VS Code - nordicsemi.com or nRF Connect for Desktop - nordicsemi.com

instead SEGGER Embedded Studio.

But not sure which software he might use.

Can you let give us some suggestion?

Kind Regards,

Takashi Matsumura

RE: Difference between NRF52-DK Version v3.0.0 and v2.1.0

Simonr — Fri, 21 Oct 2022 11:53:26 GMT

He should use this Interface MCU firmware for the latest nRF52 revision:

Please provide more context on where this "Target connection error" occurs. In Visual Studio Code or the nRF Connect Programmer app? The full log of what's occurring would be helpful to understand what exactly goes wrong.

Best regards,

Simon

RE: Difference between NRF52-DK Version v3.0.0 and v2.1.0

YakaMein — Fri, 21 Oct 2022 08:09:09 GMT

Hi Simon-san,

I see two Interface MCU firmware.

Does customer need to download (I meant update) 3.0.0 version?

If So can you let us know which one, he should update?

or he have to go to https://os.mbed.com/platforms/Nordic-nRF52840-DK/#firmware-update

and https://daplink.io/?board=Nordic-nRF52-DK ?

I believe Board has no issue But, it seems like firmware or setting needs to be change.

Can you give us some advice?

Thank you for you patience.

Kind Regards,

Takashi Matsumura

RE: Difference between NRF52-DK Version v3.0.0 and v2.1.0

YakaMein — Fri, 21 Oct 2022 07:47:23 GMT

Hi Simon-san,

Thank you for your support.

The customer said "Target connection error" happens Version 3.0.0.

Can you let us know how to figure?

Thank you so much.

Takashi

RE: Difference between NRF52-DK Version v3.0.0 and v2.1.0

Simonr — Fri, 21 Oct 2022 07:44:01 GMT

Hi Takashi

What exactly is the problem with their 3.0.0 revision of the nRF52 DK?

There was one big change made from revision 2.x.x to 3.x.x, and that is that we changed the interface MCU from a SEGGER chip to one of our own nRF5340 SoCs to use as the Interface MCU (debugger). This should still work as normal though. There was also one switch added to disable or enable flow control on the VCOM port. Those should be the only major changes.

Best regards,

Simon