nRF8001 setup issues

RE: nRF8001 setup issues

user123x — Sat, 08 Oct 2016 14:09:12 GMT

Dear Raghu

Could you kindly let us know how you are sending the services.h (hex) ?

Regards

RE: nRF8001 setup issues

David Edwin — Mon, 26 Jan 2015 12:38:31 GMT

Did you get the Echo response ACI event or did you get the exact 31 bytes that you sent back. When you send the Echo Command you should get the Echo Event as the response. Have you got this ?

RE: nRF8001 setup issues

raghu — Wed, 07 Jan 2015 16:45:15 GMT

Can you please reply to my question?? I am stuck from last 2 weeks. Please help me out...

RE: nRF8001 setup issues

raghu — Wed, 24 Dec 2014 05:43:45 GMT

After i send first setup packet, nRF never makes RDYn line low, what does it mean? nRF8001 didn't recoginze the packet i sent? or is it still waiting for something else before it can send response.

RE: nRF8001 setup issues

raghu — Wed, 24 Dec 2014 05:07:32 GMT

Hi,

I have tested my ACI lines integerity by sending 31 bytes of data in echo packet and i have received all 31 bytes correctly. So i don't see an issue here with MISO line also.

I am able to receive some response for any command i sent except for the below setup command when i sent, it just stucks there, no response from nRF8001.

0x07,0x06,0x00,0x00,0x03,0x02,0x42,0x07.

To be more clear, this is first time NRF8001 is powered-up, in the sense i have never configured or setup on this device yet. So, am i supposed to do anything before trying to set up??

RE: nRF8001 setup issues

David Edwin — Tue, 23 Dec 2014 11:22:10 GMT

Can you attach the file in your question and remove it from the comment or at least add the pre-formatted option to it. (Its the icon with 101 010 )

RE: nRF8001 setup issues

raghu — Tue, 23 Dec 2014 10:09:44 GMT

Am really sorry, if my questions are confusing. I am not using ACI library as such. I am trying to implement my own ACI functions on PIC controller. So i took binary(hex) data generated in service.h file and am sending them from my code.

by the way i dont see a way to attach a file, hence copying entire services.h file here

/**
* This file is autogenerated by nRFgo Studio 1.17.1.3252
*/

#ifndef SETUP_MESSAGES_H__
#define SETUP_MESSAGES_H__

#include "hal_platform.h"
#include "aci.h"


#define SETUP_ID 0
#define SETUP_FORMAT 2 /** nRF8001 Cx */
#define ACI_DYNAMIC_DATA_SIZE 105




#define GAP_PPCP_MAX_CONN_INT 0xffff /**< Maximum connection interval as a multiple of 1.25 msec , 0xFFFF means no specific value requested */
#define GAP_PPCP_MIN_CONN_INT  0xffff /**< Minimum connection interval as a multiple of 1.25 msec , 0xFFFF means no specific value requested */
#define GAP_PPCP_SLAVE_LATENCY 0
#define GAP_PPCP_CONN_TIMEOUT 0xffff /** Connection Supervision timeout multiplier as a multiple of 10msec, 0xFFFF means no specific value requested */

#define NB_SETUP_MESSAGES 9
#define SETUP_MESSAGES_CONTENT {\
    {0x00,\
        {\
            0x07,0x06,0x00,0x00,0x02,0x02,0x42,0x07,\
        },\
    },\
    {0x00,\
        {\
            0x1f,0x06,0x10,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x01,0x01,0x00,0x00,0x06,0x00,0x01,\
            0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,\
        },\
    },\
    {0x00,\
        {\
            0x1e,0x06,0x10,0x1c,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,\
            0x00,0x00,0x00,0x10,0x00,0x00,0x00,0x10,0x03,0x90,0x00,\
        },\
    },\
    {0x00,\
        {\
            0x1f,0x06,0x20,0x00,0x04,0x04,0x02,0x02,0x00,0x01,0x28,0x00,0x01,0x00,0x18,0x04,0x04,0x05,0x05,0x00,\
            0x02,0x28,0x03,0x01,0x02,0x03,0x00,0x00,0x2a,0x04,0x04,0x14,\
        },\
    },\
    {0x00,\
        {\
            0x1f,0x06,0x20,0x1c,0x05,0x00,0x03,0x2a,0x00,0x01,0x52,0x61,0x67,0x68,0x75,0x63,0x73,0x65,0x6d,0x69,\
            0x2e,0x63,0x6f,0x6d,0x00,0x00,0x00,0x00,0x00,0x00,0x04,0x04,\
        },\
    },\
    {0x00,\
        {\
            0x1f,0x06,0x20,0x38,0x05,0x05,0x00,0x04,0x28,0x03,0x01,0x02,0x05,0x00,0x01,0x2a,0x06,0x04,0x03,0x02,\
            0x00,0x05,0x2a,0x01,0x01,0x00,0x00,0x04,0x04,0x05,0x05,0x00,\
        },\
    },\
    {0x00,\
        {\
            0x1f,0x06,0x20,0x54,0x06,0x28,0x03,0x01,0x02,0x07,0x00,0x04,0x2a,0x06,0x04,0x09,0x08,0x00,0x07,0x2a,\
            0x04,0x01,0xff,0xff,0xff,0xff,0x00,0x00,0xff,0xff,0x04,0x04,\
        },\
    },\
    {0x00,\
        {\
            0x0d,0x06,0x20,0x70,0x02,0x02,0x00,0x08,0x28,0x00,0x01,0x01,0x18,0x00,\
        },\
    },\
    {0x00,\
        {\
            0x06,0x06,0xf0,0x00,0x02,0xd1,0xb8,\
        },\
    },\
}

