Today

• 16 min ago

  Emdebian (Bootstrap Lenny for your ARM board.) Wiki page commented on by alvaro.colunga   -   I can not boot properly the mini2440 im using this commands setenv bootargs console=ttySAC0,115200 noinitrd root=/dev/mtcblk0p2 rootwait=4 rw ip=dhcp init=/bin/sh setenv bootargs console=ttySAC0,115200 noinitrd root=/dev/mmcblk0p2 rootwait=4 rw ip=dhcp init=/bin/sh I have the sd loaded with mmcinit and the kernel image loaded with fatload mmc 0:1 0x32000000 uImage but always shows the message TCP cubic registered NET: Registered protocol family 17 s3c2410-rtc s3c2410-rtc: hctosys: invalid date/time Root-NFS: No NFS server available, giving up. VFS: Unable to mount root fs via NFS, trying floppy. VFS: Cannot open root device "mmcblk0p2" or unknown-block(2,0) 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 125568 mtdblock3 (driver?) Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) If i mount the sd card on linux i can see partition 2 has the root fs Pls help!!!

  I can not boot properly the mini2440 im using this commands setenv bootargs console=ttySAC0,115200 noinitrd root=/dev/mtcblk0p2 rootwait=4 rw ip=dhcp init=/bin/sh setenv bootargs console=ttySAC0,115200 noinitrd root=/dev/mmcblk0p2 rootwait=4 rw ip=dhcp init=/bin/sh I have the sd loaded with mmcinit and the kernel image loaded with fatload mmc 0:1 0x32000000 uImage but always shows the message TCP cubic registered NET: Registered protocol family 17 s3c2410-rtc s3c2410-rtc: hctosys: invalid date/time Root-NFS: No NFS server available, giving up. VFS: Unable to mount root fs via NFS, trying floppy. VFS: Cannot open root device "mmcblk0p2" or unknown-block(2,0) 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 125568 mtdblock3 (driver?) Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) If i mount the sd card on linux i can see partition 2 has the root fs Pls help!!!

Last 7 days

• Jan 03, 2010

  QEmuSDCardImage (How to make, and use a Emdebian qemu "SD" image.) Wiki page commented on by lidonglin8088   -   last line : michel@moskva:~/qemu/qemu-trunk.git$ sudo nbd-client -d /deb/nbd0 should be: michel@moskva:~/qemu/qemu-trunk.git$ sudo nbd-client -d /dev/nbd0 ?

  last line : michel@moskva:~/qemu/qemu-trunk.git$ sudo nbd-client -d /deb/nbd0 should be: michel@moskva:~/qemu/qemu-trunk.git$ sudo nbd-client -d /dev/nbd0 ?

Last 30 days

• Dec 25, 2009

  OpenEmbedded (Basic OpenEmbedded use) Wiki page commented on by yeah2...@gmail.com   -   Firstly,thanks for your share.But the uboot does not work on my mini2440-128,and the kernel display wrong kernel.

  Firstly,thanks for your share.But the uboot does not work on my mini2440-128,and the kernel display wrong kernel.
• Dec 21, 2009

  OpenEmbedded (Basic OpenEmbedded use) Wiki page commented on by dmitry.s.golub   -   Thanks for your excellent guide!!! It's awesome!!! I've installed *OpenEmbedded* on my *mini2440* I face the problem with low copying/writing speed via eth interface. It's approximately 1.3MB/sec when I use samba or netcat. Thus I'm wondering if it's possible to increase the speed or it's hardware issue?

  Thanks for your excellent guide!!! It's awesome!!! I've installed *OpenEmbedded* on my *mini2440* I face the problem with low copying/writing speed via eth interface. It's approximately 1.3MB/sec when I use samba or netcat. Thus I'm wondering if it's possible to increase the speed or it's hardware issue?

Older

• Dec 07, 2009

  OpenEmbedded (Basic OpenEmbedded use) Wiki page edited by bertrand.roussel.fr   -   Revision r31 Edited wiki page through web user interface.

  Revision r31 Edited wiki page through web user interface.
• Dec 05, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by girardju   -   Thanks a lot for writing this great bringup webpage.

  Thanks a lot for writing this great bringup webpage.
• Dec 01, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by dave_fes...@hotmail.com   -   Warning: scrub option will erase all factory set bad blocks! There is no reliable way to recover them. Use this command only for testing purposes if you are sure of what you are doing! Does this mean that after you create a new BBT with u-boot that you might have problems returning to use Supervivi? After playing around with several kernel and applications using u-boot I have returned to the factory install. It seems to work OK , but I like to know if I am just lucky so far and if there is the potential for problems down the track. Thanks Dave

  Warning: scrub option will erase all factory set bad blocks! There is no reliable way to recover them. Use this command only for testing purposes if you are sure of what you are doing! Does this mean that after you create a new BBT with u-boot that you might have problems returning to use Supervivi? After playing around with several kernel and applications using u-boot I have returned to the factory install. It seems to work OK , but I like to know if I am just lucky so far and if there is the potential for problems down the track. Thanks Dave
• Nov 26, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by dirixmjm   -   This helped in my case: https://www.blogger.com/comment.g?blogID=11320970&postID=8052884915704378273&pli=1

  This helped in my case: https://www.blogger.com/comment.g?blogID=11320970&postID=8052884915704378273&pli=1
• Nov 20, 2009

  Emdebian (Bootstrap Lenny for your ARM board.) Wiki page commented on by bacchi_r...@mailcity.com   -   Found how to fix the framebuffer centering in this post: http://www.friendlyarm.net/forum/topic/107?lang=en

  Found how to fix the framebuffer centering in this post: http://www.friendlyarm.net/forum/topic/107?lang=en
• Nov 20, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by barsky   -   I'm using U-Boot 1.3.2-mini2440, built by OE. Somehow I get the problem similar to what Dhaval.Modi had: When i load this to Ram it works fine. but after wrting to flash, When i switch on the baord in NAND boot mode. I am getting nand_scan(): Cannot allocate oob_buf 0 Mib I dug a bit into it, and found that it's malloc that fails. I added some prints, and found that the humble 512 bytes is the first allocation ever in the u-boot. Further investigation revealed that sbrk_base variable is -1 on first invocation of malloc from RAM (which is reasonable), while it's value is 0x33d60000 on first invocation of malloc from NAND FLASH. This is weird, as this variable is assigned from within malloc (malloc_extend_top). Something with start.S? Any ideas?

  I'm using U-Boot 1.3.2-mini2440, built by OE. Somehow I get the problem similar to what Dhaval.Modi had: When i load this to Ram it works fine. but after wrting to flash, When i switch on the baord in NAND boot mode. I am getting nand_scan(): Cannot allocate oob_buf 0 Mib I dug a bit into it, and found that it's malloc that fails. I added some prints, and found that the humble 512 bytes is the first allocation ever in the u-boot. Further investigation revealed that sbrk_base variable is -1 on first invocation of malloc from RAM (which is reasonable), while it's value is 0x33d60000 on first invocation of malloc from NAND FLASH. This is weird, as this variable is assigned from within malloc (malloc_extend_top). Something with start.S? Any ideas?
