Smart Bluetooth Forum Discussions
We use a new flash MX25L6406E for our project.
When download it,it will fail,and in download.log:
BluetoolDownloadMinidriver failed!
If use recover mode to download it ,it fail too,and in download.log:
Download minidriver successfully had written 251 bytes to address 0x00201000
Download minidriver successfully had written 251 bytes to address 0x002010FB
Download minidriver successfully had written 251 bytes to address 0x002011F6
Download minidriver successfully had written 251 bytes to address 0x002012F1
Download minidriver successfully had written 251 bytes to address 0x002013EC
Download minidriver successfully had written 251 bytes to address 0x002014E7
Download minidriver successfully had written 251 bytes to address 0x002015E2
Download minidriver successfully had written 251 bytes to address 0x002016DD
Download minidriver successfully had written 251 bytes to address 0x002017D8
Download minidriver successfully had written 251 bytes to address 0x002018D3
Download minidriver successfully had written 251 bytes to address 0x002019CE
Download minidriver successfully had written 251 bytes to address 0x00201AC9
Download minidriver successfully had written 251 bytes to address 0x00201BC4
Download minidriver successfully had written 251 bytes to address 0x00201CBF
Download minidriver successfully had written 251 bytes to address 0x00201DBA
Download minidriver successfully had written 251 bytes to address 0x00201EB5
Download minidriver successfully had written 251 bytes to address 0x00201FB0
Download minidriver successfully had written 251 bytes to address 0x002020AB
Download minidriver successfully had written 251 bytes to address 0x002021A6
Download minidriver successfully had written 251 bytes to address 0x002022A1
Download minidriver successfully had written 251 bytes to address 0x0020239C
Download minidriver successfully had written 251 bytes to address 0x00202497
Download minidriver successfully had written 251 bytes to address 0x00202592
Download minidriver successfully had written 251 bytes to address 0x0020268D
Download minidriver successfully had written 251 bytes to address 0x00202788
Download minidriver successfully had written 251 bytes to address 0x00202883
Download minidriver successfully had written 251 bytes to address 0x0020297E
Download minidriver successfully had written 251 bytes to address 0x00202A79
Download minidriver successfully had written 251 bytes to address 0x00202B74
Download minidriver successfully had written 251 bytes to address 0x00202C6F
Download minidriver successfully had written 251 bytes to address 0x00202D6A
Download minidriver successfully had written 251 bytes to address 0x00202E65
Download minidriver successfully had written 251 bytes to address 0x00202F60
Download minidriver successfully had written 251 bytes to address 0x0020305B
Download minidriver successfully had written 251 bytes to address 0x00203156
Download minidriver successfully had written 251 bytes to address 0x00203251
Download minidriver successfully had written 251 bytes to address 0x0020334C
Download minidriver successfully had written 251 bytes to address 0x00203447
Download minidriver successfully had written 251 bytes to address 0x00203542
Download minidriver successfully had written 251 bytes to address 0x0020363D
Download minidriver successfully had written 251 bytes to address 0x00203738
Download minidriver successfully had written 251 bytes to address 0x00203833
Download minidriver successfully had written 251 bytes to address 0x0020392E
Download minidriver successfully had written 251 bytes to address 0x00203A29
Download minidriver successfully had written 251 bytes to address 0x00203B24
Download minidriver successfully had written 21 bytes to address 0x00203C1F
Download minidriver successfully had written 8 bytes to address 0x002043FC
Launch minidriver at 0x00201000 succeeded
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Terminated with error
Chip erase timeout (nLastProgressReportTime)
What's wrong with this issue? And how to resolve?
BTW, I use SDK 2.2.0.
Show LessHello,
I downloaded the IDE in version 2.2.1 and it installs without problem on my Win7 system. When I try to start the IDE I get the following error:
What can I do?
Thanks in advance!
Uwe
Show LessI am testing OTAFU, when I want to sign the SOTAFu Image, my PC is in Win7 64bit, and I can't find the WsRsaSign.exe with Win7 64bit, there is only a folder Win32, when I try to run the WsRsaSign.exe in folder Win32, it stop working, so I want to ask if this command can run in Win64? or I have to run it in Win32?
My SDK is 2.2.1.
Thanks. !
Show LessHello,
I'm trying to get the PUART configured correctly. Is there a simple "Hello World" example that demonstrates how to output to the PUART? I saw the puart_control, but that's vast overkill. I'm looking for the simplest example that I can reference when writing my own code.
Thanks,
Derek
Show Less===
SDK: 2.2.1
Tag: 920737.
app: OTA hello-sensor app code.
OTA firmware size ~ 30KB.
===
Description:
Device can not be power-on after OTA reset via android/iOS handset.
Investigation:
Our current WP is default low for read/write when run-time storage and OTA download.
in factory report, we find when we use handset to upgrade firmware, after programming done and
do the system reset; device can not be power-on again. It seems boot area is destroyed for some reason.
- do we need to add more delay between OTA re-program to NV and reset owing to
that programming/erasing is on-going while system do the reset (but is boot-code area updated during that time?)
- is it becoz firmware code near 30K so in SOC lower layer, it didnt check the program addr for the boot area??
Show LessHi BRCM!
I have early access to the BCM20707_REV2 EVK and also the alpha SDK drop. A couple of questions:
- I only have the documentation in docsafe for the BCM207xx EVK that was released last Dec. Can I get access to the latest documentation, reference schematic etc...?
Second question!
- I've registered my MFI / iBeacon ID with this site - can I get access to the homekit / iAP2 patch to enable development of MFI on the SDK that I already have? SDK revision is: "WICED-SmartReady-SDK-1.0.1-ALPHA14"
Thanks,
Nick.
Show LessI'm looking to set a characteristic when a value is entered into a com port while the chip is hooked up via USB. I can't find documentation that tells me how to handle a puart rx interrupt. Does anyone know how to do this?
Show LessWith the stock firmware, I observed that the change in sensor values, in notification mode, is published every 0.2 s. Is the interval configurable or is it a BLE requirement?
Show LessI found there are two timer like find timer and 1 sec timer on BCM20737.
IR_TX function is implemented in my application. It needs to repeat between IR_LED on and off.
For example, It has to acts as IR_LED_ON in 200ms and IR_LED_OFF in 800ms.(not us)
Are there any ID-timer defined by programmer? I ran IR_LED_ON function in 200ms .
I want to implement restarting IR_LED_ON function in 800ms .
Some solution supports like function; start_timerEx( uint8 taskID, uint16 event_id, uint32 timeout_value );
I 'm looking forward to BRCM experts' reply.
Thanks in advance.
Show LessHi,
In a4wp_power_transmitter.c, I have a question about the bleptum_check_transaction_timer() function. We know when transaction timeout, device should be disconnected from central. The source code uses the following API to disconnect device:
blecm_disconnect(BT_ERROR_CODE_CONNECTION_TERMINATED_BY_LOCAL_HOST);
In my understanding, when we have multiple devices, we need to call blecm_SetPtrConMux(conhanle) before calling blecm_disconnect(), but the source code directly calls blecm_disconnect().
Is it a bug? How can it determine which device to disconnect if it doesn't call blecm_SetPtrConMux() in advance?
Thanks
Here is the reference link of using blecm_SetPtrConMux()
disconnect recipe (from central) when multiple peripherals are connected
Show Less