hi,
Am Dienstag, den 21.03.2017, 18:26 +0800 schrieb Madper Xie:
>
> > Yes I noticed that in the README.txt. So I modified the boot cmd to
> `autoboot=bootz ${loadaddr} ${ramdisk_addr}:1c5 ${fdt_addr}` ...
> Still
> doesn't boot.
where does that 1c5 come from ?
please take a look at [1] where we
Hi Ogra,
On Tue, Mar 21, 2017 at 6:20 PM, Oliver Grawert wrote:
> hi,
> Am Dienstag, den 21.03.2017, 18:13 +0800 schrieb Madper Xie:
> > Hi Ogra,
> >
> > After adding the `#define CONFIG_SUPPORT_RAW_INITRD` the uboot still
> > complains `Wrong Ramdisk Image Format Ramdisk image
hi,
Am Dienstag, den 21.03.2017, 11:20 +0100 schrieb Oliver Grawert:
>
> also a look at your boot.env.in
indeed i meant uboot.env.in
:)
ciao
oli
signature.asc
Description: This is a digitally signed message part
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings
hi,
Am Dienstag, den 21.03.2017, 18:13 +0800 schrieb Madper Xie:
> Hi Ogra,
>
> After adding the `#define CONFIG_SUPPORT_RAW_INITRD` the uboot still
> complains `Wrong Ramdisk Image Format Ramdisk image is corrupt or
> invalid`
> ...
>
> Is there any other macros should be defined?
well, your
hi,
On Do, 2017-03-16 at 21:22 +0800, Madper Xie wrote:
> Hi all,
>
> My u-boot do not support the format of the initrd.img. So I need to
> manually convert it via mkimage every time.
>
> I tried to use scriptlet to convert the initrd.img file but failed.
>
> ```
> install: |
>
Hi all,
My u-boot do not support the format of the initrd.img. So I need to
manually convert it via mkimage every time.
I tried to use scriptlet to convert the initrd.img file but failed.
```
install: |
mkimage -n 'RamdiskImage' -A arm -O linux -T ramdisk -C gzip -d
initrd.img