• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1] 2 3 4
1  General Category / Success stories / Re: Mimo 740 Touch Display on: December 03, 2009, 06:38:58 PM
I'm pretty sure I had the same problem.

Mike
2  General Category / General Discussion / Re: Another Bad Magic Number problem on: December 03, 2009, 06:37:39 PM
Oh well... worth a shot, I guess.

Good luck,
Mike
3  Linux Stuff / Kernel / Re: Help before kernal upgrade on: December 02, 2009, 09:33:56 AM
Oops..   Shocked I meant to write bootcmd!  Good catch!

Mike
4  General Category / General Discussion / Re: Another Bad Magic Number problem on: December 02, 2009, 09:31:48 AM
Hi,

After you execute 'usb start' what happens when you do: 'fatls usb 0:1'?

Do you see the files in that directory?  Specifically, do you see 'u-boot.bin'?


Mike

5  Linux Stuff / Kernel / Re: Help before kernal upgrade on: December 02, 2009, 07:23:21 AM
Hi,

No worries on the help.  Lots of folks have helped me get up to speed on this, and I'm happy to pay back my debts.

Take a quick read through on the ./readme that you'll execute.  It's pretty short and fairly easy to follow.  It's good to get an understanding of what it is that you are about to do...

I usually build my own kernels and flash them myself using the procedure I posted earlier.  I write the uImage to NAND at a specific address.  Then I modify the environment variables to match the uImage name and address location.  Also, I change the rootfs to load from the MMC.  So, I don't usually use the ./readme script or cbxbiker61's kernels, although I have done so on occasion and have figured out problems with my own home-brewed kernels as a result.  So, I'm very thankful they are there.

If you read through cbxbiker61's ./readme script, you'll find that you need to either pass in --nandkernel or --rootkernel as options.  If you pass no options, you'll get a usage error and the script will exit. 

If you choose --nandkernel, he'll write the new uImage to NAND.  If you choose --rootkernel, he'll right the uImage to the /boot directory which is in your rootfs (located on your SD card, in your case).  He provides the environment variable required to be set to boot from NAND and pull the rootfs from NAND:
 
Code:
setenv bootargs rootfstype=jffs2 console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=192.168.1.9:192.168.1.4:192.168.1.4:255.255.255.0:DB88FXX81:eth0:none

You, however want to boot from NAND (or SD) and pull the rootfs from your SD card.  If you want to boot your uImage from NAND and load your rootfs from your SD card (which is what you are doing now), doing the following should do the trick:

Code:
setenv bootargs 'console=ttyS0,115200 root=/dev/mmcblk0p1 rw rootfstype=ext2 rootdelay=10';
setenv bootargs '$(bootargs_console) $(mtdpartitions) $(bootargs_root); mmcinit; nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000'
boot

DISCLAIMER:  The above is to the best of my knowledge.  While I believe it will work, and I have thought about it a bit before sitting down to write it, I can not absolutely guarantee your success.   Wink

There might be others out there who could chime in to let you know if this all looks good, or whether I've made some egregious error....

No matter what, look at this as a gigantic learning opportunity!  Smiley

Mike
6  Linux Stuff / Kernel / Re: Help before kernal upgrade on: December 01, 2009, 03:12:18 PM
Hi,


setenv bootargs 'console=ttyS0,115200 root=/dev/mmcblk0p1 rw rootfstype=ext2 rootdelay=10';
setenv bootargs '$(bootargs_console) $(mtdpartitions) $(bootargs_root); mmcinit; nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000'
boot

I believe the above should work to get you booting with your rootfs on your SD card.  In the above, you are telling uboot to look for the rootfs on the first partition of the SD card.  Also, I added in the mmcinit command to make sure that uboot recognizes the card.

Please post with whether it works or not for you.  If it does, please repeat it and enter 'save' to write the changes to nand.  If you don't save it, the changes will only last for the single reboot and will  be lost after that.

Good luck,
Mike
7  Linux Stuff / Kernel / Re: Help before kernal upgrade on: December 01, 2009, 08:37:40 AM
I agree.  The installer will handle setting up the system to work with MMC (SD) for you.  Please post any questions about the installation procedure, after you run through the README which is included with it.

Mike
8  General Category / General Discussion / Re: Sheevaplug installer - version 1.0 on: November 30, 2009, 06:53:12 PM
Are you trying to run the rootfs and the uImage from nand or mmc?  When you run the runme app, do you pass 'nand' or 'mmc' as a parameter to it?


Just want to make sure I know what you are trying to do so that I can try to give you the correct advise.

If you are trying to setup a uImage to boot from nand and a rootfs to be loaded from your MMC device (SD card), then the instructions I gave earlier will work for you.  Just make sure the rootfs is on the first partition of the SD cards, and please format that partition to ext2 prior to loading your rootfs atop it.

