I have previously posted this on the Atmosphere forum. Had some suggestions to use Anaren platform files, but it makes no difference.

I'm using the PUART for communication with a micro.
I've managed to turn off most of the debug output with the BLE_TRACE_DISABLE define.
However, there are still some data being sent, when I get a connection, for instance, I get a long string of numbers, starting with @$*#.
Also, at startup, I get "Broadcom Debug Port: CFA Debug".

How can I turn this off?
I want only MY data to be sent on the port, not all this garbage.
I've tried new platform files, I've tried ble_traceDisable(); , ble_traceEnable(0); , ble_traceEnable(2);

None of this makes ANY difference, I still get the annoying trace output.

-- Smart SDK 2.2.2, OSX

Hi, Ms./Mr.,

I got some trouble when using GPIO Pin 35 P32 as a LED controller and four Button Keys.

The LEDG can not keep low as program control, continuously.

The program control LEDs by interrupt of button key press, as below:

void io_test_interrupt_handler(UINT8 value)

{

  ble_trace1("Button Key pressed , value:%d", value);

  if(value==2)     //GPIO_PIN_BUTTONG action

       gpio_setPinOutput(GPIO_PIN_LEDG /16, GPIO_PIN_LEDG %16, LED_OFF);

  else if(value==4)     //GPIO_PIN_BUTTONR action

       gpio_setPinOutput(GPIO_PIN_LEDR /16, GPIO_PIN_LEDR %16, LED_OFF);

  else{          // GPIO_PIN_BUTTON1 or GPIO_PIN_BUTTON2 action

       gpio_setPinOutput(GPIO_PIN_LEDR /16, GPIO_PIN_LEDR %16, LED_ON);

       gpio_setPinOutput(GPIO_PIN_LEDG /16, GPIO_PIN_LEDG %16, LED_ON);

  }

}

The related GPIO port and setting as below, catch from platform.h:

#define GPIO_PIN_BUTTON1        0

#define GPIO_SETTINGS_BUTTON1   (GPIO_INPUT  | GPIO_INIT_LOW  | GPIO_BUTTON | GPIO_INT)

#define GPIO_PIN_BUTTON2        4

#define GPIO_SETTINGS_BUTTON2   (GPIO_INPUT  | GPIO_INIT_LOW  | GPIO_BUTTON1 | GPIO_INT)

#define GPIO_PIN_BUTTONG        8

#define GPIO_SETTINGS_BUTTONG   (GPIO_INPUT  | GPIO_INIT_LOW  | GPIO_BUTTON2 | GPIO_INT)

#define GPIO_PIN_BUTTONR        33

#define GPIO_SETTINGS_BUTTONR   (GPIO_INPUT  | GPIO_INIT_LOW  | GPIO_BUTTON3 | GPIO_INT)

#define GPIO_PIN_LEDG           26

#define GPIO_SETTINGS_LEDG      (GPIO_OUTPUT | GPIO_INIT_LOW | GPIO_LED)

#define GPIO_PIN_LEDR           32

#define GPIO_SETTINGS_LEDR      (GPIO_OUTPUT | GPIO_INIT_LOW | GPIO_LED)

#define LED_ON                  0

#define LED_OFF                 1

#define GPIO_PIN_UART_TX       24

#define GPIO_PIN_UART_RX       2

The trouble are:

1. The Greed LED will light on as key press. but the Rad LED will blanking a little while only. 
   What reason let the Red LED blanking on GPIO Pin 35 P32?
2. When short HCI UART RX pin with 3V for a second, the Rad LED will start action correctly as Green LED did.
   No matter under Debug Viewer, or not. The blanking trouble disappear until power recycle again. 
3. The function, "void io_test_interrupt_handler(UINT8 value)", seems only can handle three buttons.
   The value only show out 0, 1, 2 and 4 when related key pressed.
   Especially, "0" also means depressed and one button press or release.
   How could it handle more than three buttons?

Dear expert, could you give me some help?  Thanks. Best Regards.

My NVRAM is a serial flash connected to SPIFFY1. To protect my system I want to read Unique ID Number from sflash.

How can I access this data using SPIFFY1 interface ? Since SPIFFY1 has limited availability for application use is it possible at all ? How can I assert CS since this pin is not accessible from application ? Is it always asserted ?

Hi,

I am using RTC function in BCM20737S to do a wakeup call in my design to activate some activities and then goes back to deep sleep again.

I use an external 32K LPO, that allows the RTC can wake up at anytime from 128ms to approx 144 hours.

However the sleep time of my design will be longer than 144 hours, that means once the device goes to deep sleep, it could wake up at a time that is longer than 144 hours.

How can I make the wake up time longer than 144 hours without wake up the device at every144 hours, say, to reload the RTC clock to run again.

If I do that, the device will need to wakeup every 144 hours elapsed for any longer sleep time than 144 hours though.

Please advise.

Alex

Hi WICED team,

I am trying to connect external sensors to the TAG4, and the same code that is working fine on TAG 3 doesn't seem to initiate any I2C communication on J9 of my TAG4. I have switches 2 and 4 on SW8 set to OFF, are there some other switches I need to set?

Thanks,

Filipp

SDK:WICED-Smart-SDK-2.0.1

Module:20736

Basing on hello_client, customer is developing their own application, however once customer board is powered on, following logs can be found:

ASSERT, , L#0, stat=0x20EF08
ÃASSERT, , L#0, stat=0x20EF08
ASSERT, , L#0, stat=0x20EF08
ÃASSERT, , L#0, stat=0x20EF08
ASSERT, , L#0, stat=0x20EF08
ÃASSERT, , L#0, stat=0x20EF08
ASSERT, , L#0, stat=0x20EF08
ÃASSERT, , L#0, stat=0x20EF08
ASSERT, , L#0, stat=0x20EF08

Questions:

1. What's the reason to output those logs?

2. Are there some problems on customer codes? If yes, how to fix them?

Thanks!

Hi all !

Do you know if an eval-kit is planned for the BCM20707 chip ?

And if it is, when it will be availlable ?

Thank's