embeddedxen-devel — EmbeddedXEN development discussions

[Embeddedxen-devel] error for Goldfish - embedded-xen2.0 @ compilation

[Krishna P. <pos...@gm...>]

  AR      arch/arm/lib/lib.a
  CC      lib/bcd.o
  CC      lib/div64.o
  CC      lib/sort.o
  CC      lib/parser.o
  CC      lib/halfmd4.o
  CC      lib/debug_locks.o
  CC      lib/random32.o
  CC      lib/bust_spinlocks.o
  CC      lib/hexdump.o
  CC      lib/kasprintf.o
  CC      lib/bitmap.o
  CC      lib/scatterlist.o
  CC      lib/string_helpers.o
  CC      lib/iomap_copy.o
  CC      lib/devres.o
  CC      lib/hweight.o
  CC      lib/plist.o
  CC      lib/bitrev.o
  HOSTCC  lib/gen_crc32table
  GEN     lib/crc32table.h
  CC      lib/crc32.o
  CC      lib/zlib_deflate/deflate.o
  CC      lib/zlib_deflate/deftree.o
  CC      lib/zlib_deflate/deflate_syms.o
  LD      lib/zlib_deflate/zlib_deflate.o
  LD      lib/zlib_deflate/built-in.o
  CC      lib/zlib_inflate/inffast.o
  CC      lib/zlib_inflate/inflate.o
  CC      lib/zlib_inflate/infutil.o
  CC      lib/zlib_inflate/inftrees.o
  CC      lib/zlib_inflate/inflate_syms.o
  LD      lib/zlib_inflate/zlib_inflate.o
  LD      lib/zlib_inflate/built-in.o
  LD      lib/built-in.o
  CC      lib/argv_split.o
  CC      lib/cmdline.o
  CC      lib/ctype.o
  CC      lib/dec_and_lock.o
  CC      lib/dump_stack.o
  CC      lib/extable.o
  CC      lib/find_last_bit.o
  CC      lib/idr.o
  CC      lib/int_sqrt.o
  CC      lib/ioremap.o
  CC      lib/irq_regs.o
  CC      lib/is_single_threaded.o
  CC      lib/klist.o
  CC      lib/kobject.o
  CC      lib/kobject_uevent.o
  CC      lib/kref.o
  CC      lib/prio_heap.o
  CC      lib/prio_tree.o
  CC      lib/proportions.o
  CC      lib/radix-tree.o
  CC      lib/ratelimit.o
  CC      lib/rbtree.o
  CC      lib/reciprocal_div.o
  CC      lib/rwsem-spinlock.o
  CC      lib/sha1.o
  CC      lib/show_mem.o
  CC      lib/string.o
  CC      lib/vsprintf.o
  AR      lib/lib.a
  LD      vmlinux.o
  MODPOST vmlinux.o
  GEN     .version
  CHK     include/linux/compile.h
  UPD     include/linux/compile.h
  CC      init/version.o
  LD      init/built-in.o
  LD      .tmp_vmlinux1
drivers/built-in.o: In function `events_interrupt':
lowmemorykiller.c:(.text+0x459ec): undefined reference to `xenvfb_interrupt'
drivers/built-in.o: In function `xenvkbd_pass_event':
lowmemorykiller.c:(.text+0x45b7c): undefined reference to `xenvfb_interrupt'
make: *** [.tmp_vmlinux1] Error 1

Re: [Embeddedxen-devel] Is Xenomai Guest OS no longer available?

[Rossier D. <Dan...@he...>]

> -----Original Message-----
> From: Krishna Pavan [mailto:pos...@gm...]
> Sent: lundi 2 avril 2012 09:33
> To: Sam
> Cc: emb...@li...
> Subject: Re: [Embeddedxen-devel] Is Xenomai Guest OS no longer available?
> 
> Hi Sam,
> 
> I read from the above document that Xenomai was a guest OS on top of
> EmbeddedXEN.
> https://lists.sourceforge.net/lists/listinfo/embeddedxen-devel
> 
> I think, xenomai's files are used in many VMMs for ARM, as far as I know.
> They are included in the Source Code, I guess!

Xenomai support was in the initial release of EmbeddedXEN, but since Release 2.0 we
have not kept it anymore; the hypervisor should be reworked out in order to support
(hard) realtime scheduling, but it is not the case yet.

We plan to port Linux/Xenomai (and probably RTEMS) on top of EmbeddedXEN in future projects,
but it is not our priority at the moment. However, if you are interested in such contributions,
please let us know.

Cheers
Daniel

> 
> 
> --
> ✉ Regards :: Krishna Pavan ✍

Re: [Embeddedxen-devel] Is Xenomai Guest OS no longer available?

[Krishna P. <pos...@gm...>]

Hi Sam,


> I read from the above document that Xenomai was a guest OS on top of
> EmbeddedXEN.
> https://lists.sourceforge.net/lists/listinfo/embeddedxen-devel
>
>
I think, xenomai's files are used in many VMMs for ARM, as far as I know.
They are included in the Source Code, I guess!


-- 
✉ Regards :: Krishna Pavan ✍

[Embeddedxen-devel] Is Xenomai Guest OS no longer available?

[Sam <zg...@ya...>]

http://www.embeddedcomputingconference.ch/pdf_2010_download/1B2-Rossier.pdf
 
I read from the above document that Xenomai was a guest OS on top of EmbeddedXEN. But it seems that it is no longer available in the latest 2.0 release. Is it true?
 
Is there a more detailed technical report on the integration of Xenomai as a guest OS besides the PPT document?

[Embeddedxen-devel] How to get to domU from dom0

[Krishna P. <pos...@gm...>]

Hi Thank You,


> From your screenshot it seems that you don't have a kernel but only
> EmbeddedXen.
>
>
Oh ...... I thought I got Kernel also, but it's OK,
My main objective is to break and make. I thought I will get it easily by
that approach.

Since, bootloader on QEMU for certain machine will already be present, I
wanted to test Kernel, Kernel + Xen etc etc.

Xen + linux dom0 + linux domU images together in a single binary uImage. If
> you follow the build instructions you will get a correct image.
>
> I have successfully loaded embedded-xen on qemu, I just wanted to start to
understand how it's made.

For that reason, I have started to pick from roots to make a string.


