Purchased nrf52832 development kit but detection of soc name is nef52840. Name written on soc is nrf52832.

[Yagnik_pokal]

We have bought nrf52832 development kit.

When we checking the kit in nrf52 utility than it detects the IC nrf52840.

Hence we have erased all the memory in the DK.and load a firmware which is made by us. Still, it shows the IC nrf52840.

As the name written on IC is nrf52832.

Find the attached screenshots for the same.

As there is no fault from our side.we have ordered correct kit part number. Soc name is also same. but during detection, it shows nrf52840.

What to do next? Should we miss somewhere?

[tesc]

Hi,

The board is marked with Segger ID 682567491, but the device chosen in nRF Connect is 682174237. Are you sure there are no other boards connected to the PC, and can you confirm that the selected device is the only one in the drop down list?

When the board is connected to the PC and switched on, what does the following command line commands return?

nrfjprog -i

nrfjprog -s 682567491 -r

Regards,
Terje

[Yagnik_pokal]

Hi,

Thanks for your reply,

We have checked the segger ID 682174237 serial number with the PC application. as the command given in the previous reply.

In previous forum request, device selection and kit selection is different (Kit segger ID and software detect ID).

But now it is the same. still, it shows nrf52840 instead of nrf52832.

Find the attached images for the same.

[tesc]

Hi,

Make sure the board is connected to the PC. Then what does the following cmd commands return?

"nrfjprog -i"

"nrfjprog -s 682567491 -r"

We need to know that, for figuring out what might have gone wrong.

Regards,
Terje

[Yagnik_pokal]

As I have said in the earlier conversation we have checked the commands. and it detects the same segger ID as mentioned on the DEVkit.

Find the attached screenshot for the same

.

[tesc]

Hi,

Thank you.

After some digging I found that nRF Connect do not recognize nRF52832 revision 2, and the default fallback is to display the device as nRF52840. That is the reason why it displays nRF52840, which is obviously wrong and a bug in nRF Connect.

nRF Connect should not list nRF52840 when it does not know what the model is, and this will probably be fixed for a future release. In any case we will add nRF52832 revision 2 to the list of recognizable models, so that for the future these SoCs will list correctly as nRF52832.

Thank you for notifying us about this issue and for providing the additional information needed to investigate further what could and could not be the root cause.

Regards,
Terje