I believe that using kgdb would be more beneficial than just kdb. Has anyone ported Kgdb updates to this Kernel?

The current release is for the 2.6.17 kernel in cvs for the kgdb project.

http://kgdb.linsyssoft.com/ is where I go for CVS access.

Also, since Daniels great work to port from 2.6.16 to 2.6.19 do you have any tricks to simplify the process? Or.....

Jimm

My CVS access in really here at sourceforge.net

:pserver;username=anonymous:kgdb.cvs.sourceforge.net:/cvsroot/kgdb

Jimm

Hello all. I am getting ready to try and install linux on my module next week. I have no problem building the kernel in SUSE Linux on my PC, but I have to reboot into this OS each time I want to work with this kit.

Can the source be built under Windows using cygwin or similar? Is anyone doing it that way? Any tips or instructions you would like to share?

Thank you.

Hi,

Does somebody still have this iso file:
imx31_ads_20070128-rel3-ltib.iso

on freescale there is now imx31_ads_20070511-rel4-ltib.iso and I get a lot of rejects if I try to apply the patch on it.

thanks,
Vali

Hi all,

We could install .iso image and build ltib successfully. Now we want to apply a patch so that we can use it for Litekit.The iso image we've used is imx31_ads_20070511-rel4-ltib.iso.
We are applying the patch linux-2.6.19.2 given at http://caiaq.org/download...9.2-mx3lite.patch.gz .

We followed the instructions from http://www.logicpd.com/su...iewtopic.php?t=1074.
We used command: patch -p1 < /tmp/linux-2.6.19.2-mx3lite.patch. But we are getting message like :
can't find file to patch at input line 144391
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -Nur linux-2.6.19.2/drivers/usb/Kconfig linux-2.6.19.2-mx31/drivers/usb/Kconfig
|--- linux-2.6.19.2/drivers/usb/Kconfig 2007-01-10 20:10:37.000000000 +0100
|+++ linux-2.6.19.2-mx31/drivers/usb/Kconfig 2007-05-26 13:16:23.000000000 +0200
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored

we are getting messages like this continuously. But some patches are getting applied. We are new to this and we dont know how to get which all files were rejected from .rej file.

Please tell us whether we are applying the patch properly and whether this particular patch can be applied to this release4 iso(imx31_ads_20070511-rel4-ltib.iso) image??

Thanks
Arjun

Posted By Arjun.KV on 9 Jul 2007 3:14 AM
Hi all,

We could install .iso image and build ltib successfully. Now we want to apply a patch so that we can use it for Litekit.The iso image we''ve used is imx31_ads_20070511-rel4-ltib.iso.
We are applying the patch linux-2.6.19.2 given at http://caiaq.org/download...9.2-mx3lite.patch.gz .

We followed the instructions from http://www.logicpd.com/su...iewtopic.php?t=1074.
We used command: patch -p1 < /tmp/linux-2.6.19.2-mx3lite.patch. But we are getting message like :
can''t find file to patch at input line 144391
Perhaps you used the wrong -p or --strip option?

As stated, you need to apply this patch against a clean linux-2.6.19.2 tree (unpatched, download from kernel.org).
The patch will apply cleanly, however, there will be an error at the end of the complile run regarding vmlinux.lds - just remove the lines the build system complains about.

Regards,
Daniel

Hi all,

We followed the steps given in the link http://www.logicpd.com/su...iewtopic.php?t=1074,
We came till loading the second stage bootloader on the board.
After excuting, the board hangs:

losh> load elf /tftp/192.168.0.121:/tftpboot/loader
loading from /tftp/192.168.0.121:/tftpboot/loader:
......
ELF section 0: download address: 0x80208000 load address: 0x800d0000
loaded 1256 @ 0x800d0000 Ram
...done
file loaded
losh> ls
R : load 1256
D : tftp 0
D : etc 0
D : dev 0
losh> load raw 0x81000000 1362216 /tftp/192.168.0.121:/tftpboot/zImage
loading from /tftp/192.168.0.121:/tftpboot/zImage:
loading raw binary to 0x81000000 (ram) len 0014c928:
...............................................................................efile loaded
losh> ls
R : load 1362216
D : tftp 0
D : etc 0
D : dev 0
losh> exec 0x800d03a8 -

Is this be because we patched on the rel-4 linux BSP rather than on the fresh inux-2.6.19.2 tree. One more thing is that the zImage generated is 1.3 MB while the one in the steps i saround 1.6MB. Also can somebody tell us what is the exact configuration to be done while executing ltib.

Regards

Hi all,

Pls ignore the above message. I started afresh.

I applied the patch given at http://caiaq.org/download...9.2-mx3lite.patch.gz against a clean linux-2.6.19.2 tree (unpatched, download from kernel.org).
We followed the steps given in the link http://www.logicpd.com/su...iewtopic.php?t=1074,

