[Qemu-devel] [Consult] microblaze: About running upstream main branch qemu

[Qemu-devel] [Consult] microblaze: About running upstream main branch qemu

[Chen Gang]

Hello microblaze maintainers:

I tried to run upstream qemu for microblaze, but failed. It seems only
special qemu branch can run it. And after try Xilinx qemu branch, I got
"segment fault" which is related with "-dtb".  So I want to consult:

 - Can our main upstream qemu (not other branches) run microblaze?

 - Is what I have done for Xilinx related qemu correct?

The related operation for Xilinx related qemu is below:

 * For kernel:

   - building:

     git clone https://github.com/Xilinx/linux-xlnx.git
     cd linux-xlnx
     make ARCH=microblaze CROSS_COMPILE=/upstream/release/bin/microblaze-gchen-linux- mmu_config
     make ARCH=microblaze CROSS_COMPILE=/upstream/release/bin/microblaze-gchen-linux-

   - output:

     arch/microblaze/boot/linux.bin
     scripts/dtc/dtc

   - get 'system.dtb':

     ./scripts/dtc/dtc -I dts -O dtb -o system.dtb arch/microblaze/boot/dts/system.dts

 * For ramdisk:

   wget http://www.wiki.xilinx.com/file/view/microblaze_complete.cpio.gz/419243588/microblaze_complete.cpio.gz

 * For qemu:

   - building:

     git clone git://github.com/Xilinx/qemu.git
     ./configure --target-list="arm-softmmu,microblazeel-softmmu" --enable-fdt --disable-kvm
     make

   - running:

     ./arm-softmmu/qemu-system-arm -M arm-generic-fdt -nographic -smp 2 -machine linux=on -serial mon:stdio -dtb ../linux-xlnx/system.dtb \
       -kernel ../linux-xlnx/arch/microblaze/boot/linux.bin -initrd ../microblaze_complete.cpio.gz

   - result:

     Segmentation fault (core dumped) (after a simple try, I am sure, it is caused by "dtb").

And excuse me, at present, I have to only focus on fixing upstream qemu
issues (I have no enough time resource for other qemu branches), please
understand.

Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed

Re: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu

[Max Filippov]

On Sun, Oct 19, 2014 at 5:37 PM, Chen Gang <gang.chen.5i5j@gmail.com> wrote:
>    - running:
>
>      ./arm-softmmu/qemu-system-arm -M arm-generic-fdt -nographic -smp 2 -machine linux=on -serial mon:stdio -dtb ../linux-xlnx/system.dtb \
>        -kernel ../linux-xlnx/arch/microblaze/boot/linux.bin -initrd ../microblaze_complete.cpio.gz

qemu-system-microblaze?

-- 
Thanks.
-- Max

Re: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu

[Chen Gang]

On 10/19/14 21:38, Max Filippov wrote:
> On Sun, Oct 19, 2014 at 5:37 PM, Chen Gang <gang.chen.5i5j@gmail.com> wrote:
>>    - running:
>>
>>      ./arm-softmmu/qemu-system-arm -M arm-generic-fdt -nographic -smp 2 -machine linux=on -serial mon:stdio -dtb ../linux-xlnx/system.dtb \
>>        -kernel ../linux-xlnx/arch/microblaze/boot/linux.bin -initrd ../microblaze_complete.cpio.gz
> 
> qemu-system-microblaze?
> 

OK, thanks.

And after correct it, it is still failed:

  [root@localhost qemu]#./microblazeel-softmmu/qemu-system-microblazeel -M microblaze-fdt -nographic -smp 1 -machine linux=on -serial mon:stdio -dtb ../linux-xlnx/system.dtb           -kernel ../linux-xlnx/arch/microblaze/boot/linux.bin -initrd ../microblaze_complete.cpio.gz
  Segmentation fault (core dumped)

Originally, I referenced the link below:

  http://www.wiki.xilinx.com/QEMU



Thanks
-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed

Re: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu

[Guenter Roeck]

On 10/19/2014 06:58 AM, Chen Gang wrote:
>
> On 10/19/14 21:38, Max Filippov wrote:
>> On Sun, Oct 19, 2014 at 5:37 PM, Chen Gang <gang.chen.5i5j@gmail.com> wrote:
>>>     - running:
>>>
>>>       ./arm-softmmu/qemu-system-arm -M arm-generic-fdt -nographic -smp 2 -machine linux=on -serial mon:stdio -dtb ../linux-xlnx/system.dtb \
>>>         -kernel ../linux-xlnx/arch/microblaze/boot/linux.bin -initrd ../microblaze_complete.cpio.gz
>>
>> qemu-system-microblaze?
>>
>
> OK, thanks.
>
> And after correct it, it is still failed:
>
>    [root@localhost qemu]#./microblazeel-softmmu/qemu-system-microblazeel -M microblaze-fdt -nographic -smp 1 -machine linux=on -serial mon:stdio -dtb ../linux-xlnx/system.dtb           -kernel ../linux-xlnx/arch/microblaze/boot/linux.bin -initrd ../microblaze_complete.cpio.gz
>    Segmentation fault (core dumped)
>
> Originally, I referenced the link below:
>
>    http://www.wiki.xilinx.com/QEMU
>

Try the microblaze and microblazeel subdirectories in
http://server.roeck-us.net/qemu/.

This doesn't use devicetree, but the configurations are known to be working
with kernel releases all the way back to kernel version 3.10.

Guenter

Re: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu

[Chen Gang]

On 10/19/2014 10:58 PM, Guenter Roeck wrote:
> 
> This doesn't use devicetree, but the configurations are known to be working
> with kernel releases all the way back to kernel version 3.10.
> 

Yeah, really it is !

After try upstream qemu and upstream kernel, for me, neither them can
work well. For xilinx qemu with xilinux kernel, it should be well,
although I still met issue below, is what I have done incorrect?

For kernel:

  put rootfs.cpio in kernel root directory,
  mv qemu_microblaze_defconfig to arch/microblaze/config/mmu_defconfig
  make ARCH=microblaze CROSS_COMPILE=/usr/bin/microblaze-linux-gnu- mmu_defconfig
  make -j4

