after the loading mynewt nimble bleprph application on nrf52840dk / nrf5340dk not seeing the device on nrf mobile app (scan)

Hi 

following are the steps followed for the nrf5340dk 
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177047756

nrf52840dk :

https://mynewt.apache.org/latest/tutorials/blinky/nRF52.html

while building the mynewt bleprph app and loading (slot1) not showing any error but after the load application adv device not pops on nrf mobile app.

for erase the nf52840dk following command are used 

nrfjprog --family NRF52 --erasepage 0-1
nrfjprog --family NRF52 --erasepage 0x10000-0x2FFFF
nrfjprog erase -all

newt load bootloader_nrf52

newt load nrf52_bleprph choose slot1 

My concern here is , do i erasing correct section of slot1 of nrf52840dk ?  which section we suppose to choose to load the newt app ?

Could you please help me why prph device is not showing on the nrf app after the loading mynewt nimble bleprph application on nrf52840dk or nrf5340dk?

Thanks,
Satish

  • Hi Satish

    Please check out the nRF52840 DK user guide for an overview of what GPIOs can be used as generic pins and which are already used. As for how to map them and how to define pins for various peripherals, please check out the Pin control section in our nRF Connect SDK documentation to see how you should configure your pins. 

    Best regards,

    Simon

  • Thanks  ,
    one more question ,
    i am doing continuous scan with scan interval of 100ms but some adv packet are dropped by scanner .  For avoiding it i have sent data on 37 channel and scan also scheduled for 37 channel only , still few packet drop seen .How to avoid it please guide.

    continuous scan with scan interval 100ms will do 100% duty cycle rate , correct.
    could you please suggest me scan interval for continuous scan ?

  • Hi Satish

    It's not only scan windows to take into consideration for scanning in BLE. They operate with a scan interval and  a scan window, where it will scan for the duration of the scan window every scan interval. So in order to get 100% duty cycle, you should set the scan window = scan interval in your application. However, BLE isn't a surefire protocol where you can expected a scanner to receive 100% of advertising packets no matter what you do, since the 2.4GHz band is generally a busy/noisy band and there is no ACKing in just BLE scanning. If you need no packet drops I would suggest connecting to the device and use ACKing to make sure every packet is received properly.

    Best regards,

    Simon

Related