Unable to recognize USB EFI boot devices in BIOS

[VMeht2]

We are attempting to flash a new build of the intel-aero-image onto our platform, but our BIOS is unable to recognize any flash drive we use.

We've tried both the intel-aero-image release from the Download Center (https://downloadcenter.intel.com/download/26500/UAV-installation-files-for-Intel-Aero-Platform?v=t https://downloadcenter.intel.com/download/26500/UAV-installation-files-for-Intel-Aero-Platform?v=t) and we've tried the latest build from the Jenkins server (http://ec2-52-59-242-235.eu-central-1.compute.amazonaws.com:8080/view/All/builds All [Jenkins]).

We are using a powered USB 3.0 hub and a wired keyboard, and have tried many variations of dd for a few different flash drives (two 3.0, one 2.0). This discussion ( ) also referenced some issues with the BIOS and 3.0 hubs, but we are able to use our keyboard so we don't believe the hub is the problem. We do believe it's a problem in the BIOS, as we are able to mount and view every flash drive we've used when booted into the system.

Any ideas about what we might need to fix, or where we might be erring?

[VMeht2]

Update! Turns out the issue was with dd. After trying on multiple 14.04 Ubuntu computers, we ran the instructions for making a disk image with Windows and it immediately worked.

[idata]

Hi vinaymehta,

Thanks for your interest in the Intel® Aero™ Platform for UAVs.I'm glad to hear that you were able to fix your issue by your own! Please don't hesitate to come back if any questions come up.Have a nice day!Best Regards,-Jose P.

[LuisFelipe_S_Intel]

Can you share the command you were using with dd? It might be that the issue was simply that the system had not completed syncing to the usb drive before you removed it (the dd command will end before the disk is completely written). We will update the wiki to change the command so that this is no longer an issue, thanks for following up.

[VMeht2]

Sure. We tried with block sizes of 1k and of 1M (both were listed somewhere on the Wiki), so commands looked like "sudo dd if=... of=... bs=1k" and "... bs=1M". After that, we ran 'sync' to ensure that dd is finish writing.

[idata]

Hi vinaymetha,

Thanks for sharing this information, it will be really useful for other users experiencing the same issue as you.We appreciate your contribution, have a nice day!Best Regards,-Jose P.