• State Not Answered
  • Replies 8 replies
  • Subscribers 62 subscribers
  • Views 2117 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 128967
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF51822 QFAA resets when connecting to it

PabloGC

As the title says, I'm having problems connecting to my device with my custom board and I don't know what else to do. This is my Layout:

image description

Whenever I upload my firmware to the nRF Kit it works perfectly, the chip is able to receive the data and it doesn't disconnect. The behaviour that I'm observing while trying to connect with my custom board (Malapascua) is the next:

image description

And this is with the nRF Kit:

image description

So the dBms are more or less the same but still, I don't understand why my custom board is sometimes reseting or not responding at all whenever a device tries to connect to it. The only difference I see is that my custom board is using a nRF51822 QFAA and the Kit is using a nRF51422 QFAC.

Thank you, Pablo. 

Parents
  • 0

    Hi Pablo,

    Your description is little confusing: is your "custom" board running GAP Peripheral role and you connect to it from your phone with nRF Connect app? Or is it GAP Central and it tries to connect to another BLE device (GAP Peripheral) which is Nordic Dev Kit? Also what FWs you run on the devices? Finally have you done any debugging on the embedded side? Like having UART logging and see what SD call returns unexpected error code, if it is asserted in your FW and you reset the board from FW or is it some total hard fault going from Soft Device? There are many things you can (and actually should) do before going further here on the forum...

  • 0 in reply to endnode

    Btw. if the FW works well on Dev Kit then you should check LF and HF clock sources because these are typically the only differences which matter for FWs which are using Nordic Soft Device. They typically fail during SD init not later but it can happen. If this is fine then make sure you compile for good target (ROM = flash and RAM memory limits). FW compiled for smaller chip version should still work on bigger variant (so on DK it should be always OK while on some other board with smaller chip not). Also check that chip on your custom board is Rev3! That's coded on letters after QFAA/QFAC code. If you have Rev2 it still can work but if you have Rev1 then many BLE FW examples with newer Soft Device won't work.

Reply
  • 0 in reply to endnode

    Btw. if the FW works well on Dev Kit then you should check LF and HF clock sources because these are typically the only differences which matter for FWs which are using Nordic Soft Device. They typically fail during SD init not later but it can happen. If this is fine then make sure you compile for good target (ROM = flash and RAM memory limits). FW compiled for smaller chip version should still work on bigger variant (so on DK it should be always OK while on some other board with smaller chip not). Also check that chip on your custom board is Rev3! That's coded on letters after QFAA/QFAC code. If you have Rev2 it still can work but if you have Rev1 then many BLE FW examples with newer Soft Device won't work.

Children
No Data
Related