Unable to Update Firmware
Running MetaBase indicated that the firmware was old. I attempted to update and it seems to have failed. When I click on the device in MetaBase I get:
Warning. Your device is in MetaBoot mode....
I've unpowered/repowered the board. Waited for a bunch of time. Attempted the "hardreset" (shorting power).
Nothing has worked.
The Diagnostic page will only let me click on "Update Firmware" "Run Diagnostic" is disabled.
Model: MetaMotion R Number 5
Firmware: 0.2.2
Hardware: 0.2
We're ramping up our project and need to get this resolved and/or obtain addtional devices to prototype with.
Is there a better tool to force a new firmware on this device?
Thanks
Carlton
Comments
When did you buy this device? We are currently on firmware 1.4.4 and yours is on 0.2.2. Did you not update for years?
Correct. It's over a year old as the project we were working on stalled. The project has finally been approved and we're working on a final prototype version of the product. Out of the two MetaMotion boards I have, one failed to update, the other updated fine to 1.4.4. Is there a way to force an update on the board? I'll be ordering more, but wanted this one as it had an external sensor attached to it.
Thanks
Carlton
Try rerunning the firmware update on the metaboot board.
Done so many times. Same issue.
Try with MetaBase on an iOS device
Still no go. Stuck in metaboot. I haven't tried the iOS update w/ a firmware file. Where are these files so I can try manually. Thanks
Use the "nRF Connect" app to upload these files manually, in the exact order listed:
It appears I need special hardware to make nRF Connect work?
" nRF Connect for desktop doesn't use BLE hardware on the computer itself, rather it uses an nRF DK or Dongle for providing BLE capabilities."
Use the mobile version of that app.
I really facing the same situation which is described above when I tried to update the firmware, it shows an error itunes sync error 54, so I really want a solution in this topic as soon as possible.
I'm also having the same issue, on the nRF Connect app I get an error saying "[DFU] Remote DFU error: DATA SIZE EXCEEDS LIMIT" and "Error 8 (0x8): GATT CONN TIMEOUT" followed by the sensor disconnecting. I've tried it many times and on both iOS and android devices, neither work
Using the nRF connect app as discussed in this thread is the solution.
Post reproducible steps.
Post reproducible steps.
Hi Eric,
I have also MetaMotion that has the same issue(stuck in MetaBoot)
My hardware is 0.3, 0.3.2.
I entered these URLs to get files:
http://mbientlab.com/releases/metawear/0.3/5/bootloader/0.3.2/sd_bl.zip - leading to 404
http://mbientlab.com/releases/metawear/0.3/5/bootloader/0.3.2/bl.zip - file OK!
http://mbientlab.com/releases/metawear/0.3/5/vanilla/1.4.4/firmware.zip - file OK!
I guess the SoftDevice file is the same for 0.3.2 and 0.3.1-** correct?**
I upload all of them with successful Android Toast message but the sensor is still on **MetaBoot.
I have also tried short the battery and charge again, still stuck on MetaBoot.
Any other procedure to get it back to normal firmware running?
Thanks,
Nir.
**
>
That is not the file I posted....
Your issue is not the same as the OP and has already been addressed in a previous thread:
https://mbientlab.com/community/discussion/comment/7416
Hi Eric, thanks for quick response.
I already read the previous thread (7416)
I can't find there any real solution.
You just wrote "Try refreshing the gatt services with the nRF connect app" why do you think that it solve?
From my knowledge the issue is inside the bootloader (MetaBoot):
the function "bootloader_app_start" doesn't works or maybe the** address of the application** (DFU_BANK_0) is wrong.
` if (bootloader_app_is_valid(DFU_BANK_0_REGION_START) && !bootloader_dfu_sd_in_progress())
{
// Select a bank region to use as application region.
// @note: Only applications running from DFU_BANK_0_REGION_START is supported.
bootloader_app_start(DFU_BANK_0_REGION_START);
}
what do you think?
Nir.
I posted more than that in that thread. Read it in its entirety, not just the last post.
Maybe, maybe not. Can't confirm either way as we don't have a reliable way to reproduce this issue in the office.
A question for those having this issue with rev 0.3 MMR boards: Is the battery fully charged when updating your board's?
I'm not using the rev 0.3 MMR, I'm using the MetaTracker but I just went out and bought a new battery and was able to DFU from version in the metabase app without any of the previous issues. My old battery read 14% so I didn't think that would've been the issue but turns out it was!
Okay,
So you think that the battery could be issue?
I will try to replace, but as i see in your datasheet after the battery there is voltage regulator of 3v which mean the nRF52 is powered by stable voltage.
Another question, after successful dfu update did you check battery voltage before running the APP and if it low you cancel APP start?
I will appreciate if you could answer this so it make any reason why it stuck.
Thanks,
Nir.
for me yes - the battery was fully charged when i updated my board
I never said to replace the battery.
No, I did not check.
I have a problem. Something bad has happened to my device.
The problem appeared while working on logging data from accelerometer and gyroscope at one time.
Probably the script I created caused an error that I couldn't deal with. The script was written in Python.
I was also using MetaBase application to connect, but currently the device is only detectable from the terminal level with scan_connect.py file.
This is output of the .py file.
Device information: {'model': '4', 'hardware': '0.2', 'manufacturer': 'MbientLab Inc', 'serial': '00D4BD', 'firmware': '0.2.1'}
@jackob96
Firmware 0.2.1? We are on 1.5.5, why is your firmware so low?