Smart Bluetooth Forum Discussions

Hello,

Look at the following data sheet

EEPROM is 128K supported

Serial flash is 512K supported

What is  EEPROM or serial flash  maximum supported size?

thank you.

20732 data sheet

As follows:

EEPROM Interface

The BCM20732 provides a Broadcom Serial Control (BSC) master interface.
BSC is programmed by the CPU to generate four types of bus transfers: read-only, write-only, combined read/write, and combined write/read.
BSC supports both low-speed and fast mode devices. BSC is compatible with an NXP I2C slave device, except that master arbitration (multiple I2C masters contending for the bus) is not supported.
The EEPROM can contain customer application configuration information including application code, configuration data, patches, pairing information, BD_ADDR, baud rate, SDP service record, and file system information used for code.
Native support for the Microchip 24LC128, Microchip 24AA128, and the STMicroelectronics M24128-BR is included.

Serial Flash Interface

The BCM20732 includes an SPI master controller that can be used to access serial flash memory.
The SPI master contains an AHB slave interface, transmit and receive FIFOs, and the SPI core PHY logic.
Devices natively supported include the following:
• Atmel AT25BCM512B • MXIC MX25V512ZUI-20G

Hi ,

I want to use BCM920732TAG_Q32 as a Bluetooth client.

I referred Wiced_SDK1.0.1 in which all sample apps are using it as peripheral.

As discussed in this forum WICED_SDK2.0.1 contains hello_client but it will not work for BCM920732TAG_Q32 development kit.

Please suggest some solution.

Thank you.

I have a requirement that says my device must only support the "Just Works" association model which is easily support by the Android and iOS stacks but the Microsoft Windows requires the use of their "inbox experience", can the Broadcom stack support "Just Works" or does it follow the MS model of discovery and pairing via the Windows "inbox experience"?

Following:
Is there any way to discover how much time has elapsed while asleep?

I am using devlpm_enterLowPowerMode(); to enter sleep mode. Prior to entering sleep, I am making sure to turn all my outputs low as well as executing bleprofile_Discoverable(NO_DISCOVERABLE, NULL); to make sure the module is not broadcasting.

However, measuring the output current from the battery, I am measuring 5mA. Knowing that module should be in microamps in sleep, is there something that I am missing for the current draw to be so high?

Otherwise, the module seems to sleep and upon wake from interrupt, executes a reset.

I have a board based on the BCM20732S, which previously worked but now fails to be detected and programmed.

Is it possible that something I did to it corrupted the internal eeprom?  What sorts of things could cause this, and is there any way to recover from this?

Hi,

I have been trying to compile SDK 1.0.1 using eclipse IDE on Linux.I have followed the instructions provided for eclipse set up on Linux provided in Wiced development document and I am getting the following error:

Program "/usr/local/sbin /usr/local/bin /usr/sbin /usr/bin /sbin /bin:/home/hw560218/ConnectivityTheme/softwares/Praveen_SDK/Praveen/WICED-Smart-SDK-1.0.1/make" not found in PATH 

Can anyone please help me out with this problem.Thanks in advance.

I am trying to write an attribute with 20 bytes.

#define GATT_WRITABLE (LEGATTDB_PERM_VARIABLE_LENGTH |LEGATTDB_PERM_READABLE | LEGATTDB_PERM_WRITE_CMD | LEGATTDB_PERM_WRITE_REQ) CHARACTERISTIC_UUID128_WRITABLE (HANDLE_RX_BUFFER_0_CHARACTERISTIC, HANDLE_RX_BUFFER_0, UUID_RX_BUFFER_0_CHARACTERISTIC, LEGATTDB_CHAR_PROP_READ | LEGATTDB_CHAR_PROP_WRITE, GATT_WRITABLE,  20), 1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,

i always get the trace output : permission check retCode = 03

Have you any idea what the retCode is? What's my error? Wrong permissions?

When uart receives bytes, it does go entering to interrupt call back often.

I should send uart packet several times (2 ~ 8), then uart can receive.

Byte size is regardless.

Can anybody have same experiences?

int Uart_Init(BLE_PROFILE_PUART_CFG *puart_cfg, BLECM_FUNC_WITH_PARAM puart_rx_callback)

{

puart_selectUartPads(puart_cfg->rxpin, puart_cfg->txpin, 0x00, 0x00);

// Initialize the peripheral uart driver

puart_init();

// Since we are not configuring CTS and RTS here, turn off

// hardware flow control. If HW flow control is used, then

// puart_flowOff should not be invoked.

puart_flowOff();

//BEGIN - puart interrupt

// The following lines enable interrupt when one (or more) bytes

// are received over the peripheral uart interface. This is optional.

// In the absense of this, the app is expected to poll the peripheral

// uart to pull out received bytes.

// clear interrupt

P_UART_INT_CLEAR(P_UART_ISR_RX_AFF_MASK);

// set watermark to 1 byte - will interrupt on every byte received.

P_UART_WATER_MARK_RX_LEVEL (1);

// enable UART interrupt in the Main Interrupt Controller and RX Almost Full in the UART

// Interrupt Controller

P_UART_INT_ENABLE |= P_UART_ISR_RX_AFF_MASK;

// Set callback function to app callback function.

puart_rxCb = application_puart_interrupt_callback;

// Enable the CPU level interrupt

puart_enableInterrupt();

/* END - puart interrupt */

}

void application_puart_interrupt_callback(void* unused)

{

   // There can be at most 16 bytes in the HW FIFO.

   char readbytes[16];

   UINT8 number_of_bytes_read = 0;

   while(puart_rxFifoNotEmpty() && puart_read(&readbytes[number_of_bytes_read]))

   {

   readBuffer[number_of_bytes_read] = readbytes[number_of_bytes_read];

   number_of_bytes_read++;

   ble_trace1("uart rx data is %d", (UINT8*)readBuffer[number_of_bytes_read]);

   }

  P_UART_INT_CLEAR(P_UART_ISR_RX_AFF_MASK);

P_UART_INT_ENABLE |= P_UART_ISR_RX_AFF_MASK;

}

Hi,

I know that Broadcom almost does not change the firmware of internal ROM.

But... if we need to do, how to upgrade the firmware of internal ROM?

Thanks

Chienyi

The PWM works on pins P26, P27, and P28. Physical pin of P28 is the same as P13. P13 is used for PWM3 and P28 for PWM2. Also PWM2 is connected to P14, but I could not get the PWM to work on P13/P14. All others work but not these two don't.

Also, if I use SDK 1.1.0 the PWM does not come out right, the pulses are inconsistent and change frequency after a while. Though they work just fine with SDK 1.0.1.

Plese help.

Thanks,

Mehrdad