Re: qemu/m68k
Greg Ungerer <[email protected]>
| Newsgroups | gmane.linux.uclinux.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi Waldemar, On 15/08/14 00:18, Waldemar Brodkorb wrote: > Hi uClinux hackers, > > I am trying to build a Linux System for Qemu/m68k to do runtime > testing of a uClibc spin-off called uClibc-ng. > (http://www.uclibc-ng.org) > > I am really a newbie regarding MMU-less Linux systems, so don't be > to critical ;) > > My toolchain (gcc 4.8.3, binutils 2.24) seems to work, because I can > boot a kernel: > Linux version 3.15.8 (wbx@kop-brodkorbw) (gcc version 4.8.3 (GCC) ) #25 Thu Aug 14 16:09:16 CEST 2014 > uClinux/COLDFIRE(m520x) > COLDFIRE port done by Greg Ungerer, [email protected] > Flat model support (C) 1998,1999 Kenneth Albanowski, D. Jeff Dionne > Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16320 > Kernel command line: console=ttyS0,19200 ro rootfstype=tmpfs > ... > > But when init is called I got: > Starting Linux (built with OpenADK). > Freeing unused kernel memory: 1128K (4021e000 - 40338000) > qemu: fatal: Trying to execute code outside RAM or ROM at 0x0001eedc > > qemu-system-m68k --version > QEMU emulator version 2.1.0, Copyright (c) 2003-2008 Fabrice Bellard > > I am using elf2flt from git://wh0rd.org/elf2flt.git to produce flat > binaries. > $ file bin/busybox > $ bin/busybox: BFLT executable - version 4 gotpic > > Does anyone have an advice what is wrong here? > > The uClinux website have some links to a cvs repository, which are > no longer reachable. Is there a temporary problem? I don't know what happened to the CVS there. Not sure if it will be coming back. > Where does the latest version of elf2flt is available? Hmmm. Well, that is a good question. I don't know where the definitive version really is anymore. Anyway, I can give you a starting point that works for me. I have used the tools I generated at: http://www.uclinux.org/pub/uClinux/m68k-elf-tools/tools-20101118/m68k-uclinux-tools-20101118.sh for a couple of years now. They generate working systems that run on real hardware and also under qemu. The source for generating those tools is there in that same directory: http://www.uclinux.org/pub/uClinux/m68k-elf-tools/tools-20101118/ I only use it for building Coldfire targets. That is building the uclinux-dist: http://www.uclinux.org/pub/uClinux/dist/ That is a 3.10 kernel, but you can take any linus kernel and use that with the same result. The uClibc in there may have some changes over a stock 0.9.33. A good place to start debugging these types of user space problems is with the kernel trace option of flat files. So use the flthdr tool to enable the kernel trace flag (-k) on the generated flat files, then build you rootfs with those. Then at least you can see where you app is in RAM. Regards Greg _______________________________________________ uClinux-dev mailing list [email protected] http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by [email protected] To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev