Skip to contentSkip to conversation

Status of 'unicore32' architecture in Linux kernel

DISCUSSION Guenter Roeck 3 participants 15 messages Aug 31, 2014 – Sep 9, 2014

lore
Share & tools
lore
#0 lore raw

Status of 'unicore32' architecture in Linux kernel
--------------------------------------------------

The idea was to create a working kernel and initramfs for the ongoing Linux kernel test project. This summary describes the result of this effort.

Overall, conclusion is that the architecture would need some work (both in qemu and the kernel itself) to make it testable with qemu.

Guenter

---------------------
Toolchain used was from [1]. I did not attempt to build my own toolchain.

Configuration:

make ARCH=unicore32 defconfig && make ARCH=unicore32

This configuration currently fails to build in the upstream kernel. A patch to fix the problem has been submitted and is pending upstream integration [2]. With this patch merged, the 'defconfig' image can be built.

----------------
qemu

Attempts to load the unicore32:defconfig image with qemu failed.

Research points to [3], which includes a working unicore32 linux kernel in its linux repository [4], in branch unicore32-working. This branch includes a working unicore32 qemu configuration. It also includes a critical patch which is not available in the upstream kernel.

unicore32: Add ocd console and qemu-defconfig to support qemu simulator
This patch adds a primitive OCD console to communicate with qemu. The same code is already used for early console support.

With this patch added, and with qemu_defconfig as provided by the same patch, it is possible to build and load a unicore32 image in qemu using the following qemu command line.

qemu-system-unicore32 -curses -M puv3 -m 512 -kernel arch/unicore32/boot/zImage

Caveats:
- The use of -nographic instead of -curses causes a qemu crash
- The qemu emulation only accepts a built-in initramfs.
- The only working image is arch/unicore32/boot/zImage.
All other variants, arch/unicore32/boot/Image and vmlinux, cause a crash. The same (or a similar) crash is also seen if I don't provide a built-in kernel command line and try to load zImage.
- There is no networking. There is another patch in the github linux respository [4] which is not available upstream. The driver was submitted for integration back in 2011 [5] but it was never accepted or merged.

------------------------
[1] http://mprc.pku.edu.cn/~guanxuetao/linux/
[2] https://lkml.org/lkml/2014/8/31/86
[3] https://github.com/gxt
[4] git://github.com/gxt/linux.git
[5] https://lkml.org/lkml/2011/5/27/17

#1 lore raw

Firstly, what you have done encourage me, thanks.

Quoted 6 lines · Guenter Roeck

Status of 'unicore32' architecture in Linux kernel
--------------------------------------------------

The idea was to create a working kernel and initramfs for the ongoing Linux kernel test project. This summary describes the result of this effort.

Quoted 8 lines

Overall, conclusion is that the architecture would need some work (both in qemu and the kernel itself) to make it testable with qemu.

Guenter

---------------------
Toolchain used was from [1]. I did not attempt to build my own toolchain.

I also use it, but for me, hope we can use an open source toolchain for it, in the future. If possible, I will be glad to join for it (develop open source unicore32 gcc cross compiler with other related members).

Quoted 9 lines

Configuration:

make ARCH=unicore32 defconfig && make ARCH=unicore32

This configuration currently fails to build in the upstream kernel. A patch to fix the problem has been submitted and is pending upstream integration [2]. With this patch merged, the 'defconfig' image can be built.

Thank you for what you have done.

Quoted 14 lines

----------------
qemu

Attempts to load the unicore32:defconfig image with qemu failed.

Research points to [3], which includes a working unicore32 linux kernel in its linux repository [4], in branch unicore32-working. This branch includes a working unicore32 qemu configuration. It also includes a critical patch which is not available in the upstream kernel.

unicore32: Add ocd console and qemu-defconfig to support qemu simulator
This patch adds a primitive OCD console to communicate with qemu. The same code is already used for early console support.

Quoted 6 lines

