On Wed, Oct 22, 2014 at 11:59:06AM +0200, Gerd Hoffmann wrote:
> syntax error
> ## Error: "catX" not defined
> syntax error
> ## Error: "catX" not defined
> No kernel provides dtb named vexpress-v2p-ca9.dtb
> No value for u_kernel. Getting help.
> [ ... ]
>
> Google finds me this:
>
> https://fe
Hi,
> "if (base < phys_offset)" in early_init_dt_add_memory_arch triggers.
> Seems __pa() isn't working correctly.
>
> Any chance this can be caused by setting some uboot env var incorrectly?
> There is a confusing high number of *_addr_* variables ...
Yep, that was it. Linux kernel wants be
On Di, 2014-10-21 at 20:11 +0100, Peter Maydell wrote:
> On 21 October 2014 19:31, Gerd Hoffmann wrote:
> > Looking them up in System.map finds me:
> >
> > c04eee18 T __loop_delay
> > c0868a28 T panic
> >
> > Ok, so the kernel came successfully though the uncompressing +
> > relocation + enable pa
On 21 October 2014 19:31, Gerd Hoffmann wrote:
> Looking them up in System.map finds me:
>
> c04eee18 T __loop_delay
> c0868a28 T panic
>
> Ok, so the kernel came successfully though the uncompressing +
> relocation + enable paging, but paniced before earlyprintk can print
> something.
>
> Guess I
Hi,
> > Any hints how to go on with debugging?
>
> Use the gdbstub to find out where the kernel is getting
> stuck? "Kernel produces no output" just means "we didn't
> get far enough through early boot for the kernel to start
> sending output to the UART. You might find it useful to
> turn on t
Hi,
> Retrieving file: /dtb-3.16.0-0.rc7.git1.1.fc22.armv7hl/sun7i-a20-bananapi.dtb
> 22335 bytes read in 2312 ms (8.8 KiB/s)
> Kernel image @ 0x4200 [ 0x00 - 0x5a8640 ]
> ## Flattened Device Tree blob at 4300
>Booting using the fdt blob at 0x4300
>Loading Ramdisk to 4e3d
Hi Gerd,
On 10/21/2014 03:33 PM, Gerd Hoffmann wrote:
> Hi,
>
> Played around with u-boot a bit, trying to get it work in qemu, so you
> don't have to hop through loops copying the kernel+initrd from the disk
> image to pass it to qemu on the command line.
>
> Guess why I'm asking here? No so
On 21 October 2014 14:33, Gerd Hoffmann wrote:
> All looks fine, uboot finds the virtual sdcard, loads kernel + initrd,
> passes on the fdt. kernel doesn't boot though, without printing any
> helpful clues to the serial console.
>
> Any ideas what this might be?
Probably we're not emulating some
Hi,
Played around with u-boot a bit, trying to get it work in qemu, so you
don't have to hop through loops copying the kernel+initrd from the disk
image to pass it to qemu on the command line.
Guess why I'm asking here? No so success so far :(
What I did: Started with the fedora uboot-tools
