• State Verified Answer
  • Replies 13 replies
  • Subscribers 74 subscribers
  • Views 2792 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 297257
Options

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

YakaMein

Hi Nordicsemi Team,

The one of our customers recently purchased NRF52-DK (Dev. Kit) which was Ver 2.1.0.


But This time has issue.

He thinks after version 3.0.0. cause the problem.


 
It seems like more switches were added and IC sized different than Version 2.1.0 2021.35 which normally working.

So, the questions are,
*He requires the information what's the differences between those models and how to make it work Version 3.0.0? 



Can you give us some advice?


Thank you so much.

Best Regards,
Takashi 
T448429
Parents
  • 0

    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

Reply
  • 0

    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

Children
  • 0 in reply to 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?

        

    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

Related
Terms of service