With this patch added, and with qemu_defconfig as provided by the same patch, it is possible to build and load a unicore32 image in qemu using the following qemu command line.

qemu-system-unicore32 -curses -M puv3 -m 512 -kernel arch/unicore32/boot/zImage

For me, hope they also can be merged into upstream main line, next.

Quoted 11 lines

Caveats:
- The use of -nographic instead of -curses causes a qemu crash
- The qemu emulation only accepts a built-in initramfs.
- The only working image is arch/unicore32/boot/zImage.
All other variants, arch/unicore32/boot/Image and vmlinux, cause a crash. The same (or a similar) crash is also seen if I don't provide a built-in kernel command line and try to load zImage.
- There is no networking. There is another patch in the github linux respository [4] which is not available upstream. The driver was submitted for integration back in 2011 [5] but it was never accepted or merged.

For me, suggest also Cc to [email protected], and gxt is the related maintainer for qemu unicore32, too.

In the future (maybe several months later), I am glad to try to analyze these caveats (but excuse me, at present, I have no enough time resource on it).

Quoted 6 lines

[1] http://mprc.pku.edu.cn/~guanxuetao/linux/
[2] https://lkml.org/lkml/2014/8/31/86
[3] https://github.com/gxt
[4] git://github.com/gxt/linux.git
[5] https://lkml.org/lkml/2011/5/27/17

Thanks.

Signature · 3 lines
Chen Gang

Open, share, and attitude like air, water, and life which God blessed
#2 lore raw
In reply to Guenter Roeck

Sorry for late reply.

Quoted 8 lines · ----- Guenter Roeck

Status of 'unicore32' architecture in Linux kernel
--------------------------------------------------

The idea was to create a working kernel and initramfs for the ongoing Linux kernel test project. This summary describes the result of this effort.

Overall, conclusion is that the architecture would need some work (both in qemu and the kernel itself) to make it testable with qemu.

Great. And there's a lot of work to do for unicore32.

Quoted 6 lines

Guenter

---------------------
Toolchain used was from [1]. I did not attempt to build my own toolchain.

Quoted 8 lines

Configuration:

make ARCH=unicore32 defconfig && make ARCH=unicore32

This configuration currently fails to build in the upstream kernel. A patch to fix the problem has been submitted and is pending upstream integration [2]. With this patch merged, the 'defconfig' image can be built.

Thanks. I'll apply it in my repo.

Quoted 10 lines

----------------
qemu

Attempts to load the unicore32:defconfig image with qemu failed.

Research points to [3], which includes a working unicore32 linux kernel in its linux repository [4], in branch unicore32-working. This branch includes a working unicore32 qemu configuration. It also includes a critical patch which is not available in the upstream kernel.

Yes. And these patches need to be reviewed and reconsidered. I'll try to do that in this month.

Quoted 4 lines

unicore32: Add ocd console and qemu-defconfig to support qemu simulator
This patch adds a primitive OCD console to communicate with qemu. The same code is already used for early console support.

Do you mean there's the same/similar code in QEMU.

Quoted 9 lines

With this patch added, and with qemu_defconfig as provided by the same patch, it is possible to build and load a unicore32 image in qemu using the following qemu command line.

qemu-system-unicore32 -curses -M puv3 -m 512 -kernel arch/unicore32/boot/zImage

Caveats:
- The use of -nographic instead of -curses causes a qemu crash

Yes, since qemu curses code was modified to meet the simple OCD console requirement.

Quoted 1 line

- The qemu emulation only accepts a built-in initramfs.

Yes, github version only support built-in initramfs.
NFS+LFS could be also supported, and puv3-pci sim should be added at first.

Quoted 4 lines

- The only working image is arch/unicore32/boot/zImage.
All other variants, arch/unicore32/boot/Image and vmlinux, cause a crash. The same (or a similar) crash is also seen if I don't provide a built-in kernel command line and try to load zImage.

Sorry for that. That should be fixed.

Quoted 3 lines

