Forums - What software is in the CSR1024 Bluetooth Node boards?

8 posts / 0 new
Last post
What software is in the CSR1024 Bluetooth Node boards?
Acutetech
Join Date: 29 Jul 16
Posts: 25
Posted: Wed, 2017-08-23 07:13

I have bought a couple of these. When powered up they identify themselves as "CSR Env Sensor" and have a number of standard characteristics and some proprietary characteristics. 

Is there any documentation on this software, or, preferrably, the XIDE project files? It seems the code is different from the SDK-3.1.0 env_sensor project.

Is there a corresponding Android or iOS app that interacts with these nodes?

If I bond with a device, how do I remove the bonding information from the node?

 

Thanks - Charles

  • Up0
  • Down0
Dr. Nissim Zur
Profile picture
Join Date: 6 Jun 16
Location: Skype: nissim.test CSR1010 External design house
Posts: 235
Posted: Wed, 2017-08-23 09:28

 

Hi Acutetech

You must use XIDE project files and download firmware into the boards. 

look at https://www.csrsupport.com/ web page for demo phone apps

You can call my Skype nissim.test

 

  • Up0
  • Down0
Acutetech
Join Date: 29 Jul 16
Posts: 25
Posted: Wed, 2017-08-23 10:51

Hi Nissim

The boards arrive programmed, and advertise as "CSR Env Sensor". My questions are: what is that software, where are the project files that create this image, is there a corresponding app that runs on a phone and communicates with these nodes, and how do I remove bonding (I have bonded the board to one phone and want to unbond it)?

I have managed to build and deploy one of the sample apps into one of my boards.

Regards - Charles

  • Up0
  • Down0
Dr. Nissim Zur
Profile picture
Join Date: 6 Jun 16
Location: Skype: nissim.test CSR1010 External design house
Posts: 235
Posted: Wed, 2017-08-23 12:16

one of the projects has the code.

search for 'C', from CSR Env Sensor to find who. 

The "CSR Env Sensor", is defined as separate characters. separated by the comma. 

  • Up0
  • Down0
Acutetech
Join Date: 29 Jul 16
Posts: 25
Posted: Thu, 2017-08-24 01:48

It seems that in the SDK-3.x scheme, the device name is defined in user_config.h, then incorporated in the Gatt database. There is no instance of "CSR Env Sensor" in the /apps directory, so the application in the CSR1024 Bluetooth Node boards seems to be missing from the SDK.

  • Up0
  • Down0
Dr. Nissim Zur
Profile picture
Join Date: 6 Jun 16
Location: Skype: nissim.test CSR1010 External design house
Posts: 235
Posted: Thu, 2017-08-24 02:25

Did you search all directory *.* for 'c' or "c"?

  • Up0
  • Down0
Dr. Nissim Zur
Profile picture
Join Date: 6 Jun 16
Location: Skype: nissim.test CSR1010 External design house
Posts: 235
Posted: Thu, 2017-08-24 02:26

Search also, who use this *.h file

  • Up0
  • Down0
Acutetech
Join Date: 29 Jul 16
Posts: 25
Posted: Thu, 2017-08-24 06:46

Yes, believe me!.

Device names are managed differently (and better!) in SDK-3.x from SDK-2.x. The device names are now defined in user_config.h for each project, like this:

/* Macro for the device name */
#define DEVICE_NAME                                 "Env Sensor"

This ends up in the app_gatt_db.db.

I have not (yet) followed  the code in detail, but it looks like there is common code for all parjects that further processes DEVICE_NAME - 

there is a \common\components\advertise.c file that can be used to move the device name into the advertising packets and a \common\server\gap\gap_service.c that is responsible for processing DEVICE_NAME, like this:

static void serviceDataInit(void)
{
    uint8 *p_name = g_device_name.parts.name;
    g_service_data.length = StrLen(DEVICE_NAME);

    g_device_name.parts.ad_type = AD_TYPE_LOCAL_NAME_COMPLETE;
    MemCopy(p_name, DEVICE_NAME, g_service_data.length);
    p_name[g_service_data.length] = '\0';
}

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.