Hey all;
Three things below:
1. Comprehensive 'howto' writeup from me - a solid start 2. Lessons learned comments on Martin Guy's recipe 3. Boot problem with hardware clock and ttyAM0 ------------------------------------------------
1. Howto steps are written up here: (Posted externally to share)
in seven parts: 1) Hardware & Host Computer Configuration 2) Debian SD card configuration of 2.4.26 3) NFS / Debian server configuration 4) Build custom TS-7260 kernel 5) Create initial rootfs, boot, and complete debian installation 6) Post install configuration 7) Create bootable SD card (work in progress, reply to the forum topic or this ts-7000 post with suggestions and I will include)
- This step: debootstrap/debootstrap --second-stage emptied my /etc/apt/sources.list. Had to re-instate.
- After booting with init=/bin/sh: sync; exit # exits single-user shell, halting the machine. exiting from single user mode causes a kernel panic "attempting to kill init" sync; reboot -f seems to work better. Also, doesn't /sbin/init act weird (like teleinit?) if its pid != 1?
- This step: sh /etc/init.d/rc.local which assumes ntpdate has been added to /etc/rc.local, won't work unless the line is added to the "start)" case in rc.local. Other systems I use don't have hardly anything in rc.local, yet the one here has a usage guardian "case" statement in it.
3. Boot problem:
Got that 2.6.32.3 kernel patched, built, and single-user booted per Matthieu, yeehah and thanks again Peter, et al! I also ran 'make modules_install' on the boostrapped root fs. But neither my kernel nor chitte's will not boot normally (init=/sbin/init) due to troubles finding the Hardware Clock & setting up ttyAM0
"Cannot access the Hardware Clock via any known method."
Our TS-7260 has the realtime clock option aka: (OP-BBRTC Battery Backed Real Time Clock) installed so I have the feeling I missed something. I searched around a bit on ts-7000 and Google, found some hits. Any clues? (boot messages are below).
It's odd, as an earlier boot message seems happy:
"rtc-m48t86 rtc-m48t86: setting system clock to 2010-08-04 22:18:26 UTC (1280960306)"
Other symptoms are that the crond init takes *forever* (could be related). Also there is this message (from both chitte's kernel and mine) that will repeat forever until I pull the power cord: (Search of ts-7000 reveals that this message is famous!!) Remember I have a TS-SER2 board attached.
INIT: Id "S0" respawning too fast: disabled for 5 minutes
cat /etc/inittab gives these pertinent lines:
# TS-7260's serial port S0:23:respawn:/sbin/getty 115200 ttyAM0 vt102
Slowly gettin' 'er done folks, muchas muchas gracias.
- Clark
BOOT MESSAGES for init=/sbin/init
Uncompressing Linux.......................................................................................................................... .... done, booting the kernel. Linux version 2.6.32.3-m (gcc version 3.4.4 (release) (CodeSourcery ARM 2005q3-2)) #1 PREEMPT Wed Aug 4 14:40:02 PDT 2010 CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177 CPU: VIVT data cache, VIVT instruction cache Machine: Technologic Systems TS-72xx SBC Memory policy: ECC disabled, Data cache writeback Built 1 zonelists in Zone order, mobility grouping on. Total pages: 9040 Kernel command line: console=ttyAM0,115200 rw ip=dhcp init=/sbin/init root=/dev/nfs nfsroot=172.18.131.69:/home/qf/Desktop/rootdeb PID hash table entries: 256 (order: -2, 1024 bytes) Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) Memory: 8MB 8MB 8MB 8MB 8MB 8MB 8MB 8MB = 64MB total Memory: 60748KB available (3552K code, 298K data, 112K init, 0K highmem) Hierarchical RCU implementation. NR_IRQS:120 VIC @fefb0000: id 0x00041190, vendor 0x41 VIC @fefc0000: id 0x00041190, vendor 0x41 Console: colour dummy device 80x30 Calibrating delay loop... 99.73 BogoMIPS (lpj=498688) Security Framework initialized Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 ep93xx: PLL1 running at 400 MHz, PLL2 at 192 MHz ep93xx: FCLK 200 MHz, HCLK 100 MHz, PCLK 50 MHz M2P DMA subsystem initialized bio: create slab <bio-0> at 0 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 2048 (order: 2, 16384 bytes) TCP bind hash table entries: 2048 (order: 1, 8192 bytes) TCP: Hash tables configured (established 2048 bind 2048) TCP reno registered NET: Registered protocol family 1 RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. NetWinder Floating Point Emulator V0.97 (double precision) msgmni has been set to 118 alg: No test for stdrng (krng) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) Serial: AMBA driver apb:uart1: ttyAM0 at MMIO 0x808c0000 (irq = 52) is a AMBA console [ttyAM0] enabled apb:uart2: ttyAM1 at MMIO 0x808d0000 (irq = 54) is a AMBA apb:uart3: ttyAM2 at MMIO 0x808e0000 (irq = 55) is a AMBA ts72xx-sdcard ts72xx-sdcard.0: SD card hardware revision: 00000000 ts72xx-sdcard ts72xx-sdcard.0: block device major number = 254 ts72xx-sdcard ts72xx-sdcard.0: New SD card detected, name=tssda size=3842048 (sectors) tssda: tssda1 tssda2 tssda3 tssda4 Searching for NAND flash... NAND device: Manufacturer ID: 0xec, Chip ID: 0x75 (Samsung NAND 32MiB 3,3V 8-bit) Scanning device for bad blocks cmdlinepart partition parsing not available Using static partition definition Creating 3 MTD partitions on "ts7250-nand": 0x000000000000-0x000000004000 : "TS-BOOTROM" 0x000000004000-0x000001d04000 : "Linux" 0x000001d04000-0x000002000000 : "RedBoot" ep93xx-eth version 0.12 loading eth0: ep93xx on-chip ethernet, IRQ 39, 00:d0:69:42:de:51. ep93xx_mii_bus: probed Generic PHY 0:01: PHY supports MII frame preamble suppression net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, irq=-1) net eth0: ep93xx on-chip ethernet, IRQ 39, 00:d0:69:42:de:51 ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver ep93xx-ohci ep93xx-ohci: EP93xx OHCI ep93xx-ohci ep93xx-ohci: new USB bus registered, assigned bus number 1 ep93xx-ohci ep93xx-ohci: irq 56, io mem 0x80020000 usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: EP93xx OHCI usb usb1: Manufacturer: Linux 2.6.32.3-m ohci_hcd usb usb1: SerialNumber: ep93xx usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 3 ports detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. mice: PS/2 mouse device common for all mice ep93xx-rtc ep93xx-rtc: rtc core: registered ep93xx-rtc as rtc0 rtc-m48t86 rtc-m48t86: rtc core: registered m48t86 as rtc1 rtc-m48t86 rtc-m48t86: battery ok i2c-gpio i2c-gpio.0: using pins 14 (SDA) and 15 (SCL) cpuidle: using governor ladder Registered led device: platform:grled Registered led device: platform:rdled usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver TCP cubic registered NET: Registered protocol family 17 rtc-m48t86 rtc-m48t86: setting system clock to 2010-08-04 22:18:26 UTC (1280960306) usb 1-1: new full speed USB device using ep93xx-ohci and address 2 usb 1-1: New USB device found, idVendor=15d3, idProduct=5504 usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 usb 1-1: configuration #1 chosen from 1 choice Sending DHCP requests ., OK IP-Config: Got DHCP answer from 0.0.0.0, my address is 172.18.131.56 IP-Config: Complete: device=eth0, addr=172.18.131.56, mask=255.255.255.0, gw=172.18.131.254, host=172.18.131.56, domain=stellarsolutions.local, nis-domain=(none), bootserver=0.0.0.0, rootserver=172.18.131.69, rootpath= Looking up port of RPC 100003/2 on 172.18.131.69 Looking up port of RPC 100005/1 on 172.18.131.69 PHY: 0:01 - Link is Up - 100/Full VFS: Mounted root (nfs filesystem) on device 0:13. Freeing init memory: 112K INIT: version 2.86 booting Setting the system clock. Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. Unable to set System Clock to: Wed Aug 4 22:18:37 UTC 2010 (warning). Activating swap...done. Setting the system clock. Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. Unable to set System Clock to: Wed Aug 4 22:18:39 UTC 2010 (warning). Cleaning up ifupdown.... Loading kernel modules...done. Checking file systems...fsck 1.41.3 (12-Oct-2008) done. Setting kernel variables (/etc/sysctl.conf)...done. Mounting local filesystems...failed. Activating swapfile swap...done. Setting up networking.... Configuring network interfaces...done. INIT: Entering runlevel: 2 Starting enhanced syslogd: rsyslogd. Starting periodic command scheduler: crond. INIT: Id "S0" respawning too fast: disabled for 5 minutes INIT: no more processes left in this runlevel
On Aug 4, 2010, at 4:55 AM, Petr Štetiar wrote: Dave Cramer <> [2010-08-04 07:19:39]:
> On this topic, I've tried building OE on centos which does not have all of
> the latest packages.
Sorry, I don't know much about CentOS. I would install something usable to
chroot, probably with debootstrap or something similar.
> What is the best distro to build OE on ? Are there any detailed instructions
> on getting the distro up and running on the ts7000 ? Specifically changing
> the filesystem etc ?
The best of course, is the working one :-) Try to read this[1]. I for example
use Debian/Ubuntu.
I don't know about detailed instructions for OE and ts7xxx, and I think it
isn't even necessary. Just read the general OE/Angstrom[2] docs[3],
tutorials[4] and you should be fine. With OE, I simply don't care if I build
something for Beagleboard, ts7xxx or GTA01.
What do you mean by changing filesystem? Flashing the JFFS2(or any other)
image onto NAND? If so, wouldn't it be better to build tar.gz image of rootfs
using OE and than mount it over NFS so you can test it and tweak it? Than if
it's ok, flash it?
1. http://wiki.openembedded.net/index.php/OEandYourDistro
2. http://www.angstrom-distribution.org/
3. http://www.angstrom-distribution.org/building-angstrom
4. http://www.angstrom-distribution.org/simplified-development-setup
-- ynezz
__._,_.___
![]()
__,_._,___
|