• Nov 17, 2009

  OpenEmbedded (Basic OpenEmbedded use) Wiki page commented on by bflash2k   -   Just a quick reminder: As you "bitbake" as a simple user, don't forget to add /sbin to your PATH, just to be able to use tune2fs (if needed)

  Just a quick reminder: As you "bitbake" as a simple user, don't forget to add /sbin to your PATH, just to be able to use tune2fs (if needed)
• Nov 05, 2009

  issue 2 (bitbake error from czech repository) changed by buserror   -  

  Status: Invalid

  Owner: buserror

  Status: Invalid

  Owner: buserror
• Nov 05, 2009

  issue 2 (bitbake error from czech repository) commented on by buserror   -   never heard of "czech mini2440 repository"

  never heard of "czech mini2440 repository"
• Oct 26, 2009

  issue 2 (bitbake error from czech repository) commented on by maheshkuruganti   -   A couple of mailing lists I read said it could be a Openembedded problem

  A couple of mailing lists I read said it could be a Openembedded problem
• Oct 26, 2009

  issue 2 (bitbake error from czech repository) reported by maheshkuruganti   -   I am using the openembedded from the czech mini2440 repository and when I try to compile a gpe-image I am getting this error NOTE: Running task 5615 of 6832 (ID: 2025, /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb, do_unpack) NOTE: Unpacking ../sources/gpe-mixer-0.42.tar.gz to tmp/work/armv4t-angstrom-linux-gnueabi/gpe-mixer-0.42-r1/ NOTE: Running task 5616 of 6832 (ID: 2026, /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb, do_patch) NOTE: Applying patch 'gpemixer-no-host-includes.patch' (recipes/gpe-mixer/gpe-mixer/gpemixer-no-host-includes.patch) NOTE: Applying patch 'fix-install.patch' (recipes/gpe-mixer/gpe-mixer/fix-install.patch) ERROR: Error in executing: /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb ERROR: Exception:<class 'CmdError'> Message:Command Error: exit status: 1 Output: Applying patch fix-install.patch missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.old 2009-05-09 21:11:12.000000000 +0200 |+++ Makefile 2009-05-09 21:11:39.000000000 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored Patch fix-install.patch does not apply (enforce with -f) ERROR: Printing the environment of the function ERROR: Error in executing: /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb ERROR: Exception:<class 'CmdError'> Message:Command Error: exit status: 1 Output: Applying patch fix-install.patch missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.old 2009-05-09 21:11:12.000000000 +0200 |+++ Makefile 2009-05-09 21:11:39.000000000 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored Patch fix-install.patch does not apply (enforce with -f) ERROR: Printing the environment of the function ERROR: Error in executing: /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb ERROR: Exception:<class 'CmdError'> Message:Command Error: exit status: 1 Output: Applying patch fix-install.patch missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.old 2009-05-09 21:11:12.000000000 +0200 |+++ Makefile 2009-05-09 21:11:39.000000000 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored Patch fix-install.patch does not apply (enforce with -f) ERROR: Printing the environment of the function ERROR: Build of /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb do_patch failed Traceback (most recent call last): File "/oeroot/base/bitbake/bin/bitbake", line 143, in <module> main() File "/oeroot/base/bitbake/bin/bitbake", line 140, in main cooker.cook() File "/oeroot/base/bitbake/lib/bb/cooker.py", line 643, in cook return self.buildTargets(pkgs_to_build) File "/oeroot/base/bitbake/lib/bb/cooker.py", line 550, in buildTargets failures = rq.execute_runqueue() File "/oeroot/base/bitbake/lib/bb/runqueue.py", line 841, in execute_runqueue self.execute_runqueue_internal() File "/oeroot/base/bitbake/lib/bb/runqueue.py", line 950, in execute_runqueue_internal self.cooker.tryBuild(fn) File "/oeroot/base/bitbake/lib/bb/cooker.py", line 136, in tryBuild return self.tryBuildPackage(fn, item, self.configuration.cmd, the_data) File "/oeroot/base/bitbake/lib/bb/cooker.py", line 110, in tryBuildPackage bb.build.exec_task('do_%s' % task, the_data) File "/oeroot/base/bitbake/lib/bb/build.py", line 278, in exec_task exec_func(task, localdata) File "/oeroot/base/bitbake/lib/bb/build.py", line 113, in exec_func exec_func_python(func, d) File "/oeroot/base/bitbake/lib/bb/build.py", line 136, in exec_func_python utils.better_exec(comp, g, tmp, bbfile) File "/oeroot/base/bitbake/lib/bb/utils.py", line 171, in better_exec exec code in context File "do_patch", line 4, in <module> File "do_patch", line 2, in do_patch File "/oeroot/base/bitbake/lib/bb/build.py", line 113, in exec_func exec_func_python(func, d) File "/oeroot/base/bitbake/lib/bb/build.py", line 136, in exec_func_python utils.better_exec(comp, g, tmp, bbfile) File "/oeroot/base/bitbake/lib/bb/utils.py", line 171, in better_exec exec code in context File "base_do_patch", line 4, in <module> File "base_do_patch", line 2, in base_do_patch File "/oeroot/base/bitbake/lib/bb/build.py", line 113, in exec_func exec_func_python(func, d) File "/oeroot/base/bitbake/lib/bb/build.py", line 136, in exec_func_python utils.better_exec(comp, g, tmp, bbfile) File "/oeroot/base/bitbake/lib/bb/utils.py", line 171, in better_exec exec code in context File "patch_do_patch", line 100, in <module> File "patch_do_patch", line 98, in patch_do_patch File "<bb>", line 347, in Resolve __builtin__.CmdError: Command Error: exit status: 1 Output: Applying patch fix-install.patch missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.old 2009-05-09 21:11:12.000000000 +0200 |+++ Makefile 2009-05-09 21:11:39.000000000 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored Patch fix-install.patch does not apply (enforce with -f) ERROR: Task 2026 (/oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb, do_patch) failed NOTE: Tasks Summary: Attempted 5615 tasks of which 5117 didn't need to be rerun and 1 failed. ERROR: '/oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb' failed mahesh@mahesh-laptop:/oeroot/base$ bitbake gpe-image NOTE: Handling BitBake files: / (6668/6668) [100 %] NOTE: Parsing finished. 6372 cached, 0 parsed, 296 skipped, 0 masked. NOTE: Cache is clean, not saving. NOTE: Resolving any missing task queue dependencies NOTE: Preparing runqueue ERROR: Multiple .bb files are due to be built which each provide bluez-libs (/oeroot/base/recipes/bluez/bluez4_4.35.bb /oeroot/base/recipes/bluez/bluez-libs_3.36.bb). This usually means one provides something the other doesn't and should. NOTE: Executing runqueue NOTE: Running task 5616 of 6832 (ID: 2026, /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb, do_patch) NOTE: Applying patch 'gpemixer-no-host-includes.patch' (recipes/gpe-mixer/gpe-mixer/gpemixer-no-host-includes.patch) NOTE: Applying patch 'fix-install.patch' (recipes/gpe-mixer/gpe-mixer/fix-install.patch) ERROR: Error in executing: /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb ERROR: Exception:<class 'CmdError'> Message:Command Error: exit status: 1 Output: Applying patch fix-install.patch missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.old 2009-05-09 21:11:12.000000000 +0200 |+++ Makefile 2009-05-09 21:11:39.000000000 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored Patch fix-install.patch does not apply (enforce with -f) ERROR: Printing the environment of the function ERROR: Error in executing: /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb ERROR: Exception:<class 'CmdError'> Message:Command Error: exit status: 1 Output: Applying patch fix-install.patch missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.old 2009-05-09 21:11:12.000000000 +0200 |+++ Makefile 2009-05-09 21:11:39.000000000 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored Patch fix-install.patch does not apply (enforce with -f) ERROR: Printing the environment of the function ERROR: Error in executing: /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb ERROR: Exception:<class 'CmdError'> Message:Command Error: exit status: 1 Output: Applying patch fix-install.patch missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.old 2009-05-09 21:11:12.000000000 +0200 |+++ Makefile 2009-05-09 21:11:39.000000000 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored Patch fix-install.patch does not apply (enforce with -f) ERROR: Printing the environment of the function ERROR: Build of /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb do_patch failed Traceback (most recent call last): File "/oeroot/base/bitbake/bin/bitbake", line 143, in <module> main() File "/oeroot/base/bitbake/bin/bitbake", line 140, in main cooker.cook() File "/oeroot/base/bitbake/lib/bb/cooker.py", line 643, in cook return self.buildTargets(pkgs_to_build) File "/oeroot/base/bitbake/lib/bb/cooker.py", line 550, in buildTargets failures = rq.execute_runqueue() File "/oeroot/base/bitbake/lib/bb/runqueue.py", line 841, in execute_runqueue self.execute_runqueue_internal() File "/oeroot/base/bitbake/lib/bb/runqueue.py", line 950, in execute_runqueue_internal self.cooker.tryBuild(fn) File "/oeroot/base/bitbake/lib/bb/cooker.py", line 136, in tryBuild return self.tryBuildPackage(fn, item, self.configuration.cmd, the_data) File "/oeroot/base/bitbake/lib/bb/cooker.py", line 110, in tryBuildPackage bb.build.exec_task('do_%s' % task, the_data) File "/oeroot/base/bitbake/lib/bb/build.py", line 278, in exec_task exec_func(task, localdata) File "/oeroot/base/bitbake/lib/bb/build.py", line 113, in exec_func exec_func_python(func, d) File "/oeroot/base/bitbake/lib/bb/build.py", line 136, in exec_func_python utils.better_exec(comp, g, tmp, bbfile) File "/oeroot/base/bitbake/lib/bb/utils.py", line 171, in better_exec exec code in context File "do_patch", line 4, in <module> File "do_patch", line 2, in do_patch File "/oeroot/base/bitbake/lib/bb/build.py", line 113, in exec_func exec_func_python(func, d) File "/oeroot/base/bitbake/lib/bb/build.py", line 136, in exec_func_python utils.better_exec(comp, g, tmp, bbfile) File "/oeroot/base/bitbake/lib/bb/utils.py", line 171, in better_exec exec code in context File "base_do_patch", line 4, in <module> File "base_do_patch", line 2, in base_do_patch File "/oeroot/base/bitbake/lib/bb/build.py", line 113, in exec_func exec_func_python(func, d) File "/oeroot/base/bitbake/lib/bb/build.py", line 136, in exec_func_python utils.better_exec(comp, g, tmp, bbfile) File "/oeroot/base/bitbake/lib/bb/utils.py", line 171, in better_exec exec code in context File "patch_do_patch", line 100, in <module> File "patch_do_patch", line 98, in patch_do_patch File "<bb>", line 347, in Resolve __builtin__.CmdError: Command Error: exit status: 1 Output: Applying patch fix-install.patch missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.old 2009-05-09 21:11:12.000000000 +0200 |+++ Makefile 2009-05-09 21:11:39.000000000 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored Patch fix-install.patch does not apply (enforce with -f) ERROR: Task 2026 (/oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb, do_patch) failed NOTE: Tasks Summary: Attempted 5615 tasks of which 5615 didn't need to be rerun and 1 failed. ERROR: '/oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb' failed mahesh@mahesh-laptop:/oeroot/base$ (nautilus:5054): Eel-WARNING **: "nautilus-metafile.c: metafiles" hash table still has 3 elements at quit time (keys above) bash: syntax error near unexpected token `:'

  I am using the openembedded from the czech mini2440 repository and when I try to compile a gpe-image I am getting this error NOTE: Running task 5615 of 6832 (ID: 2025, /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb, do_unpack) NOTE: Unpacking ../sources/gpe-mixer-0.42.tar.gz to tmp/work/armv4t-angstrom-linux-gnueabi/gpe-mixer-0.42-r1/ NOTE: Running task 5616 of 6832 (ID: 2026, /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb, do_patch) NOTE: Applying patch 'gpemixer-no-host-includes.patch' (recipes/gpe-mixer/gpe-mixer/gpemixer-no-host-includes.patch) NOTE: Applying patch 'fix-install.patch' (recipes/gpe-mixer/gpe-mixer/fix-install.patch) ERROR: Error in executing: /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb ERROR: Exception:<class 'CmdError'> Message:Command Error: exit status: 1 Output: Applying patch fix-install.patch missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.old 2009-05-09 21:11:12.000000000 +0200 |+++ Makefile 2009-05-09 21:11:39.000000000 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored Patch fix-install.patch does not apply (enforce with -f) ERROR: Printing the environment of the function ERROR: Error in executing: /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb ERROR: Exception:<class 'CmdError'> Message:Command Error: exit status: 1 Output: Applying patch fix-install.patch missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.old 2009-05-09 21:11:12.000000000 +0200 |+++ Makefile 2009-05-09 21:11:39.000000000 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored Patch fix-install.patch does not apply (enforce with -f) ERROR: Printing the environment of the function ERROR: Error in executing: /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb ERROR: Exception:<class 'CmdError'> Message:Command Error: exit status: 1 Output: Applying patch fix-install.patch missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.old 2009-05-09 21:11:12.000000000 +0200 |+++ Makefile 2009-05-09 21:11:39.000000000 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored Patch fix-install.patch does not apply (enforce with -f) ERROR: Printing the environment of the function ERROR: Build of /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb do_patch failed Traceback (most recent call last): File "/oeroot/base/bitbake/bin/bitbake", line 143, in <module> main() File "/oeroot/base/bitbake/bin/bitbake", line 140, in main cooker.cook() File "/oeroot/base/bitbake/lib/bb/cooker.py", line 643, in cook return self.buildTargets(pkgs_to_build) File "/oeroot/base/bitbake/lib/bb/cooker.py", line 550, in buildTargets failures = rq.execute_runqueue() File "/oeroot/base/bitbake/lib/bb/runqueue.py", line 841, in execute_runqueue self.execute_runqueue_internal() File "/oeroot/base/bitbake/lib/bb/runqueue.py", line 950, in execute_runqueue_internal self.cooker.tryBuild(fn) File "/oeroot/base/bitbake/lib/bb/cooker.py", line 136, in tryBuild return self.tryBuildPackage(fn, item, self.configuration.cmd, the_data) File "/oeroot/base/bitbake/lib/bb/cooker.py", line 110, in tryBuildPackage bb.build.exec_task('do_%s' % task, the_data) File "/oeroot/base/bitbake/lib/bb/build.py", line 278, in exec_task exec_func(task, localdata) File "/oeroot/base/bitbake/lib/bb/build.py", line 113, in exec_func exec_func_python(func, d) File "/oeroot/base/bitbake/lib/bb/build.py", line 136, in exec_func_python utils.better_exec(comp, g, tmp, bbfile) File "/oeroot/base/bitbake/lib/bb/utils.py", line 171, in better_exec exec code in context File "do_patch", line 4, in <module> File "do_patch", line 2, in do_patch File "/oeroot/base/bitbake/lib/bb/build.py", line 113, in exec_func exec_func_python(func, d) File "/oeroot/base/bitbake/lib/bb/build.py", line 136, in exec_func_python utils.better_exec(comp, g, tmp, bbfile) File "/oeroot/base/bitbake/lib/bb/utils.py", line 171, in better_exec exec code in context File "base_do_patch", line 4, in <module> File "base_do_patch", line 2, in base_do_patch File "/oeroot/base/bitbake/lib/bb/build.py", line 113, in exec_func exec_func_python(func, d) File "/oeroot/base/bitbake/lib/bb/build.py", line 136, in exec_func_python utils.better_exec(comp, g, tmp, bbfile) File "/oeroot/base/bitbake/lib/bb/utils.py", line 171, in better_exec exec code in context File "patch_do_patch", line 100, in <module> File "patch_do_patch", line 98, in patch_do_patch File "<bb>", line 347, in Resolve __builtin__.CmdError: Command Error: exit status: 1 Output: Applying patch fix-install.patch missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.old 2009-05-09 21:11:12.000000000 +0200 |+++ Makefile 2009-05-09 21:11:39.000000000 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored Patch fix-install.patch does not apply (enforce with -f) ERROR: Task 2026 (/oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb, do_patch) failed NOTE: Tasks Summary: Attempted 5615 tasks of which 5117 didn't need to be rerun and 1 failed. ERROR: '/oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb' failed mahesh@mahesh-laptop:/oeroot/base$ bitbake gpe-image NOTE: Handling BitBake files: / (6668/6668) [100 %] NOTE: Parsing finished. 6372 cached, 0 parsed, 296 skipped, 0 masked. NOTE: Cache is clean, not saving. NOTE: Resolving any missing task queue dependencies NOTE: Preparing runqueue ERROR: Multiple .bb files are due to be built which each provide bluez-libs (/oeroot/base/recipes/bluez/bluez4_4.35.bb /oeroot/base/recipes/bluez/bluez-libs_3.36.bb). This usually means one provides something the other doesn't and should. NOTE: Executing runqueue NOTE: Running task 5616 of 6832 (ID: 2026, /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb, do_patch) NOTE: Applying patch 'gpemixer-no-host-includes.patch' (recipes/gpe-mixer/gpe-mixer/gpemixer-no-host-includes.patch) NOTE: Applying patch 'fix-install.patch' (recipes/gpe-mixer/gpe-mixer/fix-install.patch) ERROR: Error in executing: /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb ERROR: Exception:<class 'CmdError'> Message:Command Error: exit status: 1 Output: Applying patch fix-install.patch missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.old 2009-05-09 21:11:12.000000000 +0200 |+++ Makefile 2009-05-09 21:11:39.000000000 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored Patch fix-install.patch does not apply (enforce with -f) ERROR: Printing the environment of the function ERROR: Error in executing: /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb ERROR: Exception:<class 'CmdError'> Message:Command Error: exit status: 1 Output: Applying patch fix-install.patch missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.old 2009-05-09 21:11:12.000000000 +0200 |+++ Makefile 2009-05-09 21:11:39.000000000 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored Patch fix-install.patch does not apply (enforce with -f) ERROR: Printing the environment of the function ERROR: Error in executing: /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb ERROR: Exception:<class 'CmdError'> Message:Command Error: exit status: 1 Output: Applying patch fix-install.patch missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.old 2009-05-09 21:11:12.000000000 +0200 |+++ Makefile 2009-05-09 21:11:39.000000000 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored Patch fix-install.patch does not apply (enforce with -f) ERROR: Printing the environment of the function ERROR: Build of /oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb do_patch failed Traceback (most recent call last): File "/oeroot/base/bitbake/bin/bitbake", line 143, in <module> main() File "/oeroot/base/bitbake/bin/bitbake", line 140, in main cooker.cook() File "/oeroot/base/bitbake/lib/bb/cooker.py", line 643, in cook return self.buildTargets(pkgs_to_build) File "/oeroot/base/bitbake/lib/bb/cooker.py", line 550, in buildTargets failures = rq.execute_runqueue() File "/oeroot/base/bitbake/lib/bb/runqueue.py", line 841, in execute_runqueue self.execute_runqueue_internal() File "/oeroot/base/bitbake/lib/bb/runqueue.py", line 950, in execute_runqueue_internal self.cooker.tryBuild(fn) File "/oeroot/base/bitbake/lib/bb/cooker.py", line 136, in tryBuild return self.tryBuildPackage(fn, item, self.configuration.cmd, the_data) File "/oeroot/base/bitbake/lib/bb/cooker.py", line 110, in tryBuildPackage bb.build.exec_task('do_%s' % task, the_data) File "/oeroot/base/bitbake/lib/bb/build.py", line 278, in exec_task exec_func(task, localdata) File "/oeroot/base/bitbake/lib/bb/build.py", line 113, in exec_func exec_func_python(func, d) File "/oeroot/base/bitbake/lib/bb/build.py", line 136, in exec_func_python utils.better_exec(comp, g, tmp, bbfile) File "/oeroot/base/bitbake/lib/bb/utils.py", line 171, in better_exec exec code in context File "do_patch", line 4, in <module> File "do_patch", line 2, in do_patch File "/oeroot/base/bitbake/lib/bb/build.py", line 113, in exec_func exec_func_python(func, d) File "/oeroot/base/bitbake/lib/bb/build.py", line 136, in exec_func_python utils.better_exec(comp, g, tmp, bbfile) File "/oeroot/base/bitbake/lib/bb/utils.py", line 171, in better_exec exec code in context File "base_do_patch", line 4, in <module> File "base_do_patch", line 2, in base_do_patch File "/oeroot/base/bitbake/lib/bb/build.py", line 113, in exec_func exec_func_python(func, d) File "/oeroot/base/bitbake/lib/bb/build.py", line 136, in exec_func_python utils.better_exec(comp, g, tmp, bbfile) File "/oeroot/base/bitbake/lib/bb/utils.py", line 171, in better_exec exec code in context File "patch_do_patch", line 100, in <module> File "patch_do_patch", line 98, in patch_do_patch File "<bb>", line 347, in Resolve __builtin__.CmdError: Command Error: exit status: 1 Output: Applying patch fix-install.patch missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.old 2009-05-09 21:11:12.000000000 +0200 |+++ Makefile 2009-05-09 21:11:39.000000000 +0200 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored Patch fix-install.patch does not apply (enforce with -f) ERROR: Task 2026 (/oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb, do_patch) failed NOTE: Tasks Summary: Attempted 5615 tasks of which 5615 didn't need to be rerun and 1 failed. ERROR: '/oeroot/base/recipes/gpe-mixer/gpe-mixer_0.42.bb' failed mahesh@mahesh-laptop:/oeroot/base$ (nautilus:5054): Eel-WARNING **: "nautilus-metafile.c: metafiles" hash table still has 3 elements at quit time (keys above) bash: syntax error near unexpected token `:'
