Smart Bluetooth Forum Discussions

Hi,

  I tried to use PIN Tx(32), Rx(33) as UART bus for communication between 20732A0 and laptop.

  But I don't see test pattern, i.e. 'u' (0x55), showing correctly from my console or even signal scope.

  Question from my side:

  1. What's the correct initialization steps for peripheral uart? Any conflict between bleapp_set_cfg(xx,xx,xx, hello_sensor_puart_cfg,xx,xx) and 'puart_selectUartPads(33, 32, 0, 0)?

  2. What's the correct setting on variable 'bleapp_trace_enable', if we want peripheral UART to be purely managed by our application not infected by BLE stock program.

Hey guys,

I'm working on a sensor board with the BCM20732S. I have attached part of the schematic and the layout. It would be great if any FAE can do a sanity check on my design. Some questions I have are:

• Is it fine using a 2-layer design? I can change to 4 layer if necessary, but 2 layer is cheaper and allows more budget for design iterations.
• Is vias under the components fine?
• Lastly, the outer L ground is just the minimum required right? Can I do polygon pour over them, creating a ground plane?

Cheers,

Darrell

PCB Top (red)

PCB Bottom (blue)

Since I use x732 on my design, it forces me to use SDK 1.0.1.

However, I'd still like to use the native MAC Eclipse rather than having to use windows under virtual box. ( my development is done on Mac exclusively).

Thank you

I'm trying to evaluate the built in ADC on the BCM20732S and I'm having difficulty accessing the low level configuration of the ADC.

In the datasheet, the ADC section mentions:

"There is a built-in reference with supply- or bandgap-based reference modes. "

There isn't a function in Drivers/adc.h to set this, however.

In the absence of any documentation of the ADC registers or low level operation, I'm looking through adc.h and I see the following:

<code>

/// ADC bandgap reference.

enum

{

  /// P25 or ADC channel 15 is always the internal bandgap reference.

    ADC_INPUT_BG_REFERENCE = ADC_INPUT_P20,

};

</code>

Which I think just hard code the high level API functions to use the internal bandgap reference.

Does anyone know if it is possible to set the supply to use VCC as (ie supply based) reference?

Are there any ARM docs that describe the ADC in detail?

I am using the SIP module, and able to work with it fully using the SDK.

I am using 2 serial ports on board - 1 is connected to the HCI UART and the other to the PUART (default pins). 

both are working correctly.

However,  I am not able to program the EEPROM to run my own application ("hello sensor" for example).

I tried the uart-firmware_upgrade app as well as the OTP one, but it seems that something is missing: the wsUartFu.exe always quits without being able to detect the target.

What is the procedure to program the EEPROM?

Any special consideration in SIP module rather than the WICED SMART tag?

when download cgs into BCM20732,means write all cgs into EEPROM(cgs file first type will write to EEPROM first type )?

Using the 732S module and basing the code from the hello_sensor example, we are finding that when moving from 1.0.1 to 1.1.0 our code does not work as before.

Namely, after program download and reset, the program hangs and the timers and push button interrupts do not work. With more tinkering, we found that if we included the devlpm_enableWakeFrom(DEV_LPM_WAKE_SOURCE_GPIO) function in the create, the button interrupts would now work and each button press would kick off a single timer count.

Some notes and observations: (not sure if all are related)

- Our program uses all GPIO except for P8, P11, and P12.

- This code works no problem on the TAG board in 1.1.0 but not on our custom board using the module. (i.e. the timer outputs every second and fine counter whatever interval is set)

- I2C does not work anymore in 1.1.0 but does in 1.0.1.

- devlpm_enableWakeFrom(DEV_LPM_WAKE_SOURCE_GPIO);
- Observed a lower current draw from battery in 1.1.0 (5mA to ~1mA) with same code.

I am thinking it may be a mix of GPIO, hardware, and sleep configuration conflicts, but am not sure.

I have attached the boot debug traces. i did a checkdiff against the debug traces from 1.0.1 and the only thing that is different with is the bd_addr is different.

Is anybody able to help shed light on this situation?

Hello,

How can I get the BCM920736 to work as a master? I see that there is a hello_client example code, but it seems that this is specific to the hello_sensor example. But what if I want to do a discovery for multiple peripherals? How can I connect to more than one peripheral.

thanks

Pawel