cancel
Showing results for 
Search instead for 
Did you mean: 

Smart Bluetooth

Anonymous
Not applicable

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.

0 Likes
1 Solution
Anonymous
Not applicable

The issue have been solved.It's SPI and I2C confliting.

View solution in original post

0 Likes
7 Replies
BoonT_56
Employee

Are you using the tag3 or your own product board?

Can you describe how do you program your board? Tools? Did you use a USB-to-serial converter?

wangguoshun@gozone-mobi.com

0 Likes
Anonymous
Not applicable

1.Are you using the tag3 or your own product board?

    I use our own product board.

2.Can you describe how do you program your board? Tools? Did you use a USB-to-serial converter?

    I use a PL2303 USB-to-serial wire for download.The download software is wiced SDK2.2.0.

I don't change with any code of hello_sensor.Just change the name to add "recover PLATFORM_NV=SFLASH UART=COM2" to download into board.

0 Likes
MichaelF_56
Moderator
Moderator

Note that we have only tested the FTDI USB to Serial cable described in this thread: Programming the TAG2/TAG3 Board using command line tools

Several on the forum have tried other cables with little to no success. You will need to review the scematic of each to verify that your cable is identical to the FTDI model (or purchase the FTDI model) as the device is extremely particular with regards to interfacing to the HCI UART.

0 Likes
Anonymous
Not applicable

But the cable I have verified with BCM2073xTAG board.Download is ok for EEPROM.

You mean flash HCI is not same with EEPROM?

0 Likes
MichaelF_56
Moderator
Moderator

Confused by the reference to this product for use with the TAG board: Products

Recall that the TAG boards do not require a USB to serial cable externally as they leverage an onboard USB to serial IC from FTDI to perform this function (standard USB cable is all that is needed).  These external USB to Serial cables are really only needed to program custom boards that were designed without the FTDI IC for cost or size reasons.

Note that enabling the serial flash vs. the EEPROM on the TAG board is a little tricky as well.

First make sure you can get this working using the procedure here: TAG3 Serial Flash Configuration

In addition, I see that the MX25L6406E flash you are using is not one of the two versions we have tested on the TAG3 board (both PNs are included in the blog above), so this could also be a driver issue as well.

Not sure at this point. Bringing up a custom board for the first time is often challenging from the perspective of getting the HCI UART to respond properly, so normally we ask customers to use the TAG3 board as a reference when debugging their own board.

0 Likes
Anonymous
Not applicable

The issue have been solved.It's SPI and I2C confliting.

View solution in original post

0 Likes
MichaelF_56
Moderator
Moderator

Thanks for updating the thread.

0 Likes