• Oct 22, 2009

  Emdebian (Bootstrap Lenny for your ARM board.) Wiki page commented on by pmatteucci   -   ok I got everything working. As far as I can tell the last tftp is a type and should be nboot.e kernel; bootm

  ok I got everything working. As far as I can tell the last tftp is a type and should be nboot.e kernel; bootm
• Oct 21, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by dirixmjm   -   Hi, I've downloaded and compiled u-boot using the proposed script under the download section. Somehow I can't get past the ooo_buf thing, although I have the plain 64Mb nand. Strangely enough, it detects the nand once, then "restarts" the detection and fails. This is the output Supervivi> go 0x33f80000 go to 0x33f80000 argument 0 = 0x00000000 argument 1 = 0x00000000 argument 2 = 0x00000000 � argument 3 = 0x00000000 U-Boot 1.3.2-mini2440 (Oct 21 2009 - 21:08:41) I2C: ready DRAM: 64 MB Flash: 2 MB NAND: Bad block table not found for chip 0 Bad block table not found for chip 0 64 MiB *** Warning - bad CRC or NAND, using default environment USB: S3C2410 USB Deviced In: serial Out: serial Err: serial U-Boot 1.3.2-mini2440 (Oct 21 2009 - 21:08:41) I2C: ready DRAM: 64 MB Flash: 2 MB NAND: nand_scan(): Cannot allocate oob_buf 0 MiB Any thoughts?

  Hi, I've downloaded and compiled u-boot using the proposed script under the download section. Somehow I can't get past the ooo_buf thing, although I have the plain 64Mb nand. Strangely enough, it detects the nand once, then "restarts" the detection and fails. This is the output Supervivi> go 0x33f80000 go to 0x33f80000 argument 0 = 0x00000000 argument 1 = 0x00000000 argument 2 = 0x00000000 � argument 3 = 0x00000000 U-Boot 1.3.2-mini2440 (Oct 21 2009 - 21:08:41) I2C: ready DRAM: 64 MB Flash: 2 MB NAND: Bad block table not found for chip 0 Bad block table not found for chip 0 64 MiB *** Warning - bad CRC or NAND, using default environment USB: S3C2410 USB Deviced In: serial Out: serial Err: serial U-Boot 1.3.2-mini2440 (Oct 21 2009 - 21:08:41) I2C: ready DRAM: 64 MB Flash: 2 MB NAND: nand_scan(): Cannot allocate oob_buf 0 MiB Any thoughts?
