Ok guys, that it almost never worked was due to a bad cable.
Now there's one thing left:
The download sequence using ChipLoad does not always work.
Sometimes I still get the "BluetoolDownloadMinidriver failed" error after hitting the reset button and then starting the command line.
It *could* be timing. Have to test it more thoroughly.
1 of 1 people found this helpful
You probably want to use a FTDI 3.3V usb-to-serial cable for this. The eeprom could be corrupted in the course
of your trials. You may want to do a recovery as below:
proximity-BCM920737TAG_Q32 recover UART=COMxx
Before downloading, a HCI reset will be executed follow by "Download MiniDriver". This is a requirement and is vendor-specific. The
minidriver will push the application in chunks of 64 bytes into the eeprom. Do a power-on-reset and try again.