btlejack-firmware icon indicating copy to clipboard operation
btlejack-firmware copied to clipboard

Published 20 hours ago • verified publisher icon virtualabs

Does not work with my Micro:Bit

Open tom-x1 opened this issue 5 years ago • 5 comments

Tried to flash my BBC Microbit with the precompiled .hex, but got the error:

In application programming write failed.

Content of details.txt:

# DAPLink Firmware - see https://mbed.com/daplink Unique ID: 0000000051114e450017800d000000310000000097969901 HIC ID: 97969901 Auto Reset: 0 Automation allowed: 1 Overflow detection: 0 Daplink Mode: Bootloader Bootloader Version: 0243 Git SHA: b403a07e3696cee1e116d44cbdd64446e056ce38 Local Mods: 0 USB Interfaces: MSD Bootloader CRC: 0x32eb3cfd Interface CRC: 0x3f2b7e12 Remount count: 1

tom-x1 avatar Mar 13 '19 17:03 tom-x1

Is your Micro:Bit in maintenance mode, as described here: https://www.mbed.com/en/platform/hardware/prototyping-production/daplink/daplink-on-kl26z/ ? You just have to plug your Micro:Bit to your computer (without pressing the reset button), and a MICROBIT mass storage device will appear and you can flash it with this firmware.

virtualabs avatar Mar 13 '19 23:03 virtualabs

Thank you for your response... I think I've tried every possible variation:

  • Copy the file while the microbit is in or out of maintenance mode
  • Download and copy the file manually to USB drive or using 'btlejack -i'
  • Using a raspberry pi 2, my windows 10 pc, another windows 10 pc
  • Tried different USB ports on my computer and differnt USB cables

Everything fails. The only difference is that on the raspberry I find a timeout error in the FAIL.TXT, on my Windows Computers the error message above appears in the FAIL.TXT.

It is possible to flash the newest genuine BBC microbit firmware and do a rollback to older versions without any problems. So the flashing process itself is working. Could it be, that I have a newer hardware revision which is not working with your firmware?

PS: There is a Version number von my microbit: v1.5

tom-x1 avatar Mar 14 '19 09:03 tom-x1

That may be possible, but I tried with all the Micro:Bit I have (even with some of them I received recently), and I had no issue at all. I need to dig deeper.

virtualabs avatar Mar 21 '19 23:03 virtualabs

In the meanwhile I got it working. But it's strange... after giving up any tries to flash your firmware, I just wanted to play around with the micro:bit like it is intended (the micro:bit was brand new and I have never seen this type of hardware before). So i've created a little program via the micro:bit website and flashed my micro:bit with it. Everything worked fine...

After playing around with it I gave your firmware another try and voila, it worked without any problems. So my conclusion is that it is maybe neccessary, to flash at least once a "genuine" micro:bit firmware on the device before trying to flash yours?

tom-x1 avatar Mar 22 '19 07:03 tom-x1

Had the exact same issue. The solution:

  • Boot into maintenance mode (plug in with button pressed)
  • (Re-)Install the default firmware from here https://microbit.org/get-started/user-guide/firmware/ (microbit V1)
  • Device will now show up as MICROBIT (usb storage)
  • Install the BTLEJack firmware by copying the .hex to the MICROBIT usb storage.

ikarus23 avatar Jun 19 '21 13:06 ikarus23