• Oct 20, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by buserror   -   BTW I fixed the USB code, and DFU now works to flash the board...

  BTW I fixed the USB code, and DFU now works to flash the board...
• Oct 20, 2009

  Emdebian (Bootstrap Lenny for your ARM board.) Wiki page commented on by kadirinay   -   While starting to boot mini2440 board MINI2440# setenv load_addr 0x32000000 must be writen.Because load_addr variable is not definition.then MINI2440# saveenv later MINI2440# bootcmd=setenv bootcmd 'mmcinit;ext2load mmc 1:2 ${load_addr} uImage; setenv bootargs ${bootargs} noinitrd root=/dev/mmcblk0p2 rw ip=dhcp; bootm ${load_addr}' Dont remember dollar sign '$' before {load_addr}...... I did and worked......

  While starting to boot mini2440 board MINI2440# setenv load_addr 0x32000000 must be writen.Because load_addr variable is not definition.then MINI2440# saveenv later MINI2440# bootcmd=setenv bootcmd 'mmcinit;ext2load mmc 1:2 ${load_addr} uImage; setenv bootargs ${bootargs} noinitrd root=/dev/mmcblk0p2 rw ip=dhcp; bootm ${load_addr}' Dont remember dollar sign '$' before {load_addr}...... I did and worked......
