From this point on you can do all your work inside U-boot for loading images for the kernel and for the filesystem. I don't have the exact usage of it on hand right now.
Also you don't need to cross-post your questions in multiple entries on the blog here :) This isn't a It's too hard to follow the questions here. You should now be inside u-boot at a MINI24440# prompt. click site
Loading Kernel Image ... i uploaded the u-boot.bin file
4. Try passing init= option to kernel.
Any words of wisdom? I get essentially the same result from the yaffs file system image that I built.
Linux version 2.6.27 ([email protected]) (gcc version 4.3.2 (Sourcery G++ Lite 2008q3-72) ) #1 PREEMPT Mon Aug 24 17:01:35 CST 2009 CPU: ARM920T  revision 0 (ARMv4T), cr=c0007177 Machine: FriendlyARM Mini2440 development It also starts from NAND as it should. The solution: >cp -rf /dev/console $rootf/dev/ Reference: http://kerneltrap.org/node/6854 Posted by Max at 10:47:00 PM Labels: tool, tricks No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments Kernel panic - not syncing: No init found.Try passing init= option to kernel. [
usbcore: registered new interface driver usb-storage USB Mass Storage support registered. I recommend trying to run u-boot without the source modification first before disabling IRQ because I'm guessing at some point, buserror or someone else will figure out why it won't run Save the environment to NAND.
You can now set the boot switch back to NAND and reboot the system. Your root device shouldnt be mtdBLOCK3....
To: Alister Hood; [email protected] Re: [coLinux-users] Warning: unable to open an initial console. s3c2440-sdi s3c2440-sdi: initialisation done. This is not recommended !!
Thanks, Alister Re: [coLinux-users] Warning: unable to open an initial console. What distro are you using, and are you running as root or as a regular user (like you should)?
I would recommend erasing the stuff you downloaded and starting over, without That would be okay, but if I try to do the nand scrub and nand createbbt, I think it erases itself from NAND, because it doesn't work after reset after doing I would like to note though, that in the above examples, you need to know your u-boot bin file size in both bytes and in hex.
If someone is willing to send me a 1GB NAND board, I'd be happy to try and diagnose it ;-)
And yes, you are flashing it to the NAND and then You'll get some errors.
5. done, b Alternatively use "init=/bin/sh" to get a shell directly. -- Henry N.
it should be mtdblk0p3
Please try to correct that and see what happens. get redirected here As you can see with my post I suspect that something has changed in the repository. The top of the page has a link to it.
Trackback URL: http://bill.station51.net/index.php?trackback/910
40. On Saturday, June 19 2010, 11:47 by alex
die Wahrheit ist irgendwo da draußen Romikgy Сообщения: 677Зарегистрирован: 15 ноя 2009, 13:37Откуда: Odessa.UA Вернуться к началу Re: Android 1G NAND Strijar » 29 авг 2011, 19:36 bekor писал(а):Разделил какрту Please don't fill out this field. s3c2440-sdi s3c2440-sdi: running at 198kHz (requested: 197kHz).
s3c2440-sdi s3c2440-sdi: running at 16875kHz (requested: 25000kHz). Solve 'undefined reference to' problem Virtualbox comes back to live after upgrade from l... saveenv
U-Boot uses uImage files, not Total pages: 16256 Kernel command line: console=ttySAC0,115200 root=/dev/mmcblk0p3 rootfstype=ext3 mini2440=0tb rootdelay=3 init=/linuxrc irq: clearing pending status 02000000 irq: clearing subpending status 00000002 PID hash table entries: 256 (order: 8, 1024 bytes)
done, booting the kernel. Please don't fill out this field. Freeing unused kernel memory: 136k freed Warning: unable to open an initial console. my review here mount -o loop,ro YourImageName /mnt file /mnt/sbin/init That should be an ELF 32-bit LSB executable, and a statically linked file. *NOT* 64 bit.
In the above example, I commented it out but you can probably just change the 1 to a 0.
Step 4: Make and compile.
cd ../../ make mini2440_config make
Assuming I've just now following my own instructions using the latest uboot from the mini2440 git repository and it's working fine.
My apologies for not responding sooner, I just didn't see this Commit interval 5 seconds
EXT3 FS on mmcblk0p3, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem).
Freeing init memory: 116K
Warning: unable Nestler wrote: > Alister Hood wrote: >> Warning: unable to open an initial console. > > This means your directory "/dev" is empty. > > Mount your image from any other
setenv bootcmd nboot.e kernel \; bootm
7. The pre-built binary works fine so that's what I'm using and I can defer this problem until later.
2. I've googled quite extensively and been unable to find a solution. You'll get some errors.
You'll need to google for how to use mkimage. dono who others cud bring up android.. In NOR-mode I get to the supervivi-prompt.