Simple BLE peripheral

rohit togale

Intellectual 830 points

Other Parts Discussed in Thread: CC2640, CC2650

and when i copy by adding main.c file i get errors saying

Can anyone suggest me to include main.c file and in testing sample BLE code..??

Thanks for your time and patience

Rohit

over 10 years ago

YiKai Chen over 10 years ago

Guru 735695 points

The main.c is already existing under "Startup" folder and that's why you have those errors.

rohit togale over 10 years ago in reply to YiKai Chen

Intellectual 830 points

Thanks alot chen..

But i want to confirm once again can we use XDS110 debugger ??

because in swru393 they mentioned to use xds100v3 for debugging...

if i use xds 110 then i am getting JTag error saying..

YiKai Chen over 10 years ago in reply to rohit togale

Guru 735695 points

I am very sure you can use XDS110 as debugger.

rohit togale over 10 years ago in reply to YiKai Chen

Intellectual 830 points

I am sensing data from touch screen and send it via Bluetooth to my android phone , Which sample code have to be modified?
And can i change the existing code and modify it and by writing my own application??

YiKai Chen over 10 years ago in reply to rohit togale

Guru 735695 points

What is the HW interface you want to use to sense data from touch screen?

Kimi Hu over 10 years ago in reply to rohit togale

Mastermind 6175 points

Hi,

SimpleBLEPeripheral project use XDS100 v3 as default debugger, you need change to XDS110

rohit togale over 10 years ago in reply to Kimi Hu

Intellectual 830 points

Hi YK chen , our Hardware interface is SPI...
Thank you YUHUA Hu We have already done these settings..

YiKai Chen over 10 years ago in reply to rohit togale

Guru 735695 points

You can refer to section 6.3.3 SPI in SWRU393_CC2640_BLE_Software_Developer's_Guide to show you how to use SPI driver.

rohit togale over 10 years ago in reply to YiKai Chen

Intellectual 830 points

I am getting this error when i make use of xds110 debugger..

I have set XDS110 debugger in target setting and made following changes

But still i am unable to get rid of this error.

Can anyone guide me in resolving this error..

rohit togale over 10 years ago in reply to YiKai Chen

Intellectual 830 points

I am getting this error when i make use of xds110 debugger..

I have set XDS110 debugger in target setting and made following changes

But still i am unable to get rid of this error.

Can anyone guide me in resolving this error..

Christin Lee over 10 years ago in reply to rohit togale

TI__Guru 57005 points

what's your hardware? do you use your own design?

rohit togale over 10 years ago in reply to Christin Lee

Intellectual 830 points

Ya we are using our own desugn..
We have used cc2640, TPS 5450 as a battery management..

YiKai Chen over 10 years ago in reply to rohit togale

Guru 735695 points

Can you take a picture to show how you connect XDS110 with your CC2640?

rohit togale over 10 years ago in reply to YiKai Chen

Intellectual 830 points

in this pic you can find 2 boards..

1)MSP432 development board consisting XDS110 debugger..(Black in color

2)The board (green in color.i.e our design having cc2640 ) having J-Tag port is connected to XDS110..

We have done following changes with respect to XDS110

a)TCK of our board is connected to SWCLK of XDS 110..

b)TMS of our board is connected to SWDIO of XDS 110..
and also in ccs we have made these changes by selecting swd mode. (which is attached above in above post)

We have done changes (a) and (b) since there was no JTag connection available on board.

rohit togale over 10 years ago in reply to YiKai Chen

Intellectual 830 points

in this pic you can find 2 boards..

1)MSP432 development board consisting XDS110 debugger..(Black in color

2)The board (green in color.i.e our design having cc2640 ) having J-Tag port is connected to XDS110..

We have done following changes with respect to XDS110

a)TCK of our board is connected to SWCLK of XDS 110..

b)TMS of our board is connected to SWDIO of XDS 110..
and also in ccs we have made these changes by selecting swd mode. (which is attached above in above post)

We have done changes (a) and (b) since there was no JTag connection available on board.

Christin Lee over 10 years ago in reply to rohit togale

TI__Guru 57005 points

have you checked out our Wiki post "HW troubleshooting"?

processors.wiki.ti.com/.../CC26xx_HW_Troubleshooting

TCK / TMS / RESET / GND is connected to debugger. For debuggers with a VDD sensing pin (VDD_SENSE), this should be connected to the board supply and the board should be powered by an external power source. Debuggers without a VDD sensing pin requires board supply voltage to be approx the same as the debugger voltage (typically 3-3.3V).