• Oct 20, 2009

  Emdebian (Bootstrap Lenny for your ARM board.) Wiki page commented on by kadirinay   -   While starting to boot mini2440 board MINI2440# setenv load_addr 0x32000000 must be writen.Because load_addr variable is not definition.then MINI2440# saveenv later MINI2440# bootcmd=setenv bootcmd 'mmcinit;ext2load mmc 1:2 ${load_addr} uImage; setenv bootargs ${bootargs} noinitrd root=/dev/mmcblk0p2 rw ip=dhcp; bootm ${load_addr}' Dont remember dollar sign '$' before {load_addr}...... I did and worked......

  While starting to boot mini2440 board MINI2440# setenv load_addr 0x32000000 must be writen.Because load_addr variable is not definition.then MINI2440# saveenv later MINI2440# bootcmd=setenv bootcmd 'mmcinit;ext2load mmc 1:2 ${load_addr} uImage; setenv bootargs ${bootargs} noinitrd root=/dev/mmcblk0p2 rw ip=dhcp; bootm ${load_addr}' Dont remember dollar sign '$' before {load_addr}...... I did and worked......
• Oct 20, 2009

  Emdebian (Bootstrap Lenny for your ARM board.) Wiki page commented on by kadirinay   -   While starting to boot mini2440 board MINI2440# setenv load_addr 0x32000000 must be writen.Because load_addr variable is not definition.then MINI2440# saveenv later MINI2440# bootcmd=setenv bootcmd 'mmcinit;ext2load mmc 1:2 ${load_addr} uImage; setenv bootargs ${bootargs} noinitrd root=/dev/mmcblk0p2 rw ip=dhcp; bootm {load_addr}' I did and worked......

  While starting to boot mini2440 board MINI2440# setenv load_addr 0x32000000 must be writen.Because load_addr variable is not definition.then MINI2440# saveenv later MINI2440# bootcmd=setenv bootcmd 'mmcinit;ext2load mmc 1:2 ${load_addr} uImage; setenv bootargs ${bootargs} noinitrd root=/dev/mmcblk0p2 rw ip=dhcp; bootm {load_addr}' I did and worked......
