Re: [Xen-devel] Basic bare metal ARM domain interface

2016-06-07 Thread Julien Grall
On 07/06/16 00:31, Ivan Pavic wrote: Hello Julien, Hello Ivan, On Fri, Jun 03, 2016 at 11:23:33AM +0100, Julien Grall wrote: On 02/06/16 20:09, Ivan Pavic wrote: Hello Julien, Hello Ivan, On Thu, Jun 02, 2016 at 12:41:02PM +0100, Julien Grall wrote: Which compiler led to use a dat

Re: [Xen-devel] Basic bare metal ARM domain interface

2016-06-06 Thread Ivan Pavic
Hello Julien, On Fri, Jun 03, 2016 at 11:23:33AM +0100, Julien Grall wrote: > > > On 02/06/16 20:09, Ivan Pavic wrote: > >Hello Julien, > > Hello Ivan, > > >On Thu, Jun 02, 2016 at 12:41:02PM +0100, Julien Grall wrote: > >> > >>Which compiler led to use a data abort? And where was the data > >

Re: [Xen-devel] Basic bare metal ARM domain interface

2016-06-03 Thread Julien Grall
On 02/06/16 20:09, Ivan Pavic wrote: Hello Julien, Hello Ivan, On Thu, Jun 02, 2016 at 12:41:02PM +0100, Julien Grall wrote: Which compiler led to use a data abort? And where was the data abort? In Xen or the guest? When I compile app directly on ODROID I used: arm-linux-gnueabihf gcc

Re: [Xen-devel] Basic bare metal ARM domain interface

2016-06-02 Thread Ivan Pavic
Hello Julien, On Thu, Jun 02, 2016 at 12:41:02PM +0100, Julien Grall wrote: > > Which compiler led to use a data abort? And where was the data > abort? In Xen or the guest? > When I compile app directly on ODROID I used: arm-linux-gnueabihf gcc version 4.8.4 (Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.1

Re: [Xen-devel] Basic bare metal ARM domain interface

2016-06-02 Thread Julien Grall
On 01/06/16 21:06, Ivan Pavic wrote: On Tue, May 31, 2016 at 10:53:06AM +0100, Julien Grall wrote: Hello Julien, Hello Ivan, thank you very much, I succeded with debug console and pin toggle (iomem). It's actually good that you answered late, because it made me look through xen traps.c and

Re: [Xen-devel] Basic bare metal ARM domain interface

2016-06-01 Thread Ivan Pavic
On Tue, May 31, 2016 at 10:53:06AM +0100, Julien Grall wrote: > > > On 30/05/16 21:21, Ivan Pavić2 wrote: > >Hello, > > Hello Ivan, > > Sorry for the late answer. > > >>>I used FreeRTOS code for console output. It is based on Mini OS code. > >>>There are two problems as I've >determined > >>>

Re: [Xen-devel] Basic bare metal ARM domain interface

2016-05-28 Thread Ivan Pavić2
Hello, > I used FreeRTOS code for console output. It is based on Mini OS code. There > are two problems as I've determined > with debugging. First is that vsnprintf blocks for some reason in print > function so i commented it out. After the snprintf blocks... > hypercall function blocked as

Re: [Xen-devel] Basic bare metal ARM domain interface

2016-05-27 Thread Ivan Pavić2
Hello, Jullien, thanks for docs and references. I used FreeRTOS code for console output. It is based on Mini OS code. There are two problems as I've determined with debugging. First is that vsnprintf blocks for some reason in print function so i commented it out. After the hypercall function

Re: [Xen-devel] Basic bare metal ARM domain interface

2016-05-27 Thread Julien Grall
On 25/05/16 20:42, Ivan Pavić2 wrote: Hello, Hello Ivan, I'm working on bare metal application for ARM Cortex A7/15 on Odroid XU3 platform. I'm using Xen 4.6. After successfully creating bare metal example(by successful I mean I've stuck processor in while loop in main function), I probabl

[Xen-devel] Basic bare metal ARM domain interface

2016-05-25 Thread Ivan Pavić2
Hello, I'm working on bare metal application for ARM Cortex A7/15 on Odroid XU3 platform. I'm using Xen 4.6. After successfully creating bare metal example(by successful I mean I've stuck processor in while loop in main function), I probably should initialize memory management unit and similiar