For others on the list, I finally was able to get my 7260 to boot to the SD card with a locally built kernel image. I think the secret was to build the "Image" target (I was building zImage), and ensure your boot cmd line options are correct. TS tech support did a great writeup for me, see it at:
ftp://oz.embeddedarm.com/ts-arm-sbc/ts-7260-linux/sources/ts-7260_kernel_compile_guide.txt
Hope this can help some others out there.
On Mon, Apr 19, 2010 at 12:35 PM, smachin1000 <> wrote:
--- In ts-7000%40yahoogroups.com, "j.chitte" <> wrote:
>
>
>
> --- In ts-7000%40yahoogroups.com, fred basset <fredbasset1000@> wrote:
> >
> > Hi All,
> >
> > I just tried rebuilding the latest stock 2.4 kernel downloaded from
> > the TS website (tskernel-2.4.26-ts11-src.tar.gz) using the cross
> > compile tools also from their website (gcc-3.4.4-glibc-2.3.2).
> >
> > To test the whole process out I thought I'd compile the kernel without
> > doing any modifications. So I did:
> >
> > make ts7260_config
> > make oldconfig
> > make dep
> > make bzImage
> > make modules INSTALL_MOD_PATH=/lib/modules
> >
> > then dd'ed the zImage file to the first partition on my SD card. My
> > kernel does not boot all the way however, see the boot msgs below.
> > What did I do wrong? Would be super grateful for any help.
> >
> > Thanks,
> > Fred
> >
>
> You copied the kernel , where do you think the modules ended up?
>
Thanks for the response. I did not copy over the modules yet as I didn't think there'd be any change in their functionality, given I was trying to compile to stock kernel using the pre-configured 7260 kernel config. I will try copying them over tonight to see if it makes a difference. I thought my problem may be a bit more fundamental than that, given it couldn't mount the root FS. I have the board configured to boot to the SD card if that makes any difference.
>
> > ---------------------------------------------
> > >> TS-SDBOOT - built Aug 10 2009
> > >> Copyright (c) 2007, Technologic Systems
> > .
> > .
> > .
> > Linux version 2.4.26-ts11 (gcc version 3.4.4) #1 Sun Apr
> > 18 08:38:42 PDT 2010
> > CPU: Arm920Tid(wb) revision 0
> > Machine: ep9301
> > Ignoring unrecognised tag 0x54410001
> > Ignoring unrecognised tag 0x54410002
> > Ignoring unrecognised tag 0x54410002
> > Ignoring unrecognised tag 0x54410002
> > Ignoring unrecognised tag 0x54410002
> > Ignoring unrecognised tag 0x54410002
> > Ignoring unrecognised tag 0x54410002
> > Ignoring unrecognised tag 0x54410002
> > Ignoring unrecognised tag 0x54410002
> > Ignoring unrecognised tag 0x54420005
> > On node 0 totalpages: 2048
> > zone(0): 2048 pages.
> > zone(1): 0 pages.
> > zone(2): 0 pages.
> > Kernel command line: root=/dev/mtdblock1 console=ttyAM0,115200
> > Console: colour dummy device 80x30
> > Calibrating delay loop... 99.94 BogoMIPS
> > Memory: 8MB = 8MB total
> > Memory: 4316KB available (1202K code, 338K data, 84K init)
> > Dentry cache hash table entries: 1024 (order: 1, 8192 bytes)
> > Inode cache hash table entries: 512 (order: 0, 4096 bytes)
> > Mount cache hash table entries: 512 (order: 0, 4096 bytes)
> > Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
> > Page-cache hash table entries: 2048 (order: 1, 8192 bytes)
> > CPU: Testing write buffer: pass
> > POSIX conformance testing by UNIFIX
> > Linux NET4.0 for Linux 2.4
> > Based upon Swansea University Computer Society NET3.039
> > Initializing RT netlink socket
> > Starting kswapd
> > devfs: v1.12c (20020818) Richard Gooch
> > devfs: boot_options: 0x1
> > ttyAM0 at MMIO 0x808c0000 (irq = 52) is a AMBA
> > ttyAM1 at MMIO 0x808d0000 (irq = 54) is a AMBA
> > ttyAM2 at MMIO 0x808e0000 (irq = 55) is a AMBA
> > pty: 1024 Unix98 ptys configured
> > Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ enabled
> > ttyS00 at 0x89c003f8 (irq = 40) is a 16550A
> > Real Time Clock Driver v1.10f
> > ep93xx_eth() version: ep93xx_eth.c: V1.0 09/04/2003 Cirrus Logic
> > RAMDISK driver initialized: 16 RAM disks of 12288K size 1024 blocksize
> > Searching for NAND flash...
> > NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB
> > 3,3V 8-bit)
> > Scanning device for bad blocks
> > Bad eraseblock 0 at 0x00000000
> > Bad eraseblock 1 at 0x00020000
> > Bad eraseblock 232 at 0x01d00000
> > Bad eraseblock 414 at 0x033c0000
> > Using static partition definition
> > Creating 3 MTD partitions on "NAND 128MiB 3,3V 8-bit":
> > 0x00000000-0x00004000 : "TS-BOOTROM"
> > mtd: partition "TS-BOOTROM" doesn't end on an erase block -- force read-only
> > 0x00004000-0x07d04000 : "Linux"
> > mtd: partition "Linux" doesn't start on an erase block boundary --
> > force read-only
> > 0x07d04000-0x08000000 : "RedBoot"
> > mtd: partition "RedBoot" doesn't start on an erase block boundary --
> > force read-only
> > NET4: Linux TCP/IP 1.0 for NET4.0
> > IP Protocols: ICMP, UDP, TCP, IGMP
> > IP: routing cache hash table of 512 buckets, 4Kbytes
> > TCP: Hash tables configured (established 512 bind 1024)
> > NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> > NetWinder Floating Point Emulator V0.97 (double precision)
> > Kernel panic: VFS: Unable to mount root fs on 1f:01
> >
>
__._,_.___
![]()
__,_._,___ |