snappy source files

[Swami]

+list, if someone also can help.
I was looking at the dtb file in device tar ball and the boot-assets, which
I used to generate the oem snap file, where both looks exactly same. I am
looking into converting this binary blob into actual dts files, so I can
compare the differences and also if I have to use a different dtb?
What is the procedure if I want to try a new .dtb file, just replacing the
corresponding file name in package.yaml should be enough? or I should
replace it in device tar ball too?

_Swami


On Wed, May 4, 2016 at 5:59 PM, Swami <s.swamyn at gmail.com> wrote:

> Thanks Oliver. It passes the crc issue now. Now, I am stuck at [1]. I am
> using the pi2.moved version to generate the snap, which contains
> bcm2709-rpi-2-b.dtb; the fdt address and device tree blob related info. are
> present in my printenv. But, it throws error as fdt address not configured?
>
> fdt_addr_r=0x00000100
> fdtaddr=f
> fdtfile=bcm2709-rpi-2-b.dtb
> fileaddr=2100000
> filesize=1d68d4
>
>
> [1] http://paste.ubuntu.com/16228908/
>
> _Swami
>
> On Wed, May 4, 2016 at 11:04 AM, Oliver Grawert <ogra at ubuntu.com> wrote:
>
>>
>> hi,
>> Am Mittwoch, 4. Mai 2016 19:15:58 CEST schrieb Swami <s.swamyn at gmail.com
>> >:
>>
>>> Thanks!. Nope, doesn't help. Still stuck at the same place. Copied the
>>> u-boot.cfg from my source at [1]. The size of uboot.env as present in
>>> pi2.moved is 131072 which is 128K and now I have modified the size to
>>> SZ_128K.
>>>
>>> [1] http://paste.ubuntu.com/16221874/
>>>
>>
>> Try setting CONFIG_SYS_REDUNDAND_ENVIRONMENT... That should help.
>>
>> ciao
>>    oli
>>
>>
>>
>> --
>> Mit Dekko von meinem Ubuntu-Gerät gesendet
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snappy-devel/attachments/20160505/76dea7f9/attachment.html>