• Oct 18, 2009

  Emdebian (Bootstrap Lenny for your ARM board.) Wiki page commented on by pmatteucci   -   hey guys! I compiled the kernet from git and converted it to uImage as per http://wiki.linuxmce.org/index.php/Mini2440 I follow all this and it works fine, the SD is partitioned and the modules & debootstrap. When I boot to mini2440 I get a "Wrong Image Format for bootm command" error. bootcmd=setenv bootcmd 'mmcinit;fatload mmc 0:1 ${load_addr} uImage; setenv bootargs ${bootargs} noinitrd root=/dev/mmcblk0p2 rw ip=dhcp; bootm {load_addr}' Also I don't get the tftp in this tutorial, when I run it it says that *** Warning: no boot file name; using '95AB58FD.img' And can't find it since my tftp only has uImage and u-boot.bin installed Can anyone help me? Thanks very much Pajolo

  hey guys! I compiled the kernet from git and converted it to uImage as per http://wiki.linuxmce.org/index.php/Mini2440 I follow all this and it works fine, the SD is partitioned and the modules & debootstrap. When I boot to mini2440 I get a "Wrong Image Format for bootm command" error. bootcmd=setenv bootcmd 'mmcinit;fatload mmc 0:1 ${load_addr} uImage; setenv bootargs ${bootargs} noinitrd root=/dev/mmcblk0p2 rw ip=dhcp; bootm {load_addr}' Also I don't get the tftp in this tutorial, when I run it it says that *** Warning: no boot file name; using '95AB58FD.img' And can't find it since my tftp only has uImage and u-boot.bin installed Can anyone help me? Thanks very much Pajolo
• Oct 18, 2009

  OpenEmbedded (Basic OpenEmbedded use) Wiki page edited by bertrand.roussel.fr   -   Revision r30 Edited wiki page through web user interface.

  Revision r30 Edited wiki page through web user interface.
• Oct 16, 2009

  OpenEmbedded (Basic OpenEmbedded use) Wiki page edited by bertrand.roussel.fr   -   Revision r29 Edited wiki page through web user interface.

  Revision r29 Edited wiki page through web user interface.
• Oct 16, 2009

  OpenEmbeddedExternalBuild (Sample script to cross-build your own program against OpenEm...) Wiki page edited by bertrand.roussel.fr   -   Revision r28 Minor commit

  Revision r28 Minor commit
• Oct 16, 2009

  OpenEmbedded (Basic OpenEmbedded use) Wiki page edited by bertrand.roussel.fr   -   Revision r27 Edited wiki page through web user interface.

  Revision r27 Edited wiki page through web user interface.
• Oct 16, 2009

  OpenEmbedded (Basic OpenEmbedded use) Wiki page edited by bertrand.roussel.fr   -   Revision r26 Edited wiki page through web user interface.

  Revision r26 Edited wiki page through web user interface.
• Oct 16, 2009

  OpenEmbedded (Basic OpenEmbedded use) Wiki page added by bertrand.roussel.fr   -   Revision r25 Small quick start for OE

  Revision r25 Small quick start for OE
• Oct 15, 2009

  Emdebian (Bootstrap Lenny for your ARM board.) Wiki page commented on by rate...@alice.it   -   Anyone has idea for screen centering under framebuffer?? Please help!

  Anyone has idea for screen centering under framebuffer?? Please help!
• Oct 14, 2009

  Emdebian (Bootstrap Lenny for your ARM board.) Wiki page commented on by rate...@alice.it   -   incredible how desperation works faster than me.. dist-upgraded to testing and now i have xorg rambling.. xfce4 work but needs some swap (how can i center the display as mine is a little overscanning right way???)

  incredible how desperation works faster than me.. dist-upgraded to testing and now i have xorg rambling.. xfce4 work but needs some swap (how can i center the display as mine is a little overscanning right way???)
• Oct 14, 2009

  Emdebian (Bootstrap Lenny for your ARM board.) Wiki page commented on by rate...@alice.it   -   Ok at all.. i get everything running or almost.. i saw last day xfce4 in repos and decided to try... just another maze ahead. I get this error from X: FBIOPUT_VSCREENINFO succeeded but modified mode --> then it dies in shell Anybody succeded there? Would be nice to try graphical capabilities and i'm on a dead end road cuase i can't gather more infos about this problem.. Help!

  Ok at all.. i get everything running or almost.. i saw last day xfce4 in repos and decided to try... just another maze ahead. I get this error from X: FBIOPUT_VSCREENINFO succeeded but modified mode --> then it dies in shell Anybody succeded there? Would be nice to try graphical capabilities and i'm on a dead end road cuase i can't gather more infos about this problem.. Help!
• Sep 24, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by buserror   -   There we go, do patch u-boot to fix the USB device code, I'm delighted to have a volunteer at last ! :-)

  There we go, do patch u-boot to fix the USB device code, I'm delighted to have a volunteer at last ! :-)
• Sep 23, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by oberonc   -   I know ,but I ask "why" .. everything can be done using the USB host + software serial over USB

  I know ,but I ask "why" .. everything can be done using the USB host + software serial over USB