We loaded the bootloader and the zImage
We are getting the following kernel panic.(lengthy one..pls see the end)

losh> load elf /tftp/192.168.0.121:/tftpboot/loader
loading from /tftp/192.168.0.121:/tftpboot/loader:
......
ELF section 0: download address: 0x80208000 load address: 0x800d0000
loaded 1240 @ 0x800d0000 Ram
...done
file loaded
losh> load raw 0x81000000 1514816 /tftp/192.168.0.121:/tftpboot/zImage
loading from /tftp/192.168.0.121:/tftpboot/zImage:
loading raw binary to 0x81000000 (ram) len 00171d40:
............................................................................................................................efile loaded
losh> exec 0x800d03a8 -
Uncompressing Linux.................................................................................................. done, .[ 53.960000] Linux version 2.6.19.2 (imx31@192.168.0.7) (gcc version 4.1.1) #4 PREEMPT Thu Jul 19 12:58:37 IST 2007
[ 52.960000] CPU: Some Random V6 Processor [4107b364] revision 4 (ARMv6TEJ), cr=00c5387f
[ 52.960000] Machine: Freescale i.MX31 litekit
[ 52.960000] Memory policy: ECC disabled, Data cache writeback
[ 52.960000] CPU0: D VIPT write-back cache
[ 52.960000] CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
[ 52.960000] CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
[ 52.960000] Built 1 zonelists. Total pages: 28448
[ 53.960000] Kernel command line: console=ttymxc0 root=/dev/nfs nfsroot=192.168.0.121:/tftpboot/rootfs rw ip=192.168.0.12:n[ 54.960000] MXC IRQ initialized
[ 52.960000] PID hash table entries: 512 (order: 9, 2048 bytes)
[ 54.960000] Clock input source is 27000000
[ 54.960000]
[ 52.960000] WARNING: Can't generate CLOCK_TICK_RATE at 16625000 Hz
[ 54.960000] Actual CLOCK_TICK_RATE is 17264423 Hz
[ 52.960000] Console: colour dummy device 80x30
[ 52.960000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 52.960000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 54.970000] Memory: 112MB = 112MB total
[ 53.970000] Memory: 110464KB available (2512K code, 552K data, 104K init)
[ 52.180000] Mount-cache hash table entries: 512
[ 54.180000] CPU: Testing write buffer coherency: ok
[ 54.180000] NET: Registered protocol family 16
[ 54.180000] MXC GPIO hardware
[ 54.180000] system_rev is: 0x11
[ 52.180000] Irq init for eth0
[ 52.180000] L2 cache: WB
[ 52.180000] kobject_add failed for MX31ADS/MX31LITE PC (-13)
[ 54.180000] Using SDMA I.API
[ 54.180000] MXC DMA API initialized
[ 54.180000] usb: isp1504 registered
[ 54.180000] usb: Host 2 registered
[ 54.180000] usb: OTG HS Host registered
[ 54.180000] usb: OTG HS Gadget registered
[ 53.190000] SCSI subsystem initialized
[ 54.190000] MXC I2C driver
[ 54.200000] NET: Registered protocol family 2
[ 52.290000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 52.290000] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[ 52.290000] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[ 54.290000] TCP: Hash tables configured (established 4096 bind 2048)
[ 54.290000] TCP reno registered
[ 54.290000] Low-Level PM Driver module loaded
[ 52.290000] Freescale i.MX31 Dynamic Power Management.
[ 54.290000] JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
[ 54.290000] io scheduler noop registered
[ 54.290000] io scheduler anticipatory registered
[ 54.290000] io scheduler deadline registered
[ 54.290000] io scheduler cfq registered (default)
[ 54.530000] No external RTC clock
[ 52.530000] Real TIme clock Driver v1.0
[ 52.530000] mxc_rtc: probe of mxc_rtc.0 failed with error -2
[ 54.530000] MXC WatchDog Driver 2.0
[ 54.540000] MXC Watchdog # 0 Timer: initial timeout 60 sec
[ 54.540000] Serial: MXC Internal UART driver
[ 54.540000] mxcintuart.0: ttymxc0 at MMIO 0x43f90000 (irq = 45) is a Freescale MXC
[ 54.830000] mxcintuart.1: ttymxc1 at MMIO 0x43f94000 (irq = 32) is a Freescale MXC
[ 54.840000] mxcintuart.2: ttymxc2 at MMIO 0x5000c000 (irq = 18) is a Freescale MXC
[ 54.850000] mxcintuart.4: ttymxc4 at MMIO 0x43fb4000 (irq = 47) is a Freescale MXC
[ 52.860000] RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
[ 54.870000] loop: loaded (max 8 devices)
[ 54.880000] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[ 54.880000] ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
[ 54.890000] MXC: IDE driver, (c) 2004-2006 Freescale Semiconductor
[ 54.900000] mxc_ide_resetproc: resetting ATA controller
[ 54.510000] ide0: Bus empty, interface released.
[ 54.510000] MXC MTD nor Driver 2.0
[ 54.510000] mxc_nor_flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
[ 53.520000] Support for command set 0003 not present
[ 52.530000] gen_probe: No supported Vendor Command Set found
[ 52.540000] mxc_nor_flash: probe of mxc_nor_flash.0 failed with error -5
[ 54.540000] MXC MTD nand Driver 2.0
[ 54.550000] NAND device: Manufacturer ID: 0x20, Chip ID: 0x76 (ST Micro NAND 64MiB 3,3V 8-bit)
[ 54.560000] Scanning device for bad blocks
[ 52.560000] Bad eraseblock 0 at 0x00000000
[ 53.910000] Creating 4 MTD partitions on "NAND 64MiB 3,3V 8-bit":
[ 53.920000] 0x00000000-0x00200000 : "nand.kernel"
[ 53.920000] 0x00200000-0x04000000 : "nand.rootfs"
[ 53.930000] 0x00000000-0x04000000 : "<NULL>"
[ 53.940000] 0x00000000-0x04000000 : "<NULL>"
[ 54.940000] mice: PS/2 mouse device common for all mice
[ 54.950000] i2c /dev entries driver
[ 54.950000] SSI module loaded successfully
[ 52.960000] RNG Driver: Loading
[ 54.960000] SEC: mxc_sec_mod_init() called
[ 54.970000] MXC MMC/SD driver
[ 54.970000] mxcmci-0 found
[ 54.100000] oprofile: using arm/arm11
[ 54.100000] TCP cubic registered
[ 54.110000] NET: Registered protocol family 1
[ 54.110000] NET: Registered protocol family 17
[ 54.120000] ieee80211: 802.11 data/management/control stack, git-1.1.13
[ 54.120000] ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
[ 52.130000] Power Management for Freescale MX31
[ 54.140000] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 2
[ 52.150000] VFS: Cannot open root device "nfs" or unknown-block(0,255)
[ 52.150000] Please append a correct "root=" boot option
[ 48.160000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,255)
[ 52.170000]

