Re: [Xen-users] [Xen-Users] Issues Booting Dom0 on ARM Cortex A15

[Brandon Perez <a0225893@xxxxxx>]

On 06/17/2015 09:10 AM, Brandon Perez wrote:
> On 06/17/2015 04:44 AM, Ian Campbell wrote:
> > CC-ing Baozi who wrote the OMAP wiki page and may have some insight into
> > issues with similar platforms.
> >
> > http://lists.xen.org/archives/html/xen-users/2015-06/msg00057.html is
> > the root of this thread and
> > http://lists.xen.org/archives/html/xen-users/2015-06/msg00062.html has
> > logs etc, although with a Xen console issue which was subsequently
> > resolved.
> >
> > On Tue, 2015-06-16 at 14:12 -0400, Brandon Perez wrote:
> > >      I resolved the error in my boot.log file with respect to the UART
> > > module, but I'm experiencing the same issue as before.
> > >
> > >      Any tips would be appreicated.
> > Looking at your original log (and assuming fixing the Xen console hasn't
> > changed anything WRT dom0 output) nothing is jumping out at me as
> > suspicious in your logs I'm afraid.
> >
> > One thing which can be useful for debugging is to include in the u-boot
> > script, right before the bootz:
> >          fdt chosen
> >          fdt print /chosen
> > which will log the actual fdt chosen status which Xen will see
> > (different versions of u-boot have different subtly broken ideas about
> > quoting stuff, so e.g. your dom0_bootargs setting might end up wrong
> > despite looking correct in the script).
> >
> > I would also suggest that having fixed your Xen console issue you try
> > the Ctrl-A thing again and try some of the debug keys to see what state
> > dom0 thinks it is in.
> >
> > Ian.
> Here's the output I see from printing out the chosen node (right before
> boot), which seems to look good to me:
>
> chosen {
>          xen,dom0-bootargs = "console=hvc0 earlyprintk=xen debug
> ignore_loglevel root=/dev/mmcblk0p2 rw rootwait fixrtc";
>          xen,xen-bootargs = "sync_console console=dtuart dtuart=serial0";
>          modules {
>                  #address-cells = <0x00000001>;
>                  #size-cells = <0x00000001>;
>                  module@0 {
>                          compatible = "xen,linux-zimage",
> "xen,multiboot-module";
>                          reg = <0xa0000000 0x00a00000>;
>                  };
>          };
> };
>
> I am still unable to get the Xen console up with that key combination.
> For whatever reason, my serial output appears to be working (I can
> printk from anywhere), but my serial input does not seem to be functional.
>
> Brandon
I figured out what the issue was with my serial input. I was using a 
device tree that had the incorrect SPI channel number for the serial 
input interrupt. It was 99, instead of 104, which it should have been 
(in the dts file, it was 67 instead of 72, as the vector numbers are 
offset by 32 due to PPIs).
I was able to get the register dump (using the 'd' command). I've 
attached it.
Brandon

Attachment: reg.dump
Description: Text document

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users