Smart Bluetooth Forum Discussions
Hello,
I noticed that the PADS layout file (.pcb) and BOM are not in sync with the schematics for the WICED Smart module. Specifically, note ANT1 connected to pin 10 of the 20737S module in the layout. There are also a number of Ex parts that are called out in the BOM. These Ex parts also show up in the layout, but not the schematic. Could these files please be updated?
Also, can you please provide an .asc file for the PADS layout? This will make it easier for wonks like me to import into Altium.
Thanks!
Jason
Show LessSDK: WICED-Smart-SDK-2.2.0
Tag: 920737.
app: hello-client.
Hello,
I am faced with the Tag-reset issue during high scan using the hello-client application.
When I try high scan, hello_client_advertisement_report() calls blecen_leAdvReportCb() and a number of TRACE messages(embedded in Blecen stack) are displayed and the tag reset itself.
I remove blecen_leAdvReportCb() as a comment, and then the device reset doesn't occur.
But I add my own logs using ble_trace about 20 lines at 2 sec intervals without blecen_leAdvReportCb() but it also occurs reset during high scan.
Actually, there are so many BT devices(up to 30) in my area and advertising report is called so many times.
Therefore, In my opinion, too many logs cause a device reset.
I thought it happened by watchdogs so I tried to disable wathdog and kick but it was no use.
- disabling watchdog(adding GLOBAL_DEFINES += WICED_DISABLE_WATCHDOG in the makefile)
- adding wdog_restart() between logs per lines.
Do you have any idea about this problem?(incresing trace buffer, or other way to disable watchdog, disable stack logs except for my app's log, or something)
Thanks,
Seo.
Show LessI've created a characteristic that has the "Write" checkbox checked under it's properties. However, using an app I downloaded to write to a characteristic, the value I want to change it to won't be written. Is there any C code that needs to be implemented?
Show LessHello,
From the BCM20737S documentation I cannot figure out how the device is programmed. I've learned, that there is HCI/DFU firmware update capability provided. But how are the modules programmed in the first place?
Is there a programming guide available somewhere? How does the SiP come out of the factory, is it pre-programmed with some HCI/DFU bootloader inside? What happens if errors occur during programming, is there a possiblity to program/flash the device from external?
Thanks,
Janos
Show LessHi, I am looking for WiFi+BLE for our project. Where can I get more information about home kit?
Hello Everyone,
In reference to the dialog in the thread here: Trying to understand programming failure and recovery process on BCM20736S
If checking RX status is completed by ROM code, it should be as reliable as recovery procedure, why the corrupted image will cause the download failure sometimes?
thanks.
Show LessHi!
I'm trying to connect a TAG-Board (BCM920737TAG) with our own module (BCM20736S).
But on the module I get the message "smp_bond_result 04" but it should be 03 (BONDED).
The software on the TAG board was created with the WICED-Assistent and most parts from hello-client.
Also lesmpkeys_numOfBondedDevice() returns 0 so the module is not bonded.
How can I bond the module to the TAG-Board?
Writing to the module works without problems.
I attached the traces of both.
I created the apps with WICED-Smart-SDK 2.2.0 and updated now to WICED-Smart-SDK 2.2.1
Show LessHello,
We're developing a new board and I would like to transfer data from the BCM20737S to a host computer over USB.
I understand that the HCI UART, when in application mode (not programming mode) still can't be used for 2-way communication with the host. So for my file transfer application, I wouldn't be able to send an acknowledge from the host to the BCM20737S to tell it the data was received ok, if using the the HCI UART.
On the TAG3 board, the FT2232 device is used to route both the HCI UART and the Peripheral UART out through USB. However, my issue with the FT2232 device is that's it's huge! All the space I've saved from using the BCM20737S would be lost if I used this device.
As an alternative, could you simply use an analog mux such as an NXP 74HC_HCT4052 to choose between routing out the HCI UART or the peripheral UART? This would allow a smaller single channel FTDI USB-UART device, such as the FT231XQ to be used. The select signal for the mux would be the same one used to set the polarity of HCI_UART_RX on power up (which is used to set programming mode or application mode).
Does anyone foresee any issues with this setup?
Are there plans to apply some kind of patch to allow the HCI UART to be used for 2-way communication with a host when in application mode?
Show LessHi there,
we are using the peripheral UART of the BCM20736S SiP module extensively for communication with our main MCU on a custom PCB. At the moment I got our custom services and characteristics running thanks to this forum!
I already devised a packet-based UART protocol that takes the 16 bytes long FIFO of the BCM20736S into account, i.e. maximum packet size is 16 bytes, which is somewhat of a nuisance as we use 20 bytes long characteristics that need to be transferred in multiple packets.
While experimenting with different funcitons we found the following:
void puart_write(UINT8 byte);
void puart_print(char * string);
BOOL32 puart_read(UINT8* readbyte);
void puart_synchronousRead( UINT8* buffer, UINT32 length );
void puart_synchronousWrite( UINT8* buffer, UINT32 length );
Is it correct, that puart_write, puart_print and puart_read use the underlying RTOS and don't care much about the hardware FIFO size of 16 bytes?
And when using the puart_synchronousRead and Write functions they directly interface the hardware?
Should I revise the UART protocol, because packets can be longer than 16 bytes?
Thanks in advance!
Best regards
Hannes Baumgart
Show LessHi there,
I'm developing on the Broadcom BCM20736S module. The firmware should present two custom services and severeal characteristics with 128 bit UUIDs together with the "standard" ones for name.
The first custom service contains four characteristics with the associated service's UUID128 imcremented by one to four. They contain 3, 20, 18 and 1 byte large data.
The second custom service is considerably larger with 11 characteristics.
I'm using the Wiced Smart Explorer on an Android 5.1.1 device. I can connect to the device with the correct name showing and discover besides Generic Attribute Service and the Generic Access Service with its characteristics Device Name and Appearance and the first Unknown Service with two unknown characteristics. They show the right UUID128, but the second custom service is missing as well as the two additional characteristics from the first custom service.
My program is minimal: Inside the _create-function I use bleprofile_Init(bleprofile_p_cfg), bleprofile_GPIOInit(bleprofile_gpio_p_cfg), bleprofile_Discoverable and an init funciton for the PUART.
Configuration for BLE, PUART and GPIO are used with the bleapp_set_cfg.
All services are primary services.
I'm a little stuck now - where should I look and did I commit any common error?
Best regards
Hannes Baumgart
Show Less