• Sep 23, 2009

  Emdebian (Bootstrap Lenny for your ARM board.) Wiki page commented on by Daniel.James.Moore   -   I keep getting this error: I: Configuring udev... udevd[8773]: init_udevd_socket: bind failed: Address already in use udevd[8773]: main: error initializing udevd socket ..... W: Failure while configuring required packages. when I run: sh-3.2# /debootstrap/debootstrap --second-stage Any suggestions? I've run the command about 15 times now and still no luck with finishing up the installation.

  I keep getting this error: I: Configuring udev... udevd[8773]: init_udevd_socket: bind failed: Address already in use udevd[8773]: main: error initializing udevd socket ..... W: Failure while configuring required packages. when I run: sh-3.2# /debootstrap/debootstrap --second-stage Any suggestions? I've run the command about 15 times now and still no luck with finishing up the installation.
• Sep 21, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by buserror   -   Buy a USB serial adapter, they are $5.

  Buy a USB serial adapter, they are $5.
• Sep 20, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by oberonc   -   Is it possible to operate vivi/u-boot using USB alone ? I dont have a serial port in my desktop computer

  Is it possible to operate vivi/u-boot using USB alone ? I dont have a serial port in my desktop computer
• Sep 18, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by buserror   -   I'm in the final stage of having a u-boot that autodetects the nand type and boots accordingly. I'll try to post it this week-end...

  I'm in the final stage of having a u-boot that autodetects the nand type and boots accordingly. I'll try to post it this week-end...
• Sep 18, 2009

  Emdebian (Bootstrap Lenny for your ARM board.) Wiki page commented on by gentijo   -   I have a mini2440, I can compile the kernel from source and I can load the prepackaged rootfs that I grabbed from somewhere that is an Angstrom build from Watterott. What I want to do now is build a rootfs from scratch that once it boots, it will run a Qt app I wrote.. I need touchscreen functionality but I don't need the whole desktop, just a blank canvas.. My question, which is the best way to go, a straight up OE release, Angstrom or embedian. I need SD support, and possibly networking, but having a device that boots quickly is important.. Right now the Angstrom build takes a min or 2 to boot.. Thank you John Gentilin

  I have a mini2440, I can compile the kernel from source and I can load the prepackaged rootfs that I grabbed from somewhere that is an Angstrom build from Watterott. What I want to do now is build a rootfs from scratch that once it boots, it will run a Qt app I wrote.. I need touchscreen functionality but I don't need the whole desktop, just a blank canvas.. My question, which is the best way to go, a straight up OE release, Angstrom or embedian. I need SD support, and possibly networking, but having a device that boots quickly is important.. Right now the Angstrom build takes a min or 2 to boot.. Thank you John Gentilin
• Sep 17, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by zol...@bendor.com.au   -   An other issue: with the fatter NAND the block size is 128K. Alas, when you want to save the environment, it erases only 64K. The NAND erase routine fails and u-boot instead of giving you an error message just gives back the prompt, without actually doing anything at all. Band-aid solution: change CNF_ENV_SIZE from 0x10000 to 0x20000 in include/configs/mini2440.h.

  An other issue: with the fatter NAND the block size is 128K. Alas, when you want to save the environment, it erases only 64K. The NAND erase routine fails and u-boot instead of giving you an error message just gives back the prompt, without actually doing anything at all. Band-aid solution: change CNF_ENV_SIZE from 0x10000 to 0x20000 in include/configs/mini2440.h.
• Sep 17, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by zol...@bendor.com.au   -   I had a problem with u-boot on a MINI2440 with 128M FLASH. It seems that if you have that new board with 128M FLASH then you have to fix a little problem with u-boot from the Czech repository. The problem is that the bigger FLASH needs different timing. In the u-boot source it is hard-coded that if you have a MINI2440 then it uses the timing for the smaller chips. The ideal solution would be if it actually checked what FLASH was connected (a register of the S3C2440 tells you that after boot) and set the timing accordingly, but as a quick fix, *ONLY IF YOU HAVE 128M FLASH WITH 2K PAGE SIZE!!!* then you can do the following: in cpu/arm920t/s3c24x0/nand_read.c, line 59 reads: #if defined(CONFIG_S3C2410) || defined(CONFIG_MINI2440) Just comment out the || defined(CONFIG_MINI2440) bit, recompile, load it with vivi and you'll have a u-boot from FLASH. Note that this is not a solution, just a band-aid. Furthermore, there are hard-coded assumptions about the FLASH being 64MB in size, but that's not causing problems apart from u-boot not knowing about half of your FLASH. Also, I don't know (yet) if that's enough to do anything useful with u-boot, but at least it starts up from the NAND. Kocsonya

  I had a problem with u-boot on a MINI2440 with 128M FLASH. It seems that if you have that new board with 128M FLASH then you have to fix a little problem with u-boot from the Czech repository. The problem is that the bigger FLASH needs different timing. In the u-boot source it is hard-coded that if you have a MINI2440 then it uses the timing for the smaller chips. The ideal solution would be if it actually checked what FLASH was connected (a register of the S3C2440 tells you that after boot) and set the timing accordingly, but as a quick fix, *ONLY IF YOU HAVE 128M FLASH WITH 2K PAGE SIZE!!!* then you can do the following: in cpu/arm920t/s3c24x0/nand_read.c, line 59 reads: #if defined(CONFIG_S3C2410) || defined(CONFIG_MINI2440) Just comment out the || defined(CONFIG_MINI2440) bit, recompile, load it with vivi and you'll have a u-boot from FLASH. Note that this is not a solution, just a band-aid. Furthermore, there are hard-coded assumptions about the FLASH being 64MB in size, but that's not causing problems apart from u-boot not knowing about half of your FLASH. Also, I don't know (yet) if that's enough to do anything useful with u-boot, but at least it starts up from the NAND. Kocsonya
• Sep 15, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by dannygrob   -   I had the allocate oob_buf error too. I had to use u-boot-nand2k.bin...check your 'nand info' if you have 2048 size. You can compile it using the guide here: http://wiki.linuxmce.org/index.php/Mini2440 by replacing 'git clone git://repo.or.cz/u-boot-openmoko/mini2440.git' with 'git clone git://gitorious.org/hiteg-development-boards/mini2440.git' then compile it following the instructions there, just replace everything with u-boot-nand2k.bin you have an upgraded board

  I had the allocate oob_buf error too. I had to use u-boot-nand2k.bin...check your 'nand info' if you have 2048 size. You can compile it using the guide here: http://wiki.linuxmce.org/index.php/Mini2440 by replacing 'git clone git://repo.or.cz/u-boot-openmoko/mini2440.git' with 'git clone git://gitorious.org/hiteg-development-boards/mini2440.git' then compile it following the instructions there, just replace everything with u-boot-nand2k.bin you have an upgraded board