PM me if you have any questions.

Mike
9  Linux Stuff / Kernel / Re: Help before kernal upgrade on: November 30, 2009, 06:28:48 PM
Hi,

I mean all of your uboot params...

When you interrupt the boot, and you are at the uboot command prompt, type "print".  I will output all of the environment variables.  Please copy and paste them here.  Before recommending anything, I'd like to know what your current config is.

Mike
10  Linux Stuff / Kernel / Re: Help before kernal upgrade on: November 30, 2009, 10:50:27 AM
Can you please print out all of your environment variable and post them?

Mike
11  General Category / General Discussion / Re: Another Bad Magic Number problem on: November 30, 2009, 08:18:09 AM
Hi,

I'm a bit confused by your description...  Do you have the previously working uImage on your thumb drive?  By the looks of it, you are able to connect to the plug via serial cable (that's where the output came from, I take it)....

So, if the goal is to write the uImage to the NAND and get your plug back up and running, you could do the following:

nand device 0
usb start

1.  Have the correct uboot.bin on the first partition of your USB stick, and write it to NAND

nand erase 0x0 0xa0000
fatload usb 0:1 0x8000000 /u-boot.bin
nand write.e 0x8000000 0x0 0xa0000
reset


2. have the uImage you want on the first partition of your USB memory stick and write this to NAND

usb start
nand erase 0x100000 0x400000
fatload usb 0:1 0x8000000 /uImage
nand write.e 0x8000000 0x100000 0x400000

If you want to have your rootfs on a MMC card, then you are done configuring the NAND.  Just have your rootfs on the first partition (ext2 based) of your SD card.

Set the following environment variables, telling uboot to use the MMC for the rootfs and boot from NAND. 

setenv bootargs 'console=ttyS0,115200 root=/dev/mmcblk0p1 rw rootfstype=ext2 rootdelay=10';
setenv boot_nand 'nand read.e 0x2000000 0x100000 0x400000'
setenv bootcmd 'mmcinit;run boot_nand; bootm 0x2000000'


then reset (or save first, if you feel brave :-))


Post back with any questions, but the above works for me.

Mike
12  General Category / General Discussion / Re: Sheevaplug installer - version 1.0 on: November 29, 2009, 05:15:55 PM
Hi,

Is there a reason you've modified the Installer 1.0 bootargs_root?

If you leave them with the standard settings, it will write to NAND correctly.

Mike
13  General Category / Success stories / Re: Mimo 740 Touch Display on: November 28, 2009, 02:42:15 PM
Hi,

I had the same experience when I first set it up.  I used KDE, and it worked better, so I did not go back to gnome. 

Mike
14  General Category / General Discussion / Re: Sheevaplug installer - version 1.0 on: November 28, 2009, 01:00:22 PM
Hi,

OK... got it working. 

My whole problem was that I was loading the uImage at the incorrect address.  Very weird for me, as my previous builds were working with the other address.   This is for booting from nand but with the rootfs on SD card:

*************************************************************************************************
setenv bootargs 'console=ttyS0,115200 root=/dev/mmcblk0p1 rw rootfstype=ext2 rootdelay=10';
setenv boot_nand 'nand read.e 0x2000000 0x100000 0x400000'
setenv bootcmd 'mmcinit;run boot_nand; bootm 0x2000000'
*************************************************************************************************

I am running the kernel I compiled with the SD card as the rootfs.  I am using NAND for the uImage.  I wrote this using the following procedure:

*************************************************************************************************
nand erase 0x100000 0x400000
fatload usb 0:1 0x8000000 /uImage
nand write.e 0x8000000 0x100000 0x400000
*************************************************************************************************

So, to summarize the first problem I had was that I did not build the SDIO_UART into the kernel (I had it incorrectly added as a module).  This caused a hang in the boot.  Then, once I figured that out, I changed the load address, and all began to work.

Hopefully, this will resolve the instability problem I've been having when multiple USB devices were plugged in simultaneously.  They were whacking the USB drive with EXT2 Inode errors.  That's the entire reason I added in the support for the SD card - to work around this issue.

On Monday, I'll try the whole thing out with my MIMO 720 touch display and my USB keyboard and mouse.  At home with me, I have the display, but not the keyboard/mouse, so it will have to wait.

Thanks for all of the suggestions.  I hope this helps someone along the way.

Mike

15  General Category / General Discussion / Re: Sheevaplug installer - version 1.0 on: November 28, 2009, 09:01:11 AM
Yes.  Thank you for your suggestion.  I made sure I was setting these env variables.

Right now, the problem appears to be  that the console is not getting updated with output from the kernel.

Mike
Pages: [1] 2 3 4