Smart Bluetooth Forum Discussions

===

SDK: 2.1.1

Tag: 920737.

app: hello-sensor connected with 4 handset

firmware size ~ 30KB.

===

Description:

We base on Hello-Sensor to implement multi-client (= 4) to connect with 1 sensor device)

in plan_air_create()

{

..

    blecm_ConMuxInit(4);

    blecm_enableConMux();

    blecm_enablescatternet();

..

}

Problem:

1th handset connect to device is ok but after 2nd handset tries to connect with device,
it will be randomly disconnected and I print its role  as client.dev_info[con_index].role == SLAVE
(is it correct or should be MASTER?) and the disc reason is 0x8 (what does it mean?)

Possible casue:
- whether or not that some in each connection link,
what is appropriate timing by using bleprofile_SendConnParamUpdateReq.

-  if device is not as master, do i need to get rid of blecm_enablescatternet() call when in create() function.

-  920737 tage can not perform slave to multi-client without putting a master in between.

Hello,

  We have a need to maximize the amount of EEPROM we can use for storing recorded application data.  That being said I believe I am understanding how I can adjust the *.btp file and the ws_upgrade.c file for the correct ds, ss, and vs locations and length to maximize the vs size.  That being said I have 2 questions in regards to this.

1) In using the cfa_memfree() I can see that there is 16196byte left FREE in RAM.  So if I subtract this from 60KB(60*1024) which is the total available RAM internally on the BCM2073x I end up with 45244 bytes total that are apparently being used up.  If I subtract out the SS location which is from what I understand 256bytes that leaves 44988bytes which I would have to assume is what my actual code size is though this can't be the case?  Can you help me understand how to calculate the actual code size based on what is output from the cfa_mm_MemFreeBytes() API function?

2) Regarding NVRAM DLConfigVSLength and correspondence to ID's which range from 0x00-0x6F.  I am rather confused by what is being termed the 'Item' or 'Record' length.  I understand that the Page size is 32bytes and that each page has a 3byte overhead.  So my question is if I was to say use a 'Item/Record' length of 128 for each of the ID's 0x00-0x6F would I need to make the DLConfigVSLength = 112(6F + 0 location) * 128 = 14336?

3) It is imperative that I truly understand how to calculate the actual code size from the cfa_mm_MemFreeBytes() function output OR is there some means to inspect some sort of a file that actually shows the compiled sections so I can see from that what the actual individual section sizes are.  Being that it is a GNU/GCC compiler I would think there is a means to show the actual compiled listing or memory map file as can be done with a typical MCU.  I can't seem to find any sort of file output that shows this vs. having to backwards calculate from the leftover memory.

Regards,

Frank

Hi Sir,

I prepare two firmware and try to do OTAFU continuously.

But the 2nd OTAFU, it become super slow.

I have to remove the device and add/pair again to make it as fast as the 1st OTAFU.

Is it an expect behaviour?

I had ever used the trace of wiced smart IDE to obtain the debug trace message from bcm2073x.

Recently, I can't use this function. When I click "start debug traces", an error message appear on "Console" tab, "Error: Error getting portID." In "trace setup", I can't find corresponding com port even if they appear in window device manager.

This is IDE version:

WICED Smart IDE for C/C++ Developers

Version: Juno Service Release 2

Build id: 20130225-0426

How can I resue trace function?

I am just writing a technical book that describes how to design Bluetooth SMART devices in Japanese.

In that book, I have to show my own codes that uses host controller interface to change connection parameters and so on.

I want to propose my readers to use a Broadcom WICE Smart SDK in that book.

Any chance a version of the OTA manager exists for non signed images?  The only difference should be the services/chars, the 4-byte prefix (secure) and the post update crc (unsecure), right?

===

SDK: 2.1.

Tag: 920737.

app: OTA hello-sensor.

OTA firmware size ~ 25KB.

===

Question:
Can we use OTAFU (OTA-firmware upgrade) instead of Secure-OTAFU with version control upgrade?
which means, if users want to download a old OTA FW of which the version is 1.0 while in device FW,
of which the version is newer as 1.1; how to avoid this downloading?
Coz in built image, HelloSensor-BCM920737TAG_Q32-rom-ram-Wiced-release.ota.bin,
I didnt find the place storing version (like 1.1) and also no fixed position in ota firmware. So
we can not avoid user downloading old firmware? TKS

Any way to protect our program which stored inside EEPOM/SPI Flash?

We don't want orthers to copy our design? are we able to have some mechanism like secure boot?

Hi Sir,

Our hardware design change the eeprom write protect pin from P1 to P4.

I have two question to ask.

1. The minidriver.hex, is there anyway to build this minidriver by ourself to change the WP pin?

2. Besides minidriver, anything else need to be modified in the code?

Upon downloading and installing the windows version of the WICED Smart SDK, I can compile without errors by selecting a target.  But the Eclipse IDE seems to be using a different compiler, and gives me a bunch of errors when I look at the code. It doesn't affect the final compilation, but is kind of irritating to look at.  Does anyone know how to fix this or turn off the automatic compilation? Thanks.