Author Topic: How I broke OTA update  (Read 430 times)

millennial

  • Jr. Member
  • **
  • Posts: 76
    • View Profile
How I broke OTA update
« on: August 21, 2016, 11:13:13 pm »
I attempted to update my mc-Gateway Host Processor from v0.7-406 to v0.7-407. I used the latest mc-OTA application release with the "erase mcScript" button. Here is what happened:

1. Found device after clicking "Search"
2. Version information looked reasonably good.
3. Loaded the v0.7-407 host processor bin file and clicked "Start"
4. Got to 100%.
5. Noticed that mc-OTA was searching again for my mc-Gateway. Here is where I may have clicked the wrong buttons...
6. (an aside: I found out after that the mc-Module 110 prompted for a bootloader update) Not sure if mc-OTA prompted here, but I remember fumbling my mouse and clicked the same button twice. Either this was a pop-up, or I clicked "Start" again twice.
7. (The order is fuzzy from my recollection here) I noticed the firmware version said "NA." Uh-oh, I panicked.
8. Tried clicking "Start" with the v0.7-407 bin, but mc-OTA said "this firmware is incompatible with your device." Uh-oh again.
9. Thought to go back to v0.7-406 bin because I still had it on my filesystem. Loaded that file and clicked "Start"
10. mc-OTA said the firmware was not compatible with my device, but offered to continue. I thought "I know for a fact that this is Host Processor firmware." I continued.
11. v0.7-406 update went to 100% completion.
12. mc-OTA did NOT auto search for the device. I manually reset my mc-Gateway and searched many times over maybe 10 minutes. No mc-Gateway found.

I tried connecting to the mc-Gateway in mc-Studio after updating the Application Processor firmware with a flash drive. This was successful and the Application Processor firmware number was updated, but the mcAir version (or similar name) was at v0.7-406. I took this to be acceptable.

I went back to the old mc-OTA updater and still could not connect. I unplugged and re-plugged the mc-Dongle and still had no luck finding my mc-Gateway.

The gateway is still turning on the orange LED proving, I think, that it can connect to the router.


I think I seriously broke my mc-Gateway Host Processor from ever receiving another update. What do I do!?
« Last Edit: August 25, 2016, 01:39:12 pm by millennial »

Share on Facebook Share on Twitter


kristofferis

  • Sr. Member
  • ****
  • Posts: 287
  • Location: Sweden
    • View Profile
Re: How I broke OTA update
« Reply #1 on: August 22, 2016, 03:51:25 am »
I have updated two mcGateways and both time I did get different results, but not as bad as yours.

First mcGateway failed when connecting after upgrading bootloader but I just needed to close and reopen mcOTA and then after reboot I could connect to mcGateway and restart the firmware update and it continued the update procedure.

On the second mcGateway the update was fully automated, just one click and the mcOTA did the job both with bootloader and firmware.

mc-Gyver

  • Global Moderator
  • Newbie
  • *****
  • Posts: 13
    • View Profile
Re: How I broke OTA update
« Reply #2 on: August 22, 2016, 10:16:58 am »
Hi Millennial,

First, we have to check if your device still has a working bootloader.
1. Power down mc-Gateway.
2. Launch mc-OTA (make sure it says "Ready").
3. Click "Search" on mc-OTA.
4. Power up mc-Gateway.

Let us know what you have on the "Device Information" window. Do not worry about "VM Firmware Version:NA" it will be updated later on once the bootloader has been successfully updated.

The bootloader needs to be updated to accommodate new features like the ability to erase a bad mc-Script.

millennial

  • Jr. Member
  • **
  • Posts: 76
    • View Profile
Re: How I broke OTA update
« Reply #3 on: August 22, 2016, 10:47:24 am »
Hi mc-Gyver,

Response to steps:
1. Done
2. Done
3. Done
4. Done

Result: Connection to device failed: Please try again
« Last Edit: August 25, 2016, 01:38:54 pm by millennial »

millennial

  • Jr. Member
  • **
  • Posts: 76
    • View Profile
Re: How I broke OTA update
« Reply #4 on: September 03, 2016, 03:17:47 pm »
Is it possible that clicking "Erase mcScript" during one connection with my mcGateway could have caused the mcGateway to not connect with mc-OTA in my next attempts?