Forum Discussion
uClinux without Flash (again)
I decided to give uClinux a try on my custom board, but I only have an SD card slot, no CFI. When reading the install guide for uClinux, and when trying it, it won't let me build a kernel project without a CFI device present? Is there any way to get around this? It seems odd that I can't build the kernel and run from DRAM, and then write to the SD Card if I wish to boot...
Thx!58 Replies
- Altera_Forum
Honored Contributor
I agree, I want to stick with linux now, no more IDE except for downloading - but I definitely don't know how to build the filesystem from scratch.
Should I just create an empty directory, and then create the following directories: /bin /sbin /etc /dev /usr /var /tmp /proc /sys I don't understand how to create entries in the /dev directory - the only device I need for now is the JTAG UART (I think) - so how do I create an entry for this? What other entries in /dev do I need? Once I do that, I can create an /etc/inittab file like you said.. Then I have to get busybox working, correct? I was able to do a make menuconfig in Cygwin in the busybox directory, but I couldn't get it in linux... should I follow the instructions on MArcs page for busybox, or should I copy it from the examples apps directory in windows??? Then onc eI have it in linux, I should be able to add any apps using the menu and do a make; make install. I did this all in windows, but I would like to do it in linux too (keep it simple like you said). So correct me if I'm wrong, but /init is automatically executed when the root initramfs is mounted, correct? and /sbin/init will be built by busybox... and init uses /etc/inittab to do more stuff?? How is the login console started then? I will try and get busybox building in linux now... can I just download from the busybox site, or is there a special build for nios2? --- Quote Start --- originally posted by hippo@Nov 28 2005, 08:07 PM cheer!!about the root fs, it should be better to build it by hand. it is simple and clean.
i would prefer doing all the works in a shell console, instead of the ide.
the ide may add something unpredictable.
you should build everything in console, and back to ide when you download and test.
you can borrow a lot from slackware/initrd, in tranditional linux life style.
setup all the dirs, bin,sbin,etc,dev,usr,usr/bin,var,tmp,proc,sys ...
check if you have all the devices you will use, zero,null,console ( and hda,hda1... etc)
it maybe missing /dev/console that give you the warning.
setup the install path to your root fs in busybox menuconfig. and make install, it will copy and
setup the symlinks.
add a symlink /init to /sbin/init for initramfs to work.
and a very simple inittab,
# startup the file system
null::sysinit:/bin/mount -t proc proc /proc
null::sysinit:/bin/mount -t sysfs sysfs /sys
# busybox console
::askfirst:/bin/sh
you should be sitting in front of busybox prompt now.
about the apps, i would prefer add them to busybox.
it saves space and troubles.
<div align='right'><{post_snapback}> (index.php?act=findpost&pid=11221)
--- quote end ---
--- Quote End ---
- Altera_Forum
Honored Contributor
To create the file system, some reading from the "linux from scratch" will help.
It is simple, just mkdir of all of them. And copy some of the dev nodes from you linux host. Eg, cp -a /dev/console /dev/zero /dev/null .... uc_rootfs/dev You don't need the jtag device, because it is registered as "/dev/console". From boot, the kernel mount initramfs as root, execute /init, which is symlink to /sbin/init, and symlink to busybox, it reads /etc/inittab. The line in my sample inittab, ::askfirst:/bin/sh execute the /bin/sh on console, and was symlink to busybox (msh). Freeing unused kernel memory: 272k freed (0x138000 - 0x17b000) init started: BusyBox v1.00-pre8 (2005.10.28-01:02+0000) multi-call binary Please press Enter to activate this console. BusyBox v1.00-pre8 (2005.10.28-01:02+0000) Built-in shell (msh) Enter 'help' for a list of built-in commands.# ls bin etc init mnt proc sbin tmp var dev home lib opt root sys usr# To build busybox, you can use the altera/kits/nios2/examples/softeware/linux/busybox. It should the same as marc's. Do "zip -r and unzip -a" to convert CRLF. make menuconfig, make, make install. I was using marc's buildroot. I will check if we have to build uclibc before busybox. You could also try marc's page. - Altera_Forum
Honored Contributor
ya, that's the busybox I tried building earlier today - I will copy it over to linux just like the kernel tree. So I guess I need to know if I need uclibc also?? ANd when I run make, that make is the host make, not nios2-elf-gcc correct (as in not make ARCH=nios2nommu ...)??
--- Quote Start --- originally posted by hippo@Nov 28 2005, 09:39 PM to create the file system, some reading from the "linux from scratch" will help.it is simple, just mkdir of all of them. and copy some of the dev nodes from you linux host.
eg, cp -a /dev/console /dev/zero /dev/null .... uc_rootfs/dev
you don't need the jtag device, because it is registered as "/dev/console".
from boot, the kernel mount initramfs as root, execute /init, which is symlink to /sbin/init,
and symlink to busybox, it reads /etc/inittab.
the line in my sample inittab,
::askfirst:/bin/sh
execute the /bin/sh on console, and was symlink to busybox (msh).
freeing unused kernel memory: 272k freed (0x138000 - 0x17b000)
init started: busybox v1.00-pre8 (2005.10.28-01:02+0000) multi-call binary
please press enter to activate this console.
busybox v1.00-pre8 (2005.10.28-01:02+0000) built-in shell (msh)
enter 'help' for a list of built-in commands.# ls
bin etc init mnt proc sbin tmp var
dev home lib opt root sys usr#
to build busybox, you can use the altera/kits/nios2/examples/softeware/linux/busybox.
it should the same as marc's. do "zip -r and unzip -a" to convert crlf.
make menuconfig, make, make install.
i was using marc's buildroot. i will check if we have to build uclibc before busybox.
you could also try marc's page.
<div align='right'><{post_snapback}> (index.php?act=findpost&pid=11225)
--- quote end ---
--- Quote End ---
- Altera_Forum
Honored Contributor
Yes, we need uClibc first. Read the uClibc/INSTALL. I am doing it on a slackware host.
It is not easy to do it without buildroot. I have resoled the compile prolem in buildroot, which you had before. The kernel header must be set to 2.6.9 in menuconfig. I have tested it in slackware 10.2. After the buildroot done, you can follow the marc's page to build busybox. I have tested the examples/software/linux/busybox, and it works too. First copy the config file to .config, edit the paths in Makefile,Rules.mk, for $(APP_PLUGIN),$(UCLIBC_PLUGIN), just as marc' page said. Then make menuconfig, make, make install. Below is my .config of buildroot, # # Automatically generated make config: don't edit# BR2_HAVE_DOT_CONFIG=y# BR2_arm is not set# BR2_armeb is not set# BR2_cris is not set# BR2_i386 is not set# BR2_m68k is not set# BR2_mips is not set# BR2_mipsel is not set BR2_nios2=y# BR2_powerpc is not set# BR2_sh is not set# BR2_sparc is not set BR2_ARCH="nios2" # # Build options# BR2_WGET="wget --passive-ftp" BR2_SVN="Subversion (svn) checkout command"# BR2_TAR_VERBOSITY is not set BR2_STAGING_DIR="$(BUILD_DIR)/staging_dir" BR2_JLEVEL=1 # # Toolchain Options# # # Kernel Header Options# # BR2_KERNEL_HEADERS_2_4_25 is not set# BR2_KERNEL_HEADERS_2_4_27 is not set# BR2_KERNEL_HEADERS_2_4_29 is not set BR2_KERNEL_HEADERS_2_6_9=y# BR2_KERNEL_HEADERS_2_6_10 is not set# BR2_KERNEL_HEADERS_2_6_11 is not set BR2_DEFAULT_KERNEL_HEADERS="2.6.9" # # uClibc Options# # BR2_UCLIBC_VERSION_SNAPSHOT is not set# BR2_ENABLE_LOCALE is not set # # Binutils Options# # BR2_BINUTILS_VERSION_2_14_90_0_8 is not set BR2_BINUTILS_VERSION_2_15=y# BR2_BINUTILS_VERSION_2_15_94_0_2_2 is not set# BR2_BINUTILS_VERSION_2_16 is not set# BR2_BINUTILS_VERSION_2_16_90_0_1 is not set# BR2_BINUTILS_VERSION_2_16_90_0_2 is not set# BR2_BINUTILS_VERSION_2_16_90_0_3 is not set BR2_BINUTILS_VERSION="2.15" # # Gcc Options# # BR2_GCC_VERSION_3_3_3 is not set# BR2_GCC_VERSION_3_3_5 is not set# BR2_GCC_VERSION_3_4_2 is not set BR2_GCC_VERSION_3_4_3=y# BR2_GCC_VERSION_4_0_0 is not set# BR2_GCC_VERSION_4_1_0 is not set BR2_GCC_VERSION="3.4.3" BR2_GCC_USE_SJLJ_EXCEPTIONS="" BR2_EXTRA_GCC_CONFIG_OPTIONS=""# BR2_INSTALL_LIBSTDCPP is not set# BR2_INSTALL_OBJC is not set # # Ccache Options# BR2_CCACHE=y # # Gdb Options# # BR2_PACKAGE_GDB is not set# BR2_PACKAGE_GDB_SERVER is not set# BR2_PACKAGE_GDB_CLIENT is not set # # elf2flt# BR2_ELF2FLT=y # # Common Toolchain Options# # BR2_ENABLE_MULTILIB is not set BR2_LARGEFILE=y BR2_TARGET_OPTIMIZATION="-Os -pipe" # # Package Selection for the target# # # The default minimal system# # BR2_PACKAGE_BUSYBOX is not set # # The minimum needed to build a uClibc development system# # BR2_PACKAGE_BASH is not set# BR2_PACKAGE_BZIP2 is not set# BR2_PACKAGE_COREUTILS is not set# BR2_PACKAGE_DIFFUTILS is not set# BR2_PACKAGE_ED is not set# BR2_PACKAGE_FINDUTILS is not set# BR2_PACKAGE_FLEX is not set# BR2_PACKAGE_GAWK is not set# BR2_PACKAGE_GCC_TARGET is not set# BR2_PACKAGE_CCACHE_TARGET is not set# BR2_PACKAGE_GREP is not set# BR2_PACKAGE_MAKE is not set# BR2_PACKAGE_PATCH is not set# BR2_PACKAGE_SED is not set# BR2_PACKAGE_TAR is not set # # Other stuff# # BR2_PACKAGE_AUTOCONF is not set# BR2_PACKAGE_AUTOMAKE is not set# BR2_PACKAGE_BERKELEYDB is not set# BR2_PACKAGE_BISON is not set# BR2_PACKAGE_BOA is not set# BR2_PACKAGE_CUSTOMIZE is not set# BR2_PACKAGE_ISC_DHCP is not set# BR2_PACKAGE_DIRECTFB is not set# BR2_PACKAGE_DISTCC is not set# BR2_PACKAGE_DNSMASQ is not set# BR2_PACKAGE_DROPBEAR_SSHD is not set# BR2_PACKAGE_E2FSPROGS is not set# BR2_PACKAGE_FAKEROOT is not set# BR2_PACKAGE_FILE is not set# BR2_PACKAGE_FREETYPE is not set# BR2_PACKAGE_GETTEXT is not set# BR2_PACKAGE_GZIP is not set# BR2_PACKAGE_HOSTAP is not set# BR2_PACKAGE_HOTPLUG is not set# BR2_PACKAGE_IPROUTE2 is not set# BR2_PACKAGE_IPTABLES is not set# BR2_PACKAGE_JPEG is not set# BR2_PACKAGE_LESS is not set# BR2_PACKAGE_LIBELF is not set# BR2_PACKAGE_LIBFLOAT is not set# BR2_PACKAGE_LIBGLIB12 is not set# BR2_PACKAGE_LIBMAD is not set# BR2_PACKAGE_LIBPCAP is not set# BR2_PACKAGE_LIBPNG is not set# BR2_PACKAGE_LIBSYSFS is not set# BR2_PACKAGE_LIBTOOL is not set# BR2_PACKAGE_LINKS is not set# BR2_PACKAGE_LRZSZ is not set# BR2_PACKAGE_LTP-TESTSUITE is not set# BR2_PACKAGE_LZO is not set# BR2_PACKAGE_M4 is not set# BR2_PACKAGE_MICROCOM is not set# BR2_PACKAGE_MICROPERL is not set# BR2_PACKAGE_MICROWIN is not set# BR2_PACKAGE_MKDOSFS is not set# BR2_PACKAGE_MPG123 is not set# BR2_PACKAGE_MROUTED is not set# BR2_PACKAGE_MTD is not set# BR2_PACKAGE_NANO is not set# BR2_PACKAGE_NCURSES is not set# BR2_PACKAGE_NETKITBASE is not set# BR2_PACKAGE_NETKITTELNET is not set# BR2_PACKAGE_NETSNMP is not set# BR2_PACKAGE_NEWT is not set# BR2_PACKAGE_NTP is not set# BR2_PACKAGE_OPENSSH is not set# BR2_PACKAGE_OPENSSL is not set# BR2_PACKAGE_OPENVPN is not set# BR2_PACKAGE_PCIUTILS is not set# BR2_PACKAGE_PORTAGE is not set# BR2_PACKAGE_PORTMAP is not set# BR2_PACKAGE_PPPD is not set# BR2_PACKAGE_PROCPS is not set# BR2_PACKAGE_PYTHON is not set# BR2_PACKAGE_RAIDTOOLS is not set# BR2_READLINE is not set# BR2_PACKAGE_RSYNC is not set# BR2_PACKAGE_RXVT is not set# BR2_PACKAGE_SFDISK is not set# BR2_PACKAGE_SLANG is not set# BR2_PACKAGE_SOCAT is not set# BR2_PACKAGE_STRACE is not set# BR2_PACKAGE_TCPDUMP is not set# BR2_PACKAGE_TFTPD is not set# BR2_PACKAGE_TINYLOGIN is not set# BR2_PACKAGE_TINYX is not set# BR2_PACKAGE_TN5250 is not set# BR2_PACKAGE_TTCP is not set# BR2_PACKAGE_UDEV is not set# BR2_PACKAGE_UDHCP is not set# BR2_PACKAGE_UTIL-LINUX is not set# BR2_PACKAGE_VALGRIND is not set# BR2_PACKAGE_VTUN is not set# BR2_PACKAGE_WGET is not set# BR2_PACKAGE_WHICH is not set# BR2_PACKAGE_WIRELESS_TOOLS is not set# BR2_PACKAGE_XORG is not set# BR2_PACKAGE_ZLIB is not set # # Target Options# # BR2_TARGET_ROOTFS_CRAMFS is not set# BR2_TARGET_ROOTFS_EXT2 is not set# BR2_TARGET_ROOTFS_JFFS2 is not set# BR2_TARGET_ROOTFS_SQUASHFS is not set# BR2_TARGET_ROOTFS_TAR is not set # # Board Support Options# # # Generic System Support# # BR2_TARGET_GENERIC_ACCESS_POINT is not set# BR2_TARGET_GENERIC_FIREWALL is not set# BR2_TARGET_GENERIC_DEV_SYSTEM is not set - Altera_Forum
Honored Contributor
Ok - so I built busybox using the examples directory in windows - I just did it in windows for now because I couldn't get linux working yet. It built fine, and I installed it into a directory in my kernel build tree. so here is what I have:
In /bin I have: -rwxr-xr-x 1 jdhar vpgrp 259100 2005-11-29 10:21 busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:31 cat -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:32 chgrp -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:32 chmod -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:32 chown -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:32 cp -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:32 dd -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:32 dmesg -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:32 echo -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:32 false -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:32 kill -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:32 ln -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:32 ls -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:32 mkdir -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:32 mknod -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:33 more -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:32 mount -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:32 msh -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:32 mv -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:32 ps -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:33 pwd -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:33 rm -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:33 rmdir -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:32 sh -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:32 sync -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:33 touch -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:33 true -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:33 umount -> busybox* lrwxrwxrwx 1 jdhar vpgrp 7 2005-11-29 10:32 uname -> busybox* In /dev I have a lot, but some important ones: @console,c,5,1 @null,c,1,3 @ttyJ0,c,232,16 for /sbin, I copied agetty.exe from the IDE to /sbin/agetty: -rwxr-xr-x 1 jdhar vpgrp 55212 2005-11-28 14:36 agetty* lrwxrwxrwx 1 jdhar vpgrp 14 2005-11-29 10:33 fdisk -> ../bin/busybox* lrwxrwxrwx 1 jdhar vpgrp 14 2005-11-29 10:33 freeramdisk -> ../bin/busybox* lrwxrwxrwx 1 jdhar vpgrp 14 2005-11-29 10:33 init -> ../bin/busybox* lrwxrwxrwx 1 jdhar vpgrp 14 2005-11-29 10:33 insmod -> ../bin/busybox* lrwxrwxrwx 1 jdhar vpgrp 14 2005-11-29 10:33 klogd -> ../bin/busybox* lrwxrwxrwx 1 jdhar vpgrp 14 2005-11-29 10:33 logread -> ../bin/busybox* lrwxrwxrwx 1 jdhar vpgrp 14 2005-11-29 10:33 lsmod -> ../bin/busybox* lrwxrwxrwx 1 jdhar vpgrp 14 2005-11-29 10:34 pivot_root -> ../bin/busybox* lrwxrwxrwx 1 jdhar vpgrp 14 2005-11-29 10:34 rmmod -> ../bin/busybox* lrwxrwxrwx 1 jdhar vpgrp 14 2005-11-29 10:34 syslogd -> ../bin/busybox* In /, I have a link to /sbin/init And in /etc, I have two files: inittab and rc.. my inittab is: # Startup the file system# null::sysinit:/bin/mount -t proc proc /proc# null::sysinit:/bin/mount -t sysfs sysfs /sys ::sysinit:/bin/sh /etc/rc # busybox console ttyJ0::respawn:/sbin/agetty 115200 ttyJ0 ::askfirst:/bin/sh and /etc/rc is just an echo so I can see something... I still get the warning - can't open console message. Is there any way to see if init is even being called?? - Altera_Forum
Honored Contributor
Ok, so here's some other news... I got buildroot to build with the flags you told me to set. Let me see if I understand this much:
- buildroot generates a toolchain which is basically similar to the toolchain I was using off the NIOS II Linux CD, however, this is nios2-linux-uclibc... and the other was nios2-elf-gcc...?? - I can use either to build the kernel the same way I have been doing, it's just I guess the buildroot toolchain requires an extra step to convert the vmlinux file to a .bin file that can be downloaded??? - /buildroot/build_nios2/root <-- this is the root filesystem that I will want initramfs to use?? - I should use busybox and set the target to /buildroot/build_nios2/root so it can populate it with applications?? - Now busybox requires uclibc... is that something I have to download again, because buildroot already used it, didn't it? Do I have to setup the environment somehow to know where uclibc is?? One thing I don't understand is how the nodes in /dev are created since it doesn't seem that busybox does that, or buildroot... - Altera_Forum
Honored Contributor
--- Quote Start --- originally posted by jdhar@Nov 30 2005, 03:32 AM ok, so here's some other news... i got buildroot to build with the flags you told me to set. let me see if i understand this much:- buildroot generates a toolchain which is basically similar to the toolchain i was using off the nios ii linux cd, however, this is nios2-linux-uclibc... and the other was nios2-elf-gcc...?? --- Quote End --- Yes, they are the same compiler. Only the default link library differ. <div class='quotetop'>QUOTE </div> --- Quote Start --- - I can use either to build the kernel the same way I have been doing, it's just I guess the buildroot toolchain requires an extra step to convert the vmlinux file to a .bin file that can be downloaded???[/b] --- Quote End --- Yes, you can use either. You can convert a vmlinux, which is an ELF format , to binary for programming the flash with the objcopy command.
<div class='quotetop'>QUOTE </div> --- Quote Start --- - /buildroot/build_nios2/root <-- this is the root filesystem that I will want initramfs to use??[/b] --- Quote End --- Yes, you should copy them to another place to be used as your root fs. Remove usr/include usr/lib to save space. <div class='quotetop'>QUOTE </div> --- Quote Start --- - I should use busybox and set the target to /buildroot/build_nios2/root so it can populate it with applications??[/b] --- Quote End --- Yes, "make install" will populate it. <div class='quotetop'>QUOTE </div> --- Quote Start --- - Now busybox requires uclibc... is that something I have to download again, because buildroot already used it, didn't it? Do I have to setup the environment somehow to know where uclibc is??[/b] --- Quote End --- The buildroot builds the uclibc already. So you don't have to download again. If you use marc's patch, update Makefile,Rules.mak, seach barco and change to your staging_dir. If you use examples///busybox, and the following three line to the beginning of Rules.mak .nios2-linux-uclibc-objcopy -O binary vmlinux vmlinux.bin
And in staging_dir , add symlink scripts --> lib, in staging_dir/bin, add symlink elf2flt --> nios2-linux-uclibc-elf2flt . Note, you must prepare a initial .config for busybox before menuconfig. <div class='quotetop'>QUOTE </div> --- Quote Start --- One thing I don't understand is how the nodes in /dev are created since it doesn't seem that busybox does that, or buildroot...[/b] --- Quote End --- Either use "mknod" to create them, or copy them from your Linux host.STAGING_DIR = /usr/local/src/buildroot/build_nios2/staging_dir UCLIBC_PLUGIN = $(STAGING_DIR) APP_PLUGIN = $(STAGING_DIR)cp -a /dev/zero /dev/null /dev/console rootfs/dev - Altera_Forum
Honored Contributor
Ok, here's what I did:
buildroot: followed the instructions on Marcs page, no problems here, it build the nios2 toolchain in the staging directory along with some sort of root filesystem. I copied this file system to a separate place busybox: I used the config file off his home page, modified the patch file to point to my staging directory instead, and compiled - created the busybox executable with no problems. Ran make install and it copied it to my new root fs directory... I then did the cp -a on all the /dev entries you listed, so those are now in my root directory, and I created the symlink to /sbin/init I haven't modified inittab at all since buildroot created this <--- should I do this??? Kernel: Built the kernel using the new toolchain this time, not the Nios 2 linux CD one... And it worked!!! I added the ::askfirst::.. line to inittab, and I got the busybox shell. I'm not sure how others got all of this working in windows, but I'm glad I finally got it in linux... thanks for all your help, I think this thread is definitely big enough! http://forum.niosforum.com/work2/style_emoticons/<#EMO_DIR#>/smile.gif - Altera_Forum
Honored Contributor
Great!! http://forum.niosforum.com/work2/style_emoticons/<#EMO_DIR#>/laugh.gif
<div class='quotetop'>QUOTE </div> --- Quote Start --- I haven't modified inittab at all since buildroot created this <--- should I do this???[/b] --- Quote End --- You can use this, and add the line of /bin/sh as you already did it. I would like to invite you to post this as a project on the forum. This would be very helpful to those who develope custom boards. I am working on a PIO based MMC/SD card driver, with my spare time. I shall post it as another project when ready. - Altera_Forum
Honored Contributor
--- Quote Start --- originally posted by hippo@Nov 30 2005, 01:24 AM great!! http://forum.niosforum.com/work2/style_emoticons/<#emo_dir#>/laugh.gif<div class='quotetop'>quote
--- quote end ---
--- quote start ---
i haven't modified inittab at all since buildroot created this <--- should i do this??? --- Quote End --- You can use this, and add the line of /bin/sh as you already did it. I would like to invite you to post this as a project on the forum. This would be very helpful to those who develope custom boards. I am working on a PIO based MMC/SD card driver, with my spare time. I shall post it as another project when ready. <div align='right'><{post_snapback}> (index.php?act=findpost&pid=11258)</div> [/b] --- Quote End --- I take it you are using true MMC mode instead of SPI, which is why you are using PIO? That should be really cool once it is done; I am actually moving away from MMC/SD now to CF just because of lack of driver support http://forum.niosforum.com/work2/style_emoticons/<#EMO_DIR#>/sad.gif Is the driver included in the kernel any good, or does that not even work? When I'm more comfortable with playing around with the boot process of linux (I have already learnt so much!), I will definitely either post a project or make a sort of extension to Marcs instructions - anyone reading this thread should get all the information they need as I knew nothing when I started, but it would be nice to have it one place!