Smart Bluetooth Forum Discussions

What is the method of error detection/correction when a 20732 is booted through HCI UART?

Our system has a board with 20732 BLE and a board with ARMS running Linux.

ARMS will reset BLE board, and then download BLE firmware over HCI UART, to boot BLE.

What happens if there's a data error during download?

Hi,

I've read in the "WICED Secure Over-the-Air Firmware Upgrade" application note that version information is included in the firmware image, and then the major version information is checked vs the previous major version. Then it (the LE Stack) will not allow the upgrade to continue of the new major version is lower than the previous major version.

1. Is this version checking only done when using the SOTAFU (Secure OTAFU) process? So the non-secure OTAFU process will  not perform this check?

2. Does this check occur during in the ROM code?

3. Since the secure firmware image format includes the product id and major and minor version (and is specified as a parameter to the WsRsaSign.exe application), does that mean the WS_UPGRADE_APP_INFO structure is not used in the SOTAFU version check?

     a. The WS_UPGRADE_APP_INFO does not seem to be used anywhere then, is that true?

Thanks,

Mike

In WICED-SMART-SDK2.1.0,  I use hello-sensor.

For interrupt, I uses P0 GPIO which is SW1 in BCM920737 Tag board.

I use deep sleep mode to save power, but interrupt handler callback function is not called sometimes.

I set the deep sleep mode to be toggled with button SW1.

It can wake up but some times it can not be into deep sleep mode although I press SW1.

I checked SW1 is high before I pressed (I modified P0 into pull up) and goes low when I pressed.

Through reset, it can be called. When I remove deep sleep mode function, interrupt handler can be called well.

I put the board to go deepsleep mode using devlpm_init(), devlpm_enableWakeFrom(GPIO_PIN_BUTTON).

At the end of hello_sensor_create(), I put bleprofile_PrepareHidOff().

and I put pull up resistor on P0, so PO acts like pull up port and goes to low when I press SW1.

My code is added,

I hope to know what is wrong with this.

I had one BCM920737TAG board, and I downloaded "wiced_sense-BCM920737TAG_Q32 download" into my board.

Then, the board trace port output like this continuously, why?

"

wiced_sense_battery_measurements_average  = 2822

Battery: Level = 85

"

BTW, I have commented out all relative sensors like this:

// Whether to support the accelerometer

#define WICED_SENSE_SUPPORT_ACCEL           0

// Whether to support gyro or not.

#define WICED_SENSE_SUPPORT_GYRO            0

// Whether to support the humidity sensor

#define WICED_SENSE_SUPPORT_HUMIDITY        0

// Whether to support the magnetometer

#define WICED_SENSE_SUPPORT_MAGNETOMETER    0

// Whether to support the pressure sensor

#define WICED_SENSE_SUPPORT_PRESSURE        0

// Whether to support the temperature sensor

#define WICED_SENSE_SUPPORT_TEMPERATURE     0

I've notice that the Android App only displays the temperature in Fahrenheit, or at least I don't seem to be able to persuade it otherwise.

Anyone finding this, or is it a coding woopsie?

I've looked at the iOS app source code and can see that seems to go the other way, only allowing display of Celsius.

  sensorData.x = ([self randomNumFrom:SENSOR_TEMP_MIN to:SENSOR_TEMP_MAX] - 320) * 5 / 9

Colin

Hello,

I have a Wiced Sense Module and I am trying to get some precise control of the PWM functionality and for that I require a 32KHz timer interrupt to update the PWM value.

From what I have read, the fine timers maximum resolution is 1KHz.

Is there a way to call an interrupt every few microseconds to update the PWM.

Also from the datasheet I can't figure out a way to change the duty cycle of the PWM.

Please help on these us

Is there an API call available that can be used to perform a soft reset?

I am aware that I can use a watchdog timeout to perform a soft reset but this takes 2 seconds which is not very suitable for my application.