Smart Bluetooth Forum Discussions
If I want to not show a service or characteristic is there way this information can be hidden but still be used by a client that knows it's UUID?
Show LessHi,
I would like to develop a custom product using WICED™ Sense Development Kit. I would like to know is it possible to interface any external IC to the WICED™ Sense Development Kit. Where can i find the technical data sheet for the BCM20737S. Is there ADC channels available in BCM20737S. Is there any headers available to interface the external IC. Which all interfaces are available in WICED™ Sense Development Kit.
Thanks and regards,
Shiju
Show LessI read one discussion that the user application code is stored in the internal NVRAM.
Then where is external EEPROM used for?
and when I download binary into Tag board, it seems that some data is written in external EEPROM.
Can you please explain ?
Show LessI've been using the BCM20737TAG board to develop my sample application. The SDK uses the HDI port to program the 737 chip, and my application uses the peripheral uart to communicate with another CPU.
I'd like to transition to putting a 20737S directly on my board. Preferably it will be connected to the master CPU via the peripheral uart. My question is, without using the tedious SDK and HCI interface, how can I perform the initial programming of the 737S? I've received hints that there is some protocol in place to program the 737S, over the peripheral uart, but I can't find any supporting documentation for that. Perhaps my question is, what application is pre-loaded on the 737S, and can it receive firmware updates over a uart?
Show LessIs there an API available to read the BCM20732/6/7 JTAG ID?
This would help customers identify which chip they have on their board during manufacturing test.
thanks
Show LessWith the addition of wireless charging, the
BCM20736 is first of its kind to deliver a complete
Bluetooth Smart solution, including wireless
charging. How does it achieve wireless charging?
Show Less
I have ordered the new BCM920737 eval board, for SDK 2.x.
As I understand, this BT chip supports audio profile.
But I cannot find any audio related information, e.g. how to get out the audio transmitted via BT (assuming I could configure and use SDK to initialize properly).
Is there a datasheet for the BCM20737 comming soon?
On which pins will the audio signal be provided?
I hope that the board will be able to provide S/PDIF or even I2S signals in order to connect a DAC. Just a bit lost due to missing information.
Is my impression right that audio would be provided just as PWM out?
Best regards
Torsten (tjaekel)
Show LessI've setup the wiced smart SDK and put the wiced_sense firmware under the App folder of the SDK and tried compile and download the firmware by:
$ ./make wiced_sense-BCM920737TAG_Q32 download UART=/dev/ttyUSB0
Compiling wiced_sense.c
Linking target ELF
OK, made elf.
Call to wiced_sense_spar_crt_setup @ 00207971
OK, made /home/edwardrf/Workspaces/wiced/Wiced-Smart/spar/../../build/wiced_sense-BCM920737TAG_Q32-rom-ram-Wiced-release/A_20737A1-wiced_sense-rom-ram-spar.cgs. MD5 sum is:
176b2b490643d8036361c00039537247 ../../build/wiced_sense-BCM920737TAG_Q32-rom-ram-Wiced-release/A_20737A1-wiced_sense-rom-ram-spar.cgs
--------------------------------------------------------------------------------
Patches start at 0x00204568 (RAM address)
Patches end at 0x002052D0 (RAM address)
Application starts at 0x00204F70 (RAM address)
Application ends at 0x0020794E (RAM address)
Patch size (including reused RAM) 3432 bytes
Patch size 2568 bytes
Application size 10718 bytes
------
Total RAM footprint 13286 bytes (13.0kiB)
--------------------------------------------------------------------------------
Converting CGS to HEX...
Conversion complete
Creating OTA images...
Conversion complete
OTA image footprint in NV is 12823 bytes
Downloading application...
Download complete
Application running
However, the wiced ble device disappeared and not responding to button press, no sign of the app running at all, what did I do wrong here?
Show LessThe only example code using the peripheral uart is the peripheral uart download example. And that only reads and writes a single byte at a time. I see the undocumented routines puart_synchronousRead and puart_synchronousWrite. Can I start reading data a byte at a time until I determine the incoming message length, and then use this read routine to read the rest of the message? Or will starting that routine reintialize the receive buffer and miss some bits if they already started? And does this call return control to the OS until all the data bytes requested are read and placed in the specified buffer? Same basic question for the write routine. If I just pass the location of the start of the message buffer and length, will this routine transmit the message on the peripheral uart?
Show Less