SimpleBLEPeripheral - P0_0 P1_2 Pins

Hi Marco,

You can check out the board file (e. g. C:\ti\simplelink\ble_sdk_2_02_00_31_s\src\boards\CC2650_LAUNCHXL ) to see the initial configuration of pins. I'm not sure what P0_0 and P1_2 is referring to.

Controlling pins is described in the Software Developer's Guide, chapter 6.5.1 ( www.ti.com/.../getliterature.tsp ).

Cheers,
Marie H.

Hi Marco,

In that case you should check out the board file in C:\Texas Instruments\BLE-CC254x-1.4.2.2\Components\hal\target\CC2540USB\hal_board_cfg.h (See SDG chapter 7.5.1).

Cheers,
Marie H

Hi,

I have looked in the file you indicated but i can't find any traces about P0_0 and P1_2. How can I solve this?

thanks.

I would like to controll following cc2541 pins since I have developed a new PCB with a LED Digit.
Pins:
P0_0 - P0_1 - P1_6 - P1_2 - P1_5 - P1_7 - P1_4 - P1_3.

I'm using a software based on SimpleBLEPeripheral which I tested on Keyfob but I'm still not able to controll all pin which I need.

How can you help me?

Thanks.

Hi Marco,

Are you sure you're using the correct version of the board file? (See SDG chapter 7.5.1.)

How are you trying to control the pins, and how do you know it's failing?

Cheers,
Marie H.

Hi,

I'm using the original board file. I configured PIN in GPIO in this way:
//-----------------------------------------------------------------------------
P0SEL = P0SEL;
P1SEL = P1SEL;
P0DIR = P0DIR|BIT0|BIT1;
P1DIR = P1DIR|(BIT2|BIT3|BIT4|BIT5|BIT6|BIT7);
//------------------------------------------------------------------------------

//Set LOW all PINS connected to the LED.
P0_0 = 0;
P0_1 = 0;
P1_2 = 0;
P1_3 = 0;
P1_4 = 0;
P1_5 = 0;
P1_6 = 0;
P1_7 = 0;
//------------------------------------------------------------------------------
/* Start OSAL */
osal_start_system();

------------------------------

Before then I start the OSAL all LED are off so all PINs are LOW. After calling osal_start_system() led related with P0_0 and P1_2 go On so i think that that pins are setted HIGH.

I have debugged and I belive that it happens with SM_ProcessEvent but I still didn't found source code.

Thanks.

Sorry, I was wrong. The problems occurs with the SimpleBLEPeripheral Event. I have noticed it commenting the SimpleBLEPeripheral_Init function and verifying that my leds didn't turn on so P0_0 and P1_2 are LOW.

I have found that P0_0 and P1_2 are set HIGH calling this function.

VOID GAP_DeviceInit( gapRole_TaskID,
gapRole_profileRole, 0,
gapRole_IRK, gapRole_SRK,
&gapRole_signCounter );

How can I avoid this?

I have already done it but I still have the problem. It looks like that P0_0 and P1_2 are set HIGH by some event occurring after osal start system.

I haven't solved this issue yet. How can I solve it?

Thanks,
Marco

Hi Marco,

I'm not seeing this behavior with the simpleBLEperipheral (on CC2541EM). Could there be some hardware problem?

Cheers,
Marie H.

Hi,

I try to explain better my problem. I need to control the following list of pin: P0_0 - P0_1 - P1_2 - P1_3 - P1_4 - P1_5 - P1_6 - P1_7. I'm configuring them as GP output with the following snippet:

P0SEL = P0SEL&(~(BIT0|BIT1));
P1SEL = P1SEL&(~(BIT2|BIT3|BIT4|BIT5|BIT6|BIT7));

P0DIR = P0DIR|((BIT0|BIT1));
P1DIR = P1DIR|(BIT2|!BIT3|BIT4|BIT5|BIT6|BIT7);

//PIN P1_3 is configured as GP output.

I have the proof that LCD and other parts of the example firmware "SimpleBLEPeripheral" use the same bits for other reasons. I'd like to avoid the use of this pins for other functionalities. How can I do it? Where do I have to modify the software?

I have commented HalLcdInit in HalDriverInit but this create problems with BLE scanning by the Dongle. Are this two functionalities related?


Thanks,
Marco

Hi Marco,

Have you tried disabling HAL_LCD in the project predefines? (Commenting HalDriverInit is not a comprehensive way of disabling the LCD.)

Cheers,
Marie H

Hi Marco,

Open the project options by right clicking the project.Under C/C++ Compiler, change the HAL_LCD entry in the Defined symbols list to false.

Cheers,

Marie H.