For qemu:

  ./configure --target-list="microblaze-softmmu" --enable-fdt --disable-kvm
  make -j4
  /upstream/xilinx/qemu/microblaze-softmmu/qemu-system-microblaze -M petalogix-s3adsp1800 -kernel ../linux-xlnx/arch/microblaze/boot/linux.bin  -no-reboot -append "console=ttyUL0,115200 doreboot" -nographic
  Early console on uartlite at 0x84000000
  bootconsole [earlyser0] enabled
  Ramdisk addr 0x00000000, 
  FDT at 0x905413f4
  Linux version 3.14.0-dirty (root@localhost.localdomain) (gcc version 4.9.1 20140717 (Red Hat Cross 4.9.1-1) (GCC) ) #1 Mon Oct 20 23:15:34 CST 2014
  setup_cpuinfo: initialising
  setup_cpuinfo: No PVR support. Using static CPU info from FDT
  wt_msr
  setup_memory: max_mapnr: 0x8000
  setup_memory: min_low_pfn: 0x90000
  setup_memory: max_low_pfn: 0x98000
  setup_memory: max_pfn: 0x98000
  Zone ranges:
    DMA      [mem 0x90000000-0x97ffffff]
    Normal   empty
  Movable zone start for each node
  Early memory node ranges
    node   0: [mem 0x90000000-0x97ffffff]
  On node 0 totalpages: 32768
  free_area_init_node: node 0, pgdat c03b4774, node_mem_map c0574000
    DMA zone: 256 pages used for memmap
    DMA zone: 0 pages reserved
    DMA zone: 32768 pages, LIFO batch:7
  early_printk_console remapping from 0x84000000 to 0xffffd000
  pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
  pcpu-alloc: [0] 0 
  Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
  Kernel command line: console=ttyUL0,115200
  PID hash table entries: 512 (order: -1, 2048 bytes)
  Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
  Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
  Memory: 124192K/131072K available (2883K kernel code, 120K rwdata, 752K rodata, 1572K init, 198K bss, 6880K reserved)
  Kernel virtual memory layout:
    * 0xffffe000..0xfffff000  : fixmap
    * 0xffffd000..0xffffe000  : early ioremap
    * 0xf0000000..0xffffd000  : vmalloc & ioremap
  NR_IRQS:33
  /plb@0/interrupt-controller@81800000: num_irq=4, edge=0xa
  ERROR: CPU CCF input clock not found
  /plb@0/timer@83c00000: irq=1
  ERROR: timer CCF input clock not found
  ERROR: Using CPU clock frequency
  xilinx_timer_set_mode: shutdown
  xilinx_timer_set_mode: periodic
  sched_clock: 32 bits at 62MHz, resolution 16ns, wraps every 68719476720ns
  Calibrating delay loop... Killed

The compiler information:

  [root@localhost qemu]# gcc -v
  Using built-in specs.
  COLLECT_GCC=gcc
  COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.8.3/lto-wrapper
  Target: x86_64-redhat-linux
  Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --with-linker-hash-style=gnu --enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto --enable-plugin --enable-initfini-array --enable-java-awt=gtk --disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-isl=/builddir/build/BUILD/gcc-4.8.3-20140624/obj-x86_64-redhat-linux/isl-install --with-cloog=/builddir/build/BUILD/gcc-4.8.3-20140624/obj-x86_64-redhat-linux/cloog-install --with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux
  Thread model: posix
  gcc version 4.8.3 20140624 (Red Hat 4.8.3-1) (GCC) 
  [root@localhost qemu]# ld -v
  GNU ld version 2.23.2
  [root@localhost linux-xlnx]# /usr/bin/microblaze-linux-gnu-gcc -v
  Using built-in specs.
  COLLECT_GCC=/usr/bin/microblaze-linux-gnu-gcc
  COLLECT_LTO_WRAPPER=/usr/libexec/gcc/microblaze-linux-gnu/4.9.1/lto-wrapper
  Target: microblaze-linux-gnu
  Configured with: ../gcc-4.9.1-20140717/configure --bindir=/usr/bin --build=x86_64-redhat-linux-gnu --datadir=/usr/share --disable-decimal-float --disable-dependency-tracking --disable-gold --disable-libgomp --disable-libmudflap --disable-libquadmath --disable-libssp --disable-nls --disable-plugin --disable-shared --disable-silent-rules --disable-sjlj-exceptions --disable-threads --enable-checking= --enable-gnu-unique-object --enable-initfini-array --enable-languages=c,c++ --enable-linker-build-id --enable-nls --enable-obsolete --enable-targets=all --exec-prefix=/usr --host=x86_64-redhat-linux-gnu --includedir=/usr/include --infodir=/usr/share/info --libexecdir=/usr/libexec --localstatedir=/var --mandir=/usr/share/man --prefix=/usr --program-prefix=microblaze-linux-gnu- --sbindir=/usr/sbin --sharedstatedir=/var/lib --sysconfdir=/etc --target=microblaze-linux-gnu --with-bugurl=http://bugzilla.redhat.com/bugzilla/ --with-linker-hash-style=gnu --with-newlib --with-sysroot=/usr/microblaz
e-linux-gnu/sys-root --with-system-libunwind --with-system-zlib --without-headers --with-isl=/builddir/build/BUILD/gcc-4.9.1-20140717/isl-install --with-cloog=/builddir/build/BUILD/gcc-4.9.1-20140717/cloog-install
  Thread model: single
  gcc version 4.9.1 20140717 (Red Hat Cross 4.9.1-1) (GCC) 
  [root@localhost linux-xlnx]# /usr/bin/microblaze-linux-gnu-ld -v
  GNU ld version 2.24.0-5.fc20 20140613

Welcome any suggestions or completions.

Thanks.
-- 
Chen Gang

Open share and attitude like air water and life which God blessed

Re: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu

[Guenter Roeck]

On 10/20/2014 08:23 AM, Chen Gang wrote:
> On 10/19/2014 10:58 PM, Guenter Roeck wrote:
>>
>> This doesn't use devicetree, but the configurations are known to be working
>> with kernel releases all the way back to kernel version 3.10.
>>
>
> Yeah, really it is !
>
> After try upstream qemu and upstream kernel, for me, neither them can
> work well. For xilinx qemu with xilinux kernel, it should be well,
> although I still met issue below, is what I have done incorrect?
>

Difficult to say.

I use gcc 4.8.0 from kernel.org and qemu 2.1.2 with its default configuration
for the microblaze big endian target. No idea if that makes a difference,
but I would suggest to start with those.

For microblazeel I use gcc 4.9.1 built with buildroot 2014.08 for both
kernel and initramfs. Initramfs for that target is built from busybox.

Guenter

Re: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu

[Chen Gang]

On 10/21/14 12:37, Guenter Roeck wrote:
> On 10/20/2014 08:23 AM, Chen Gang wrote:
>> On 10/19/2014 10:58 PM, Guenter Roeck wrote:
>>>
>>> This doesn't use devicetree, but the configurations are known to be working
>>> with kernel releases all the way back to kernel version 3.10.
>>>
>>
>> Yeah, really it is !
>>
>> After try upstream qemu and upstream kernel, for me, neither them can
>> work well. For xilinx qemu with xilinux kernel, it should be well,
>> although I still met issue below, is what I have done incorrect?
>>
> 
> Difficult to say.
> 
> I use gcc 4.8.0 from kernel.org and qemu 2.1.2 with its default configuration
> for the microblaze big endian target. No idea if that makes a difference,
> but I would suggest to start with those.
> 
> For microblazeel I use gcc 4.9.1 built with buildroot 2014.08 for both
> kernel and initramfs. Initramfs for that target is built from busybox.
> 

OK, thank you very much for your information.

But sorry, I have to stop trying, because that is far from upstream qemu
and upstream kernel (at present, I have no enough time resource on it).

My original goal is "use upstream microblaze qemu to test upstream gcc,
binutils and glibc of microblaze". And now I find another ways: "use sim
which is in upstream binutils to perform the related test".


And welcome any new ideas, suggestions, and completions.

Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed

Re: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu

[Guenter Roeck]

