• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 [2] 3 4 ... 12
16  Hardware and U-Boot firmware / U-Boot stuff / Re: MMC/SD support in u-boot on: September 18, 2009, 08:35:39 PM
westyd1982,  The solution to this problem in a slightly different context was given here by me ~1 week ago. I am in a bit of a hurry; search for recent msgs from me and you would see it.
17  Hardware and U-Boot firmware / U-Boot stuff / Found out reason!! Part 2. Why mult boot from usb was failing on: September 12, 2009, 01:32:55 PM
This is a followup to my own last post here.

My guess beiw about a buggy 'mode' in the usb start interface (?) appears right.  If I add 3 repetitions of the same run usb boot in the multiboot cmd chain, then every time it fails on the first time, and every time so far, it boots on the second attempt!!  Probably a subset of the command is all that is needed before the actual usb boot run cmd; but just repeating the full commands adds less than 2 seconds to the whole boot!  In about 10 consecutive boots under various conditions, with usb drive or sdcard from usb adapter, third repetition was never hit once!

18  Linux Stuff / Kernel / Re: new release on: September 11, 2009, 10:13:26 PM
Thank you very much!
19  Linux Stuff / Kernel / Re: new release on: September 11, 2009, 08:03:34 PM
Pardon me if this is out of topic here. While searching for it, I came across this thread.

I have done the alpha-6 kernel setup.  Now have moved the kernel and the rootfs to a SDCard and boot consistently from the SDCard (it is much faster boot).

Is there a recipe somewhere how I can upgrade my kernel to a or .6 on the sdcard (without touching the kernel in my nand -- which is the alapha-6-- or anything else in the nand)?  I have some interest in trying wireless, bluetooth, etc.  I read that these might be beginning to work in the later kernels...  Thank you!
20  Hardware and U-Boot firmware / U-Boot stuff / Found out reason!! Why mult boot from usb was failing on: September 11, 2009, 07:51:49 PM
Until today, I was too busy; was getting only a half hour or so everyday to work on my plug.  So today I methodically manually tested it.  Suspecting multiple problems was the reason I kept asking all those clarifications, I did have multiple problems!!

1.  The multi boot wiki page had a type it has to be 'usb 0:1', not as shown there 'usb0:1'.   When I asked my question in a couple of posts ago, I might not have been clear about it; I had other problems that is why I could not find it by simply trying it.  [In fact I had post a question about this at the Wiki page about this, yesterday I think.]

2.  With the above correction,  the boot now succeeds but not every time, from the sdcard in usbslot (w/ adapter).  There appears to be some 'mode' type problem or 'timing'.  I have a feeling if I simply repeat the same command 3 times (not tried yet) in the multiboot line, it might succeed a lot more frequently.

3.  My usb hardrive has not succeeded once yet, I do not not again it is the same type of problem where it might succeed only say once in 10, or the drive is incompatible.  When I try to do manually usb start, sometimes it sees two usb devices, some times one ( I have only one), but most time it does not see my drive; but a few times it see the drive.  So I surmise, if I keep repeating the command, once in a while the usb drive might  work too.

I know that for the linux load there is that delay, I wonder if that delay is effective for the kernel boot too, or even a higher delay is needed when the kernel comes off of the usb drive.  [I hope not all got tired of this thread and at least a few people would see the results --- it took a long time of experimentation -- I gave up all tennis watching today Smiley ]
21  Hardware and U-Boot firmware / U-Boot stuff / Re: Env setup for: uboot from mmccard, if fails then boot from usb sequence on: September 10, 2009, 09:39:13 PM
Two related questions:

1. In the multi boot wiki page there are references to both usb0:1 and usb 0:1.  Are both forms correct?  What is he semantics of usb0:1 ?

2.  There is also an initird section there, what is that for?
bootargs_usb=console=ttyS0,115200 root=/dev/sda1 ro panic=10 rootdelay=10
bootcmd_usb1=setenv bootargs $(bootusb_args); usb start; ext2load usb 0:1 0x00200000 /boot/uImage
bootcmd_usb2=ext2load usb 0:1 0x01100000 /boot/uInitrd; bootm 0x00200000 0x01100000
bootcmd=run bootcmd_usb1; run bootcmd_usb2; run bootcmd_nand
22  General Category / General Discussion / Re: Post your working SD cards here! on: September 10, 2009, 09:21:38 PM
Well, hotswapping data cards when the appropriate fs is used may not be same as pulling out a card from where the os is running, especially when it is ext2. 
23  Hardware and U-Boot firmware / U-Boot stuff / Re: Env setup for: uboot from mmccard, if fails then boot from usb sequence on: September 09, 2009, 07:30:03 PM
restamp, birdman,

Yes, I confirm birdman's last post.  I was trying to boot as restamp suggested.  In fact that was based on what I had success with when the kernel is in nand.  After that the same sdcard can booted as an sdcard in the mmc slot or as a usb device in the usb slot thru the adapter. 

Furthermore, with identical ext2 filesystems, and the whole set of files copied over to a usb hardrive (with rsync),  for rootfs booting purposes from the harddrive, or the sdcard thru the adapter in the usb slot, no enviroment changes are needed in uboot.  Simply put one or the other in and hit boot; for me the usb drive needed a 10 delay, and the sdcard may work with a 5 sec delay, but I use 10 sec for both.

With the uImage on the rootfs externally as /uImage, the commands in the multi boot wiki worked fine --- I test as single boot also.  But I cannot get either the sdcard or the usbdrive to boot from the usb.

