Upgrade Firmware is stuck at 0%


#1

I have made sure that my Mbot has been connected properly with the right serial port (I even check my device manager) However everytime on multiple computers (running Windows on both) the Mbot wont upgrade its firmware properly. Itll flash 3 colors on the LEDs, Red, green, blue make 3 sound tones and then the upgrade firmware bar will remain stuck at 0% and then fail.

What can I do to fix this?


#2

Hi Darkazure00,

Please refer to this instruction to upgrade firmware again have a check.22. How to Upgrade Firmware for mBot.docx.zip (407.6 KB)
Please note: Temporarily remove the Bluetooth/2.4G module from mBot while you upgrading the firmware.

If above points make no sense, you may change the USB cable have a check.


#3

I have exactly the same problem.

This is brand new robot version 1.0, just assembled it to teach my son.

I’ve tried Mac OS (El Capitan 10.11.6) and Windows 10 laptops. If I try to connect to my BT version of the mBot from iPad app, it shows that internal firmware version is 0.0.0.

I tried 2 versions of software 3.3.8 and 3.4.0 (which is what became available today). Tried programming with and without Bluetooth module connected.


#4

Just to show what is going on I’ve created a short video (from MacOS but Windows 10 is exactly the same):


#5

Hi Surge,

You can only upgrade firmware or reset default program without the Bluetooth connection.
I’d suggest that you remove the Bluetooth module from mCore and try again.

Besides, you may change the USB cable have a check.
Except the mBot robot, do you have any other main Board from makeblock?


#6

@tec_support
Thank you for reply. I will try with my scanner cable.
I’ve read pretty much all threads related to connectivity and definitely tried with and without Bluetooth module. The exact same behaviour.

I was wondering if there is a debug log that mBlock writes somewhere that I can see what the actual failure is. In my past life issues with serial always were related to serial port configuration and software/hardware error correction, etc.

mBot is the first robot I got from Makeblock with plan to expand as my son gets a hang how to program it well. Looking forward to a drone if it will be reasonably priced.


#7

@tec_support

Just tried with the cable from my Epson scanner. Exactly the same result… fails, then beens and flashes led in sync with beeping. LED colours seems more or less random.


#8

@tec_support

I’ve tried to flash a small program. While I know that upgraded firmware is required on the board I’m getting the following output on the console when Arduino app is being called to upload it:

`Using Port : /dev/tty.wchusbserial1420
Using Programmer : arduino
Overriding Baud Rate : 115200
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x4c
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x5b
avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0x33
avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0x3b
avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0x8b
avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0xfb
avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0x37
avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0x37
avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0x8f
avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x04

avrdude done. Thank you.`


#9

Hi Surge,

Could you please take a picture for your mBot robot?
Besides, from the picture, I see that you choose the serial port /dev/tty.wchusbserial1420, please check if this is the correct port from mBot? You can disconnect the mBot and see if this serial port will disappear, then plug it back and see if it appear again.


#10

@tec_support

Hello,

just took a photo and also recorded a video from above when I switch on the board, connect to it and try to upload firmware:

2 new photos by Sergei Mutovkin

Regarding the serial driver, I’ve tried all of the drivers (except the commercial) and the result is always the same. Also installed driver from the mBlock IDE on the Windows computer and tried as well. On Windows also tried connecting to various USB ports to check that built-in hub does not affect connectivity. Also tried two different USB cables on Windows and Mac.


#11

Hi Surge,

Thanks for the info.
Could you please add my skype Account (1021306172@qq.com) for better communication and we may arrange a remote access (need use Windows PC) to double check the issue. Our available time is between 9:00 am~6:3 pm on working day.

Besides, have you ever tried use the Arduino software to Upgrade firmware for mBot, if you are not sure how to do that, please download the Arduino software on your Windows PC, we will check it if we can do the remote access.


#12

@tec_support

The store where I got my Robot has fantastic Customer Service - they shipped me a replacement mCore board. So I will check that one as soon as it comes. I will need to arrange use of that Windows laptop as it is not mine.
I’m a Mac/Linux guy, Windows is not my cup of tea (still can’t rehabilitate from the days of amateurs writing their apps in VB 6.0 :grin:).

Regarding Arduino IDE, I have it installed, I was playing earlier this year with Uno based starter kit and programming worked like charm, but didn’t require any drivers. My recommendation is to use slightly more expensive part that does not need drivers to be installed as compared to slightly cheaper chip that does.


#13

Hi Surge,

That’s good to hear, you can test the new mCore board and hope it works.


#14

@tec_support
I just received the new mCore board, connected it and it works great. Was able to upgrade firmware and reset default program. So I guess the original board was damaged in some way.


#15

Hi Surge,

Glad to hear the new board works and thanks for the feedback. Great day!


#16