#endif

RE: nRF8001 setup issues

David Edwin — Tue, 23 Dec 2014 10:00:59 GMT

Can you attach the services.h file that you are using ?

RE: nRF8001 setup issues

raghu — Tue, 23 Dec 2014 09:46:28 GMT

Hello,

While i try to capture from scope, can you please tell me if the setup data am trying to send are correct? Am using version D chip of nRF8001.

Thanks, Raghu

RE: nRF8001 setup issues

raghu — Tue, 23 Dec 2014 09:02:03 GMT

Hi,

Thanks for the reply. Unfortunately i dont have way to collect traces. It's through debugging, am looking at the responses received by the NRF8001.

If i send only first packet of setup and wait for response, the NRF8001 is never sending response.

RE: nRF8001 setup issues

David Edwin — Tue, 23 Dec 2014 08:52:04 GMT

Each setup message will generate a command response event which needs to be processed, which appears to be your mis-understanding. See section 24 of the nRF8001 data sheet for the setup command.

All command responses for the setup will carry the Transaction_continue except the last command response which will have Transaction_complete as the status code. The status codes are listed in the appendix of the nRF8001 datasheet.

A status of 0x83 means device state is invalid.

Action: Send a trace of the aci commands and events from chip reset time If that is not possible can you get an SPI capture with an logic analyzer ?

For placing the Setup in NVM look at these posts

devzone.nordicsemi.com/.../

[Edited] I notice that you are using the setup format for a C version IC on a D version IC. This will work, but you will lose some features. I suggest that you select the D version in the pulldown in nRFgo studio. nRFgo Studio -> nRF8001 configuration -> Device pulldown

I suggest that you still take a look at the porting guide for the nRF8001 so you do not miss any of the steps.

Since you have received the ACI Device Started Event, it looks like the MISO path is ok, but you need to verify the MOSI path. I would suggest that you verify the ACI as suggested in the porting guide and then do the Setup.

RE: nRF8001 setup issues

raghu — Tue, 23 Dec 2014 08:10:32 GMT

and also i have one more question. How can i instruct to save setup data in NVM or RAM? when i see contents of services.h and services_lock.h, both look same

RE: nRF8001 setup issues

raghu — Tue, 23 Dec 2014 08:07:06 GMT

I am using PIC controller as application controller, am packing the ACI packets and sending over SPI and receving the responses also correctly.

On power up am receiving device started event, in which the operating mode is "2" which means setup mode. So i took the data generated by gostudio and am trying to send the below packets oen by one continuously without waiting for response, and am expecting success response at the end of last packet, but i received 0x83 response. Why is that am not able to setup nRF8001?

the packets am sending are

unsigned char setup1[8] = {0x07,0x06,0x00,0x00,0x03,0x02,0x42,0x07};

unsigned char setup2[32] = {0x1F,0x06,0x10,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x01,0x01,0x00,0x00, 0x06,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00};

unsigned char setup3[32] = {0x1F,0x06,0x10,0x1C,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00, 0x00,0x00,0x00,0x00,0x00,0x00,0x10,0x00,0x00,0x00,0x10,0x03,0x90,0x00,0xFF};

unsigned char setup4[32] = {0x1F,0x06,0x10,0x38,0xFF,0xFF,0x02,0x58,0x0A,0x05,0x00,0x00,0x00,0x10,0x00,0x00,0x00, 0x10,0x00,0x00,0x00,0x10,0x00,0x00,0x00,0x10,0x00,0x00,0x00,0x00,0x00,0x00};

unsigned char setup5[6] = {0x05,0x06,0x10,0x54,0x00,0x00};

unsigned char setup6[32] = {0x1F,0x06,0x20,0x00,0x04,0x04,0x02,0x02,0x00,0x01,0x28,0x00,0x01,0x00,0x18,0x04,0x04, 0x05,0x05,0x00,0x02,0x28,0x03,0x01,0x02,0x03,0x00,0x00,0x2A,0x04,0x04,0x14};

unsigned char setup7[32] = {0x1F,0x06,0x20,0x1C,0x05,0x00,0x03,0x2A,0x00,0x01,0x52,0x61,0x67,0x68,0x75,0x63,0x73, 0x65,0x6D,0x69,0x2E,0x63,0x6F,0x6D,0x00,0x00,0x00,0x00,0x00,0x00,0x04,0x04};

unsigned char setup8[32] = {0x1F,0x06,0x20,0x38,0x05,0x05,0x00,0x04,0x28,0x03,0x01,0x02,0x05,0x00,0x01,0x2A,0x06, 0x04,0x03,0x02,0x00,0x05,0x2A,0x01,0x01,0x00,0x00,0x04,0x04,0x05,0x05,0x00};

unsigned char setup9[32] = {0x1F,0x06,0x20,0x54,0x06,0x28,0x03,0x01,0x02,0x07,0x00,0x04,0x2A,0x06,0x04,0x09,0x08, 0x00,0x07,0x2A,0x04,0x01,0xFF,0xFF,0xFF,0xFF,0x00,0x00,0xFF,0xFF,0x04,0x04};

unsigned char setup10[14] = {0x0D,0x06,0x20,0x70,0x02,0x02,0x00,0x08,0x28,0x00,0x01,0x01, 0x18,0x00};

unsigned char setup11[7] = {0x06,0x06,0xF0,0x00,0x83,0xE2,0x04};

RE: nRF8001 setup issues

David Edwin — Tue, 23 Dec 2014 07:55:01 GMT

Can you elaborate on the method you used to verify the ACI. I would suggest that you use the ACI transport layer verification project as a start point github.com/.../ble_aci_transport_layer_verification