So I repeat my quetiion:  does anybody know for the multi boot in our Wiki for usb boot, are the parameters given when the uImage is in the same boot partition as the rootfs, or there was a separate volume for the uImage?

I have not done this yet, but I feel I can get a mixed-type of multi boot working by booting from the sdcard slot as in the wiki, and then using my older kernel in nand, rootfs in usb bootcmd portion as he second in the mutliboot chain.  Of course this would not allow nand boot as the third one...
24  Hardware and U-Boot firmware / U-Boot stuff / Re: Env setup for: uboot from mmccard, if fails then boot from usb sequence on: September 08, 2009, 11:40:15 PM

OK I got the /uImage on my SDCard, by following the procedure in Multi Boot in the Wiki, I can boot kernel and rootfs fom the SDCard in the mmcslot.  The whole boot is faster.

However with the same card in the usb (thru an adapter), or he same image on a usb hard drive, the procedure in the Wiki for USB sda1 start gives a bad magic number error in the boot console.  Any ideas?  I have a couple of clarifications about the Wiki page:

1.  Is the parameter like usb0:1 without any blank, or usb 0:1 as I have seen elsewhere in the forum here?

2.  Is he Wiki description parameter when the uImage in the same rootfs root as /uImag, without a boot volume partition.  I have only a combined partion like yours; is the parameters there to be modified in any form?  (of course I have changed the /boot/uImage path their to my /uImage and that works fine for when the sd card is in the mmc slot.

Since your setup is similrar to mine, what is he line you use for he usb load setup?  BTW, usb drive is connected directly to the usb port, and when sd card is used there. again to an adapter without any hub.  BTW, I can boot from the same usb drive or sdcard in the usbslot, correctly if I start from the kernerl in the nand...  So what is the cause of this bad magic number (ext2 fs) ?

25  Hardware and U-Boot firmware / U-Boot stuff / Re: booting from USB drive > 2GB on: September 07, 2009, 06:17:31 PM
Do you have the uImage in nand, and just the rootfs on your dev/sda1?  If so, I think there my be an error in you env settings;  I cannot easily tell you, since I am on a remote ssh...
26  Hardware and U-Boot firmware / U-Boot stuff / Re: booting from USB drive > 2GB on: September 07, 2009, 01:45:24 PM
I posted about this recently here.  Adding a boot delay may work. Search for it: look for posts from me.
27  Hardware and U-Boot firmware / Hardware / Re: Alternative power supplies on: September 07, 2009, 01:42:17 PM
I must have missed it.  What is the voltage you are supplying to this dc socket for powering the plug?
28  Linux Stuff / Kernel / Re: uBoot and booting from SD/USB? on: September 05, 2009, 02:46:58 PM

Thank you!  BTW, I only have normally one usb drive on the usb port directly connected.  And for copying over uImage, I have no problem to make an sdcard the external device if needed.

Ok I want to follow your advise to
locate the kernel uImage on the medium you used to populate it to your NAND originally
  I dont have any notes of my steps, but I recall it went without a hitch.  Where will I find this image?  BTW, there is no easy way to check the integrity of the nand area to make the dd is the way to go.  If I cannot confirm the integrity, I do not wish to take that route.  After copy when I tried to boot, would I get any indication such as bad checksum, when I try to use if it was bad?  That is sufficient confirmation for me, it it was checking ...
29  Hardware and U-Boot firmware / Hardware / Re: Internal Battery Powered "Plug" on: September 05, 2009, 02:34:07 PM
My guess is it wont work below 4.5v reliably.  I have not studied its circuits, but it probably generates first a 5v and then all other volatages are regenerated with dc-dc tiny supplies inside.  Because of those secondary supplies, it may even work done to 4.4 at the 5v input; otherwise most would start becoming unreliable at 4.7v.  So your best bet is 4x NiMh inside, if you allow for a fatter plug; with a modern set of 2600mah AAAs, that could run for 3 to 4 hours without any external devices during the first year of the battery life; or you have to use 2x LiIo.  I would be interested in your experimental results.
30  Linux Stuff / Kernel / Re: uBoot and booting from SD/USB? on: September 05, 2009, 01:17:40 PM
I think this is one of the problems to overcome you may have hinted at earlier.  I've been running this way w the rootfs on usb for some time (booting the the rootfs from usb, kernel still in nand) after my Alpha-6 upgrade.

I am going to copy over my uImage to my currently running usb (hardrive) rootfs  as /uImage.    But I fail at the uImage mount step:

# ls -l /dev/mtd*
crw-rw---- 1 root root 90, 0 Sep  3 17:01 /dev/mtd0
crw-rw---- 1 root root 90, 1 Sep  3 17:01 /dev/mtd0ro
crw-rw---- 1 root root 90, 2 Sep  3 17:01 /dev/mtd1
crw-rw---- 1 root root 90, 3 Sep  3 17:01 /dev/mtd1ro
brw-rw---- 1 root disk 31, 0 Sep  3 17:00 /dev/mtdblock0
brw-rw---- 1 root disk 31, 1 Sep  3 17:00 /dev/mtdblock1

# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00400000 00020000 "uImage"
mtd1: 1fb00000 00020000 "rootfs"

# mount -t ubifs /dev/mtdblock0 /mnt/mtdblock0/
mount: wrong fs type, bad option, bad superblock on /dev/mtdblock0,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

I cant find/remember the intermediate step needed before the mount, which I think you already  know about.  Help, please.
Pages: 1 [2] 3 4 ... 12