第4章 起動と終了

4.1. 起動

Armadilloの電源を投入してください。次のように起動ログがシリアル通信ソフトウェアに表示されます。

Hermit-At v2.1.3 (armadillo4x0) compiled at 16:30:29, Jun 28 2011
Uncompressing  kernel......................................................................................................done.
Uncompressing ramdisk...............................................................................................................................................................................................................................................................................................................................................................................................................................................done.
Linux version 2.6.26-at15 (2.6.26) (atmark@atde3) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 PREEMPT Wed Jun 29 18:09:54 JST 2011
CPU: ARM926EJ-S [41069264] revision 4 (ARMv5TEJ), cr=00053177
Machine: Armadillo-460
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Kernel command line: console=ttymxc1,115200
MXC IRQ initialized
PID hash table entries: 512 (order: 9, 2048 bytes)
MXC GPT timer initialized, rate = 133000000
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 112768KB available (2972K code, 211K data, 128K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 480 bytes
NET: Registered protocol family 16
MXC WDOG1 Enabled
CPU is i.MX25 Revision 1.2
Clock input source is 24000000
MXC GPIO hardware
GPIO-56 autorequested
Initializing CPLD: v1
Using SDMA I.API
MXC DMA API initialized
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
MXC I2C driver
MXC I2C driver
MXC I2C driver
MC34704 regulator successfully probed
mc34704 0-0054: Loaded
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
NET: Registered protocol family 1
checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd
Freeing initrd memory: 13776K
usb: Host 2 host (serial) registered
usb: DR host (utmi) registered
msgmni has been set to 247
io scheduler noop registered
io scheduler cfq registered (default)
mx2fb: Unable to set clock to 0
Console: switching to colour frame buffer device 60x17
mxc_sdc_fb mxc_sdc_fb.0: fb0: DISP0 BG fb device registered successfully.
mxc_sdc_fb mxc_sdc_fb.0: fb1: DISP0 FG fb device registered successfully.
Serial: MXC Internal UART driver
mxcintuart.1: ttymxc1 at MMIO 0x43f94000 (irq = 32) is a Freescale MXC
console [ttymxc1] enabled
mxcintuart.2: ttymxc2 at MMIO 0x5000c000 (irq = 18) is a Freescale MXC
mxcintuart.3: ttymxc3 at MMIO 0x50008000 (irq = 5) is a Freescale MXC
mxcintuart.4: ttymxc4 at MMIO 0x5002c000 (irq = 40) is a Freescale MXC
brd: module loaded
loop: module loaded
FEC Ethernet Driver
PPP generic driver version 2.4.2
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
Driver 'sd' needs updating - please use bus_type methods
armadillo-nor: Found 1 x16 devices at 0x0 in 16-bit bank
 Intel/Sharp Extended Query Table at 0x010A
 Intel/Sharp Extended Query Table at 0x010A
 Intel/Sharp Extended Query Table at 0x010A
 Intel/Sharp Extended Query Table at 0x010A
 Intel/Sharp Extended Query Table at 0x010A
Using buffer write method
Using auto-unlock on power-up/resume
cfi_cmdset_0001: Erase suspend on write enabled
armadillo-nor: use default partitions(4)
Creating 4 MTD partitions on "armadillo-nor":
0x00000000-0x00020000 : "nor.bootloader"
0x00020000-0x00220000 : "nor.kernel"
0x00220000-0x01fe0000 : "nor.userland"
0x01fe0000-0x02000000 : "nor.config"
fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.0: irq 35, io mem 0x53ff4400
fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
fsl-ehci fsl-ehci.1: irq 37, io mem 0x53ff4000
fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
input: gpio-keys as /devices/platform/gpio-keys.0/input/input0
i2c /dev entries driver
rtc-s35390a 3-0030: rtc core: registered rtc-s35390a as rtc0
i2c-gpio i2c-gpio.3: using pins 128 (SDA) and 129 (SCL, no clock stretching)
mxsdhci: MXC Secure Digital Host Controller Interface driver
mxsdhci: MXC SDHCI Controller Driver.
mmc0: SDHCI detect irq 159 irq 9 INTERNAL DMA
Registered led device: red
Registered led device: green
Registered led device: yellow
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
i.MX ADC at 0x50030000 irq 46
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Static Power Management for Freescale i.MX25
input: imx_adc_ts as /devices/virtual/input/input1
i.MX ADC input touchscreen loaded.
rtc-s35390a 3-0030: setting system clock to 2000-01-01 00:01:34 UTC (946684894)
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 13776KiB [1 disk] into ram disk... done.
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 128K
init started:  BusyBox v1.00 (2010.11.16-08:44+0000) multi-call binary
Starting fsck for root filesystem.
fsck 1.25 (20-Sep-2001)
ext2fs_check_if_mount: No such file or directory while determining whether /dev/ram0 is mounted.
/dev/ram0: clean, 944/1136 files, 12564/13776 blocks
Checking root filesystem: done
Remounting root rw: done
Mounting proc: done
Mounting usbfs: done
Mounting sysfs: done
Cleaning up system: done
Running local start scripts.
Starting udevd: done
Loading /etc/config: done
Changing file permissions: done
Configure /home/ftp: done
Starting syslogd: done
Starting klogd: done
Starting basic firewall: done
Setting hostname: done
Configuring network interfaces: udhcpc (v0.9.9-pre) started
fec: PHY @ 0x0, ID 0x0007c0f1 -- LAN8720
Sending discover...
eth0: link down
eth0: link up, 100Mbps, full-duplex
Sending discover...
Sending select for 172.16.2.99...
Lease of 172.16.2.99 obtained, lease time 86400
done
Starting inetd: done
Setting at-cgi: done
Starting lighttpd: done
Creating avahi.services: done
Starting avahi.daemon: done
Mounting ramfs /home/ftp/pub: done

atmark-dist v1.28.2 (AtmarkTechno/Armadillo-460)
Linux 2.6.26-at15 [armv5tejl arch]

armadillo460-0 login:

図4.1 起動ログ


4.2. ログイン

起動が完了するとログインプロンプトが表示されます。表4.1「シリアルコンソールログイン時のユーザ名とパスワード」に示すユーザでログインすることができます。

表4.1 シリアルコンソールログイン時のユーザ名とパスワード

ユーザ名パスワード権限
rootrootrootユーザ
guest(なし)一般ユーザ

4.3. 終了方法

安全に終了させる場合は、次のようにコマンドを実行し、「The system is halted.」と表示されたのを確認してから電源を切断します。

[armadillo ~]# halt
[armadillo ~]#
System is going down for system reboot now.

Starting local stop scripts.
Exiting Syslogd!
Syncing all filesystems:                        done
Unmounting all filesystems:                     done
The system is going down NOW !!
Sending SIGTERM to all processes.
The system is halted. Press Reset or turn off power

図4.2 終了方法


リムーバブルディスクを使用していない場合は、電源を切断し終了させることもできます。

[警告]

リムーバブルディスクにデータを書き込んでいる途中に電源を切断した場合、ファイルシステム、及び、データが破損する恐れがあります。リムーバブルディスクをアンマウントしてから電源を切断するようにご注意ください。

4.4. リセット方法

Armadillo-460が起動している状態でSW2を押すとリセット状態となり、SW2を離すと起動が開始します。

[警告]

確実にリセットするためには、1msec以上の間SW2を押した状態にする必要があります。動作が不安定になることを防ぐため、SW2はしっかりと押してください。

[警告]

リムーバブルディスクにデータを書き込んでいる途中にSW2を押した場合、ファイルシステム、及び、データが破損する恐れがあります。リムーバブルディスクをアンマウントしてからSW2を押すようにご注意ください。