On Tue, Oct 21, 2014 at 06:41:14PM +0800, Chen Gang wrote:
> On 10/21/14 12:37, Guenter Roeck wrote:
> > On 10/20/2014 08:23 AM, Chen Gang wrote:
> >> On 10/19/2014 10:58 PM, Guenter Roeck wrote:
> >>>
> >>> This doesn't use devicetree, but the configurations are known to be working
> >>> with kernel releases all the way back to kernel version 3.10.
> >>>
> >>
> >> Yeah, really it is !
> >>
> >> After try upstream qemu and upstream kernel, for me, neither them can
> >> work well. For xilinx qemu with xilinux kernel, it should be well,
> >> although I still met issue below, is what I have done incorrect?
> >>
> > 
> > Difficult to say.
> > 
> > I use gcc 4.8.0 from kernel.org and qemu 2.1.2 with its default configuration
> > for the microblaze big endian target. No idea if that makes a difference,
> > but I would suggest to start with those.
> > 
> > For microblazeel I use gcc 4.9.1 built with buildroot 2014.08 for both
> > kernel and initramfs. Initramfs for that target is built from busybox.
> > 
> 
> OK, thank you very much for your information.
> 
> But sorry, I have to stop trying, because that is far from upstream qemu
> and upstream kernel (at present, I have no enough time resource on it).
> 
> My original goal is "use upstream microblaze qemu to test upstream gcc,
> binutils and glibc of microblaze". And now I find another ways: "use sim
> which is in upstream binutils to perform the related test".
> 
You lost me. qemu 2.1.2 is the upstream qemu, and I do use upstream binutils
(2.24 if I recall corectly) as well as upstream gcc and upstream kernel.
Did I indicate otherwise in anything I said ? FWIW, should be able to use
qemu from distributions without recompiling it.

Thanks,
Guenter

Re: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu

[Chen Gang]

OK, thanks, I shall try it within 2 days.

Send from Lenovo A788t.

Guenter Roeck <linux@roeck-us.net> wrote:

>On 10/19/2014 06:58 AM, Chen Gang wrote:
>>
>> On 10/19/14 21:38, Max Filippov wrote:
>>> On Sun, Oct 19, 2014 at 5:37 PM, Chen Gang <gang.chen.5i5j@gmail.com> wrote:
>>>>     - running:
>>>>
>>>>       ./arm-softmmu/qemu-system-arm -M arm-generic-fdt -nographic -smp 2 -machine linux=on -serial mon:stdio -dtb ../linux-xlnx/system.dtb \
>>>>         -kernel ../linux-xlnx/arch/microblaze/boot/linux.bin -initrd ../microblaze_complete.cpio.gz
>>>
>>> qemu-system-microblaze?
>>>
>>
>> OK, thanks.
>>
>> And after correct it, it is still failed:
>>
>>    [root@localhost qemu]#./microblazeel-softmmu/qemu-system-microblazeel -M microblaze-fdt -nographic -smp 1 -machine linux=on -serial mon:stdio -dtb ../linux-xlnx/system.dtb           -kernel ../linux-xlnx/arch/microblaze/boot/linux.bin -initrd ../microblaze_complete.cpio.gz
>>    Segmentation fault (core dumped)
>>
>> Originally, I referenced the link below:
>>
>>    http://www.wiki.xilinx.com/QEMU
>>
>
>Try the microblaze and microblazeel subdirectories in
>http://server.roeck-us.net/qemu/.
>
>This doesn't use devicetree, but the configurations are known to be working
>with kernel releases all the way back to kernel version 3.10.
>
>Guenter
>

Re: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu

[Chen Gang]

OK, thanks, there are multiple branches in upstream qemu. Sorry
for my original said, and I can only say: for upstream  develop
master branch, it does not support microblaze.

Excuse me, I does not mainly focus on only using qemu, and I
also found another easier way for test microblaze toolchain (use sim of binutils). So next, I will mainly focus on sim.

I also met some issues for sim, but I guess, I can analyze it,
maybe also have chances to make patch for it (that is the main
reason why I want to focus on it).

Thanks.

Send from Lenovo A788t.

Guenter Roeck <linux@roeck-us.net> wrote:

>On Tue, Oct 21, 2014 at 06:41:14PM +0800, Chen Gang wrote:
>> On 10/21/14 12:37, Guenter Roeck wrote:
>> > On 10/20/2014 08:23 AM, Chen Gang wrote:
>> >> On 10/19/2014 10:58 PM, Guenter Roeck wrote:
>> >>>
>> >>> This doesn't use devicetree, but the configurations are known to be working
>> >>> with kernel releases all the way back to kernel version 3.10.
>> >>>
>> >>
>> >> Yeah, really it is !
>> >>
>> >> After try upstream qemu and upstream kernel, for me, neither them can
>> >> work well. For xilinx qemu with xilinux kernel, it should be well,
>> >> although I still met issue below, is what I have done incorrect?
>> >>
>> > 
>> > Difficult to say.
>> > 
>> > I use gcc 4.8.0 from kernel.org and qemu 2.1.2 with its default configuration
>> > for the microblaze big endian target. No idea if that makes a difference,
>> > but I would suggest to start with those.
>> > 
>> > For microblazeel I use gcc 4.9.1 built with buildroot 2014.08 for both
>> > kernel and initramfs. Initramfs for that target is built from busybox.
>> > 
>> 
>> OK, thank you very much for your information.
>> 
>> But sorry, I have to stop trying, because that is far from upstream qemu
>> and upstream kernel (at present, I have no enough time resource on it).
>> 
>> My original goal is "use upstream microblaze qemu to test upstream gcc,
>> binutils and glibc of microblaze". And now I find another ways: "use sim
>> which is in upstream binutils to perform the related test".
>> 
>You lost me. qemu 2.1.2 is the upstream qemu, and I do use upstream binutils
>(2.24 if I recall corectly) as well as upstream gcc and upstream kernel.
>Did I indicate otherwise in anything I said ? FWIW, should be able to use
>qemu from distributions without recompiling it.
>
>Thanks,
>Guenter

Re: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu

[Chen Gang]

And I still shall try qemu and kernel distribution for testing.

But excuse me, maybe I can not finish within this month, I shall try to
finish within next month.

Thanks.

发自我的 iPad

> 在 2014年10月22日，上午8:28，Chen Gang <gang.chen.5i5j@gmail.com> 写道：
> 
> OK, thanks, there are multiple branches in upstream qemu. Sorry
> for my original said, and I can only say: for upstream  develop
> master branch, it does not support microblaze.
> 
> Excuse me, I does not mainly focus on only using qemu, and I
> also found another easier way for test microblaze toolchain (use sim of binutils). So next, I will mainly focus on sim.
> 
> I also met some issues for sim, but I guess, I can analyze it,
> maybe also have chances to make patch for it (that is the main
> reason why I want to focus on it).
> 
> Thanks.
> 
> Send from Lenovo A788t.
> 
> Guenter Roeck <linux@roeck-us.net> wrote:
> 
>>> On Tue, Oct 21, 2014 at 06:41:14PM +0800, Chen Gang wrote:
>>>> On 10/21/14 12:37, Guenter Roeck wrote:
>>>>> On 10/20/2014 08:23 AM, Chen Gang wrote:
>>>>>> On 10/19/2014 10:58 PM, Guenter Roeck wrote:
>>>>>> 
>>>>>> This doesn't use devicetree, but the configurations are known to be working
>>>>>> with kernel releases all the way back to kernel version 3.10.
>>>>> 
>>>>> Yeah, really it is !
>>>>> 
>>>>> After try upstream qemu and upstream kernel, for me, neither them can
>>>>> work well. For xilinx qemu with xilinux kernel, it should be well,
>>>>> although I still met issue below, is what I have done incorrect?
>>>> 
>>>> Difficult to say.
>>>> 
>>>> I use gcc 4.8.0 from kernel.org and qemu 2.1.2 with its default configuration
>>>> for the microblaze big endian target. No idea if that makes a difference,
>>>> but I would suggest to start with those.
>>>> 
>>>> For microblazeel I use gcc 4.9.1 built with buildroot 2014.08 for both
>>>> kernel and initramfs. Initramfs for that target is built from busybox.
>>> 
>>> OK, thank you very much for your information.
>>> 
>>> But sorry, I have to stop trying, because that is far from upstream qemu
>>> and upstream kernel (at present, I have no enough time resource on it).
>>> 
>>> My original goal is "use upstream microblaze qemu to test upstream gcc,
>>> binutils and glibc of microblaze". And now I find another ways: "use sim
>>> which is in upstream binutils to perform the related test".
>> You lost me. qemu 2.1.2 is the upstream qemu, and I do use upstream binutils
>> (2.24 if I recall corectly) as well as upstream gcc and upstream kernel.
>> Did I indicate otherwise in anything I said ? FWIW, should be able to use
>> qemu from distributions without recompiling it.
>> 
>> Thanks,
>> Guenter

