Why are you trying to flash your Edison with this method instead of using the flashall or the Flash Tool Lite?
The recommended method to flash is using the Flash Tool Lite https://software.intel.com/en-us/articles/flash-tool-lite-user-manual .
For background - what we're trying to do is implement a remote firmware update:
- The Edison receives a notification that a new version of the firmware is available.
- The Edison downloads the new firmware.
- Software on the Edison performs the update by unzipping the firmware, copying it to /update and running reboot ota.
When I run our implementation of this process on my Edison I see the error message "Unable to read file ota_update.scr" when the Edison reboots, and the update doesn't happen.
I am using configure_edison -flashFile to try to troubleshoot the issue because it also performs a firmware update by copying a firmware image to /update and running reboot ota.
Note: If I format the Edison drive from Windows as FAT32, copy the same firmware image to the drive using the Windows file explorer, and then run reboot ota on the Edison, the update succeeds. The issue only seems to occur if the Edison mounts the /update partition and copies the firmware image to it.
Is this the first time you’ve tried to flash your board? The reboot ota command has some limitations in newer images, that’s why the Flash tool Lite is the recommended method to flash the Edison Platform. You can see more information here https://communities.intel.com/docs/DOC-98643 .
Are you trying to flash the latest Edison image or a custom image?
I'm using a custom image that one of my colleagues has successfully used in this scenario.
I have just received a new Edison device which I will test on shortly.
Thanks for following up.
I've received a new Edison to test. Using the same image and processes it works fine. I can successfully use the configure_edison --flashFile command to update the firmware. It also works running an OTA update using our software to download an image and perform a "reboot ota"
We haven't been able to identify what is different between the two Edison devices - they were both flashed with the same image to start with. We'll do some more analysis and let you know if we find anything.
Could it be that the other Edision is failing? Only emmc could fail if at all, but I doubt.....
I've sent the Edison that had the problem to my colleagues in the US (I'm in the UK) for further analysis. It may be a while before they get a chance to look at it, but I will let you know when I hear anything back.
I am really impressed about your sentence :" I've received a new Edison to test. Using the same image and processes it works fine. I can successfully use the configure_edison --flashFile command to update the firmware. It also works running an OTA update using our software to download an image and perform a "reboot ota"".
how you did it ?
my environment is quite different : on Edison I'm triyng ota update using IOT-device-management with the powerful sample : edison_sample.c. (GitHub - Azure/azure-iot-sdks: SDKs for a variety of languages and platforms that help connect devices to Microsoft Azur… )
IOT device management do all "dirty job" for you (receive commands,follow remote job steps, download, and update) , but each image image i supply to IOT DM always says " "not enough space" .
I verify that the .ext4 rootfs (about 1.1 GB ) file is greater than the /update (about 768 mb) partition itself .
I tried build my own image with bitbake with IOT-DM enabled ( azure-iot-sdks/how_to_create_an_image_for_Intel_Edison.md at dmpreview · Azure/azure-iot-sdks · GitHub ) but is always too large.
Also "cleaning" the edison-image.bb it remains too large ( .ext4 rootfs is about 890 MB ).
Did you use a smaller image ? if so, how you built it ?
Did you use bitbake (see the reference I indicate up) ?
Did you ask support from Microsoft IOT developers ?
do you think is still possible develop on Edison ?
I'm continuing to try and try to find affordable solution inside Edison world, but it only confirm to became more and more frustrated to use edison to build a mass market product .
If my boss ask to me about continuing on edison road, althought their size I should say "they are not ready yet" ...
1 of 1 people found this helpful
We're planning to publish a tutorial soon that shows how to build a custom image that includes the IoT-DM service running on an Edison - when it's ready I'll add the link to it here.
Thanks for your interest.
pay attention to build an edison-image withi IOT-DM but... of acceptable size.
in this way we can really test "firmware update" IOT-DM job, otherwise the example is meaningless.
Note: reset to factory default is a problem quite identical.
We are going in production delay, when you plan to publish ?