nRF51422 ant bootloader with custom board

[Max]

Hi, I'm using a nRF51422 with s310 sd on sdk 10.0.0 and I have two different behaviours that are cousing me some problems.

I'm testing it with a DK (board 10003) and a custom board that is our final product. I want to use the OTA functionality and quite everything works with the DK board. With the custom one as soon i write the bootloader on the chip i can't debug/run the code anymore. I've checked the s310 memory layout for the app and the bootloader (APP: 0x1D000 BOOTLOADER: 0x3B800).

Can't figure out why. Thanks Max

[bjorn-spockeli]

Is the chip on you custom board identical to the chip on the DK in terms of Flash and RAM ?

[Max]

DK is QFAAE0 and custom is QFAAF0

[bjorn-spockeli]

Which version of the S310 are you using, v1.0.0, v2.0.1 or v3.0.0? QFAAE0 is a IC revision 2 chip and is only compatible with S310 v1.0.0 and S310 v2.0.1. The QFAAF0 chip is IC revision 3 and only compatible with S310 v3.0.0.

[Max]

I'm using S310 v3.0.0 for both, you mean compatible with OTA updates?

[bjorn-spockeli]

No, the S310 v3.0.0 is only compatible with IC revision 3 hardware, see this page on our Infocenter. However, the S310 v3.0.0 should run fine on a QFAAF0 chip. Does the QFAAF0 chip advertise as DfuTarg if you flash it with the bootloader and the SoftDevice? The bootloader is usually placed at 0x3C000 and not 0x3B800, but as long as the size is set to 0x3C00 and youre not using the bootloader settings flash page at 0x3FC00 for anything else, then you should be fine.