Proplem transfer Peripheral app from nrf52810 QFN48 to QFN32

RE: Proplem transfer Peripheral app from nrf52810 QFN48 to QFN32

OldXiao — Thu, 18 Sep 2025 03:35:15 GMT

The reason: make wrong on oscillator pins.

I don't check the datasheet of this chip, and it's pin definition is different with what I got from Internet.

But, I am still doubt that the initialization code can be executed successfully.

I remembered that it will switched to outside oscillater after started SD, so it should trigger some error soon after that except the whole system can still run even the connection to oscillater is wrong.

Thank you,Kenneth.

RE: Proplem transfer Peripheral app from nrf52810 QFN48 to QFN32

OldXiao — Thu, 18 Sep 2025 00:41:53 GMT

Thank you so much.

I misunderstanded the build code,the build code for my chip is "C0",that is mass production devices.

So,the reason BLE not started maybe related to hardware, for the app can work on other board.

First, I want to clarify some questions:

1) If I can enter debug mode and execute the main() successfully, that means:

power ok --> DECx caps work well

CPU ok --> oscillater works well

2) If return code from ble_stack_init() /advertising_init is right, the SD runs well.

3) can use nrf5 SDK17.1 + S113 7.2 to develop for nrf52810?

If answer to those question is yes,then why can't find the device with nrfConnect app?

Maybe:

1)oscillater is not stable;

2)problem on antenna circuit;

3)some functions to SD for "C0" build does not work.

Any other reason?

RE: Proplem transfer Peripheral app from nrf52810 QFN48 to QFN32

Kenneth — Wed, 17 Sep 2025 18:20:48 GMT

Hello,

Some of the build codes you refer to are Engineering build codes, meaning they manufactured during test and qualification, they can for instance have not optimized trim values etc, the middle letter B show they are Engineering build codes, also see Table 5 here:
https://docs.nordicsemi.com/bundle/ps_nrf52810/page/ordering_info.html

These engineering devices typically are manufactured in small quantities while waiting for the mass production devices. So I would say that those build codes you have that are BB0 and CB0 are something you should ideally avoid if possible. Instead order new samples of the mass production devices.

You can also find an overview here off the hardware revisions that exists:
https://docs.nordicsemi.com/bundle/comp_matrix_nrf52810/page/COMP/nrf52810/nRF52810_ic_revision_overview.html

Unfortunately I can see the Table below have not been updated for a while, but all revision 1, 2, and 3 should work with the same SDK and softdevices:
https://docs.nordicsemi.com/bundle/comp_matrix_nrf52810/page/COMP/nrf52810/nRF52810_ic_rev_sdk_sd_comp_matrix.html

Even though the above table have not been updated, I can see this is indirectly described in the product change notice:
https://docs.nordicsemi.com/bundle/PCN/resource/PCN_113-v1.2.pdf

Kenneth

RE: Proplem transfer Peripheral app from nrf52810 QFN48 to QFN32

OldXiao — Wed, 17 Sep 2025 15:10:57 GMT

Checked again:

QFAA B00 -> nrf52 SDK 17.1 + S112/S113

QFAA BB0 -> nrf52 SDK 14.2 + S112/S132

QCAA CB0 -> nrf52 SDK 14.2 + S132/S112

I did not know this limited, otherwise will chose QFN48 package.

And I understand why almost all nrf52810 application selecting QFN48.

Will try nrf52 SDK 14.2 + S112,but my code maybe need change,for I develop it based on 17.2+S113.

RE: Proplem transfer Peripheral app from nrf52810 QFN48 to QFN32

Kenneth — Wed, 17 Sep 2025 14:15:34 GMT

Hello,

The assert you see is the same reason as the assert discussed in various thread like this:
https://devzone.nordicsemi.com/f/nordic-q-a/69091/nrf52840-softdevice-assertion-failed-pc-at-0x0001505c
https://devzone.nordicsemi.com/f/nordic-q-a/121074/error-1813-unknown-error-code-at-kgj-h-o-h-536871936-pc-at-0x0001505c

(The links above is for a different chip and softdevice, but the root cause should be the same)

Kenneth

RE: Proplem transfer Peripheral app from nrf52810 QFN48 to QFN32

OldXiao — Wed, 17 Sep 2025 13:40:14 GMT

In nRF52810 - Compatible downloads - nordicsemi.com,

I made this selection:

This is the available option:

So, I have to use SDK 14.2 + S112?

Now,I'm using SDK17.1 + S113