• Sep 15, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by dannygrob   -   I had the allocate oob_buf error too. I had to use u-boot-nand2k.bin...check your nand info if you have 2048 size. You can compile it using the guide here: http://wiki.linuxmce.org/index.php/Mini2440 by replacing git clone git://repo.or.cz/u-boot-openmoko/mini2440.git with git://gitorious.org/hiteg-development-boards/mini2440.git then compile it following the instructions there you have an upgraded board

  I had the allocate oob_buf error too. I had to use u-boot-nand2k.bin...check your nand info if you have 2048 size. You can compile it using the guide here: http://wiki.linuxmce.org/index.php/Mini2440 by replacing git clone git://repo.or.cz/u-boot-openmoko/mini2440.git with git://gitorious.org/hiteg-development-boards/mini2440.git then compile it following the instructions there you have an upgraded board
• Sep 13, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by Dhaval.Modi   -   Hi, I am using uboot 1.3.3 from git repostry at git clone git://repo.or.cz/u-boot-openmoko/mini2440.git When i load this to Ram it works fine. but after wrting to flash, When i switch on the baord in NAND boot mode. I am getting nand_scan(): Cannot allocate oob_buf 0 Mib Thanks

  Hi, I am using uboot 1.3.3 from git repostry at git clone git://repo.or.cz/u-boot-openmoko/mini2440.git When i load this to Ram it works fine. but after wrting to flash, When i switch on the baord in NAND boot mode. I am getting nand_scan(): Cannot allocate oob_buf 0 Mib Thanks
• Sep 12, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by findlaybrian   -   Daniel, A suggestion, the uboot that this is documented with is a different size than the one you will get from the git repository. If you look though these commands you will see several of them that ask for the image size such as: {{{ load ram 0x33f80000 232448 x nand write.e 32000000 0 38c00 }}} Because I just blindly copied these strings (stupid me), I got some very strange results as I copied a truncated image to RAM, then to flash. So you may want to take a look at that, the current git image is larger so you will be losing a few bytes there. As soon as I got that right, everything works as advertised.. Hope that helps. Good Luck .. Brian

  Daniel, A suggestion, the uboot that this is documented with is a different size than the one you will get from the git repository. If you look though these commands you will see several of them that ask for the image size such as: {{{ load ram 0x33f80000 232448 x nand write.e 32000000 0 38c00 }}} Because I just blindly copied these strings (stupid me), I got some very strange results as I copied a truncated image to RAM, then to flash. So you may want to take a look at that, the current git image is larger so you will be losing a few bytes there. As soon as I got that right, everything works as advertised.. Hope that helps. Good Luck .. Brian
• Sep 12, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by findlaybrian   -   Daniel, A suggestion, the uboot that this is documented with is a different size than the one you will get from the git repository. If you look though these commands you will see several of them that ask for the image size such as: load ram 0x33f80000 232448 x nand write.e 32000000 0 38c00 Because I just blindly copied these strings (stupid me), I got some very strange results as I copied a truncated image to RAM, then to flash. So you may want to take a look at that, the current git image is larger so you will be losing a few bytes there. As soon as I got that right, everything works as advertised.. Hope that helps. Good Luck .. Brian

  Daniel, A suggestion, the uboot that this is documented with is a different size than the one you will get from the git repository. If you look though these commands you will see several of them that ask for the image size such as: load ram 0x33f80000 232448 x nand write.e 32000000 0 38c00 Because I just blindly copied these strings (stupid me), I got some very strange results as I copied a truncated image to RAM, then to flash. So you may want to take a look at that, the current git image is larger so you will be losing a few bytes there. As soon as I got that right, everything works as advertised.. Hope that helps. Good Luck .. Brian
• Sep 12, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by Dhaval.Modi   -   hi, I have a mini2440, with 64Mb ram and 128Mb Flash. I am not able to boot. i am getting : nand_scan(): Cannot allocate oob_buf mini2440. error. please help me . Thanks

  hi, I have a mini2440, with 64Mb ram and 128Mb Flash. I am not able to boot. i am getting : nand_scan(): Cannot allocate oob_buf mini2440. error. please help me . Thanks
• Sep 08, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by Daniel.James.Moore   -   um. I've followed this guide multiple times today attempting to flash u-boot on my mini2440. However, I cannot get the mini2440 to boot into u-boot when I have the boot switch selecting NAND. My console doesn't show it booting. I performed this flash last week and it worked. I had to erase uBoot inorder to test WinCE. Please advise.

  um. I've followed this guide multiple times today attempting to flash u-boot on my mini2440. However, I cannot get the mini2440 to boot into u-boot when I have the boot switch selecting NAND. My console doesn't show it booting. I performed this flash last week and it worked. I had to erase uBoot inorder to test WinCE. Please advise.
• Sep 08, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by buserror   -   The RAM doesn't start at address zero. it rarely does on any modern system! The address space is documented in the s3c2440 datasheet, and you'll see that RAM physical address starts at 0x30000000.

  The RAM doesn't start at address zero. it rarely does on any modern system! The address space is documented in the s3c2440 datasheet, and you'll see that RAM physical address starts at 0x30000000.
• Sep 02, 2009

  MiniBringup (Given a factory fresh mini2440, flash u-boot and a clean env...) Wiki page commented on by arcadiosincero   -   I'm going to use an emulated mini2440-via-qemu to demonstrate my embedded systems project for school, and I'm finding these instructions invaluable. Thank you very much! Everything pretty much worked as stated. I have a question though ... just for the sake of knowing ... you say up there when you tftp u-boot over the network you "load it bang in the middle of the RAM for convenience". What does that mean exactly? Why is it convenient? I tried using address 0 instead of 32000000 just to see what would happen, and it didn't work.

  I'm going to use an emulated mini2440-via-qemu to demonstrate my embedded systems project for school, and I'm finding these instructions invaluable. Thank you very much! Everything pretty much worked as stated. I have a question though ... just for the sake of knowing ... you say up there when you tftp u-boot over the network you "load it bang in the middle of the RAM for convenience". What does that mean exactly? Why is it convenient? I tried using address 0 instead of 32000000 just to see what would happen, and it didn't work.
• Sep 01, 2009

  issue 1 (Kernel headers are not correct in OE build) Status changed by buserror   -   yes I added an explicit fix for it. It used not to be necessary to do it. And yes I tested it, the /boot/uImage installed as part of the .ipkg works fine now.

  Status: Fixed

  yes I added an explicit fix for it. It used not to be necessary to do it. And yes I tested it, the /boot/uImage installed as part of the .ipkg works fine now.

  Status: Fixed