- There is no networking. There is another patch in the github linux respository [4] which is not available upstream. The driver was submitted for integration back in 2011 [5] but it was never accepted or merged.

Yes, exactly.
Thanks Guenter.

Quoted 7 lines

------------------------
[1] http://mprc.pku.edu.cn/~guanxuetao/linux/
[2] https://lkml.org/lkml/2014/8/31/86
[3] https://github.com/gxt
[4] git://github.com/gxt/linux.git
[5] https://lkml.org/lkml/2011/5/27/17

#3 lore raw
Quoted 22 lines · Xuetao Guan

Sorry for late reply.

Quoted 8 lines · ----- Guenter Roeck

Status of 'unicore32' architecture in Linux kernel
--------------------------------------------------

The idea was to create a working kernel and initramfs for the ongoing Linux kernel test project. This summary describes the result of this effort.

Overall, conclusion is that the architecture would need some work (both in qemu and the kernel itself) to make it testable with qemu.

Great. And there's a lot of work to do for unicore32.

Quoted 8 lines

Guenter

---------------------
Toolchain used was from [1]. I did not attempt to build my own toolchain.

Configuration:

Quoted 9 lines
Quoted 6 lines

make ARCH=unicore32 defconfig && make ARCH=unicore32

This configuration currently fails to build in the upstream kernel. A patch to fix the problem has been submitted and is pending upstream integration [2]. With this patch merged, the 'defconfig' image can be built.

Thanks. I'll apply it in my repo.

Linus already accepted the patch upstream after I sent it to him directly, so this problem has been solved by now.

Quoted 15 lines
Quoted 10 lines

----------------
qemu

Attempts to load the unicore32:defconfig image with qemu failed.

Research points to [3], which includes a working unicore32 linux kernel in its linux repository [4], in branch unicore32-working. This branch includes a working unicore32 qemu configuration. It also includes a critical patch which is not available in the upstream kernel.

Yes. And these patches need to be reviewed and reconsidered. I'll try to do that in this month.

Quoted 1 line
Quoted 6 lines
Quoted 3 lines

unicore32: Add ocd console and qemu-defconfig to support qemu simulator
This patch adds a primitive OCD console to communicate with qemu. The same code is already used for early console support.

Do you mean there's the same/similar code in QEMU.

No, I mean that the ocd functions in the linux kernel (such as ocd_putc) are used by both earlyprintk and the ocd console code.

Quoted 11 lines
Quoted 9 lines

With this patch added, and with qemu_defconfig as provided by the same patch, it is possible to build and load a unicore32 image in qemu using the following qemu command line.

qemu-system-unicore32 -curses -M puv3 -m 512 -kernel arch/unicore32/boot/zImage

Caveats:
- The use of -nographic instead of -curses causes a qemu crash

Yes, since qemu curses code was modified to meet the simple OCD console requirement.

The lack of support for -nographic is a problem for scripted testing. The issue is that we have to interpret console output for scripted testing, and having to go through curses makes that a bit difficult.

Wonder if '-nographic' can be modeled as '-curses' with no available terminal configuration. At least in theory that should work, but executing the above command with TERM=dumb yields no output. Wonder how difficult it would be to change that.

Quoted 8 lines
Quoted 1 line

- The qemu emulation only accepts a built-in initramfs.

Yes, github version only support built-in initramfs.
NFS+LFS could be also supported, and puv3-pci sim should be added at first.

Quoted 4 lines

- The only working image is arch/unicore32/boot/zImage.
All other variants, arch/unicore32/boot/Image and vmlinux, cause a crash. The same (or a similar) crash is also seen if I don't provide a built-in kernel command line and try to load zImage.

Quoted 6 lines

Sorry for that. That should be fixed.

Quoted 3 lines

- There is no networking. There is another patch in the github linux respository [4] which is not available upstream. The driver was submitted for integration back in 2011 [5] but it was never accepted or merged.

Yes, exactly.

Too bad. Not exactly necessary for our current scope of testing, but it would be nice to be able to test networking.

Quoted 2 lines