Re: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu

[Chen Gang]

Hello Guenter Roeck:

I still shall try qemu and kernel distribution, next, since it can do
it successfully (whether 'sim' can be success or not).

But excuse me, maybe I can not finish microblaze qemu test within this
month, hope I can finish within next month (2014-11-30).

Thank your information about qemu, again.


Thanks.

On 10/22/2014 08:28 AM, Chen Gang wrote:
> OK, thanks, there are multiple branches in upstream qemu. Sorry
> for my original said, and I can only say: for upstream  develop
> master branch, it does not support microblaze.
> 
> Excuse me, I does not mainly focus on only using qemu, and I
> also found another easier way for test microblaze toolchain (use sim of binutils). So next, I will mainly focus on sim.
> 
> I also met some issues for sim, but I guess, I can analyze it,
> maybe also have chances to make patch for it (that is the main
> reason why I want to focus on it).
> 
> Thanks.
> 
> Send from Lenovo A788t.
> 
> 
> 
> 
> 
> Guenter Roeck <linux@roeck-us.net> wrote:
> 
> 
> 
> On Tue, Oct 21, 2014 at 06:41:14PM +0800, Chen Gang wrote:
>> On 10/21/14 12:37, Guenter Roeck wrote:
>>> On 10/20/2014 08:23 AM, Chen Gang wrote:
>>>> On 10/19/2014 10:58 PM, Guenter Roeck wrote:
>>>>>
>>>>> This doesn't use devicetree, but the configurations are known to be working
>>>>> with kernel releases all the way back to kernel version 3.10.
>>>>>
>>>>
>>>> Yeah, really it is !
>>>>
>>>> After try upstream qemu and upstream kernel, for me, neither them can
>>>> work well. For xilinx qemu with xilinux kernel, it should be well,
>>>> although I still met issue below, is what I have done incorrect?
>>>>
>>>
>>> Difficult to say.
>>>
>>> I use gcc 4.8.0 from kernel.org and qemu 2.1.2 with its default configuration
>>> for the microblaze big endian target. No idea if that makes a difference,
>>> but I would suggest to start with those.
>>>
>>> For microblazeel I use gcc 4.9.1 built with buildroot 2014.08 for both
>>> kernel and initramfs. Initramfs for that target is built from busybox.
>>>
>>
>> OK, thank you very much for your information.
>>
>> But sorry, I have to stop trying, because that is far from upstream qemu
>> and upstream kernel (at present, I have no enough time resource on it).
>>
>> My original goal is "use upstream microblaze qemu to test upstream gcc,
>> binutils and glibc of microblaze". And now I find another ways: "use sim
>> which is in upstream binutils to perform the related test".
>>
> You lost me. qemu 2.1.2 is the upstream qemu, and I do use upstream binutils
> (2.24 if I recall corectly) as well as upstream gcc and upstream kernel.
> Did I indicate otherwise in anything I said ? FWIW, should be able to use
> qemu from distributions without recompiling it.
> 
> Thanks,
> Guenter
> 


-- 
Chen Gang

Open share and attitude like air water and life which God blessed

Re: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu

[Chen Gang]

On 10/26/14 21:28, Chen Gang wrote:
> Hello Guenter Roeck:
> 
> I still shall try qemu and kernel distribution, next, since it can do
> it successfully (whether 'sim' can be success or not).
> 

I got confirmation from microblaze members, at present, microblaze sim
can not full simulate entire system, so I shall try qemu and kernel
distribution for it (which can do full simulation for microblaze).

I shall try my best to finish it within this month.

Thanks.

> But excuse me, maybe I can not finish microblaze qemu test within this
> month, hope I can finish within next month (2014-11-30).
> 
> Thank your information about qemu, again.
> 
> 
> Thanks.
> 
> On 10/22/2014 08:28 AM, Chen Gang wrote:
>> OK, thanks, there are multiple branches in upstream qemu. Sorry
>> for my original said, and I can only say: for upstream  develop
>> master branch, it does not support microblaze.
>>
>> Excuse me, I does not mainly focus on only using qemu, and I
>> also found another easier way for test microblaze toolchain (use sim of binutils). So next, I will mainly focus on sim.
>>
>> I also met some issues for sim, but I guess, I can analyze it,
>> maybe also have chances to make patch for it (that is the main
>> reason why I want to focus on it).
>>
>> Thanks.
>>
>> Send from Lenovo A788t.
>>
>>
>>
>>
>>
>> Guenter Roeck <linux@roeck-us.net> wrote:
>>
>>
>>
>> On Tue, Oct 21, 2014 at 06:41:14PM +0800, Chen Gang wrote:
>>> On 10/21/14 12:37, Guenter Roeck wrote:
>>>> On 10/20/2014 08:23 AM, Chen Gang wrote:
>>>>> On 10/19/2014 10:58 PM, Guenter Roeck wrote:
>>>>>>
>>>>>> This doesn't use devicetree, but the configurations are known to be working
>>>>>> with kernel releases all the way back to kernel version 3.10.
>>>>>>
>>>>>
>>>>> Yeah, really it is !
>>>>>
>>>>> After try upstream qemu and upstream kernel, for me, neither them can
>>>>> work well. For xilinx qemu with xilinux kernel, it should be well,
>>>>> although I still met issue below, is what I have done incorrect?
>>>>>
>>>>
>>>> Difficult to say.
>>>>
>>>> I use gcc 4.8.0 from kernel.org and qemu 2.1.2 with its default configuration
>>>> for the microblaze big endian target. No idea if that makes a difference,
>>>> but I would suggest to start with those.
>>>>
>>>> For microblazeel I use gcc 4.9.1 built with buildroot 2014.08 for both
>>>> kernel and initramfs. Initramfs for that target is built from busybox.
>>>>
>>>
>>> OK, thank you very much for your information.
>>>
>>> But sorry, I have to stop trying, because that is far from upstream qemu
>>> and upstream kernel (at present, I have no enough time resource on it).
>>>
>>> My original goal is "use upstream microblaze qemu to test upstream gcc,
>>> binutils and glibc of microblaze". And now I find another ways: "use sim
>>> which is in upstream binutils to perform the related test".
>>>
>> You lost me. qemu 2.1.2 is the upstream qemu, and I do use upstream binutils
>> (2.24 if I recall corectly) as well as upstream gcc and upstream kernel.
>> Did I indicate otherwise in anything I said ? FWIW, should be able to use
>> qemu from distributions without recompiling it.
>>
>> Thanks,
>> Guenter
>>
> 
> 

-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed

Re: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu

[Chen Gang]

After a little try, I succeed run microblaze under upstream qemu 2.1.2
and upstream Linux kernel 3.17-rc7, with the xilinux own ramdisk:
"microblaze_complete.cpio.gz". :-)

