Porting Ubuntu-Core

[Woodrow Shen]

Hi Shengyang,

My board also works now, thanks.

On Wed, Feb 15, 2017 at 10:02 AM, Shengyang E <esy at ucrobotics.com> wrote:

> You can look at: https://bugs.launchpad.net/ubuntu-image/+bug/1630769
> We modified the gadget.yaml as follows:
> device-tree: s900-96board.dtb
> volumes:
>   bubblegum96:
>     schema: mbr
>     bootloader: u-boot
>     structure:
>       - name: Bootstrap
>         type: bare
>         size: 6M
>         offset: 2M
>         content:
>           - image: bootloader.bin
>             offset: 512
>           - image: u-boot.bin
>             offset: 1048576
>       - name: system-boot
>         type: 0C
>         filesystem: vfat
>         filesystem-label: system-boot
>         offset: 8388608
>         size: 128M
>         content:
>           - source: boot-assets/
>             target: /
>
> it works.
>
> 2017-02-14 13:04 GMT+08:00 Woodrow Shen <woodrow.shen at canonical.com>:
>
>> Hi all,
>>
>> As I used new ubuntu-image (0.14+real1) to create my armhf image, I also
>> got the same error as well. In order to try to fit the new spec of
>> gadget.yaml, I modified the gadget.yaml as follows:
>>
>> device-tree: actduino_bubble_gum_sdboot_linux.dtb
>> volumes:
>>   roseapple-pi:
>>     schema: mbr
>>     bootloader: u-boot
>>     structure:
>>       - name: bootloader
>>         size: 4M
>>         content:
>>           - image: bootloader.bin
>>             offset: 2097664 #4097*512
>>           - image: u-boot.bin
>>             offset: 3145728 #6144*512
>>         type: bare
>>       - name: system-boot
>>         type: 0C
>>         filesystem: vfat
>>         filesystem-label: system-boot
>>         offset: 8388608
>>         size: 128M
>>         content:
>>           - source: boot-assets/
>>             target: /
>>
>> And then this can avoid above the error during image creation. However,
>> the generated image lost the content of bootloader.bin & u-boot.bin at
>> the specific offset. So I think it may not follow the correct spec of
>> gadget.yaml. Can anyone help us to resolve the problem? Thanks.
>>
>> Regards,
>> Woodrow
>>
>> On Wed, Dec 21, 2016 at 11:15 AM, Bo Dong <bdong at ucrobotics.com> wrote:
>>
>>> Hi Guys,
>>>
>>> We're now porting Ubuntu Core to an ARM64 on-chip computer, Bubblegum-96
>>> board. (http://www.96boards.org/product/bubblegum-96/)
>>> Here are some issues we got.
>>>
>>> When using ubuntu-image (tag:0.10+real 1 stable),
>>>
>>> *$ sudo /snap/bin/ubuntu-image --channel stable --image-size 2G
>>> --extra-snaps bubblegum96-gadget_16.04-1.1_arm64.snap --extra-snaps
>>> bubblegum96-kernel_3.10.0_arm64.snap -o bubblegum96.img bubblegum96.model*
>>>
>>> it could make valid image,bubblegum96.img.
>>>
>>> After update ubuntu-image using command *$ sudo snap refresh --beta
>>> --devmode ubuntu-image*, the ubuntu-image will be updated to beta (tag:
>>> 0.12+real 1). We using command
>>>
>>> $ sudo /snap/bin/ubuntu-image --channel beta --image-size 2G
>>> --extra-snaps bubblegum96-gadget_16.04-1.1_arm64.snap --extra-snaps
>>> bubblegum96-kernel_3.10.0_arm6*4.snap -o bubblegum96.img
>>> bubblegum96.model  *again, and it will report failure. It shows "gadget.yaml
>>> parse error: mbr structures cannot be larger than 446 bytes."
>>>
>>> The gadget.yaml file is the same before and after update ubuntu-image.
>>> Here it is:
>>> $ cat gadget.yaml
>>> device-tree: s900-96board.dtb
>>> volumes:
>>>   lemaker-guitar:
>>>     schema: mbr
>>>     bootloader: u-boot
>>>     structure:
>>>       - name: Bootstrap
>>>         type: mbr
>>>         size: 8M
>>>         content:
>>>           - image: bootloader.bin
>>>             offset: 2097664
>>>           - image: u-boot.bin
>>>             offset: 3145728
>>>       - type: 0C
>>>         filesystem: vfat
>>>         filesystem-label: system-boot
>>>         offset: 8388608
>>>         size: 128M
>>>         content:
>>>           - source: boot-assets/
>>>             target: /
>>>
>>> If we change the size: 8M directly to size:440, the image we made will
>>> be useless. Actually I don't know how to config offset after change the
>>> size.
>>>
>>> If we change the schema: mbr directly to schema: gpt, and change the
>>> type: mbr to type: gpt, it will fail again, and shows "gadget.yaml
>>> parse error: Invalid gadget.yaml @ volumes:lemaker-guitar:structu
>>> re:0:type"
>>>
>>> I'd appreciate it a lot if there is anyone could help us with this.
>>>
>>> Thanks&&Best Regards
>>>
>>>
>>>
>>> --
>>> 董波
>>> uCRobotic
>>> Mobile: +86 15624957162 <+86%20156%202495%207162>
>>>
>>> http://www.ucrobotics.com.cn/
>>>
>>>
>>> --
>>> Snapcraft mailing list
>>> Snapcraft at lists.snapcraft.io
>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>>> an/listinfo/snapcraft
>>>
>>>
>>
>>
>> --
>> Woodrow Shen
>> Software Engineer, Canonical ltd.
>> Devices | CE | Delivery, Taipei
>>
>> --
>> Snapcraft mailing list
>> Snapcraft at lists.snapcraft.io
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> an/listinfo/snapcraft
>>
>>
>
> --
> Snapcraft mailing list
> Snapcraft at lists.snapcraft.io
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/snapcraft
>
>


-- 
Woodrow Shen
Software Engineer, Canonical ltd.
Devices | CE | Delivery, Taipei
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snapcraft/attachments/20170215/846bd6ab/attachment.html>