Broadcom has put 32KB EEPROM (default NVRAM) which is not good for OTA upgrade - 64KB or more is required, otherwise memory might get corrupted. To fix that I tried to switch to onboard SFlash (64KB). Following the manual I changed: RD2, RD3, RD4, R100, R101.

To give it a try I booted up from ROM (button SW5) and ran:

ROM.proximity-BCM920732TAG_Q32 recover UART=COM6 PLATFORM_NV=SFLASH VERBOSE=1

but I am getting the error:

Recovering platform ...

Tools\ChipLoad\Win32\chipload.exe -BLUETOOLMODE -PORT COM6 -BAUDRATE 115200 -NODLMINIDRIVER -MINIDRIVER Platforms/BCM920732TAG_Q32/uart_64bytes_DISABLE_EEPROM_WP_PIN1.hex -BTP Platforms/BCM920732TAG_Q32/20732_SFLASH.btp -CONFIG build/proximity-BCM920732TAG_Q32-rom-ram-Wiced-release/proximity-BCM920732TAG_Q32-rom-ram-Wiced-release.hex > build/proximity-BCM920732TAG_Q32-rom-ram-Wiced-release/download.log 2>&1 && echo Recovery complete && "Tools/common/Win32/echo.exe" && echo Application running || echo **** Recovery failed - retry ****

**** Recovery failed - retry ****

The last part (most important) from download.log says:

A total of 2 contiguous memory areas were filled:

[FF000000..FF000027] DATA (40 bytes)

[FF003000..FF006075] DATA (12406 bytes)

Download config error trying to verify 40 bytes at address 0xFF000000    (SOURCE:  CONFIG   Configuration data   build/proximity-BCM920732TAG_Q32-rom-ram-Wiced-release/proximity-BCM920732TAG_Q32-rom-ram-Wiced-release.hex) (Data mismatch at address 0xFF000001. Expected byte value 0x08 but device contains 0xFF)

The above procedure for EEPROM works fine (PLATFORM_NV=SFLASH is omitted in this case since EEPROM is default).

Am I missing something for SFLASH ?

Thanks

Lukas

On page 13 of BCM20732S Technical Reference Manual on page 13 it shows Pin 39 has having dual functionality.

I want to be able to use GPIO:28 alternate function LED1 from the description

How do I go about getting this to work?

In glucose profile code I see there are a few arrays

blebgm_iopData

blebgm_iopDataValid

blebgm_iopContextData

I have data passing from sensor over peripheral UART to Broadcom chip. I am parsing data after I receive it ...

Would you suggest that now I fill in the above mentioned arrays with that data as this is what the RACP commands access?

It seems like all the notifications and indications are a part of the Record Access Control characteristic already. I understand I could also send an indication to the collector if I wanted to but I am looking to have the collector ask for the data from the sensor.

I have seen the "fake iop data" passing and working already, so I am wondering if just populating the actual glucose measurement results into these arrays is the way to go

Thanks

Can someone please explain to me how the glucose concentration field ought to be handled?

Seems like the profile data is all fake and not real world .. .also the actual BT BLE profile uses SI units

So what is typical in the blood glucose field is either mg/dL or mmol/L but the spec has it listed as kg/L or mol/L

Can someone provide me with a valid example of what say a glucose value of 100 mg/dL should be in the actual

glucose concentration SFLOAT field itself?

Thanks

Hi,

We are working on building a BLE based Keyboard/Mouse with/without the USB dongle.

Do you have any reference design based on which we can use to manufacture?

Thanks,

Krishna

Hi,

May I ask what kinds of RTOS is used in BCM20732? Is there no license free about that?

I read "LICENSE.txt" file in SDK but I could not find any information regarding to OS and its license.

Thanks,

SM

Hi,

any suggestion to interface analog signals with range from 0 to 5V with BCM20732 AD channels that must work on range 0 to 3.3V?

Thanks,

Fernando.