Compiler is "gcc version 4.9.1 20140717 (Red Hat Cross 4.9.1-1) (GCC)"
for microblaze, and "gcc version 4.8.3 20140624 (Red Hat 4.8.3-1) (GCC)"
for x86_64 qemu.

Next I shall try to use virtio file to share the local data to virtual
guest (I guess, it should be OK).


Thanks again!



On 10/27/2014 09:47 AM, Chen Gang wrote:
> On 10/26/14 21:28, Chen Gang wrote:
>> Hello Guenter Roeck:
>>
>> I still shall try qemu and kernel distribution, next, since it can do
>> it successfully (whether 'sim' can be success or not).
>>
> 
> I got confirmation from microblaze members, at present, microblaze sim
> can not full simulate entire system, so I shall try qemu and kernel
> distribution for it (which can do full simulation for microblaze).
> 
> I shall try my best to finish it within this month.
> 
> Thanks.
> 
>> But excuse me, maybe I can not finish microblaze qemu test within this
>> month, hope I can finish within next month (2014-11-30).
>>
>> Thank your information about qemu, again.
>>
>>
>> Thanks.
>>
>> On 10/22/2014 08:28 AM, Chen Gang wrote:
>>> OK, thanks, there are multiple branches in upstream qemu. Sorry
>>> for my original said, and I can only say: for upstream  develop
>>> master branch, it does not support microblaze.
>>>
>>> Excuse me, I does not mainly focus on only using qemu, and I
>>> also found another easier way for test microblaze toolchain (use sim of binutils). So next, I will mainly focus on sim.
>>>
>>> I also met some issues for sim, but I guess, I can analyze it,
>>> maybe also have chances to make patch for it (that is the main
>>> reason why I want to focus on it).
>>>
>>> Thanks.
>>>
>>> Send from Lenovo A788t.
>>>
>>>
>>>
>>>
>>>
>>> Guenter Roeck <linux@roeck-us.net> wrote:
>>>
>>>
>>>
>>> On Tue, Oct 21, 2014 at 06:41:14PM +0800, Chen Gang wrote:
>>>> On 10/21/14 12:37, Guenter Roeck wrote:
>>>>> On 10/20/2014 08:23 AM, Chen Gang wrote:
>>>>>> On 10/19/2014 10:58 PM, Guenter Roeck wrote:
>>>>>>>
>>>>>>> This doesn't use devicetree, but the configurations are known to be working
>>>>>>> with kernel releases all the way back to kernel version 3.10.
>>>>>>>
>>>>>>
>>>>>> Yeah, really it is !
>>>>>>
>>>>>> After try upstream qemu and upstream kernel, for me, neither them can
>>>>>> work well. For xilinx qemu with xilinux kernel, it should be well,
>>>>>> although I still met issue below, is what I have done incorrect?
>>>>>>
>>>>>
>>>>> Difficult to say.
>>>>>
>>>>> I use gcc 4.8.0 from kernel.org and qemu 2.1.2 with its default configuration
>>>>> for the microblaze big endian target. No idea if that makes a difference,
>>>>> but I would suggest to start with those.
>>>>>
>>>>> For microblazeel I use gcc 4.9.1 built with buildroot 2014.08 for both
>>>>> kernel and initramfs. Initramfs for that target is built from busybox.
>>>>>
>>>>
>>>> OK, thank you very much for your information.
>>>>
>>>> But sorry, I have to stop trying, because that is far from upstream qemu
>>>> and upstream kernel (at present, I have no enough time resource on it).
>>>>
>>>> My original goal is "use upstream microblaze qemu to test upstream gcc,
>>>> binutils and glibc of microblaze". And now I find another ways: "use sim
>>>> which is in upstream binutils to perform the related test".
>>>>
>>> You lost me. qemu 2.1.2 is the upstream qemu, and I do use upstream binutils
>>> (2.24 if I recall corectly) as well as upstream gcc and upstream kernel.
>>> Did I indicate otherwise in anything I said ? FWIW, should be able to use
>>> qemu from distributions without recompiling it.
>>>
>>> Thanks,
>>> Guenter
>>>
>>
>>
> 


-- 
Chen Gang

Open share and attitude like air water and life which God blessed

Re: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu

[Chen Gang]

On 10/27/14 22:47, Chen Gang wrote:
> 
> After a little try, I succeed run microblaze under upstream qemu 2.1.2
> and upstream Linux kernel 3.17-rc7, with the xilinux own ramdisk:
> "microblaze_complete.cpio.gz". :-)
> 
> Compiler is "gcc version 4.9.1 20140717 (Red Hat Cross 4.9.1-1) (GCC)"
> for microblaze, and "gcc version 4.8.3 20140624 (Red Hat 4.8.3-1) (GCC)"
> for x86_64 qemu.
> 
> Next I shall try to use virtio file to share the local data to virtual
> guest (I guess, it should be OK).
> 

I finished testing the microblaze hello world program with both dynamic
glibc and static glibc under qemu (I put it to 'ramfs' manualy, and it
runs well)  :-)

