
open init file in your favorite editor.If you are lucky then it would be lying in root directory. Because if your major number is not the required one then it will not invoke respective kernel functionality and in that case it will only be a junk character device.Īlso can you post the whole log file (copy all those dmesg and post those somewhere and give link here.)Īnd if you are sure that /dev/ttyS0 is there then do the following steps :įind out which init file kernel is using as parent process. I'm new to Buildroot, so any hint or suggestion is more than welcome.Įxtract rootfs and type ls -all /dev/ttyS0 and check it's major and minor number. To somehow create device(s) there (Buildroot does not do that), and then rebuild the filesystem?

Have I missed something in configuring the filesystem? Or should I use filesystem in I have checked the contents of rootfs.cpio like this: done.Ĭan't open /dev/ttyS0: No such device or address When I launch QEMU kernel boots, but then I get this message: The initrd argument in call to qemu-system-arm is pointing to Kernel is of version 3.3.7 and for the filesystem I've selected to be cpio, non-compressed. and I've configured it to create toolchain, kernel and filesystem image for ARM Cortex-A9 target. I decided to use buildroot, version 2012.05. I have managed to launch simple "Hello World" example following this instructions:īut now I want to create filesystem by myself.

Could you(or anyone reading this) take a few minutes to see if you can boot that wiki arm image it's only 3.2 MB in size if it works for you then at least I'll know that the problem is on my laptop.I am working with QEMU 1.1.0, emulating Versatile Express board with ARM Cortex-A9.

I can boot the x86 examples from qemu's wiki page just fine but not for arm. S62=00000000 s63=00000000 d31=0000000000000000Īborted (core dumped)I also tried the above using a different machine(-M integratorcp) and cpu(-cpu cortex-a8) but it just hangs with no error output at all, how can I turn on human readable debugging information for qemu.
Qemu system arm no output code#
Qemu: fatal: Trying to execute code outside RAM or ROM at 0x04000000 Pulseaudio: set_sink_input_volume() failed Code: $ QEMU_PA_SAMPLES=128 QEMU_AUDIO_DRV=pa qemu-system-arm -M vexpress-a9 -cpu cortex-a9 -m 512 -net nic,macaddr=52:54:00:fa:ce:13 -net user,hostfwd=tcp::2013-:22 -kernel zImage.integrator -initrd arm_root.img -append "root=/dev/ram" -display vnc=localhost:17
