Smart Bluetooth Forum Discussions

I have a WICED-Smart Board and I am trying to SOTAFU but stop in the Sign the SOTAFU Image step .I got the outcome as the image below.Please help me .

Hello,

Does anyone know of a location for documentation about API functions other than what are specified in the quick start guide, the "How to write applications" guide, and the Broadcom Wiced Smart 2.2.1 API reference guide?

Specifically, I'm looking for documentation about functions I've seen referenced in discussions (such as 'devlpm_registerForLowPowerQueries' - not this one in particular, just an example) or that may be available to handle things like creating timestamps and timeouts.

Thanks,

David Smith

Hi

I need to implemet an OTA scheme.

For the testing purpose I

     1. Converted a bin file generated by Wiced SDK to uint8[] array. The bin file was 7 KB.

     2. Called ws_upgrade_int(); ws_upgrade_init_nv_locations();

     3. Stored the array contents directly in upgrade_ds_location using ws_upgrade_store_to_nv().

     4. called ws_upgrade_finish to alter SS1 and SS2.

The issue is that it is not restarting after Step4.

Is there anything wrong in my test procedure. I am using BCM20736 with serial flash.

Is there anyway to clear data in a characteristic before writing new data to it? I'm running into and issue where if I write 5 bytes of data to a characteristic and then 3 bytes of data, the first 3 bytes get overwritten like they should, but the remaining 2 bytes from the first write are still there. Is there anyway to clear previous data before writing new data to a characteristic?

I began working on something I hadn't touched in about two months and started having an issue I had never run into before. After having the chip try to change one of its characteristics, the app would crash. I traced the crash into the bleprofile_WriteHandle() function, but since I don't have access to the source code of that function, I can't trace the crash further. Is there anyway to run some sort of debugger so I could step through my code and find the issue?

Hello,

As i cannot find a typical layout out the bcm20737s i am wondering what is the recommended decoupling for the power supply to the module?

I found some schmatics from the wiced sense which had decoupling and TVS diodes on the power supply.

Is the wiced sense using the bcm20737s?

Regards,

Luke.

Hello,

I am running a bcm20737s at 2.8v. i am also powering a sensor at 2.8v which will communicate with the bcm20737s over i2c.

what is the logic detection of the bcm20737s? Also it is recomened that i put a 10k pull up on my i2c lines. As i am running at 2.8v should this be adjusted?

Luke.

I need help with this problem

I installed the 32bit jre1.8.0_60

When I installed the IDE i got this error message:

This is what is posted on the launchanywhere website:

As a result of Issue# IOJ-1737900, the Without VM installer fails to launch with Java 8 Update 60 on Windows. However, this issue does not affect With VM installers. When this issue occurs, the user receives this error in the screenshot:

Cause

The installer is using the Java location specified in the PATH environment variable, specifically: C:\ProgramData\Oracle\Java\javapath Then, the installer is appending \bin\java.exe to that directory path. But: C:\ProgramData\Oracle\Java\javapath\bin\java.exe does not exist. Hence, the installer fails to launch and instead displays this error in the screenshot: The root cause is the File version notation of java executable (java.exe) from Java 8 Update 60 has changed. For instance, the File version of java.exe for earlier versions of java 8 such as Java 8 Update 45 is the following: 8.0.45.15 Similarly, the File version of java.exe for Java 8 Update 51 is the following: 8.0.51.16 This has changed starting from Java 8 Update 60. The File version of java.exe for Java 8 Update 60 is the following: 8.0.600.27 Notice the third number is a 3 digit number (600) in case of Java 8 Update 60 whereas the same is a 2 digit number for earlier Java 8 updates. The InstallAnywhere launcher code uses the java file version in order to determine and pick up a valid JVM path for the installer to use. The above change in the java file version is causing the launcher to fail and not use the valid JVM path.

1. modify the hello_client.c as below to  add  LEGATTDB_CHAR_PROP_NOTIFY | LEGATTDB_CHAR_PROP_INDICATE permission;

CHARACTERISTIC_UUID16 (0x0062, 0x0063, UUID_CHARACTERISTIC_BATTERY_LEVEL,

                           LEGATTDB_CHAR_PROP_READ | LEGATTDB_CHAR_PROP_NOTIFY | LEGATTDB_CHAR_PROP_INDICATE,

                           LEGATTDB_PERM_READABLE /*| LEGATTDB_PERM_WRITE_CMD |LEGATTDB_PERM_WRITE_REQ*/, 1),

        0x60,

2.  using the following code to modify characteristic value and send out the notification:

    BLEPROFILE_DB_PDU db_pdu;

    bleprofile_ReadHandle(0x63, &db_pdu);

    db_pdu.pdu[0]=0x50;

    bleprofile_WriteHandle(0x63, &db_pdu);

    blecm_SetPtrConMux(hello_client.handle_to_master);

    bleprofile_sendNotification(0x63, db_pdu.pdu, (INT32) db_pdu.len);

3. the connected android device can't receive the notification, but the value has been modified;

4. bleprofile_sendNotification(HANDLE_HELLO_CLIENT_DATA_VALUE, db_pdu.pdu, (INT32) db_pdu.len); ----for this characteristic,

    the connected device can receive the notification.

Hello,

I have 2 interrupt lines i must tie to the bcm20737s module. I am wondering are there any recommended i/o to connect to or ones to stay away from?

Thanks,

Luke.