Thanks for all the help so far in getting our cross compile environment going. We got it set up and successfully compiled and linked an arm executable. Now we are having download headaches-- how do we tell what is going on (both right and wrong?). This is on a brutus-- we are following the directions on the intel site (http://developer.intel.com/design/strong/applnots/sa1100lx). We expect to be able to see the kernel console using a terminal program on the host (but it's not clear to us how the kernel knows to use the com port on the brutus as the console). So far, we aren't getting anything to boot. The details: We fixed up the make file thusly, ARCH:=arm CROSS_COMPILE = arm-linux- %make config %make zImage and compiled there kernel, getting a nice zImage in arch/arm. We copied our app to the ramdisk and compressed it again to ramdisk.gz We are uing angelboot to do the download with the opt file configued with: opt file: base 0x8000 entry 0xc0008000 device /dev/ttyS0 options "9600 8N1" baud 115200 otherfile ramdisk.gz otherbase 0x800000 We connected a null modem serial cable from COM1 (/dev/tty/S0) on our linux host to port J23 on the brutus (also com1 there?) We connected another null modem serial cable from j22 on the brutus to a com port on a windows 98 machine and accessed the port using hyperterminal. Our parms here were 9600 baud n81 (we are using cheap machines, w/only one external serial port!). Kicking off angelboot downloads our ramdisk and zImage (or at least it looks like it. But no LOGON prompt comes up on our hyper terminal. I'm assumming that the boot loader should get immediate control right after angel finishes the download and nothing further should be required on our part. Any help would be much appreciated! We've tried some variations (using an uncompressed ramdisk and specifying the entry parm inthe opt file as 0xc0008020 instead of 0xc0008000 but nothing helps :( Thanks, Dave unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
