第5章 起動と終了

5.1. 起動

Armadillo-IoTに電源を接続すると、シリアル通信ソフトウェアには次のように表示されます。

Hermit-At v3.3.0 (armadillo-iotg-std) compiled at 10:41:18, Dec 08 2014
hermit> 

図5.1 電源投入直後のログ


Linuxシステムを起動するには、次のように "boot"コマンドを実行してください。コマンドを実行するとブートローダーがLinuxシステムを起動させます。シリアル通信ソフトウェアにはLinuxの起動ログが表示されます。

hermit> boot
Uncompressing  kernel...........................................................
.........................................................done.
Uncompressing ramdisk...........................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
..............................................................................do
ne.
Linux version 2.6.26-at21 (2.6.26) (atmark@atde5) (gcc version 4.6.3 (Debian 4.6
.3-14atmark1) ) #1 PREEMPT Sun Dec 14 13:40:35 JST 2014
CPU: ARM926EJ-S [41069264] revision 4 (ARMv5TEJ), cr=00053177
Machine: Armadillo-410
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: 72992KB available (3432K code, 235K data, 124K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 624 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
GPIO-6 autorequested
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
i2c-gpio i2c-gpio.3: using pins 17 (SDA) and 18 (SCL, no clock stretching)
i2c-gpio i2c-gpio.4: using pins 66 (SDA) and 65 (SCL, no clock stretching)
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 a
n initrd
Freeing initrd memory: 52993K
usb: Host 2 host (serial) registered
usb: DR host (utmi) registered
msgmni has been set to 246
io scheduler noop registered
io scheduler cfq registered (default)
Serial: MXC Internal UART driver
mxcintuart.1: ttymxc1 at MMIO 0x43f94000 (irq = 32) is a Freescale MXC
console [ttymxc1] enabled
brd: module loaded
loop: module loaded
FEC Ethernet Driver
PPP generic driver version 2.4.2
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver net1080
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
usbcore: registered new interface driver sierra_net
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-0x00420000 : "nor.kernel"
0x00420000-0x01f00000 : "nor.userland"
0x01f00000-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.
usbcore: registered new interface driver usbserial
usbserial: USB Serial Driver core
usbserial: USB Serial support registered for Sierra USB modem
usbcore: registered new interface driver sierra
sierra: USB Driver for Sierra Wireless USB modems: v.1.7.40
input: gpio-keys as /devices/platform/gpio-keys.0/input/input0
input: gpio-keys-polled as /devices/virtual/input/input1
rtc-s35390a 3-0030: rtc core: registered rtc-s35390a as rtc0
i2c /dev entries driver
adc081c 3-0054: ADC081C021/027 driver probed
mxsdhci: MXC Secure Digital Host Controller Interface driver
mxsdhci: MXC SDHCI Controller Driver.
mmc0: SDHCI detect irq 159 irq 9 INTERNAL DMA
mxsdhci: MXC SDHCI Controller Driver.
mmc1: SDHCI detect irq 71 irq 8 INTERNAL DMA
Registered led device: led1
Registered led device: led2
Registered led device: led3
Registered led device: led4
Registered led device: yellow
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.16.
usbcore: registered new interface driver snd-usb-audio
usbcore: registered new interface driver snd-usb-caiaq
ASoC version 0.13.2
ALSA device list:
  No soundcards found.
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 10
NET: Registered protocol family 17
NET: Registered protocol family 15
Static Power Management for Freescale i.MX25
rtc-s35390a 3-0030: setting system clock to 2000-01-01 00:01:48 UTC (946684908)
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 52993KiB [1 disk] into ram disk... done.
usb 1-1: new full speed USB device using fsl-ehci and address 2
usb 1-1: not running at top speed; connect to a high speed hub
usb 1-1: config 1 has an invalid interface number: 7 but max is 5
usb 1-1: config 1 has no interface number 5
usb 1-1: configuration #1 chosen from 1 choice
sierra 1-1:1.0: Sierra USB modem converter detected
usb 1-1: Sierra USB modem converter now attached to ttyUSB0
sierra 1-1:1.1: Sierra USB modem converter detected
usb 1-1: Sierra USB modem converter now attached to ttyUSB1
sierra 1-1:1.2: Sierra USB modem converter detected
usb 1-1: Sierra USB modem converter now attached to ttyUSB2
sierra 1-1:1.3: Sierra USB modem converter detected
usb 1-1: Sierra USB modem converter now attached to ttyUSB3
sierra 1-1:1.4: Sierra USB modem converter detected
usb 1-1: Sierra USB modem converter now attached to ttyUSB4
usb0: register 'sierra_net' at usb-fsl-ehci.0-1, Sierra Wireless USB-Ethernet Mo
dem, 56:4d:db:fc:01:07
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 124K
Mounting proc: done
Starting fsck for root filesystem.
fsck 1.25 (20-Sep-2001)
/dev/ram0: clean, 2461/2968 files, 47898/52993 blocks
Checking root filesystem: done
Remounting root rw: 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
Mounting devpts: done
Starting syslogd: done
Starting klogd: done
Loading kernel module: awl13_sdio
awl13: Version 3.0.2 Load.
Starting basic firewall: done
Setting hostname: done
Configuring network interfaces: fec: PHY @ 0x0, ID 0x0007c0f1 -- LAN8720
udhcpc (v1.20.2) started
eth0: link up, 100Mbps, full-duplex
Sending discover...
Sending select for 192.0.2.100...
Lease of 192.0.2.100 obtained, lease time 86400
done
Starting inetd: done
Starting lighttpd: done
Creating avahi.services: done
Starting avahi.daemon: done
Mounting ramfs /home/ftp/pub: done
Running local start script (/etc/config/rc.local).

atmark-dist v1.36.0 (AtmarkTechno/Armadillo-IoTG-Std)
Linux 2.6.26-at21 [armv5tejl arch]

armadillo-iotg login: 

図5.2 起動ログ


[ティップ]

Armadillo-IoTの起動状態をユーザーLEDから確認することができます。このため、Armadillo-IoTにUSBシリアル変換アダプタを接続せずに電源を投入した場合でも、Linuxの起動を確認することができます。

起動状態LED1LED2LED3LED4
ブートローダーが保守モード点灯消灯消灯消灯
Linuxの起動中点灯点灯消灯消灯
Linuxが起動完了点灯消灯消灯消灯

5.2. ログイン

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

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

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

5.3. 終了方法

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

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

Starting local stop scripts.
Syncing all filesystems: done
Unmounting all filesystems: done
The system is going down NOW!
Sent SIGTERM to all processes
Sent SIGKILL to all processes
Requesting system halt
System halted.

図5.3 終了方法


SDカードなどのストレージをマウントしていない場合は、電源を切断し終了させることもできます。

[警告]

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