Hi, i have tried embedian but iam very unhappy with the packet support there... So i am going to install Debian for arml.... Anyone some experience with that? (uboot and kernel is already setted up and rootfs will be on a sdhc card) Yours Andreas
Try this: http://blog.leshak.ru/english/pages/how-to-install-debian-50-lenny-to-ar... That worked for me on ext2 fs, I have some problems with using ext3 on sd/sdhc though.
Thx for your reply... I have managed to install it on a 2GB SD-CARD... i have made some mknode /dev/input/ts c ... mknode /dev/input/mice c ... mknode /dev/input/rtc c ... but the nodes will disapear after a reboot.... i have also installed x11 with jwm ... and tslib xserver-input-evtouch and here i have the problem the touch is accurate but i cannot "click" with the touch any ideas about my 2 problems? Yours Andreas
I tried, but I'm confused -- a lot. I installed u-boot so when I boot from nand I get the MINI2440 # prompt. I wrote zImage_t35 into kernel, or so I thought but ... U-Boot 1.3.2-mini2440 (Oct 6 2009 - 12:51:09) I2C: ready DRAM: 64 MB Flash: 2 MB NAND: 64 MiB Found Environment offset in OOB.. USB: S3C2410 USB Deviced In: serial Out: serial Err: serial MAC: 08:08:11:18:12:27 Hit any key to stop autoboot: 0 Loading from NAND 64MiB 3,3V 8-bit, offset 0x60000 ** Unknown image type Wrong Image Format for bootm command ERROR: can't get kernel image! On top of that, I tried to follow the link for making a Debian SD card. Do I really need a 32 GB card? Any help would be much appreciated. Thanks, Dave
z_Image_t35 loaded with u-boot? U-boot ONLY loads uImages.
For my Linux/Debian test i have used a 2GB SD-Card. I am playing at the moment with the mjpgstreamer. I would like to use the x11 server but i am tun unexperienced to get the touch running correctly... and uBoot is for uImages. Yours Andreas b.t.w. does anyone has download the new DVD from arm9.net and would be so kind to mirror it? ARM9.NET is so terrible slow about 5kb/sec ...
Thanks for the help. I only found zImages on this site. Do I have to roll my own kernel to get a uImage? That will keep me busy for the rest of this year. DaveS
Well, I found and installed the mkimage program and used it to convert zImage to uImage. And I was able to flash uImage and the kernel starts working, but then it panics. VFS: Cannot open root device "mtdblock3" or unknown-block(31,3) I may have screwed up the environment variables. Is there a way to restore them? Thanks DaveS
While in minicom do a <printenv> and show us the results.
MINI2440 # printenv
bootdelay=3
baudrate=115200
ethaddr=08:08:11:18:12:27
serverip=10.0.0.4
netmask=255.255.255.0
usbtty=cdc_acm
mtdparts=mtdparts=mini2440-nand:256k@0(u-boot),128k(env),5m(kernel),-(root)
mini2440=mini2440=0tb
bootargs_base=console=ttySAC0,115200 noinitrd
bootargs_init=init=/sbin/init
root_nfs=/mnt/nfs
set_root_nfs=setenv root_nfs root=/dev/nfs rw
nfsroot=${serverip}:${root_nfs}
ifconfig_static=run setenv ifconfig
ip=${ipaddr}:${serverip}::${netmask}:mini24400
ifconfig_dhcp=run setenv ifconfig ip=dhcp
ifconfig=ip=dhcp
set_bootargs_mmc=setenv bootargs ${bootargs_base} ${bootargs_init}
${mini2440} ${}
set_bootargs_nand=setenv bootargs ${bootargs_base} ${bootargs_init}
${mini2440} $}
set_bootargs_nfs=run set_root_nfs; setenv bootargs ${bootargs_base}
${bootargs_in}
mtdids=nand0=mini2440-nand
filesize=266864
bootcmd=nboot.e kernel ; bootm
root_nand=/dev/mtdblkp3
rootfstype=jffs2
root=/dev/mmcblk0p4
gatewayip=192.168.8.254
root_mmc=/dev/mmcblkp4
ipaddr=192.168.8.77
bootargs=root=/dev/mtdblock3 rootfstype=jffs2 console=ttySAC0,115200
mini2440=1tb
partition=nand0,0
mtddevnum=0
mtddevname=u-boot
Environment size: 1162/131068 bytes
MINI2440 #
Thanks, DaveS
I got rid of some of the environment variables and now have:
---------------------------------------
printenv
bootdelay=3
baudrate=115200
ethaddr=08:08:11:18:12:27
serverip=10.0.0.4
netmask=255.255.255.0
usbtty=cdc_acm
mtdparts=mtdparts=mini2440-nand:256k@0(u-boot),128k(env),5m(kernel),-(root)
mini2440=mini2440=0tb
bootargs_base=console=ttySAC0,115200 noinitrd
bootargs_init=init=/sbin/init
ifconfig_static=run setenv ifconfig
ip=${ipaddr}:${serverip}::${netmask}:mini2440:eth0
ifconfig_dhcp=run setenv ifconfig ip=dhcp
ifconfig=ip=dhcp
set_bootargs_mmc=setenv bootargs ${bootargs_base} ${bootargs_init}
${mini2440} ${root_mmc}
set_bootargs_nand=setenv bootargs ${bootargs_base} ${bootargs_init}
${mini2440} ${root_nand}
mtdids=nand0=mini2440-nand
gatewayip=192.168.8.254
ipaddr=192.168.8.77
filesize=266864
bootcmd=nboot.e kernel ; bootm
root_mmc=/dev/mmcblk0p4
bootargs=root=/dev/mmcblk0p4 rootfstype=jfs console=ttySAC0,115200
mini2440=1tb
partition=nand0,0
mtddevnum=0
mtddevname=u-boot
Environment size: 883/131068 bytes
----------------------------------------------------
And get this panic message:
VFS: Cannot open root device "mmcblk0p4" or unknown-block(179,4)
Please append a correct "root=" boot option; here are the available
partitions:
1f00 256 mtdblock0 (driver?)
1f01 128 mtdblock1 (driver?)
1f02 5120 mtdblock2 (driver?)
1f03 60032 mtdblock3 (driver?)
1f04 65536 mtdblock4 (driver?)
b300 1931264 mmcblk0 driver: mmcblk
b301 8192 mmcblk0p1
b302 8192 mmcblk0p2
b303 8192 mmcblk0p3
b304 1906560 mmcblk0p4
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(179,4)
The SD card, partition 4, has a root file system that boots on another ARM9
device, Technologic Systems TS-7800), and it mounts fine on my Linux
desktop, so it looks like it can actually find the card. The files on there
came from debrootstrap.
It appears you are doing something I am not familiar with , IE mmcbblk0p4. The only thing that seems odd to me is you are saying: bootargs=root=/dev/mmcblk0p4 rootfstype=jfs console=ttySAC0,115200 rather than rootfstype=jffs2? in the last posting. What root file system type have you got on the SD card? You are not using the 3.5" display?
Here's the command that made the file system on my Thinkpad. mkfs.jfs -L DebRoot /dev/mmcblk0p4 I tried changing the rootfstype=jffs, but that didn't change anything. Maybe the kernel on the mini2440 doesn't support jfs format. I installed mkfs.jffs2 using synaptic (in mtd-utils). I'll try that next. I will be using the display, and may have to use an angstrom kernel later. I'm not sure exactly what I'm doing - sort of like a lot of monkeys trying to type a novel. I want to use a debian base because I like apt-get. I'd like to get lenny running for the latest stuff. And I need Python 2.5+. On top of that I want a graphics toolkit that supports primitive functions without a lot of overhead - something with directfb support? That's a pretty big wishlist for someone who hasn't yet gotten past a kernel panic. Any suggestions are much appreciated. DaveS
"rootfstype=jffs" perhaps you meant jffs2. Had to read up about JFS. Interesting, but isn't YAFFS good enough or does JFS have some special features? The kernel appears to support JFS, but it does need to be enabled # CONFIG_JFS_FS is not set in the out-of-box configuration file. I assume you have read about booting from SD cards on buserror's site? Suggestions? Have you tried following some of the links on the wiki page, especially: http://labs.kernelconcepts.de/Projects/Micro2440/ I would get rootfs working in NAND before trying to do it on a SD card.
For a simple test use a EXT3 Formated SD-CARD and compile your kernel with EXT3 support. Than expand the whole Qtopia arm image on that card... thats the way i am using my mini. But of course i would be happier if i could have that in the NAND flash of the board. to let uboot boot the rootfs from a sd card i have done this: bootcmd=nboot.e kernel ; bootm bootdelay=1 bootargs=root=/dev/mmcblk0p2 rootwait=4 rw ip=192.168.50.230 init=/sbin/init noinitrd console=ttySAC0,115200 But a simple question anyway can i format a SD card with the yaffs2 filesystem? And if yes, how? I think the yaffs2 FS is more better than the EXT3 on an SD-CARD. Yours Andreas
I also have tried many times to install debian lenny with the YAFFS2 filesystem onto the on-board flash but it doesn't work because of the same errors as above (the filesystem driver question). Therefor I made a complete root filesystem for armel on a chrooted debian. The settings I made with "make menuconfig" seems to be correct and I also have cross-compiled without errors (kernel/zImage and modules that I have copied in the root filesystem later). Then I have created the root filesystem for armel with debootstrap in the debian i686 chroot and installed the compiled drivers and modules in the right places. I also have copied the kernel zImage in the boot directory of the armel root filesystem. Standard debian applications where also installed by debootstrap before. Last but not least I made mkyaffs2image (the yaffs2 converter tool) onto the directory where the armel root filesystem is in and uploaded it onto the on-board flash into partition "root" with supervivi after I have formated it with vivi. I also uploaded the zImage on the kernel partition. The upload and partition process I did in "NOR"-state and the boot test in "NAND"-state of the flash switch. Can somebody please tell me what I did wrong? And how I can make it working? Thanks! PS: I have set the boot options in vivi to "noinitrd rootfstype=yaffs2 mini2440=0tb init=/sbin/init". The kernel has successfully detected network card, touchscreen, card slot, leds, backlight, ...
It is working for me as I have used vboot instead of supervivi now :)
I have attached a nice screenshot of the messages on the display but the quality isn't that good (yeah, I have patched the kernel to version 2.6.32.10 with "ketchup"). In the next time I will report some more things about the progress. My plans are much bigger than only install debian lenny as it is now. I think its a good starting point because apt/dpkg is available. That are the greatest tools! YAFFS2 also works fine as filesystem base and its verry fast :) I want to make german keyboard layout, networking and apt working at first. Then a user interface (like IceWM), gtk2 and small media applications like xmms and internet radio tuner programs and maybe more.
After I reconfigured and reinstalled the kernel, nothing works anymore :( Something is wrong in my kernel configuration but it will take verry long to figure it out... Damn! I have to start again but I know what I need to make better now ;)