Armadilloフォーラム

Qtにてタッチパネルが認識されない

t-hara

2017年6月15日 18時24分

お世話になります。いっとうと申します。

Howto : Armadillo-440でQt! 第1回 (http://armadillo.atmark-techno.com/howto/armadillo-440-qt-1

上記を再現しようとしています。手順のRAMDISKのサイズ変更無しでsamegameの起動まで成功した
のですが、タッチパネルが認識されません。USBに何も接続していない状況で、
evtest /dev/input/event1
にてデバイスを特定しました。起動時のメッセージです。
[root@armadillo440 (ttymxc1) ~]# evtest /dev/input/event1
Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "imx_adc_ts"
Supported events:
Event type 0 (Sync)
Event type 1 (Key)
Event code 330 (Touch)
Event type 3 (Absolute)
Event code 0 (X)
Value 732
Min 100
Max 4000
Event code 1 (Y)
Value 2003
Min 100
Max 4000
Event code 24 (Pressure)
Value 0
Min 0
Max 1
Testing ... (interrupt to exit)
Event: time 946687214.025692, type 3 (Absolute), code 0 (X), value 1785
Event: time 946687214.025692, type 3 (Absolute), code 1 (Y), value 1990
Event: time 946687214.025692, type 3 (Absolute), code 24 (Pressure), value 1
Event: time 946687214.025692, type 1 (Key), code 330 (Touch), value 1
Event: time 946687214.025692, -------------- Report Sync ------------
Event: time 946687214.045673, type 3 (Absolute), code 0 (X), value 1781
Event: time 946687214.045673, type 3 (Absolute), code 1 (Y), value 1999
Event: time 946687214.045673, -------------- Report Sync ------------
Event: time 946687214.065659, type 3 (Absolute), code 0 (X), value 1796
Event: time 946687214.065659, type 3 (Absolute), code 1 (Y), value 2006
Event: time 946687214.065659, -------------- Report Sync ------------
Event: time 946687214.085654, type 3 (Absolute), code 0 (X), value 1797
Event: time 946687214.085654, type 3 (Absolute), code 1 (Y), value 2004
Event: time 946687214.085654, -------------- Report Sync ------------
Event: time 946687214.105651, type 3 (Absolute), code 24 (Pressure), value 0
Event: time 946687214.105651, type 1 (Key), code 330 (Touch), value 0
Event: time 946687214.105651, -------------- Report Sync ------------

[root@armadillo440 (ttymxc1) ~]# export QWS_MOUSE_PROTO=tslib:/dev/input/event1
[root@armadillo440 (ttymxc1) ~]# samegame -qws
selected device is not a touchscreen I understand

これを回避するにはどうしたら良いでしょうか。

コメント

お世話になります。いっとうです。

タッチパネルは未だ動作しません。tslibが有れば切り分け出来るかと思ったのですが、Qtを試すサンプルイメージにはインストールされていないようで、どうやって切り分けしていけば良いか見えない状況です。

念の為、dmesgとunameの結果を添付致します。

mmc0: no vqmmc regulator found
mmc0: SDHCI controller on sdhci-esdhc-imx25.0 [sdhci-esdhc-imx25.0] using DMA
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
i.MX ADC at 0x50030000 irq 62
usbcore: registered new interface driver snd-usb-audio
usbcore: registered new interface driver snd-usb-caiaq
armadillo4x0_wm8978 armadillo4x0_wm8978.0: wm8978-hifi <-> imx-ssi.0 mapping ok
oprofile: no performance counters
oprofile: using timer interrupt.
nf_conntrack version 0.5.0 (1922 buckets, 7688 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP: cubic registered
NET: Registered protocol family 10
ip6_tables: (C) 2000-2006 Netfilter Core Team
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 15
registered taskstats version 1
eSDHC1 Vcc: incomplete constraints, leaving on
regulator-dummy: incomplete constraints, leaving on
input: gpio-keys as /devices/platform/gpio-keys/input/input0
input: imx_adc_ts as /devices/virtual/input/input1
i.MX ADC input touchscreen loaded.
rtc-s35390a 2-0030: setting system clock to 2000-01-01 00:50:02 UTC (946687802)
ALSA device list:
#0: armadillo4x0_wm8978
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 50574KiB [1 disk] into ram disk... done.
VFS: Mounted root (ext2 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 172K (c05e4000 - c060f000)
udevd (1264): /proc/1264/oom_adj is deprecated, please use /proc/1264/oom_score_adj instead.
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
random: busybox urandom read with 47 bits of entropy available
libphy: imx25-fec-1:00 - Link is Up - 100/Full
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
random: nonblocking pool is initialized
[root@armadillo440 (ttymxc1) ~]#

[root@armadillo440 (ttymxc1) /]# uname -a
Linux armadillo440.Qt-0 3.14.36-at5 #1 PREEMPT Mon Dec 21 20:28:55 JST 2015 armv5tejl unknown

以上、よろしくお願い致します。

> お世話になります。いっとうと申します。
>
> Howto : Armadillo-440でQt! 第1回 (http://armadillo.atmark-techno.com/howto/armadillo-440-qt-1
>
> 上記を再現しようとしています。手順のRAMDISKのサイズ変更無しでsamegameの起動まで成功した
> のですが、タッチパネルが認識されません。USBに何も接続していない状況で、
> evtest /dev/input/event1
> にてデバイスを特定しました。起動時のメッセージです。
> [root@armadillo440 (ttymxc1) ~]# evtest /dev/input/event1
> Input driver version is 1.0.1
> Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
> Input device name: "imx_adc_ts"
> Supported events:
> Event type 0 (Sync)
> Event type 1 (Key)
> Event code 330 (Touch)
> Event type 3 (Absolute)
> Event code 0 (X)
> Value 732
> Min 100
> Max 4000
> Event code 1 (Y)
> Value 2003
> Min 100
> Max 4000
> Event code 24 (Pressure)
> Value 0
> Min 0
> Max 1
> Testing ... (interrupt to exit)
> Event: time 946687214.025692, type 3 (Absolute), code 0 (X), value 1785
> Event: time 946687214.025692, type 3 (Absolute), code 1 (Y), value 1990
> Event: time 946687214.025692, type 3 (Absolute), code 24 (Pressure), value 1
> Event: time 946687214.025692, type 1 (Key), code 330 (Touch), value 1
> Event: time 946687214.025692, -------------- Report Sync ------------
> Event: time 946687214.045673, type 3 (Absolute), code 0 (X), value 1781
> Event: time 946687214.045673, type 3 (Absolute), code 1 (Y), value 1999
> Event: time 946687214.045673, -------------- Report Sync ------------
> Event: time 946687214.065659, type 3 (Absolute), code 0 (X), value 1796
> Event: time 946687214.065659, type 3 (Absolute), code 1 (Y), value 2006
> Event: time 946687214.065659, -------------- Report Sync ------------
> Event: time 946687214.085654, type 3 (Absolute), code 0 (X), value 1797
> Event: time 946687214.085654, type 3 (Absolute), code 1 (Y), value 2004
> Event: time 946687214.085654, -------------- Report Sync ------------
> Event: time 946687214.105651, type 3 (Absolute), code 24 (Pressure), value 0
> Event: time 946687214.105651, type 1 (Key), code 330 (Touch), value 0
> Event: time 946687214.105651, -------------- Report Sync ------------
>
> [root@armadillo440 (ttymxc1) ~]# export QWS_MOUSE_PROTO=tslib:/dev/input/event1
> [root@armadillo440 (ttymxc1) ~]# samegame -qws
> selected device is not a touchscreen I understand
>
> これを回避するにはどうしたら良いでしょうか。
>

at_yuma.arakawa

2017年6月22日 19時56分

荒川です。

ソフトウェアの組み合わせとして、
下記ページの「フラッシュメモリイメージファイル」の
「ブートローダー」・「Linuxカーネル」・「ユーザーランド」を書き込んだ状態から、
Howtoの手順をお試しいただくと、いかがでしょうか。

- Armadillo-440 ドキュメント・ダウンロード | 組み込みLinuxのArmadilloサイト
http://armadillo.atmark-techno.com/armadillo-440/downloads-linux2-6-26

フラッシュメモリの書き換え方法は以下を参照してください。

- 第6章 フラッシュメモリの書き換え方法
http://manual.atmark-techno.com/armadillo-4x0/armadillo-400_series_soft…

お世話になっております。いっとうです。

下記件試しました。ブート時にRAMDISKが作成出来ず、kernelpanicになってしまいます。
ATDEからhermitで以下をDownloadしました。またカーネルパラメータの初期化、ブート
デバイスの初期化を実行しました。
linux-a400-1.17.bin.gz
loader-armadillo4x0-v2.2.0.bin
romfs-a440-1.12.img.gz

Hermit-At v2.2.0 (armadillo4x0) compiled at 12:00:50, Jun 04 2013
hermit>boot
Uncompressing kernel...............................................................................................................done.
Copying ramdisk.......................................................................................................................done.
Doing console=ttymxc1
Doing ramdisk_size=61440
Linux version 2.6.26-at27 (2.6.26) (atmark@atde3) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 PREEMPT Tue Sep 27 19:12:03 JST 2016
CPU: ARM926EJ-S [41069264] revision 4 (ARMv5TEJ), cr=00053177
Machine: Armadillo-440
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 ramdisk_size=61440
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: 95824KB available (3260K code, 226K 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
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: 30464K
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)
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.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
rtc-s35390a 1-0030: error resetting chip
rtc-s35390a: probe of 1-0030 failed with error -5
rtc-s35390a 2-0030: rtc core: registered rtc-s35390a as rtc0
i2c /dev entries driver
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
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
wm8978: WM8978 Audio Codec v0.2
asoc: WM8978 HiFi <-> imx-i2s-1 mapping ok
ALSA device list:
#0: armadillo440 (WM8978)
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 2-0030: setting system clock to 2000-01-01 00:17:33 UTC (946685853)
RAMDISK: Couldn't find valid RAM disk image starting at 0.
List of all partitions:
1f00 128 mtdblock0 (driver?)
1f01 2048 mtdblock1 (driver?)
No filesystem could mount root, tried: ext3 ext2 msdos vfat
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

念の為、再度Downloadしてみます。

> 荒川です。
>
> ソフトウェアの組み合わせとして、
> 下記ページの「フラッシュメモリイメージファイル」の
> 「ブートローダー」・「Linuxカーネル」・「ユーザーランド」を書き込んだ状態から、
> Howtoの手順をお試しいただくと、いかがでしょうか。
>
> - Armadillo-440 ドキュメント・ダウンロード | 組み込みLinuxのArmadilloサイト
> http://armadillo.atmark-techno.com/armadillo-440/downloads-linux2-6-26
>
> フラッシュメモリの書き換え方法は以下を参照してください。
>
> - 第6章 フラッシュメモリの書き換え方法
> http://manual.atmark-techno.com/armadillo-4x0/armadillo-400_series_soft…

お世話になっております。いっとうです。

説明書を再確認して、ブートローダーをDownload後に再起動を入れたところ、無事にタッチパネルが動作しました。
Linuxで動かそうと思うと、このデバイスではこれが限界でしょうか。

以上、よろしくお願い致します。

> お世話になっております。いっとうです。
>
> 下記件試しました。ブート時にRAMDISKが作成出来ず、kernelpanicになってしまいます。
> ATDEからhermitで以下をDownloadしました。またカーネルパラメータの初期化、ブート
> デバイスの初期化を実行しました。
> linux-a400-1.17.bin.gz
> loader-armadillo4x0-v2.2.0.bin
> romfs-a440-1.12.img.gz
>
> Hermit-At v2.2.0 (armadillo4x0) compiled at 12:00:50, Jun 04 2013
> hermit>boot
> Uncompressing kernel...............................................................................................................done.
> Copying ramdisk.......................................................................................................................done.
> Doing console=ttymxc1
> Doing ramdisk_size=61440
> Linux version 2.6.26-at27 (2.6.26) (atmark@atde3) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 PREEMPT Tue Sep 27 19:12:03 JST 2016
> CPU: ARM926EJ-S [41069264] revision 4 (ARMv5TEJ), cr=00053177
> Machine: Armadillo-440
> 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 ramdisk_size=61440
> 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: 95824KB available (3260K code, 226K 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
> 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: 30464K
> 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)
> 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.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
> rtc-s35390a 1-0030: error resetting chip
> rtc-s35390a: probe of 1-0030 failed with error -5
> rtc-s35390a 2-0030: rtc core: registered rtc-s35390a as rtc0
> i2c /dev entries driver
> 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
> 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
> wm8978: WM8978 Audio Codec v0.2
> asoc: WM8978 HiFi <-> imx-i2s-1 mapping ok
> ALSA device list:
> #0: armadillo440 (WM8978)
> 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 2-0030: setting system clock to 2000-01-01 00:17:33 UTC (946685853)
> RAMDISK: Couldn't find valid RAM disk image starting at 0.
> List of all partitions:
> 1f00 128 mtdblock0 (driver?)
> 1f01 2048 mtdblock1 (driver?)
> No filesystem could mount root, tried: ext3 ext2 msdos vfat
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
>
> 念の為、再度Downloadしてみます。
>
>
>
> > 荒川です。
> >
> > ソフトウェアの組み合わせとして、
> > 下記ページの「フラッシュメモリイメージファイル」の
> > 「ブートローダー」・「Linuxカーネル」・「ユーザーランド」を書き込んだ状態から、
> > Howtoの手順をお試しいただくと、いかがでしょうか。
> >
> > - Armadillo-440 ドキュメント・ダウンロード | 組み込みLinuxのArmadilloサイト
> > http://armadillo.atmark-techno.com/armadillo-440/downloads-linux2-6-26
> >
> > フラッシュメモリの書き換え方法は以下を参照してください。
> >
> > - 第6章 フラッシュメモリの書き換え方法
> > http://manual.atmark-techno.com/armadillo-4x0/armadillo-400_series_soft…