ArneB
Hi DJ & EZ-Robot community,
I have problems updating the firmware on my two EZ-B boards. I have a stable bluetooth connection and started the updater, but on both boards it stucks after these messages:
Attempting connection to COM40
EZ-B reports EZ-B Firmware V2
Connected
Starting Boot Loader...
sending ping
sending ping
sending bootloader
I am EZ-B BootLoader. Gimmie Firmware!
Updating... (22.656 Bytes)
After waiting for more than 5 minutes I have switched off the board and the EZ-B controller boots up with the old V2 firmware. Some more remarks: Batteries are fresh, nothing is connected to the ports. I have even tried a direct connection from my USB->Serial adapter (FTDI chipset) to the RxD/TxD/GND pins on the EZ-B base board, but got the same result... Tested on a Win7/64-Bit and Win XP/32 bit computer...
What can I do now ? Is there anything, which I can test/enable/measure ?
Thank you for your help :-)
Arne
P.S. Yes, I have seen the FW update tutorial...
Great! This diagnosis will help if someone else has the same experience
Hi DJ,
I am still waiting for the debug version...
But it is a relaxed waiting, because in the meantime I have exchanged the Toshiba bluetooth stack in my old Dell laptop with an original Microsoft stack (have a look here how to do it) and now I was able to update my EZ-B !
But I have currently updated only one of my two boards, therefore a debug version of the firmware updater would be very helpful to detect the problem.
Great news
Is the other laptop not microsoft stack? If so there is no debugging that i can do. We cannot support alternative bluetooth stacks. We've tried, but they are far too buggy. The microsoft stack is the only supported and recommended in our documentation
i'm super glad to hear you got it working!
My new laptop doesn't have bluetooth at all, therefore I am using a USB->Serial converter and connected it directly to the EZ-B. It is strange, that this direct connection doesn't work...
That is strange @ArneB.. There are many direct TTL connection robots in the forum that work. Even I have two in the lab, with no issues. I keep thinking there is some driver or utility that is affecting the communication. The firmware utility is speaking to the EZ-B to load the bootloader, but not able to send the firmware. I really think it is the serial logging utility that you have installed. It must have replaced the Serial Driver with it's own buggy one.