Thanks Guenter.

You are welcome. Thanks for the feedback.

Guenter

#4 lore raw

[...]

Quoted 10 lines
Quoted 8 lines
Quoted 5 lines

unicore32: Add ocd console and qemu-defconfig to support qemu simulator
This patch adds a primitive OCD console to communicate with qemu. The same code is already used for early console support.

Do you mean there's the same/similar code in QEMU.

No, I mean that the ocd functions in the linux kernel (such as ocd_putc) are used by both earlyprintk and the ocd console code.

Yes. By the way, it's only for qemu and fpga debug.

Quoted 12 lines
Quoted 6 lines
Quoted 6 lines

With this patch added, and with qemu_defconfig as provided by the same patch, it is possible to build and load a unicore32 image in qemu using the following qemu command line.

Quoted 6 lines
Quoted 4 lines

qemu-system-unicore32 -curses -M puv3 -m 512 -kernel arch/unicore32/boot/zImage

Caveats:
- The use of -nographic instead of -curses causes a qemu crash

Yes, since qemu curses code was modified to meet the simple OCD console requirement.

Quoted 8 lines

The lack of support for -nographic is a problem for scripted testing. The issue is that we have to interpret console output for scripted testing, and having to go through curses makes that a bit difficult.

Wonder if '-nographic' can be modeled as '-curses' with no available terminal configuration. At least in theory that should work, but executing the above command with TERM=dumb yields no output. Wonder how difficult it would be to change that.

I see. I'll try to make -nographic work anyway.

Quoted 11 lines
Quoted 11 lines
Quoted 2 lines

- The qemu emulation only accepts a built-in initramfs.

Yes, github version only support built-in initramfs.
NFS+LFS could be also supported, and puv3-pci sim should be added at first.

Quoted 4 lines

- The only working image is arch/unicore32/boot/zImage.
All other variants, arch/unicore32/boot/Image and vmlinux, cause a crash. The same (or a similar) crash is also seen if I don't provide a built-in kernel command line and try to load zImage.

Sorry for that. That should be fixed.

Quoted 7 lines
Quoted 4 lines
Quoted 3 lines

- There is no networking. There is another patch in the github linux respository [4] which is not available upstream. The driver was submitted for integration back in 2011 [5] but it was never accepted or merged.

Yes, exactly.

Too bad. Not exactly necessary for our current scope of testing, but it would be nice to be able to test networking.

I'll review and submit networking code again. Or, maybe pci-nic function, to support qemu as well.

Quoted 6 lines
Quoted 3 lines

Thanks Guenter.

You are welcome. Thanks for the feedback.

Guenter

Thanks.

Xuetao

#5 lore raw
Quoted 30 lines · Xuetao Guan

[...]

Quoted 10 lines
Quoted 8 lines
Quoted 5 lines

unicore32: Add ocd console and qemu-defconfig to support qemu simulator
This patch adds a primitive OCD console to communicate with qemu. The same code is already used for early console support.

Do you mean there's the same/similar code in QEMU.

No, I mean that the ocd functions in the linux kernel (such as ocd_putc) are used by both earlyprintk and the ocd console code.

Yes. By the way, it's only for qemu and fpga debug.

Quoted 16 lines
Quoted 6 lines
Quoted 6 lines

With this patch added, and with qemu_defconfig as provided by the same patch, it is possible to build and load a unicore32 image in qemu using the following qemu command line.

Quoted 6 lines
Quoted 4 lines

qemu-system-unicore32 -curses -M puv3 -m 512 -kernel arch/unicore32/boot/zImage

Caveats:
- The use of -nographic instead of -curses causes a qemu crash

Yes, since qemu curses code was modified to meet the simple OCD console requirement.

The lack of support for -nographic is a problem for scripted testing. The issue is that we have to interpret console output for scripted testing, and having to go through curses makes that a bit difficult.

Quoted 7 lines
Quoted 4 lines