The command line we used is "console=ttymxc0 root=/dev/nfs nfsroot=192.168.0.121:/tftpboot/rootfs rw ip=192.168.0.12::192.168.0.1:255.255.255.0 noalign".

And the /etc/export file looks like this:

#
/tftpboot/rootfs 192.168.0.12(rw,sync)

NFS server is running and when i checked with this command:
# /usr/sbin/exportfs
/home/imx31/ltib-imx31ads-20070511/rootfs
192.168.0.12

Could anyone tell us what needs to be done here?
Also since no rootfs directory was generated, i used the one which i got when i built the ADS rel4 BSP code.

Thanks

Posted By Arjun.KV on 9 Jul 2007 3:14 AM
Hi all,

[ 52.130000] Power Management for Freescale MX31
[ 54.140000] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 2
[ 52.150000] VFS: Cannot open root device "nfs" or unknown-block(0,255)
[ 52.150000] Please append a correct "root=" boot option
[ 48.160000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,255)
[ 52.170000]

The command line we used is "console=ttymxc0 root=/dev/nfs nfsroot=192.168.0.121:/tftpboot/rootfs rw ip=192.168.0.12::192.168.0.1:255.255.255.0 noalign".

And the /etc/export file looks like this:

#
/tftpboot/rootfs 192.168.0.12(rw,sync)

NFS server is running and when i checked with this command:
# /usr/sbin/exportfs
/home/imx31/ltib-imx31ads-20070511/rootfs
192.168.0.12

Could anyone tell us what needs to be done here?
Also since no rootfs directory was generated, i used the one which i got when i built the ADS rel4 BSP code.

Thanks

It seems that NFS has some problem when kernel execute
maybe you can check these items :

1. check again that you have selected the "NFS filesystem support" in kernel config
2. make sure your NFS server is work normally.
you can use another linux system to try to mount this directory that you share. In my /etc/exports , it look like some different with yours

you can reference it if you need.


Alvin

I was able to mount the root. I commented out the set command line function in bootloader.c and just included the jffs file format(which was linked as a module earlier). But then i get the following kernel panic.


[ 52.140000] Power Management for Freescale MX31
[ 54.140000] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 2
[ 52.950000] VFS: Mounted root (jffs filesystem).
[ 54.960000] Freeing init memory: 96K
[ 52.960000] Warning: unable to open an initial console.
[ 48.970000] Kernel panic - not syncing: No init found. Try passing init= option to kernel.
[ 52.980000]

The Kernel command line is :
console=ttymxc0,115200 root=/dev/mtdblock2 rw ip=off