Next, I need focus on networking (I have found qemu related device, and
kernel related device, and I also know, it needs telnetd in busy box).
But sorry, it seems I can not finish within this month :-(

 - I wasted much time resources on choosing qemu or sim, next I should
   notice about it (do not waste time, again).

 - and another excuse is: I have to do it in my free time (within 2.5
   hours per day, in average). My current job is not related with it
   (at present, it is about Global Platform Java applet for iPhone OS).

Next month:

 - I should finish microblaze qemu test under DejaGNU, should finish
   within next month (2014-11-30).

 - I also shall start tile cross compiling for gcc/binutils, and use it
   to Linux kernel, and test it with qemu. I shall try to finish them
   within 2 months (finish before 2014-12-31).

 - At least, finish 1 patch for gcc, 1 patch for binutils, 1 patch for
   qemu/kvm/xen, 3 patches for kernel, within next month (2014-11-30).


Welcome any ideas, suggestions or completions (especially for net device,
net drivers, busy box for telnet ...).

Thanks.


> 
> Thanks again!
> 
> 
> 
> On 10/27/2014 09:47 AM, Chen Gang wrote:
>> On 10/26/14 21:28, Chen Gang wrote:
>>> Hello Guenter Roeck:
>>>
>>> I still shall try qemu and kernel distribution, next, since it can do
>>> it successfully (whether 'sim' can be success or not).
>>>
>>
>> I got confirmation from microblaze members, at present, microblaze sim
>> can not full simulate entire system, so I shall try qemu and kernel
>> distribution for it (which can do full simulation for microblaze).
>>
>> I shall try my best to finish it within this month.
>>
>> Thanks.
>>
>>> But excuse me, maybe I can not finish microblaze qemu test within this
>>> month, hope I can finish within next month (2014-11-30).
>>>
>>> Thank your information about qemu, again.
>>>
>>>
>>> Thanks.
>>>
>>> On 10/22/2014 08:28 AM, Chen Gang wrote:
>>>> OK, thanks, there are multiple branches in upstream qemu. Sorry
>>>> for my original said, and I can only say: for upstream  develop
>>>> master branch, it does not support microblaze.
>>>>
>>>> Excuse me, I does not mainly focus on only using qemu, and I
>>>> also found another easier way for test microblaze toolchain (use sim of binutils). So next, I will mainly focus on sim.
>>>>
>>>> I also met some issues for sim, but I guess, I can analyze it,
>>>> maybe also have chances to make patch for it (that is the main
>>>> reason why I want to focus on it).
>>>>
>>>> Thanks.
>>>>
>>>> Send from Lenovo A788t.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Guenter Roeck <linux@roeck-us.net> wrote:
>>>>
>>>>
>>>>
>>>> On Tue, Oct 21, 2014 at 06:41:14PM +0800, Chen Gang wrote:
>>>>> On 10/21/14 12:37, Guenter Roeck wrote:
>>>>>> On 10/20/2014 08:23 AM, Chen Gang wrote:
>>>>>>> On 10/19/2014 10:58 PM, Guenter Roeck wrote:
>>>>>>>>
>>>>>>>> This doesn't use devicetree, but the configurations are known to be working
>>>>>>>> with kernel releases all the way back to kernel version 3.10.
>>>>>>>>
>>>>>>>
>>>>>>> Yeah, really it is !
>>>>>>>
>>>>>>> After try upstream qemu and upstream kernel, for me, neither them can
>>>>>>> work well. For xilinx qemu with xilinux kernel, it should be well,
>>>>>>> although I still met issue below, is what I have done incorrect?
>>>>>>>
>>>>>>
>>>>>> Difficult to say.
>>>>>>
>>>>>> I use gcc 4.8.0 from kernel.org and qemu 2.1.2 with its default configuration
>>>>>> for the microblaze big endian target. No idea if that makes a difference,
>>>>>> but I would suggest to start with those.
>>>>>>
>>>>>> For microblazeel I use gcc 4.9.1 built with buildroot 2014.08 for both
>>>>>> kernel and initramfs. Initramfs for that target is built from busybox.
>>>>>>
>>>>>
>>>>> OK, thank you very much for your information.
>>>>>
>>>>> But sorry, I have to stop trying, because that is far from upstream qemu
>>>>> and upstream kernel (at present, I have no enough time resource on it).
>>>>>
>>>>> My original goal is "use upstream microblaze qemu to test upstream gcc,
>>>>> binutils and glibc of microblaze". And now I find another ways: "use sim
>>>>> which is in upstream binutils to perform the related test".
>>>>>
>>>> You lost me. qemu 2.1.2 is the upstream qemu, and I do use upstream binutils
>>>> (2.24 if I recall corectly) as well as upstream gcc and upstream kernel.
>>>> Did I indicate otherwise in anything I said ? FWIW, should be able to use
>>>> qemu from distributions without recompiling it.
>>>>
>>>> Thanks,
>>>> Guenter
>>>>
>>>
>>>
>>
> 
> 

-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed

Re: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu

[Chen Gang]

At present, I use telnet (without password), login to microblaze qemu
successfully! :-)

 - I compile busy box with the glibc in orginal 'ramfs', so get telnetd:
   use new busybox replace the old one, and add symbol link 'telnetd' to
   busybox in "/bin".

 - configure qemu with network support (device "xlnx.xps-ethernetlite").

   yum install libvirt
   yum install tunctl
   tunctl -b
   ip link set tap0 up
   brctl addif virbr0 tap0
   ./microblaze-softmmu/qemu-system-microblaze -M petalogix-s3adsp1800 \
     -kernel ../linux-stable.microblaze/arch/microblaze/boot/linux.bin \
     -no-reboot -append "console=ttyUL0,115200 doreboot" -nographic \
     -net nic,vlan=0,model=xlnx.xps-ethernetlite,macaddr=00:16:35:AF:94:00 \
     -net tap,vlan=0,ifname=tap0,script=no,downscript=no

 - fix a kernel bug: add "xlnx,xps-ethernetlite-2.00.b" for compatible
   with its firmware (can find it under "/sys/firmware..../compatible",
   within microblaze qemu bash environments). Related diff:

   diff --git a/drivers/net/ethernet/xilinx/xilinx_emaclite.c b/drivers/net/ethernet/xilinx/xilinx_emaclite.c
   index 28dbbdc..298fad3 100644
   --- a/drivers/net/ethernet/xilinx/xilinx_emaclite.c
   +++ b/drivers/net/ethernet/xilinx/xilinx_emaclite.c
   @@ -1236,6 +1236,7 @@ static struct of_device_id xemaclite_of_match[] = {
           { .compatible = "xlnx,opb-ethernetlite-1.01.b", },
           { .compatible = "xlnx,xps-ethernetlite-1.00.a", },
           { .compatible = "xlnx,xps-ethernetlite-2.00.a", },
   +       { .compatible = "xlnx,xps-ethernetlite-2.00.b", },
           { .compatible = "xlnx,xps-ethernetlite-2.01.a", },
           { .compatible = "xlnx,xps-ethernetlite-3.00.a", },
           { /* end of list */ },

Next, I shall send related kernel patch for upstream kernel, and continue
for microbaze DejaGNU with microbaze qemu, and sorry again, I did not
finish it within this month.


Thanks.



On 10/30/14 22:20, Chen Gang wrote:
> On 10/27/14 22:47, Chen Gang wrote:
>>
>> After a little try, I succeed run microblaze under upstream qemu 2.1.2
>> and upstream Linux kernel 3.17-rc7, with the xilinux own ramdisk:
>> "microblaze_complete.cpio.gz". :-)
>>
>> Compiler is "gcc version 4.9.1 20140717 (Red Hat Cross 4.9.1-1) (GCC)"
>> for microblaze, and "gcc version 4.8.3 20140624 (Red Hat 4.8.3-1) (GCC)"
>> for x86_64 qemu.
>>
>> Next I shall try to use virtio file to share the local data to virtual
>> guest (I guess, it should be OK).
>>
> 
> I finished testing the microblaze hello world program with both dynamic
> glibc and static glibc under qemu (I put it to 'ramfs' manualy, and it
> runs well)  :-)
> 
> Next, I need focus on networking (I have found qemu related device, and
> kernel related device, and I also know, it needs telnetd in busy box).
> But sorry, it seems I can not finish within this month :-(
> 
>  - I wasted much time resources on choosing qemu or sim, next I should
>    notice about it (do not waste time, again).
> 
>  - and another excuse is: I have to do it in my free time (within 2.5
>    hours per day, in average). My current job is not related with it
>    (at present, it is about Global Platform Java applet for iPhone OS).
> 
> Next month:
> 
>  - I should finish microblaze qemu test under DejaGNU, should finish
>    within next month (2014-11-30).
> 
>  - I also shall start tile cross compiling for gcc/binutils, and use it
>    to Linux kernel, and test it with qemu. I shall try to finish them
>    within 2 months (finish before 2014-12-31).
> 
>  - At least, finish 1 patch for gcc, 1 patch for binutils, 1 patch for
>    qemu/kvm/xen, 3 patches for kernel, within next month (2014-11-30).
> 
> 
> Welcome any ideas, suggestions or completions (especially for net device,
> net drivers, busy box for telnet ...).
> 
> Thanks.
> 
> 
>>
>> Thanks again!
>>
>>
>>
>> On 10/27/2014 09:47 AM, Chen Gang wrote:
>>> On 10/26/14 21:28, Chen Gang wrote:
>>>> Hello Guenter Roeck:
>>>>
>>>> I still shall try qemu and kernel distribution, next, since it can do
>>>> it successfully (whether 'sim' can be success or not).
>>>>
>>>
>>> I got confirmation from microblaze members, at present, microblaze sim
>>> can not full simulate entire system, so I shall try qemu and kernel
>>> distribution for it (which can do full simulation for microblaze).
>>>
>>> I shall try my best to finish it within this month.
>>>
>>> Thanks.
>>>
>>>> But excuse me, maybe I can not finish microblaze qemu test within this
>>>> month, hope I can finish within next month (2014-11-30).
>>>>
>>>> Thank your information about qemu, again.
>>>>
>>>>
>>>> Thanks.
>>>>
>>>> On 10/22/2014 08:28 AM, Chen Gang wrote:
>>>>> OK, thanks, there are multiple branches in upstream qemu. Sorry
>>>>> for my original said, and I can only say: for upstream  develop
>>>>> master branch, it does not support microblaze.
>>>>>
>>>>> Excuse me, I does not mainly focus on only using qemu, and I
>>>>> also found another easier way for test microblaze toolchain (use sim of binutils). So next, I will mainly focus on sim.
>>>>>
>>>>> I also met some issues for sim, but I guess, I can analyze it,
>>>>> maybe also have chances to make patch for it (that is the main
>>>>> reason why I want to focus on it).
>>>>>
>>>>> Thanks.
>>>>>
>>>>> Send from Lenovo A788t.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Guenter Roeck <linux@roeck-us.net> wrote:
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Oct 21, 2014 at 06:41:14PM +0800, Chen Gang wrote:
>>>>>> On 10/21/14 12:37, Guenter Roeck wrote:
>>>>>>> On 10/20/2014 08:23 AM, Chen Gang wrote:
>>>>>>>> On 10/19/2014 10:58 PM, Guenter Roeck wrote:
>>>>>>>>>
>>>>>>>>> This doesn't use devicetree, but the configurations are known to be working
>>>>>>>>> with kernel releases all the way back to kernel version 3.10.
>>>>>>>>>
>>>>>>>>
>>>>>>>> Yeah, really it is !
>>>>>>>>
>>>>>>>> After try upstream qemu and upstream kernel, for me, neither them can
>>>>>>>> work well. For xilinx qemu with xilinux kernel, it should be well,
>>>>>>>> although I still met issue below, is what I have done incorrect?
>>>>>>>>
>>>>>>>
>>>>>>> Difficult to say.
>>>>>>>
>>>>>>> I use gcc 4.8.0 from kernel.org and qemu 2.1.2 with its default configuration
>>>>>>> for the microblaze big endian target. No idea if that makes a difference,
>>>>>>> but I would suggest to start with those.
>>>>>>>
>>>>>>> For microblazeel I use gcc 4.9.1 built with buildroot 2014.08 for both
>>>>>>> kernel and initramfs. Initramfs for that target is built from busybox.
>>>>>>>
>>>>>>
>>>>>> OK, thank you very much for your information.
>>>>>>
>>>>>> But sorry, I have to stop trying, because that is far from upstream qemu
>>>>>> and upstream kernel (at present, I have no enough time resource on it).
>>>>>>
>>>>>> My original goal is "use upstream microblaze qemu to test upstream gcc,
>>>>>> binutils and glibc of microblaze". And now I find another ways: "use sim
>>>>>> which is in upstream binutils to perform the related test".
>>>>>>
>>>>> You lost me. qemu 2.1.2 is the upstream qemu, and I do use upstream binutils
>>>>> (2.24 if I recall corectly) as well as upstream gcc and upstream kernel.
>>>>> Did I indicate otherwise in anything I said ? FWIW, should be able to use
>>>>> qemu from distributions without recompiling it.
>>>>>
>>>>> Thanks,
>>>>> Guenter
>>>>>
>>>>
>>>>
>>>
>>
>>
> 

-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed

Re: [Qemu-devel] [Consult] microblaze: About running upstream main branch qemu

[Chen Gang]

At present, I use simplified sshd, ssh and scp (dropbear open source
program) to communicate with microblaze qemu successfully, and let gcc
'make check' have real effect. It is just testing (may run a week!!).

So we can say, the related environments construction based on qemu is
finished. This thread can be ended (but the related thread for gcc is
not ended, for it also needs the testing result).

The recent operations is below, it is generated by the latest upstream
microblaze toolchain (need build toolchain firstly, also at last, will
use microblaze qemu and dropbear to test this toolchain):

 - zlib (for dropbear):

   export CHOST=microblaze-gchen-linux
   export PATH=/upstream/release/bin:$PATH
   ./configure --prefix=/upstream/release && make && make install

 - dropbear (it is a simple sshd, ssh and scp):

   export PATH=/upstream/release/bin:$PATH
   ./configure --prefix=/upstream/release \
     --host=microblaze-gchen-linux \
     CC=microblaze-gchen-linux-gcc

   modify /ustream/release/include/stdio.h to avoid redefining sscanf to
   iso99_sscanf

   link libz.a (static lib) to 'dropbear' (sshd) and 'dbclient' (ssh).
   and "make scp" to generate 'scp' command.

   for supporting 'none' username:

     under ramfs, "echo 'none:x:0:0:none:/:/bin/sh' > ./etc/passwd"

   for supporting no passwords (it is temporary fix):

     modify  common-session.c: "ses.authstate.pw_passwd[0] = '\0';"

   put 'dropbear', 'dbclient' and 'scp' to "./sbin" of ramfs and symbol
   links to "./usr/bin" of ramfs.

   for temporary fix its stable issue, need modify code to let it 'fork'
   as soon as startup, and only permit one child connection each time.

   usage:

     in microblaze qemu:

       "/sbin/dropbear -F -E -B -p 192.168.122.2:22"

     in host (x86_64), use system scp and ssh is OK (without password):

       ssh none@192.168.122.2 "cd /test; ./test"
       scp test.c none@192.168.122.2:/test/
       scp none@192.168.122.2:/test/* ./

 - For dejagnu:

   need `echo "192.168.122.2   microblaze-xilinx-gdb" >> /etc/hosts`
   under /usr/local/share/dejagnu/*, use ssh/scp instead of rsh/rcp.
     (need replace all, or will cause failure during make check).
   for "/usr/local/share/dejagnu/baseboards/microblaze-xilinx-gdb.exp",
   need add additional variables:

     set_board_info sockethost "192.168.122.2"
     set_board_info username none
     set timeout 600



Welcome any ideas, suggestions or completions.

Thanks.

On 11/01/2014 01:09 AM, Chen Gang wrote:
> 
> At present, I use telnet (without password), login to microblaze qemu
> successfully! :-)
> 
>  - I compile busy box with the glibc in orginal 'ramfs', so get telnetd:
>    use new busybox replace the old one, and add symbol link 'telnetd' to
>    busybox in "/bin".
> 
>  - configure qemu with network support (device "xlnx.xps-ethernetlite").
> 
>    yum install libvirt
>    yum install tunctl
>    tunctl -b
>    ip link set tap0 up
>    brctl addif virbr0 tap0
>    ./microblaze-softmmu/qemu-system-microblaze -M petalogix-s3adsp1800 \
>      -kernel ../linux-stable.microblaze/arch/microblaze/boot/linux.bin \
>      -no-reboot -append "console=ttyUL0,115200 doreboot" -nographic \
>      -net nic,vlan=0,model=xlnx.xps-ethernetlite,macaddr=00:16:35:AF:94:00 \
>      -net tap,vlan=0,ifname=tap0,script=no,downscript=no
> 
>  - fix a kernel bug: add "xlnx,xps-ethernetlite-2.00.b" for compatible
>    with its firmware (can find it under "/sys/firmware..../compatible",
>    within microblaze qemu bash environments). Related diff:
> 
>    diff --git a/drivers/net/ethernet/xilinx/xilinx_emaclite.c b/drivers/net/ethernet/xilinx/xilinx_emaclite.c
>    index 28dbbdc..298fad3 100644
>    --- a/drivers/net/ethernet/xilinx/xilinx_emaclite.c
>    +++ b/drivers/net/ethernet/xilinx/xilinx_emaclite.c
>    @@ -1236,6 +1236,7 @@ static struct of_device_id xemaclite_of_match[] = {
>            { .compatible = "xlnx,opb-ethernetlite-1.01.b", },
>            { .compatible = "xlnx,xps-ethernetlite-1.00.a", },
>            { .compatible = "xlnx,xps-ethernetlite-2.00.a", },
>    +       { .compatible = "xlnx,xps-ethernetlite-2.00.b", },
>            { .compatible = "xlnx,xps-ethernetlite-2.01.a", },
>            { .compatible = "xlnx,xps-ethernetlite-3.00.a", },
>            { /* end of list */ },
> 
> Next, I shall send related kernel patch for upstream kernel, and continue
> for microbaze DejaGNU with microbaze qemu, and sorry again, I did not
> finish it within this month.
> 
> 
> Thanks.
> 
> 
> 
> On 10/30/14 22:20, Chen Gang wrote:
>> On 10/27/14 22:47, Chen Gang wrote:
>>>
>>> After a little try, I succeed run microblaze under upstream qemu 2.1.2
>>> and upstream Linux kernel 3.17-rc7, with the xilinux own ramdisk:
>>> "microblaze_complete.cpio.gz". :-)
>>>
>>> Compiler is "gcc version 4.9.1 20140717 (Red Hat Cross 4.9.1-1) (GCC)"
>>> for microblaze, and "gcc version 4.8.3 20140624 (Red Hat 4.8.3-1) (GCC)"
>>> for x86_64 qemu.
>>>
>>> Next I shall try to use virtio file to share the local data to virtual
>>> guest (I guess, it should be OK).
>>>
>>
>> I finished testing the microblaze hello world program with both dynamic
>> glibc and static glibc under qemu (I put it to 'ramfs' manualy, and it
>> runs well)  :-)
>>
>> Next, I need focus on networking (I have found qemu related device, and
>> kernel related device, and I also know, it needs telnetd in busy box).
>> But sorry, it seems I can not finish within this month :-(
>>
>>  - I wasted much time resources on choosing qemu or sim, next I should
>>    notice about it (do not waste time, again).
>>
>>  - and another excuse is: I have to do it in my free time (within 2.5
>>    hours per day, in average). My current job is not related with it
>>    (at present, it is about Global Platform Java applet for iPhone OS).
>>
>> Next month:
>>
>>  - I should finish microblaze qemu test under DejaGNU, should finish
>>    within next month (2014-11-30).
>>
>>  - I also shall start tile cross compiling for gcc/binutils, and use it
>>    to Linux kernel, and test it with qemu. I shall try to finish them
>>    within 2 months (finish before 2014-12-31).
>>
>>  - At least, finish 1 patch for gcc, 1 patch for binutils, 1 patch for
>>    qemu/kvm/xen, 3 patches for kernel, within next month (2014-11-30).
>>
>>
>> Welcome any ideas, suggestions or completions (especially for net device,
>> net drivers, busy box for telnet ...).
>>
>> Thanks.
>>
>>
>>>
>>> Thanks again!
>>>
>>>
>>>
>>> On 10/27/2014 09:47 AM, Chen Gang wrote:
>>>> On 10/26/14 21:28, Chen Gang wrote:
>>>>> Hello Guenter Roeck:
>>>>>
>>>>> I still shall try qemu and kernel distribution, next, since it can do
>>>>> it successfully (whether 'sim' can be success or not).
>>>>>
>>>>
>>>> I got confirmation from microblaze members, at present, microblaze sim
>>>> can not full simulate entire system, so I shall try qemu and kernel
>>>> distribution for it (which can do full simulation for microblaze).
>>>>
>>>> I shall try my best to finish it within this month.
>>>>
>>>> Thanks.
>>>>
>>>>> But excuse me, maybe I can not finish microblaze qemu test within this
>>>>> month, hope I can finish within next month (2014-11-30).
>>>>>
>>>>> Thank your information about qemu, again.
>>>>>
>>>>>
>>>>> Thanks.
>>>>>
>>>>> On 10/22/2014 08:28 AM, Chen Gang wrote:
>>>>>> OK, thanks, there are multiple branches in upstream qemu. Sorry
>>>>>> for my original said, and I can only say: for upstream  develop
>>>>>> master branch, it does not support microblaze.
>>>>>>
>>>>>> Excuse me, I does not mainly focus on only using qemu, and I
>>>>>> also found another easier way for test microblaze toolchain (use sim of binutils). So next, I will mainly focus on sim.
>>>>>>
>>>>>> I also met some issues for sim, but I guess, I can analyze it,
>>>>>> maybe also have chances to make patch for it (that is the main
>>>>>> reason why I want to focus on it).
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> Send from Lenovo A788t.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Guenter Roeck <linux@roeck-us.net> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Oct 21, 2014 at 06:41:14PM +0800, Chen Gang wrote:
>>>>>>> On 10/21/14 12:37, Guenter Roeck wrote:
>>>>>>>> On 10/20/2014 08:23 AM, Chen Gang wrote:
>>>>>>>>> On 10/19/2014 10:58 PM, Guenter Roeck wrote:
>>>>>>>>>>
>>>>>>>>>> This doesn't use devicetree, but the configurations are known to be working
>>>>>>>>>> with kernel releases all the way back to kernel version 3.10.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Yeah, really it is !
>>>>>>>>>
>>>>>>>>> After try upstream qemu and upstream kernel, for me, neither them can
>>>>>>>>> work well. For xilinx qemu with xilinux kernel, it should be well,
>>>>>>>>> although I still met issue below, is what I have done incorrect?
>>>>>>>>>
>>>>>>>>
>>>>>>>> Difficult to say.
>>>>>>>>
>>>>>>>> I use gcc 4.8.0 from kernel.org and qemu 2.1.2 with its default configuration
>>>>>>>> for the microblaze big endian target. No idea if that makes a difference,
>>>>>>>> but I would suggest to start with those.
>>>>>>>>
>>>>>>>> For microblazeel I use gcc 4.9.1 built with buildroot 2014.08 for both
>>>>>>>> kernel and initramfs. Initramfs for that target is built from busybox.
>>>>>>>>
>>>>>>>
>>>>>>> OK, thank you very much for your information.
>>>>>>>
>>>>>>> But sorry, I have to stop trying, because that is far from upstream qemu
>>>>>>> and upstream kernel (at present, I have no enough time resource on it).
>>>>>>>
>>>>>>> My original goal is "use upstream microblaze qemu to test upstream gcc,
>>>>>>> binutils and glibc of microblaze". And now I find another ways: "use sim
>>>>>>> which is in upstream binutils to perform the related test".
>>>>>>>
>>>>>> You lost me. qemu 2.1.2 is the upstream qemu, and I do use upstream binutils
>>>>>> (2.24 if I recall corectly) as well as upstream gcc and upstream kernel.
>>>>>> Did I indicate otherwise in anything I said ? FWIW, should be able to use
>>>>>> qemu from distributions without recompiling it.
>>>>>>
>>>>>> Thanks,
>>>>>> Guenter
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
> 


-- 
Chen Gang

Open share and attitude like air water and life which God blessed