Wonder if '-nographic' can be modeled as '-curses' with no available terminal configuration. At least in theory that should work, but executing the above command with TERM=dumb yields no output. Wonder how difficult it would be to change that.

I see. I'll try to make -nographic work anyway.

Another possibility would be to support "-display none". Unfortunately that also causes qemu to crash :-(.

Guenter

#6 lore raw
In reply to Xuetao Guan
Quoted 30 lines · Xuetao Guan

[...]

Quoted 10 lines
Quoted 8 lines
Quoted 5 lines

unicore32: Add ocd console and qemu-defconfig to support qemu simulator
This patch adds a primitive OCD console to communicate with qemu. The same code is already used for early console support.

Do you mean there's the same/similar code in QEMU.

No, I mean that the ocd functions in the linux kernel (such as ocd_putc) are used by both earlyprintk and the ocd console code.

Yes. By the way, it's only for qemu and fpga debug.

Quoted 16 lines
Quoted 6 lines
Quoted 6 lines

With this patch added, and with qemu_defconfig as provided by the same patch, it is possible to build and load a unicore32 image in qemu using the following qemu command line.

Quoted 6 lines
Quoted 4 lines

qemu-system-unicore32 -curses -M puv3 -m 512 -kernel arch/unicore32/boot/zImage

Caveats:
- The use of -nographic instead of -curses causes a qemu crash

Yes, since qemu curses code was modified to meet the simple OCD console requirement.

The lack of support for -nographic is a problem for scripted testing. The issue is that we have to interpret console output for scripted testing, and having to go through curses makes that a bit difficult.

Quoted 7 lines
Quoted 4 lines

Wonder if '-nographic' can be modeled as '-curses' with no available terminal configuration. At least in theory that should work, but executing the above command with TERM=dumb yields no output. Wonder how difficult it would be to change that.

I see. I'll try to make -nographic work anyway.

Please try the following patch. That seems to do it. I am sure it can be improved, but it is a start.

Thanks,
Guenter

---

Quoted 1 line

From a7c89177b3c00e4c16bea25a0b4b2f9dc511e07b Mon Sep 17 00:00:00 2001

From: Guenter Roeck <[email protected]>
Date: Tue, 2 Sep 2014 20:55:02 -0700
Subject: [PATCH] qemu: unicore32: Add support for non-curses display

Add basic support for DT_NONE and DT_NOGRAPHIC display types.

---
 target-unicore32/helper.c | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)
target-unicore32/helper.c +13 -1
index e5ebbf4..dda3772 100644
@@ -13,6 +13,7 @@
 #include "exec/gdbstub.h"
 #include "exec/helper-proto.h"
 #include "qemu/host-utils.h"
+#include "sysemu/sysemu.h"
 #ifndef CONFIG_USER_ONLY
 #include "ui/console.h"
 #endif
@@ -223,7 +224,18 @@ static void putc_on_screen(unsigned char ch)
 
 void helper_cp1_putc(target_ulong x)
 {
-    putc_on_screen((unsigned char)x);   /* Output to screen */
+    switch(display_type) {
+    case DT_CURSES:
+	putc_on_screen((unsigned char)x);   /* Output to screen */
+	break;
+    case DT_NOGRAPHIC:
+    case DT_NONE:
+	putchar((int)x);
+	break;
+    default:
+	break;
+    }
+
     DPRINTF("%c", x);                   /* Output to stdout */
 }
 #endif
Signature · 1 line
1.9.1
#7 lore raw
Quoted 36 lines · ----- Guenter Roeck
Quoted 35 lines · Xuetao Guan

[...]

Quoted 10 lines
Quoted 8 lines
Quoted 5 lines

unicore32: Add ocd console and qemu-defconfig to support qemu simulator
This patch adds a primitive OCD console to communicate with qemu. The same code is already used for early console support.

Do you mean there's the same/similar code in QEMU.

No, I mean that the ocd functions in the linux kernel (such as ocd_putc) are used by both earlyprintk and the ocd console code.

