Updated Firmware on Huskylens 2

If the image flashing process is interrupted, you can power off the HUSKYLENS 2, then press and hold the A button while powering it on again, and retry the update.

The first startup after a successful update may take a bit longer than usual. However, if it still does not boot after more than 20 seconds, this is considered abnormal.

For the first batch of shipments, the device was preloaded with firmware v1.1.5. All subsequent shipments have been updated to firmware v1.2.1.

If the issue still cannot be resolved, please contact [email protected] to request after-sales support.

My experience with HuskyLens 2 and micro:bit compatibility

I would like to share my experience with the HuskyLens 2, because it highlights a serious problem regarding the claimed compatibility with the micro:bit.

Both DFROBOT and reseller product pages clearly state that the HuskyLens 2 is compatible with the micro:bit. However, the device I received was shipped with firmware version 1.1.5, and with this factory firmware no I2C communication works with the micro:bit. As delivered, the product is therefore not usable as advertised.

Because of this incompatibility, I followed the official DFROBOT firmware update procedure, using the official firmware provided by the manufacturer, in order to obtain the advertised micro:bit compatibility. During the update process, an error occurred at around 78%, and since then the HuskyLens 2 is permanently stuck on the boot screen and no longer starts.

What is particularly unacceptable is that:

There is no warning that a failed firmware update can permanently brick the device.

There is no recovery mode, no rollback procedure, and no safe update via SD card.

The need to update the firmware in order to use the HuskyLens 2 with a micro:bit is not mentioned anywhere on the product page.

If this information had been clearly stated, I would never have attempted the firmware update.

From a user’s perspective — and especially in an educational context — claiming micro:bit compatibility while the I2C interface does not work with the factory firmware is misleading. Compatibility should mean that the product works as delivered, or at least that firmware requirements and risks are clearly disclosed before purchase.

In the end, this means €89 spent on a HuskyLens that I can no longer use, simply for having followed the official DFROBOT procedure.

Thank you, DFROBOT !

Thanks for your advice. I'm sorry for your very bad experience, but now I'll wait for upgrading. 

But now I ask to myself: why do these issues happen ?

Happened with mine too, after updating the screen is now dead, appears bricked - device doesn't show up in Windows File Explorer. 

There must be an issue with the latest image version (huskylensV2-v1.1.6.1031.img)? 

DFRobot PLEASE SORT IT OUT!