Unable to generate dsk.xz file

ostroproject / ostro-os

Ostro OS

Other

93 stars 43 forks source link

Unable to generate dsk.xz file #113

Closed js333031 closed 8 years ago

js333031 commented 8 years ago

I used these instructions to try to bitbake my own image with the goal of using bmaptool to flash my Edison.

I modified my conf/local.conf: MACHINE ?= "edison" OSTRO_VM_IMAGE_TYPES = "dsk.xz"

Bitbaked: bitbake -k ostro-image-noswupd

Images show up in tmp-glibc/deploy/images/edison/ but no file with dsk in its filename.

I tried to also use bmaptool on my Ubuntu dev machine, using these these instructions but got following error: bmaptool: ERROR: bmap file not found, please, use --nobmap option to flash without bmap

Above error is shown when using: sudo -E ./bmaptool copy ../images/edison/ostro-image-noswupd-edison.tar.bz2 /dev/sde

kad commented 8 years ago

Unfortunately flashing for platforms like Edison is not possible with bmaptool. Edison uses different image formats and flashing mechanisms than dsk image type.

js333031 commented 8 years ago

Thanks for the quick response.

This needs to be properly documented.

dbkinder commented 8 years ago

So certain combinations of MACHINE and OSTRO_VM_IMAGE_TYPES are not allowed then? And no error message is shown in disallowed cases? Indeed we should document this and update the local.conf.sample too.

The .dsk (and friends) image type only works for intel-corei7-64 and intel-quark MACHINE. What are the available options for Edison and BeagleBone?

kad commented 8 years ago

Both Edison and BeagleBone has their own image type set by corresponding BSP and don't respect OSTRO_VM_IMAGE_TYPES variables.

dbkinder commented 8 years ago

OK. I'm updated the building-images.rst file now...

dbkinder commented 8 years ago

Doc updated in PR #194 (now merged) https://stg.ostroproject.org/documentation/howtos/booting-and-installation.html

@pohly I think this issue can be closed now (documentation updated)