Yes. By the way, it's only for qemu and fpga debug.

Quoted 20 lines
Quoted 6 lines
Quoted 6 lines

With this patch added, and with qemu_defconfig as provided by the same patch, it is possible to build and load a unicore32 image in qemu using the following qemu command line.

Quoted 6 lines
Quoted 4 lines

qemu-system-unicore32 -curses -M puv3 -m 512 -kernel arch/unicore32/boot/zImage

Caveats:
- The use of -nographic instead of -curses causes a qemu crash

Yes, since qemu curses code was modified to meet the simple OCD console requirement.

The lack of support for -nographic is a problem for scripted testing. The issue is that we have to interpret console output for scripted testing, and having to go through curses makes that a bit difficult.

Wonder if '-nographic' can be modeled as '-curses' with no available terminal configuration. At least in theory that should work, but executing the above command with TERM=dumb yields no output. Wonder how difficult it would be to change that.

Quoted 7 lines
Quoted 2 lines

I see. I'll try to make -nographic work anyway.

Please try the following patch. That seems to do it. I am sure it can be improved, but it is a start.

Thanks,
Guenter

Thanks. I'll test it.
BTW, Qemu codestyle is different, and tab should be replaced with blanks.

Xuetao

Quoted 49 lines

---
From a7c89177b3c00e4c16bea25a0b4b2f9dc511e07b Mon Sep 17 00:00:00 2001
From: Guenter Roeck <[email protected]>
Date: Tue, 2 Sep 2014 20:55:02 -0700
Subject: [PATCH] qemu: unicore32: Add support for non-curses display

Add basic support for DT_NONE and DT_NOGRAPHIC display types.

---
 target-unicore32/helper.c | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)
target-unicore32/helper.c +13 -1
index e5ebbf4..dda3772 100644
@@ -13,6 +13,7 @@
 #include "exec/gdbstub.h"
 #include "exec/helper-proto.h"
 #include "qemu/host-utils.h"
+#include "sysemu/sysemu.h"
 #ifndef CONFIG_USER_ONLY
 #include "ui/console.h"
 #endif
@@ -223,7 +224,18 @@ static void putc_on_screen(unsigned char ch)
 
 void helper_cp1_putc(target_ulong x)
 {
-    putc_on_screen((unsigned char)x);   /* Output to screen */
+    switch(display_type) {
+    case DT_CURSES:
+	putc_on_screen((unsigned char)x);   /* Output to screen */
+	break;
+    case DT_NOGRAPHIC:
+    case DT_NONE:
+	putchar((int)x);
+	break;
+    default:
+	break;
+    }
+
     DPRINTF("%c", x);                   /* Output to stdout */
 }
 #endif
Signature · 1 line
1.9.1
#8 lore raw
Quoted 1 line · Xuetao Guan

[ ... ]

Quoted 9 lines
Quoted 5 lines

Please try the following patch. That seems to do it. I am sure it can be improved, but it is a start.

Thanks,
Guenter

Thanks. I'll test it.
BTW, Qemu codestyle is different, and tab should be replaced with blanks.

Here is where I am. User space code (busybox) was compiled using the unicore toolchain available on the web.

...
serio: i8042 KBD port at 0x6eb00060,0x6eb00064 irq 22
mousedev: PS/2 mouse device common for all mice Enable UniCore-F64 support.
Warning: unable to open an initial console. Freeing unused kernel memory: 1156K (c0408000 - c0529000)

Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

The kernel tries to execute the init program, which fails with SIGSEGV. I confirmed that the init program is loaded and starts to execute.

Any idea what might cause such a problem ?

Thanks,
Guenter

#9 lore raw
Quoted 28 lines · ----- Guenter Roeck
Quoted 1 line · Xuetao Guan

[ ... ]

Quoted 9 lines
Quoted 5 lines

Please try the following patch. That seems to do it. I am sure it can be improved, but it is a start.

Thanks,
Guenter

Thanks. I'll test it.
BTW, Qemu codestyle is different, and tab should be replaced with blanks.

