Is anyone currently running busybox on and ARM7TDMI using NON_XIP? I have been banging my head against a wall all day because I cannot seem to get it to run correctly. I'm using the Snapgear 3.4.4 arm-linux toolchain and it compiles everything correctly for the non XIP case, all userland binaries are showing up with the "ram load" flag when running them through arm-linux-flthdr EXCEPT for busybox. For some reason, this keeps showing up with the "Has-PIC-GOT" flag and I think that this is what's causing me troubles, but I have no idea why elf2flt is throwing in this flag. All of my libraries were compiled without XIP as well, and like I said before, all my other non-busybox binaries are showing the correct flags.
My BB binary contains only one applet, ls, and only for testing. If I try to run it as is, I get a kernel bug: Unhandled fault: vector exception (0x000) at 0x00000000 Ok fine, so I try to force a ram load by running "arm-linux-flthdr -r busybox" and it adds the ram load flag in there, but I still get the kernel bug. Next, I try running arm-linux-elf2flt directly on the busybox_unstripped.gdb elf image and it gives me a FLAT file with the correct ram load flag only, but of course running THAT one gives me other errors (I also put in the kernel trace flag) /var> ./busyboxb --help BINFMT_FLAT: Loading file: ./busybox Mapping is 4e0000, Entry point is 690, data_start is fd20 Load ./busybox: TEXT=4e0040-4efd20 DATA=4efd24-4f23a4 BSS=4f23a4-4f5994 BINFMT_FLAT: reloc outside program 0x1f978 (0 - 0x15954/0xfce0), killing busybox! I'm lost now and sure could use some help/pointers. Is this a hopeless scenario? Do I HAVE to have XIP in order to use busybox? -JB _______________________________________________ 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