>
> Qemu terminal session (ctrl-alt-1) and dom0 output and shell in Qemu
> terminal session 3 (ctrl-alt-3).
>
> Yeah! I got it from Rossier Daniel, and I have successfully got a demo.


> > - you don't provide a disk image for the rootfs (-hda
> tools/rootfs/rootfs_v6.img)
>

Hey, you in the sense, If I/You/We provide kernel only and do not provide
rootfs, ..... that was the case.

BTW, I have got all the packages downloaded.

> My aim will be to use Kernel alone.

I don't understand your use case " to use Kernel alone" .


The same break and make, I just wanted to try.


> At some point your kernel will need some user space to jump to... This
> user space can be minimal (e.g busybox shell only) and completely contained
> in a RAM disk but is nevertheless required.
>
>
Oh, that was really very useful information.

I don't understand what you mean with "If you use a lone kernel image
> alone, in ELF format / compressed format, it's not working," if you try to
> boot qemu with a dom0 kernel image alone, it won't work since the kernel
> will lack some initialization and support provided by the hypervisor. You
> should nevertheless be able to boot a standard vanilla kernel image (not
> provided by our project).
>
> Yeah, that vanilla kernel, is somehow responsible for all the other
thoughts, I have had.

lone kernel image of vanilla works, I don't know, If some tweaking has
already been done. I just tried a downloaded one.

As said above, all images xen + dom0 kernel + domU kernel are packed
> together in a single binary which is loaded at startup.
>

Probably, I need to look into the makefile, to know, how it has been done.



> P.S. Please prefer plain text emails without embedded pictures for mailing
> lists.
>

yeah! sure, I will, just attached pics for easy understanding, I will
maximum try to avoid those.



-- 
✉ Thanks & Regards :: Krishna Pavan ✍

[Embeddedxen-devel] FW: How to get to domU from dom0

[Bornet R. <rom...@he...>]

Keep list in the loop...

From: Krishna Pavan [mailto:pos...@gm...] 
Sent: mardi 20 mars 2012 13:53
To: Bornet Romain
Subject: Re: [Embeddedxen-devel] How to get to domU from dom0

Hi Thank You,
 
From your screenshot it seems that you don't have a kernel but only EmbeddedXen.


Oh ...... I thought I got Kernel also, but it's OK,
My main objective is to break and make. I thought I will get it easily by that approach.

Since, bootloader on QEMU for certain machine will already be present, I wanted to test Kernel, Kernel + Xen etc etc. 
Xen + linux dom0 + linux domU images together in a single binary uImage. If you follow the build instructions you will get a correct image.

I have successfully loaded embedded-xen on qemu, I just wanted to start to understand how it's made.

For that reason, I have started to pick from roots to make a string.
 
   
Qemu terminal session (ctrl-alt-1) and dom0 output and shell in Qemu terminal session 3 (ctrl-alt-3).

Yeah! I got it from Rossier Daniel, and I have successfully got a demo. 
 
> - you don't provide a disk image for the rootfs (-hda tools/rootfs/rootfs_v6.img)

Hey, you in the sense, If I/You/We provide kernel only and do not provide rootfs, ..... that was the case.

BTW, I have got all the packages downloaded. 

> My aim will be to use Kernel alone.
I don't understand your use case " to use Kernel alone" .

The same break and make, I just wanted to try.
 
At some point your kernel will need some user space to jump to... This user space can be minimal (e.g busybox shell only) and completely contained in a RAM disk but is nevertheless required.


Oh, that was really very useful information. 
I don't understand what you mean with "If you use a lone kernel image alone, in ELF format / compressed format, it's not working," if you try to boot qemu with a dom0 kernel image alone, it won't work since the kernel will lack some initialization and support provided by the hypervisor. You should nevertheless be able to boot a standard vanilla kernel image (not provided by our project).

Yeah, that vanilla kernel, is somehow responsible for all the other thoughts, I have had.

lone kernel image of vanilla works, I don't know, If some tweaking has already been done. I just tried a downloaded one. 
As said above, all images xen + dom0 kernel + domU kernel are packed together in a single binary which is loaded at startup.

Probably, I need to look into the makefile, to know, how it has been done.

 
P.S. Please prefer plain text emails without embedded pictures for mailing lists.

yeah! sure, I will, just attached pics for easy understanding, I will maximum try to avoid those. 



-- 
✉ Thanks & Regards :: Krishna Pavan ✍

Re: [Embeddedxen-devel] How to get to domU from dom0

[Bornet R. <rom...@he...>]

Hi,

--- Original Message ---
> From: Krishna Pavan [mailto:pos...@gm...] 
> Sent: mardi 20 mars 2012 11:58
> To: Bornet Romain
> Cc: Rossier Daniel; emb...@li...
> Subject: Re: [Embeddedxen-devel] How to get to domU from dom0
> 
> Hi,
> 
> Thank You Bornet Romain,
> 
> It was a mistake completely on my part.
> I should have checked with the Serial Console Output also.
> 
> Here's the pic, where the Kernel+Xen boots up ( and waits for FileSystem I guess)
> I would like to know, 

From your screenshot it seems that you don't have a kernel but only EmbeddedXen.

> How uImage has to be packed with Xen together?

Our build system automatically packages the Xen + linux dom0 + linux domU images together in a single binary uImage. If you follow the build instructions you will get a correct image.

> How that image can be loaded on QEMU-for-ARM, so that it starts booting and show all that initialisation text, as it would do, if run on a actual board?
By building the image as documented and starting Qemu with our scripts you will get domU output and shell in the first Qemu terminal session (ctrl-alt-1) and dom0 output and shell in Qemu terminal session 3 (ctrl-alt-3).

> - you don't provide a disk image for the rootfs (-hda tools/rootfs/rootfs_v6.img)

Yes we provide a rootfs image. Apparently you didn't download and install all the necessary files (3 tar.gz archives in total).
Please refer to the Getting Started page (https://sourceforge.net/apps/mediawiki/embeddedxen/index.php?title=Quick_Start_Guide) for more information regarding environment setup and Qemu startup commands.

> My aim will be to use Kernel alone.

I don't understand your use case " to use Kernel alone" . At some point your kernel will need some user space to jump to... This user space can be minimal (e.g busybox shell only) and completely contained in a RAM disk but is nevertheless required.

> Somehow, If you use a lone kernel image alone, in ELF format / compressed format, it's not working, I mean other images [ embedded-xen works 100% ]. 

I don't understand what you mean with "If you use a lone kernel image alone, in ELF format / compressed format, it's not working," if you try to boot qemu with a dom0 kernel image alone, it won't work since the kernel will lack some initialization and support provided by the hypervisor. You should nevertheless be able to boot a standard vanilla kernel image (not provided by our project).

> But embedded-xen uImage is working.
> Somework has to be done to make it so, I guess,

As said above, all images xen + dom0 kernel + domU kernel are packed together in a single binary which is loaded at startup.

> I am trying and would be interested to know, how could that be made.
> 
> If known,
> 
> Please tell me what needs to be done?
> 
> -- 
> ? Regards :: Krishna Pavan ?

Hope this helps,
    Romain

P.S. Please prefer plain text emails without embedded pictures for mailing lists. It has more chances to show up correctly in every email client and is easier to quote, reply and forward.

Re: [Embeddedxen-devel] How to get to domU from dom0

[Bornet R. <rom...@he...>]

Hi Krishna and list,

--- Original Message ---
> From: Krishna Pavan [mailto:pos...@gm...] 
> Sent: mardi 20 mars 2012 10:14
> To: Rossier Daniel
> Cc: emb...@li...
> Subject: Re: [Embeddedxen-devel] How to get to domU from dom0
> 
> Thank You Embedded-Xen-Devel & Rossier,
> 
> I would like to know
> -pflash file  -->  use 'file' as a parallel flash image flash1 & flash2 are used.
> 1. Are they some kind of BIOS? related to that of linux & colibri?

The Qemu -pflash option can be used to boot an emulated system from an emulated flash (NAND/NOR) device. Qemu needs to be patched for supporting this option and our current version in EmbeddedXen tree is not already patched for this support. We currently boot from an emulated harddisk interface (-had Qemu option).

To be short, you can ignore these options and remove them from the Qemu command-line. It is a remaining of older project in our scripts and we will remove them from the distributed scripts to not confuse the user.

> 2. If need to run either kernel alone on QEMU-for-ARM, If it's Embedded Xen or other, Will it be possible by supplying a zImage/uImage/vmlinux[ELF]?
> I have been experiencing and trying to run the uImage.embeddedxen.versatilev6 alone like this, I get a blankscreen and nothing else....
>
> Screenshot is here 
> 
> Please Suggest !

Please use the provided startup scripts at the root of the EmbeddedXen tree (stv6h script in your case). You will thus have all necessary Qemu options configured correctly.

In your example, there are some errors / missing options compared to what we use in our scripts
- memory size is set to 128MB in your command line (-m 128) where we use 256MB
- you don't provide a disk image for the rootfs (-hda tools/rootfs/rootfs_v6.img)

Hope this helps
    Romain

Re: [Embeddedxen-devel] How to get to domU from dom0

[Rossier D. <Dan...@he...>]

> -----Original Message-----
> From: Rossier Daniel [mailto:Dan...@he...]
> Sent: lundi 19 mars 2012 15:36
> To: Krishna Pavan; emb...@li...
> Subject: Re: [Embeddedxen-devel] How to get to domU from dom0
> 
> > -----Original Message-----
> > From: Krishna Pavan [mailto:pos...@gm...]
> > Sent: lundi 19 mars 2012 15:10
> > To: emb...@li...
> > Subject: [Embeddedxen-devel] How to get to domU from dom0
> >
> > Hi,
> >
> > tools/qemu-1.0-reds/arm-softmmu/qemu-system-arm -s -localtime -M
> > versatilepb -cpu arm1136 -kernel uImage.embeddedxen.versatilev6
> > -pflash
> > tools/resources/flash1 -pflash tools/resources/flash2 -m 256 -hda
> > tools/rootfs/rootfs_v6.img
> >
> > from stv6h
> 
> The image "uImage.embeddedxen.versatilev6" actually contains all the
> necessary binary including hypervisor, dom0 and domU.
> 
> > But, How to move from domU from dom0 ?
> 
> Easy, on the emulated framebuffer (qemu: ctrl+alt+1), you get what is
> happening on domU. On the serial console, (ctrl+alt+3) you have all the dom0
> activities. This is how it works today on qemu; on HTC, a simple touch on the
> "magnifier" virtual key performs the switch between the two domains.

Just to make things clear: switch between the two domains mean switching the screen/focus.
The two domains are obviously scheduled continuously and therefore run (nearly) simultaneously.

> 
> Cheers
> Daniel
> 
> >
> > I have searched docs, but
> >
> > Is it that I have missed any docs in the packages?
> >
> >
> > Please Suggest!
> > --
> > ✉ Regards :: Krishna Pavan ✍
> 
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-
> msazure _______________________________________________
> Embeddedxen-devel mailing list
> Emb...@li...
> https://lists.sourceforge.net/lists/listinfo/embeddedxen-devel

Re: [Embeddedxen-devel] How to get to domU from dom0

[Rossier D. <Dan...@he...>]

> -----Original Message-----
> From: Krishna Pavan [mailto:pos...@gm...]
> Sent: lundi 19 mars 2012 15:10
> To: emb...@li...
> Subject: [Embeddedxen-devel] How to get to domU from dom0
> 
> Hi,
> 
> tools/qemu-1.0-reds/arm-softmmu/qemu-system-arm -s -localtime -M
> versatilepb -cpu arm1136 -kernel uImage.embeddedxen.versatilev6 -pflash
> tools/resources/flash1 -pflash tools/resources/flash2 -m 256 -hda
> tools/rootfs/rootfs_v6.img
> 
> from stv6h

The image "uImage.embeddedxen.versatilev6" actually contains all the necessary binary including
hypervisor, dom0 and domU. 

> But, How to move from domU from dom0 ?

Easy, on the emulated framebuffer (qemu: ctrl+alt+1), you get what is happening on domU. On the serial console, (ctrl+alt+3) you have all the dom0 activities. This is how it works today on qemu; on HTC, a simple touch on the "magnifier" virtual key performs the switch between the two domains.

Cheers
Daniel

> 
> I have searched docs, but
> 
> Is it that I have missed any docs in the packages?
> 
> 
> Please Suggest!
> --
> ✉ Regards :: Krishna Pavan ✍

[Embeddedxen-devel] How to get to domU from dom0

[Krishna P. <pos...@gm...>]

Hi,

tools/qemu-1.0-reds/arm-softmmu/qemu-system-arm -s -localtime -M
versatilepb -cpu arm1136 -kernel uImage.embeddedxen.versatilev6 -pflash
tools/resources/flash1 -pflash tools/resources/flash2 -m 256 -hda
tools/rootfs/rootfs_v6.img

from stv6h

But, How to move from domU from dom0 ?

I have searched docs, but

Is it that I have missed any docs in the packages?


Please Suggest!
-- 
✉ Regards :: Krishna Pavan ✍

Re: [Embeddedxen-devel] Regarding Embedded Xen 2.0 Compilation.

[Rossier D. <Dan...@he...>]

Hi Krishna,

Please use the official embeddedxen-devel mailing list to post your requests.

Are you sure you downloaded everything? (not only the _base, but also the other images?)
Please go here: https://sourceforge.net/projects/embeddedxen/files/embeddedxen-2.0/
and download/extract all files. Then, you launch the command again.

Cheers
Daniel

From: Krishna Pavan [mailto:pos...@gm...]
Sent: lundi 19 mars 2012 12:48
To: Rossier Daniel
Subject: Regarding Embedded Xen 2.0 Compilation.

Hi Daniel Rossier,

I have worked on the two previous Embedded Xen Versions.
This 2.0 is what I need to try.

Now, I have compilation errors here.

make PLATFORM=versatilev6 DOMAINS="linux-2.6.26-dom0 fab4:linux-2.6.26-domU"
make: *** [versatilev6.linux-2.6.26-dom0/vmlinux] Error 1

My Doubts is

Where is the source_code for linux? Do we have to download and place the configs you have provided in the directories?


--
✉ Regards :: Krishna Pavan ✍

Re: [Embeddedxen-devel] HTC Desire configuration files

[Hector M. <hec...@gm...>]

Hi Romain,

Thanks for your help!

So, will be a good starting to have some prints in the real device, for
me could be enough.
I suppose that you are referring to:


/* We initialise the serial device(s) very early so we can get debugging. */
    arch_console_init();

in 'xen/arch/arm/kernel/setup.c' , isn't it ?

Because when you call "serial_init_preirq()" you are using "printk".

At this point works in real device for HTC Desire ?
Do you have any configuration for dom0 and xen ?

Would be nice start in some point like this.

Thanks in advance.
Hector.





El 11/03/12 23:03, Bornet Romain escribió:
> Hi Hector,
>
> Sorry for the late answer. I'll try to answer all your questions with as much details as possible.
>
> ________________________________
> From: Hector Marco [hec...@gm...]
> Sent: Friday, March 09, 2012 11:05 AM
> To: Bornet Romain
> Subject: Re: [Embeddedxen-devel] HTC Desire configuration files
>
>>> Hi Romain,
>>> Yes, I am interested in porting embeddedxen 2.0 to HTC Desire,
>>> because I have a real HTC Desire device.
>>> But I don't understand the followin:
>>> 1) I need to compare dom0 kernel but what about XEN ?
>>>    One thing is port XEN hypervisor, and other is port Dom0 , isn't it ?
>>>    I have seen in hypervisor-4.0.2/arch/arm/mach-msm "board-bravo.c" but
>>>    ¿ XEN is ready for HTC desire already ?
> Yes you are right when saying that supporting a new platform involves 2 parts, dom0 and XEN.
> We had at some time in the project a basic, experimental support for HTC Desire within Xen and it is the reason why you see a board-bravo.c file in the source tree. Unfortunately, we did not maintain further this port further when we switched over to HTC Desire HD. You should nevertheless be able to update the support for HTC Desire based on the existing board-bravo.c and on the board-spade.c used for the Desire HD.
>
>>> 2) How can I do debugging ?
>>>    If XEN is not ready for HTC_Desire How I could be do the debugging ?
> Debugging is always difficult on such devices. When developing for HTC Desire or Desire HD, we had to "tinker" some direct access to the framebuffer to print out some debug messages but we never got a proper debugging infrastructure. It is often a problem when developing on consumer market devices.
>
>>> I found the following:
>>> Jtag (http://www.multi-com.pl/index.php/en_US,details,id_pr,7883,menu_mode,categories.html)
>>> Module for HTC desire (http://www.multi-com.pl/index.php/en_US,details,id_pr,8149,menu_mode,categories.html)
>>> But, I prefer don't open the device.
> For our work on HTC Desire and Desire HD, we never worked with JTAG on-chip debuggers. It would have been nice and would have spare us much debugging time but, at that time, we did not find a suitable solution. Your JTAG probe and module sound interesting but I cannot say much on it since I never used them.
>
>>> The other option that I found is to use a board.
> This would be in fact the best option. Having a development board with open connectors, debug interfaces is always nice to work with.
>
>>> The only two board that I found in that link
>>> (http://www.bsquare.com/dragonboard.aspx) for chipset MSM were:
>>> - MSM8655T-based Snapdragon
>>> - Qualcomm Snapdragon MSM8660TM-based
>>> Neither are for:
>>> - HTC desire (Qualcomm QSD8250 Snapdragon)
>>> - HTC Desire S (Qualcomm MSM8255 Snapdragon)
>>> - HTC desire HD (Qualcomm MSM8255 Snapdragon)
>>> - HTC sensation (Qualcomm MSM8260 Snapdragon)
>>> - HTC Sentation XL. (Qualcomm MSM8255)
> Right, there is no development board (at least publicly available) for the particular processors found on the HTC devices you mentioned. In our lab we recently bought a Dragonboard (http://www.bsquare.com/dragonboard.aspx) with an APQ8060 dual-core chip. We plan to port EmbeddedXen to this platform and to add some new features in the future but we still don't have any precise roadmap for this.
>
>>> I tried the old configuration for HTC Desire whit the new relase embeddedxen2.0
>>> but nothing is shown, just the first screen white with HTC green letters.
>>> How Could I see the XEN output ?
> As said above, we cannot see XEN output directly on HTC phones. With some basic framebuffer driver, we were able to print out some messages but nothing more. And this only in the early boot stage, before Android gets initialized and uses the framebuffer itself.
>
>>> I compiled the original kernel (without XEN) for HTC desire activating ttyMSM2 but
>>> not worked. ( http://code.google.com/p/android-serialport-api/wiki/Htc) and  I
>>> think is not the best way because the UART need to be up and for HTC devices
>>> is in Untested devices list.
> We also tried to get a serial console on the devices but did not invest much time in this since we did not find how to correctly activate it on the Desire/Desire HD + it seems to require some special cable with level shifters, tinkered USB connector,...
>
>>> So first I think I need a way to do a good debugging.
> And I'm afraid that there is no way to do *good* debugging on these devices at a such low level. But I perhaps missed something at that time ?
>
>>> In conclusion I am a bit lost :)
>>> Thanks in advance.
>>> Hector.
> Regards,
>      Romain
>
> El 08/03/12 22:37, Bornet Romain escribió:
>
> Hi Hector,
>
>
>
> ________________________________________
> From: Hector Marco [hec...@gm...<mailto:hec...@gm...>]
> Sent: Thursday, March 08, 2012 2:59 PM
> To: emb...@li...<mailto:emb...@li...>
> Subject: [Embeddedxen-devel] HTC Desire configuration files
>
>
> Hi everyone,
>
>
> Congratulations for the new release!
> Currently I have an HTC Desire (not HD).
> Do you have any configuration for XEN or Linux for HTC Desire ?
>
>
> The latest release does not include out-of-the-box support for HTC Desire but we started the development on such devices before switching to Desire HD. We did not maintain the port on the the HTC Desire but it should be rather easy to have the latest EmbeddedXen and a dom0 running again on Desire.
> Our paravitualized dom0 kernel was based on the 2.6.29 kernel for HTC Desire available from HTC.
>
> If you are interested in porting EmbeddedXen 2.0 to Desire, the best way is to compare the 2.6.32-dom0 tree for Desire HD with the original kernel sources and apply similar changes to the 2.6.29 or 2.6.32 kernel sources for Desire. If you go this way, don't hesitate to ask for help on the list since we already know a bit on this device from our earlier experience.
>
> A few links to useful reference kernel sources:
> Desire HD original sources from HTC: http://dl4.htc.com/RomCode/Source_and_Binaries/ace_2.6.32_g5ed1769.tar.gz
> Desire 2.6.29 original sources from HTC: http://dl4.htc.com/RomCode/Source_and_Binaries/bravo_54b7033a.tar.gz
> Desire 2.6.32 original sources from HTC: http://dl4.htc.com/RomCode/Source_and_Binaries/bravo-2.6.32-gd96f2c0.tar.gz
>
>
>
> Thanks in advance.
> Hector.
>
>
> Have fun with EmbeddedXen !
>     Romain
>

Re: [Embeddedxen-devel] HTC Desire configuration files

[Bornet R. <rom...@he...>]

Hi Hector,

Sorry for the late answer. I'll try to answer all your questions with as much details as possible.

________________________________
From: Hector Marco [hec...@gm...]
Sent: Friday, March 09, 2012 11:05 AM
To: Bornet Romain
Subject: Re: [Embeddedxen-devel] HTC Desire configuration files

>> Hi Romain,

>> Yes, I am interested in porting embeddedxen 2.0 to HTC Desire,
>> because I have a real HTC Desire device.

>> But I don't understand the followin:

>> 1) I need to compare dom0 kernel but what about XEN ?
>>    One thing is port XEN hypervisor, and other is port Dom0 , isn't it ?
>>    I have seen in hypervisor-4.0.2/arch/arm/mach-msm "board-bravo.c" but
>>    ¿ XEN is ready for HTC desire already ?

Yes you are right when saying that supporting a new platform involves 2 parts, dom0 and XEN.
We had at some time in the project a basic, experimental support for HTC Desire within Xen and it is the reason why you see a board-bravo.c file in the source tree. Unfortunately, we did not maintain further this port further when we switched over to HTC Desire HD. You should nevertheless be able to update the support for HTC Desire based on the existing board-bravo.c and on the board-spade.c used for the Desire HD.

>> 2) How can I do debugging ?
>>    If XEN is not ready for HTC_Desire How I could be do the debugging ?

Debugging is always difficult on such devices. When developing for HTC Desire or Desire HD, we had to "tinker" some direct access to the framebuffer to print out some debug messages but we never got a proper debugging infrastructure. It is often a problem when developing on consumer market devices.

>> I found the following:

>> Jtag (http://www.multi-com.pl/index.php/en_US,details,id_pr,7883,menu_mode,categories.html)
>>Module for HTC desire (http://www.multi-com.pl/index.php/en_US,details,id_pr,8149,menu_mode,categories.html)
>> But, I prefer don't open the device.

For our work on HTC Desire and Desire HD, we never worked with JTAG on-chip debuggers. It would have been nice and would have spare us much debugging time but, at that time, we did not find a suitable solution. Your JTAG probe and module sound interesting but I cannot say much on it since I never used them.

>> The other option that I found is to use a board.

This would be in fact the best option. Having a development board with open connectors, debug interfaces is always nice to work with.

>> The only two board that I found in that link
>> (http://www.bsquare.com/dragonboard.aspx) for chipset MSM were:
>> - MSM8655T-based Snapdragon
>> - Qualcomm Snapdragon MSM8660TM-based
>> Neither are for:
>> - HTC desire (Qualcomm QSD8250 Snapdragon)
>> - HTC Desire S (Qualcomm MSM8255 Snapdragon)
>> - HTC desire HD (Qualcomm MSM8255 Snapdragon)
>> - HTC sensation (Qualcomm MSM8260 Snapdragon)
>> - HTC Sentation XL. (Qualcomm MSM8255)

Right, there is no development board (at least publicly available) for the particular processors found on the HTC devices you mentioned. In our lab we recently bought a Dragonboard (http://www.bsquare.com/dragonboard.aspx) with an APQ8060 dual-core chip. We plan to port EmbeddedXen to this platform and to add some new features in the future but we still don't have any precise roadmap for this.

>> I tried the old configuration for HTC Desire whit the new relase embeddedxen2.0
>> but nothing is shown, just the first screen white with HTC green letters.
>> How Could I see the XEN output ?
As said above, we cannot see XEN output directly on HTC phones. With some basic framebuffer driver, we were able to print out some messages but nothing more. And this only in the early boot stage, before Android gets initialized and uses the framebuffer itself.

>> I compiled the original kernel (without XEN) for HTC desire activating ttyMSM2 but
>> not worked. ( http://code.google.com/p/android-serialport-api/wiki/Htc) and  I
>> think is not the best way because the UART need to be up and for HTC devices
>> is in Untested devices list.

We also tried to get a serial console on the devices but did not invest much time in this since we did not find how to correctly activate it on the Desire/Desire HD + it seems to require some special cable with level shifters, tinkered USB connector,...

>> So first I think I need a way to do a good debugging.
And I'm afraid that there is no way to do *good* debugging on these devices at a such low level. But I perhaps missed something at that time ?

>>In conclusion I am a bit lost :)
>> Thanks in advance.
>>Hector.

Regards,
     Romain

El 08/03/12 22:37, Bornet Romain escribió:

Hi Hector,



________________________________________
From: Hector Marco [hec...@gm...<mailto:hec...@gm...>]
Sent: Thursday, March 08, 2012 2:59 PM
To: emb...@li...<mailto:emb...@li...>
Subject: [Embeddedxen-devel] HTC Desire configuration files


Hi everyone,


Congratulations for the new release!
Currently I have an HTC Desire (not HD).
Do you have any configuration for XEN or Linux for HTC Desire ?


The latest release does not include out-of-the-box support for HTC Desire but we started the development on such devices before switching to Desire HD. We did not maintain the port on the the HTC Desire but it should be rather easy to have the latest EmbeddedXen and a dom0 running again on Desire.
Our paravitualized dom0 kernel was based on the 2.6.29 kernel for HTC Desire available from HTC.

If you are interested in porting EmbeddedXen 2.0 to Desire, the best way is to compare the 2.6.32-dom0 tree for Desire HD with the original kernel sources and apply similar changes to the 2.6.29 or 2.6.32 kernel sources for Desire. If you go this way, don't hesitate to ask for help on the list since we already know a bit on this device from our earlier experience.

A few links to useful reference kernel sources:
Desire HD original sources from HTC: http://dl4.htc.com/RomCode/Source_and_Binaries/ace_2.6.32_g5ed1769.tar.gz
Desire 2.6.29 original sources from HTC: http://dl4.htc.com/RomCode/Source_and_Binaries/bravo_54b7033a.tar.gz
Desire 2.6.32 original sources from HTC: http://dl4.htc.com/RomCode/Source_and_Binaries/bravo-2.6.32-gd96f2c0.tar.gz



Thanks in advance.
Hector.


Have fun with EmbeddedXen !
    Romain

[Embeddedxen-devel] Tr. : HTC Desire configuration files

[Bornet R. <rom...@he...>]

Hi Hector,

>________________________________________
> From: Hector Marco [hec...@gm...]
> Sent: Thursday, March 08, 2012 2:59 PM
> To: emb...@li...
> Subject: [Embeddedxen-devel] HTC Desire configuration files


> Hi everyone,

> Congratulations for the new release!
> Currently I have an HTC Desire (not HD).
> Do you have any configuration for XEN or Linux for HTC Desire ?

The latest release does not include out-of-the-box support for HTC Desire but we started the development on such devices before switching to Desire HD. We did not maintain the port on the the HTC Desire but it should be rather easy to have the latest EmbeddedXen and a dom0 running again on Desire.

Our paravitualized dom0 kernel was based on the 2.6.29 kernel for HTC Desire available from HTC.

If you are interested in porting EmbeddedXen 2.0 to Desire, the best way is to compare the 2.6.32-dom0 tree for Desire HD with the original kernel sources and apply similar changes to the 2.6.29 or 2.6.32 kernel sources for Desire. If you go this way, don't hesitate to ask for help on the list since we already know a bit on this device from our earlier experience.

A few links to useful reference kernel sources:

Desire HD original sources from HTC: http://dl4.htc.com/RomCode/Source_and_Binaries/ace_2.6.32_g5ed1769.tar.gz

Desire 2.6.29 original sources from HTC: http://dl4.htc.com/RomCode/Source_and_Binaries/bravo_54b7033a.tar.gz

Desire 2.6.32 original sources from HTC: http://dl4.htc.com/RomCode/Source_and_Binaries/bravo-2.6.32-gd96f2c0.tar.gz


> Thanks in advance.
> Hector.

Have fun with EmbeddedXen !
    Romain

[Embeddedxen-devel] HTC Desire configuration files

[Hector M. <hec...@gm...>]

Hi everyone,

Congratulations for the new release!
Currently I have an HTC Desire (not HD).
Do you have any configuration for XEN or Linux for HTC Desire ?



Thanks in advance.
Hector.

Re: [Embeddedxen-devel] Error in building Embedded Xen 2.0

[Rossier D. <Dan...@he...>]

Hi Vibi,

> -----Original Message-----
> From: vibi sreenivasan [mailto:mai...@gm...]
> Sent: lundi 5 mars 2012 19:38
> To: Rossier Daniel
> Cc: xe...@li...
> Subject: Error in building Embedded Xen 2.0
> 
> Hi,
> i downloaded the package embeddedxen-2.0-base.tar.gz & tried to compile
> it according to the README in side the package.
> I extracted the toolchain & added it to the PATH environment variable.
> 
> make PLATFORM=versatilev6 DOMAINS="linux-2.6.26-dom0 fab4:linux-
> 2.6.26-domU"
> make: *** [versatilev6.linux-2.6.26-dom0/vmlinux] Error 1

Well, according to your make, you are actually building two domains (dom0 & domU).
However, the embeddedxen-2.0-base.tar.gz only contains the hypervisor and basic config files.
To compile the two guest domains, you still need to download embeddexen-2.0-single-dom0.tar.gz (for dom0),
and embeddedxen-2.0.domU.tar.gz, and extract them the same way you did for the base tar.gz.
You will then get the missing files.


> Am i missing something ? Is there any other procedure to compile ?

Please let me know if it works.

Cheers
Daniel


> 
> regards
> vibi
> 
> On Fri, Mar 2, 2012 at 12:33 PM, Rossier Daniel <Dan...@he...>
> wrote:
> > Hello,
> >
> > We are proud to announce the release 2.0 of EmbeddedXEN !
> >
> > https://sourceforge.net/projects/embeddedxen/
> >
> >
> > This is the first official release of EmbeddedXEN based upon a new
> > revisited architecture (hence release 2).
> >
> > We are on the process of documenting the architecture (wiki,
> > publication, etc.).
> >
> > EmbeddedXEN supports two guest OSes (dom0 and domU). Further
> technical
> > details ils about EmbeddedXEN will come up soon through various
> > publications including a dedicated Wiki.
> >
> > EmbeddedXEN is continuously evolving; we have still some issues
> > regarding the networking,
> >
> > but a fully functional version will be released in the upcoming weeks.
> >
> > As a first release including a domU, we packaged the SqueezeOS (with
> > its
> > application) running on
> >
> > a Linux 2.6.26 in order to show the possibility of EmbeddedXEN.
> > SqueezeOS is running on Logitech SBTouch device,
> >
> > and no modifications in the rootfs have been done. You can run
> > SqueezePlay in emulation or even on HTC !
> >
> > Currently supported are:
> >
> > - Linux-2.6.26-dom0 on QEMU/versatilev6 (ARM-11)
> > - Linux-2.6.29-dom0 on QEMU/goldfish (Cortex-A8/ARMv7)
> > - Linux-2.6.32-dom0 on HTC Desire HD(Snapdragon/ARMv7)
> > - Linux-2.6.26-domU which is our para-virtualized version of SqueezeOS
> >
> > Hardware virtualization of the following devices is supported:
> >
> > UART, console, framebuffer, keyboard, touchscreen, block device,
> > audio, and networking (in a couple of days/weeks).
> >
> > Different packages are available (base, single-dom0, domU,
> > others-dom0) according the environment you target.
> >
> > As usual, a very good thing would be to use clone the git repository
> > in order to stay in touch
> >
> > with the very last changes. Contributions, new ideas, bugs tracking
> > are also very welcome :-)
> >
> >
> >
> > Further details about architecture and internals of EmbeddedXEN will
> > follow soon.
> >
> > Have a nice time with EmbeddedXEN 2.0 !
> >
> > Cheers
> > Daniel
> >
> >
> >
> >
> > _______________________________________________
> > Xen-arm mailing list
> > Xe...@li...
> > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm
> >

[Embeddedxen-devel] EmbeddedXEN 2.0 available !

[Rossier D. <Dan...@he...>]

Hello,

We are proud to announce the release 2.0 of EmbeddedXEN !

This is the first official release of EmbeddedXEN based upon a new revisite=
d architecture (hence release 2).

EmbeddedXEN supports two guest OSes (dom0 and domU). Further technical deta=
ils about EmbeddedXEN will come up soon through various publications includ=
ing a dedicated Wiki.

EmbeddedXEN is continuously evolving; we have still some issues regarding t=
he networking, but a fully functional version will be released in the upcom=
ing weeks.

As a first release including a domU, we packaged the SqueezeOS (with its ap=
plication) running on a Linux 2.6.26 in order to show the possibility of Em=
beddedXEN. SqueezeOS is running on Logitech SBTouch device, and no modifica=
tions in the rootfs have been done. You can run SqueezePlay in emulation or=
 even on HTC !

Currently supported are:

- Linux-2.6.26-dom0 on QEMU/versatilev6 (ARM-11)
- Linux-2.6.29-dom0 on QEMU/goldfish (Cortex-A8/ARMv7)
- Linux-2.6.32-dom0 on HTC Desire HD(Snapdragon/ARMv7)
- Linux-2.6.26-domU which is our para-virtualized version of SqueezeOS

Hardware virtualization of the following devices is supported:

UART, console, framebuffer, keyboard, touchscreen, block device, audio, and=
 networking (in a couple of days/weeks).

Do not hesitate to download all files and have a look at the different flav=
ours.

As usual, a very good thing would be to use clone the git repository in ord=
er to stay in touch with the very last changes. Contributions, new ideas, b=
ugs tracking are also very welcome :-) If you have such interest, please do=
 not hesitate !

Have a nice time with EmbeddedXEN 2.0 !

Cheers
Daniel

Re: [Embeddedxen-devel] Question about debugging.

[Rossier D. <Dan...@he...>]

Hi Marco,

We are working hard to release a new version of EmbeddedXEN by end of this month; you will have the virtualization on HTC ready at this time. But for the time being, there is no working version on EmbeddedXEN sourceforge. Please be patient and stay tuned.

Cheers
Daniel

> -----Original Message-----
> From: Hector Marco [mailto:hec...@up...]
> Sent: lundi 20 février 2012 14:23
> To: emb...@li...
> Subject: [Embeddedxen-devel] Question about debugging.
> 
> Hello everyone,
> 
> I am trying to put xen in my HTC Desire, but when I execute "fastboot boot
> boot.img" XEN fail and is showed anything, the screen is white with HTC
> letters.
> 
> How can I do debugging a real device like HTC Desire?
> As you do you do debugging?
> 
> Thanks you.
> 
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers is
> just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro
> Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> Embeddedxen-devel mailing list
> Emb...@li...
> https://lists.sourceforge.net/lists/listinfo/embeddedxen-devel

[Embeddedxen-devel] Question about debugging.

[Hector M. <hec...@up...>]

Hello everyone,

I am trying to put xen in my HTC Desire, but when I execute "fastboot
boot boot.img" XEN fail and is showed anything, the screen is white with
HTC letters.

How can I do debugging a real device like HTC Desire?
As you do you do debugging?

Thanks you.

[Embeddedxen-devel] Annoucement: next release of EmbeddedXEN

[Rossier D. <Dan...@he...>]

Hello!

The next release EmbeddedXEN is scheduled by end of February 2012. This release brings a lot of improvements and fixes with the support of the following devices:

- versatilev6 (QEMU) (ARMv6)
- goldfish (emulator) (MSM/ARMv7)
- HTC Desire HD (Snapdragon/ARMv7)

This release will be supplied with a guest domU which contains a SqueezeOS image which run on a SqueezeBox Touch from Logitech (further details on http://wiki.slimdevices.com/index.php/SqueezeOS)

Stay tuned!

Daniel Rossier

EmbeddedXEN results from several Years of Research in the field of ARM-based CPUs and hypervisor technology based on XEN. The overall architecture has been revisited in order to support the hardware diversity of ARM CPUs platforms and provide an excellent framework to deal with a native OS and a third-party OS cross-compiled from a different ARM CPU. EmbeddedXEN provide a virtualized hardware interface to the third-party OS. EmbeddedXEN has been initiated and is under current development at the Reconfigurable Embedded Digital Systems (REDS) Institute of HEIG-VD, Switzerland.

[Embeddedxen-devel] PANIC: Could not open: .android/avd/llr-vp.ini

[Hector M. <hec...@gm...>]

Hi everyone,

I am trying to execute the emulator and got the following error:

$ make sim
"PANIC: Could not open: /home/punxos/.android/avd/llr-vp.ini"

I could not find the AVD "llr-vp.ini" in the git repositori.

I did the following:

1.- Install SDK linux and add it to $PATH. (android-sdk-linux)
    Should I use "embeddedxen/tools/desire/emulator" instead of
    the emulator provided by android-sdk-linux ?

2.- Clone the repositori (git clone
git://embeddedxen.git.sourceforge.net/gitroot/embeddedxen/embeddedxen)

3.- Create uimage for goldfish and linux-2.6.59-dom0
    In this point the file "uImage.embeddedxen.goldfish" is created.

4.- Finally I ran "make sim" but the AVD "llr-vp.ini" was not found
by the emulator.

Should I to create it  myself ?
What about others devices like HTC desire ?

I am trying avoid eclipse for now.

Thanks!
Hector.

Re: [Embeddedxen-devel] [Android-virt] [Xen-devel] [ANNOUNCE] Xen port to Cortex-A15 / ARMv7 with virt extensions

[Catalin M. <cat...@ar...>]

On Thu, Dec 01, 2011 at 04:44:40PM +0000, Arnd Bergmann wrote:
> On Thursday 01 December 2011, Catalin Marinas wrote:
> > On Thu, Dec 01, 2011 at 03:42:19PM +0000, Arnd Bergmann wrote:
> > > On Thursday 01 December 2011, Catalin Marinas wrote:
> > > How do you deal with signed integer arguments passed into SVC or HVC from
> > > a caller? If I understand the architecture correctly, the upper
> > > halves of the argument register end up zero-padded, while the callee
> > > expects sign-extension.
> > 
> > If you treat it as an "int" (32-bit) and function prototype defined
> > accordingly, then the generated code only accesses it as a W (rather
> > than X) register and the top 32-bit part is ignored (no need for
> > sign-extension). If it is defined as a "long" in the 32-bit world, then
> > it indeed needs explicit conversion given the different sizes for long
> > (for example sys_lseek, the second argument is a 'long' and we do
> > explicit sign extension in the wrapper).
...
> What about unsigned long and pointer? Can we always rely on the upper
> half of the register to be zero-filled when we get an exception from 32
> bit into 64 bit state, or do we also have to zero-extend those?

They are also fine, no need for zero-extension.

-- 
Catalin

Re: [Embeddedxen-devel] [Android-virt] [Xen-devel] [ANNOUNCE] Xen port to Cortex-A15 / ARMv7 with virt extensions

[Arnd B. <ar...@ar...>]

On Thursday 01 December 2011, Catalin Marinas wrote:
> On Thu, Dec 01, 2011 at 03:42:19PM +0000, Arnd Bergmann wrote:
> > On Thursday 01 December 2011, Catalin Marinas wrote:
> > How do you deal with signed integer arguments passed into SVC or HVC from
> > a caller? If I understand the architecture correctly, the upper
> > halves of the argument register end up zero-padded, while the callee
> > expects sign-extension.
> 
> If you treat it as an "int" (32-bit) and function prototype defined
> accordingly, then the generated code only accesses it as a W (rather
> than X) register and the top 32-bit part is ignored (no need for
> sign-extension). If it is defined as a "long" in the 32-bit world, then
> it indeed needs explicit conversion given the different sizes for long
> (for example sys_lseek, the second argument is a 'long' and we do
> explicit sign extension in the wrapper).

Ok, so it's actually different from most other 64 bit architectures, which
normally operate on 64-bit registers and expect the caller to do the
correct sign-extension.

Doing the sign-extension for long arguments then falls into the same
category as long long and unsigned long long arguments, which also need
a wrapper, as you mentioned. Strictly speaking, we only need to do it
for those where the long argument has a meaning outside of the 0..2^31
range, e.g. io_submit can only take small positive numbers although
the type is 'long'.

What about unsigned long and pointer? Can we always rely on the upper
half of the register to be zero-filled when we get an exception from 32
bit into 64 bit state, or do we also have to zero-extend those?

	Arnd

Re: [Embeddedxen-devel] [Android-virt] [Xen-devel] [ANNOUNCE] Xen port to Cortex-A15 / ARMv7 with virt extensions

[Catalin M. <cat...@ar...>]

On Thu, Dec 01, 2011 at 03:42:19PM +0000, Arnd Bergmann wrote:
> On Thursday 01 December 2011, Catalin Marinas wrote:
> > Given the way register banking is done on AArch64, issuing an HVC on a
> > 32-bit guest OS doesn't require translation on a 64-bit hypervisor. We
> > have a similar implementation at the SVC level (for 32-bit user apps on
> > a 64-bit kernel), the only modification was where a 32-bit SVC takes a
> > 64-bit parameter in two separate 32-bit registers, so packing needs to
> > be done in a syscall wrapper.
> 
> How do you deal with signed integer arguments passed into SVC or HVC from
> a caller? If I understand the architecture correctly, the upper
> halves of the argument register end up zero-padded, while the callee
> expects sign-extension.

If you treat it as an "int" (32-bit) and function prototype defined
accordingly, then the generated code only accesses it as a W (rather
than X) register and the top 32-bit part is ignored (no need for
sign-extension). If it is defined as a "long" in the 32-bit world, then
it indeed needs explicit conversion given the different sizes for long
(for example sys_lseek, the second argument is a 'long' and we do
explicit sign extension in the wrapper).

-- 
Catalin