Here is where I am. User space code (busybox) was compiled using the unicore toolchain available on the web.

...
serio: i8042 KBD port at 0x6eb00060,0x6eb00064 irq 22
mousedev: PS/2 mouse device common for all mice Enable UniCore-F64 support.
Warning: unable to open an initial console. Freeing unused kernel memory: 1156K (c0408000 - c0529000)

Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
Quoted 8 lines

The kernel tries to execute the init program, which fails with SIGSEGV. I confirmed that the init program is loaded and starts to execute.

Any idea what might cause such a problem ?

Thanks,
Guenter

'slink /init /bin/busybox 777 0 0' should be inserted in initramfs config
Also, I recommend compile busybox statically for initramfs.

I need more information, including full kmsg and initramfs configs

My qemu commands as following. Maybe useful.

qemu-new:

        @test -d $(DIR_WORKING)/qemu-unicore32 ||               \
                mkdir -p $(DIR_WORKING)/qemu-unicore32
        @echo "Remove old qemu repo ..."
        @rm -fr $(DIR_WORKING)/qemu
        @cd $(DIR_WORKING); git clone $(QEMU_GITREPO)
        @cd $(DIR_WORKING)/qemu;                                \
                git br unicore32 origin/unicore32;              \
                git co unicore32

qemu-make:

        @echo "Configure qemu ..."
        @cd $(DIR_WORKING)/qemu; ./configure                    \
                --enable-trace-backend=stderr                   \
                --target-list=$(QEMU_TARGETS)                   \
                --enable-debug                                  \
                --disable-sdl                                   \
                --interp-prefix=$(DIR_GNU_UC)                   \
                --prefix=$(DIR_WORKING)/qemu-unicore32          \
                >> $(QEMU_BUILDLOG) 2>&1
        @echo "Make qemu and make install ..."
        @make -C $(DIR_WORKING)/qemu -j4 >> $(QEMU_BUILDLOG) 2>&1
        @make -C $(DIR_WORKING)/qemu install >> $(QEMU_BUILDLOG) 2>&1

qemu-run:

        @echo "Remove old log file"
        @rm -fr $(QEMU_TRACELOG)
        @echo "Running QEMU in this tty ..."
        @$(DIR_WORKING)/qemu-unicore32/bin/qemu-system-unicore32\
                -curses                                         \
                -M puv3                                         \
                -m 512                                          \
                -icount 0                                       \
                -kernel $(DIR_WORKING)/zImage                   \
                -net nic                                        \
                -net tap,ifname=tap_$(USER),script=no,downscript=no     \
                -append "root=/dev/nfs nfsroot=192.168.200.161:/export/guestroot/,tcp rw ip=192.168.122.4"    \
                2> $(QEMU_TRACELOG)
#10 lore raw
Quoted 35 lines · Xuetao Guan
Quoted 33 lines · ----- Guenter Roeck
Quoted 1 line · Xuetao Guan

[ ... ]

Quoted 9 lines
Quoted 5 lines

Please try the following patch. That seems to do it. I am sure it can be improved, but it is a start.

Thanks,
Guenter

Thanks. I'll test it.
BTW, Qemu codestyle is different, and tab should be replaced with blanks.

Here is where I am. User space code (busybox) was compiled using the unicore toolchain available on the web.

...
serio: i8042 KBD port at 0x6eb00060,0x6eb00064 irq 22
mousedev: PS/2 mouse device common for all mice Enable UniCore-F64 support.
Warning: unable to open an initial console. Freeing unused kernel memory: 1156K (c0408000 - c0529000)

Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

The kernel tries to execute the init program, which fails with SIGSEGV. I confirmed that the init program is loaded and starts to execute.

Any idea what might cause such a problem ?

Quoted 8 lines
Quoted 3 lines

Thanks,
Guenter

'slink /init /bin/busybox 777 0 0' should be inserted in initramfs config
Also, I recommend compile busybox statically for initramfs.

