That file should be under tmp/deploy/images and is a result of running "bitbake image-spi-galileo". I guess youu may have run "bitbake image-spi" instead (as earlier BSP Build Guides used) and that generated lzma file with slightly different name.
Thanks AlexT, I believe I entered what it said in the BSP for a full image, bitbake image-full galileo, or something
like that, I dont have the BSP open, but it was to build the full image, I only see the grub directory, bzimage,
the clanton.ext3 file and the initram file, all the right files are there for the sd image, but there is no
lzma file, I will run bitbake image-spi-galileo and see if it creates it, thanks.
yeah - I had same problem - running bitbake image-spi seems to have fixed it in that it creates the desired lzma file
the next thing I noticed is that the spi-flash-tools/Makefile run will choke on the build for sign.c since it does not seem to have the right variables set for the openssl include files and libcrypto.so - I fixed that manually but is there something that I have set up incorrectly here?
Yeah, building a full image (image-full-galileo target) doesn't produce necessary files for creating a firmware package, you need to build an SPI image specifically (image-spi-galileo target).
I had no problems with that. That may be distro-dependant though and sensitive to tools/libraries being "too new" on some. I use OpenSUSE 12.3 without any problems, what's yours?
Charles, please provide more details about the Makefile problem: error message, Linux distribution used, etc.
Sorry - my bad - turns out I did not have openssl libs installed on my system
Ubuntu 12.04.4 LTS x86_64
Ah, okay, openssl dev package is definitely something the build needs to work. Ubuntu 12.04 is tested to work ok with these builds, so from that side you should be fine.