a problem in "ACI_DEVICE_STANDBY"

[Mohsen]

hi. Im working with nrf8001 type c in a self-designed board and im using arduino library driver on github by nordic. my mcu is stm32 and i ported library to my mcu. when I debug my program i find that my program go to "ACI_DEVICE_STANDBY" case in aci loop and nrf respond me with "03 84 0F" . as i understand, it means that nrf will advertise in this state. but when i use a smartphone with android 4.4 and BLE enabled i cant see nrf8001 in nrf uart app that made by nordic in play store. and im using service.h in "hello world" project.(type c , internal 32768, external crystal 16 MHz). please help what problems may be exist im my project or what points I have to check again? thank you.

[run_ar]

If you are using a rev C chip you need to regenerate the services.h files, as the once used in ble_sdk_arudino is for rev D. It would also be interesting to see the status code of for the command response 0x03 0x84 0x0F 0x??

[Mohsen]

Thanks for ur comment. I have recreated services.h for type C by nrf-go studio, but nothings changed. My response from nrf8001 is "00 03 84 0F". Could you please explain more about debug byte(first byte), because there's no explanation about debug byte in manual for nrf8001. Thank you in advance.

[run_ar]

The debug byte is for internal debuggin and should be discarded. regardless you are still missing the byte after 0F which is the status byte, so I don't know what is wrong. Note that the length byte is 03, which means you should clock out 0x84 0x0F and 0x?? after this. Have you verified your driver using the ACI transport layer verification project?

[Mohsen]

thank you for your comment. my received response is: "00 03 84 0F 00" that means "Success". before it i received "00 03 84 06 02" and then "00 04 81 03 00 02" i didnt verified my driver with "ACI transport layer verification project", is it necessary? i think it could be a fault in my antena design :(

[run_ar]

As far as I understand you get "setup completed" then 'device started in standby'. After this you send the connect command and the device starts to advertise. I think that even if you have a bad antenna, it would still be possible to receive advertisement packets as long as the devices are close together. Can I see your xml file? it would also be interesting to know what 16 MHz and 32KHz clock source you are using?