Also tried giving init = /linuxrc, but got the message as
Failed to execute linuxrc Attempting defaults ...

Anybody faced this problem? and why am i getting the warning as unable to open an initial console, while i have initialized all the serial and non standard drivers.

Could anyone help me out in this?

Thanks

If you don't have a /dev filesystem created, then the kernel/init may not be able to find /dev/console to bind to. Make sure you either create a /dev directory with the proper device files, or use devfs and have it in the fstab of your jffs image.

Thanks everyone for all the help. Finally am able to run Linux on the litekit.

Regards
Arjun

Thanks to all generous souls!!!
We are able to run Linux on litekit.
I am currently not able to open /dev/fb0. I tried

cat test.bmp > /dev/fb0

its say
errpor /dev/fb0: No such device

Anyone able to configure LCD in linux platform ?
Please reply

Posted By motraat on 13 Aug 2007 9:37 AM
Thanks to all generous souls!!!
We are able to run Linux on litekit.
I am currently not able to open /dev/fb0. I tried

cat test.bmp > /dev/fb0

its say
errpor /dev/fb0: No such device

Anyone able to configure LCD in linux platform ?
Please reply

just do a "mknod fb0 c 29 0" in /dev, enable the mxc framebuffer in the kernel config and configure your display settings.
I got DirectFB running instantly on my litekit.

Daniel

Hello Daniel,

If I am not wrong, this patch is provided by you only. Thanks again for that. I have used .tar from linux tree. Then patched it using your target. I am not using freescale BSP.

Patch runs fine and also I am able to run my compiled programs on board.
I can see /dev/fb0 without even using following command
mknod fb0 c 29 0. But when try any thing with framebuffer, I get following message.

-sh: /dev/fb0: No such device.

Am I missing something.

I have already integrated my dispaly for freescale board on linux. I used V4L to use IPU unit in that case.

Can you provide any small utility to test in Litekit case.

regards
motraat@iss.fraunhofer.de

Posted By motraat on 13 Aug 2007 9:37 AM
Hello Daniel,

I can see /dev/fb0 without even using following command
mknod fb0 c 29 0. But when try any thing with framebuffer, I get following message.

-sh: /dev/fb0: No such device.

Then either your /dev/fb0 has wrong major/minor numbers (other than 29,0) or you did not activate the framebuffer driver in your kernel configuration. You should see apropriate messages in the dmesg log in case this code has loaded.

Writing random data to /dev/fb0 is a good test which should at least output some snow crash on the display. However, don't use /dev/random for that - it does not output anything, but I didn't have the time to track this down.

Best regards,
Daniel

Hi,

Device looks alright. I can see correct major and minor as below:

-sh-2.05b# ls -ll /dev/fb0
crw-r--r-- 1 root root 29, 0 Aug 15 2007 /dev/fb0

But nothing works on frame buffer.

-sh-2.05b# cat /dev/fb0
cat: /dev/fb0: No such device
-sh-2.05b# /usr/sbin/fbset
fbset: fbset(open): No such device

I tried to explore but no luck so far.

Another thing:
Normally we can see Choice of LCD in menuconifg-->drivers-->Graphics-->

But I could only see epson as choice Sharp does not look as one of the choice.

Also under few configurations, I got following error :

drivers/built-in.o: In function 'prpvf_stop' :
mxc_mmc.c(.text+0x3ab20): undefined reference to 'mxcfb_set_refresh_mode'

Is there any one who is using Sharp LCD and can see display?

regards
motra

For those of you successfully running Linux on the i.MX31 Litekit, what sources are you using to build the user space tools? I've been trying to build busybox, but I am getting problems regarding missing include files and libraries all over the place. Building and installing the kernel worked great though, following the instructions in this thread.

- HM

Hi HM,

Busy box and other tools are working in my case. I generated stable kernel as per directions of Daniel http://www.logicpd.com/su...viewtopic.php?t=1135 . Also I generated rootfs directory with freescale BSP and patches provided by randy http://www.logicpd.com/su...viewtopic.php?t=1074

Randy's patch is not so clean, one has to manual change many things. But he clearly mentioned what exactly needs to be changed.

- motra

Hi motra,

I too am trying to interface our Sharp LCD. But I dont even see the /dev/fbo. This is after enabling the frame buffer driver kernel. Also I dont see any message related to frame buffer in the dmesg logs.

mx31# cat /proc/devices
Character devices:
.....
29 fb
.....
mx31# mknod fb0 c 29 0
mx31# ls -l fb0
crw-r--r-- 1 root root 29, 0 Jan 1 00:03 fb0
mx31# /usr/sbin/fbset
open /dev/fb0: No such device

Were you able to solve this problem? If so please post help or atleast the dmesg log.

Regards,
Arjun