I need more information, including full kmsg and initramfs configs

Hi,

I made everything I have available at http://server.roeck-us.net/qemu/unicore32/.
I tried multiple variants for creating the root file system, including the one on https://github.com/gxt/UniCore32.git and the one using mkrootfs.sh in the link above. No difference - I always see the same crash. Note that the 'init' program is loading, but crashes with above error (0x0000000b is SIGSEGV unless I am missing something).

Note that I used the latest qemu for unicore from upstream sources; I was unable to compile it from [email protected]:gxt/QEMU.git. Qemu configuration did not seem to make a difference. The toolchain was extracted from uc4-1.0.5-hard.tgz.

Hope this helps,
Guenter

#11 lore raw
Quoted 10 lines · ----- Guenter Roeck

On 09/04/2014 11:13 PM, Xuetao Guan wrote:
Hi,

I made everything I have available at http://server.roeck-us.net/qemu/unicore32/.
I tried multiple variants for creating the root file system, including the one on https://github.com/gxt/UniCore32.git and the one using mkrootfs.sh in the link above. No difference - I always see the same crash. Note that the 'init' program is loading, but crashes with above error (0x0000000b is SIGSEGV unless I am missing something).

Quoted 7 lines

Note that I used the latest qemu for unicore from upstream sources; I was unable to compile it from [email protected]:gxt/QEMU.git. Qemu configuration did not seem to make a difference. The toolchain was extracted from uc4-1.0.5-hard.tgz.

Hope this helps,
Guenter

I guess you used the newest kernel to run busybox.
However, as for unicore32, the newest kernel uses different ABI with uc4-1.0.5 toolchain. I'm sorry to make it so confusing.
I'll update and submit another-ABI patches asap.

Thanks,
Xutao

#12 lore raw
Quoted 16 lines · Xuetao Guan
Quoted 14 lines · ----- Guenter Roeck

On 09/04/2014 11:13 PM, Xuetao Guan wrote:
Hi,

I made everything I have available at http://server.roeck-us.net/qemu/unicore32/.
I tried multiple variants for creating the root file system, including the one on https://github.com/gxt/UniCore32.git and the one using mkrootfs.sh in the link above. No difference - I always see the same crash. Note that the 'init' program is loading, but crashes with above error (0x0000000b is SIGSEGV unless I am missing something).

Note that I used the latest qemu for unicore from upstream sources; I was unable to compile it from [email protected]:gxt/QEMU.git. Qemu configuration did not seem to make a difference. The toolchain was extracted from uc4-1.0.5-hard.tgz.

Quoted 8 lines
Quoted 3 lines

Hope this helps,
Guenter

I guess you used the newest kernel to run busybox.
However, as for unicore32, the newest kernel uses different ABI with uc4-1.0.5 toolchain. I'm sorry to make it so confusing.
I'll update and submit another-ABI patches asap.

Whatever is more recent. Guess you'll have to either update the toolchain or the kernel. If the plan is to update the kernel, can you send me a patch to do that so I can test it ?

Thanks,
Guenter

#13 lore raw
Quoted 9 lines · ----- Guenter Roeck

On 09/08/2014 05:57 AM, Xuetao Guan wrote:

Whatever is more recent. Guess you'll have to either update the toolchain or the kernel. If the plan is to update the kernel, can you send me a patch to do that so I can test it ?

Thanks,
Guenter

I'll update unicore kernel at first, and cc patches to you.

Thanks.
Xuetao

#14 lore raw
Quoted 4 lines · Xuetao Guan
Quoted 2 lines · ----- Guenter Roeck

On 09/08/2014 05:57 AM, Xuetao Guan wrote:

Quoted 9 lines
Quoted 7 lines

Whatever is more recent. Guess you'll have to either update the toolchain or the kernel. If the plan is to update the kernel, can you send me a patch to do that so I can test it ?

Thanks,
Guenter

I'll update unicore kernel at first, and cc patches to you.

Ok.

Thanks,
Guenter