rohit togale over 10 years ago in reply to Christin Lee

Intellectual 830 points

Christin the same conection we used . i.e XDS110 Debugger for the MSP432 which is our board. There we got no errors..

Is it because cc2640 is cortex m3 processor.?
XDS110 debugger has worked for our one more development kit , so we tried same JTAG (from launch pad) to connect it to our new board cc2640.. .

YiKai Chen over 10 years ago in reply to rohit togale

Guru 735695 points

Try to refer to discussions in e2e.ti.com/.../431666

Christin Lee over 10 years ago in reply to rohit togale

TI__Guru 57005 points

We used XDS110 debugger in CC2650 sensor tag and launchpad as well, it should not be any problem. But since you are using your own HW design, please go thru the list. Check the TCK/TMS is at 3.3V from the XDS110, and CC2640 is powered - up probably.

rohit togale over 10 years ago in reply to Christin Lee

Intellectual 830 points

Thank you Christin and Yk Chen , you have given very valuable feedback.
Thanks alot...

YiKai Chen over 10 years ago in reply to rohit togale

Guru 735695 points

You are welcome.

rohit togale over 10 years ago in reply to YiKai Chen

Intellectual 830 points

want to establish a communication between two android devices.

1is our Capsense touch pad, and second is android mobile.

As an when i press (or touch by finger), the CapSense buttons, respective key pressed information has to be transmitted to the sensor controller of CC2640.

Here MUX is used to select the respective rows of of capsense using GPIO pins.

ex:if gpio (0) is selected then 1st row is selected.

Then that imformation i want to store it in buffer(cc2640) and transmit it to MOBILE via bluetooth.

Can anyone suggest me how to proceed and what all additional information i need to know run this application.

Thanks and regards.

please find the image of it below. and help me in resolving.

YiKai Chen over 10 years ago in reply to rohit togale

Guru 735695 points

1. You have to setup driver that can read your CapSense Touch pad data successfully on CC2640.
2. You can refer to SensorTag example which show you how to send X/Y/Z data from accelerometer and revise it to send your CapSense Touch pad data accordingly.

rohit togale over 10 years ago in reply to YiKai Chen

Intellectual 830 points

What you mean by Setting up a driver?

YiKai Chen over 10 years ago in reply to rohit togale

Guru 735695 points

I see you use sensor controller to connect with CapSense Touch and setup a driver means make sensor controller is able to read data from CapSense Touch.

Christin Lee over 10 years ago in reply to rohit togale

TI__Guru 57005 points

Hi,

What I would suggest you to do is :

With respect to BLE part,

1. Download simpleBLEPeripheral into your device and you can use different characteristic to send data to your phone. ex: you can use char 4 to send notification data. So what I would suggest you to do is modifying the characteristic you are interested in to use and make sure you can send whatever data over the air to your phone first.

With respect of cap touch data.

1. Use sensor controller studio capacitive datalogger, understand how to use the tool and export it to either CCS or IAR as stand alone project first.

2. After managing that, merge the task into simpleBLEPeripheral project and send the capacitive data thru characteristic.

rohit togale over 10 years ago in reply to YiKai Chen

Intellectual 830 points

I have modified Board.h file and assigned inputs as shown in the image.

Is this a right way to modify the pins, Because we replaced IOID with DIO..as per our schematic.

Christin Lee over 10 years ago in reply to rohit togale

TI__Guru 57005 points

The software does not recognize DIO_x, you should use what software recognize, not the names on your schematic

rohit togale over 10 years ago in reply to Christin Lee

Intellectual 830 points

Can i write it as #define Sensor_In0 GPIO_DIO_0??

Christin Lee over 10 years ago in reply to rohit togale

TI__Guru 57005 points

Hi,

Please take a look at ioc.h which can be found in
C:\ti\tirtos_simplelink_2_13_00_06\products\cc26xxware_2_21_01_15600\driverlib
Then you can see that each IOID_X is assigned to a number
#define IOID_25 0x00000019 // IO Id 25

If you insist to use your own naming convention. You will need to do
ex:
#define GPIO_DIO_0 IOID_0
#define Sensor_In0 GPIO_DIO_0
assuming your Sensor_In0 is mapped to IOID_0

Bluetooth®︎

Bluetooth forum

Simple BLE peripheral