• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 2 3 [4] 5
46  General Category / General Discussion / Re: SheevaPlug - not ready for prime time? on: June 30, 2009, 06:32:38 AM
just my $0.02

Just my $0.02. The Sheevaplug Development Kit is just that, a development kit for tech savvy early adopters. I think GlobalScale Technologies is hoping those tech savvy early adopters will create products from the development kits (e.g Pogoplug) that will sell to non-tech savvy consumers.

So here's your chance to make a product!
47  Hardware and U-Boot firmware / U-Boot stuff / Re: Update u-boot and boot hangs at "done, booting the kernel" on: June 29, 2009, 08:21:04 AM
Hi Prafulla,
I know you're busy ...

I downloaded the kernel source from:
http://www.pogoplug.com/opensource/pogoplug-linux-2.6.22.18.tar.bz2
There is a "include/asm-arm/" folder but no "mach_types.h" file. I searched for "machine-id" with no results. The search for "machine_id" gave a couple of files but nothing related to arm processors.

So then I downloaded the Sheevaplug kernel source in "SheevaPlug_LSP.zip" with the same result, no "mach_types.h" file.

Then I looked in the uboot source and found "mach_types.h". It lists MACH_TYPE_? 0 through 727. It's not obvious to me how to figure out which to use for archNumber.

Any pointer would be appreciated. Thanks.

Update: I'm not certain, but looking through the code it looks like the arcNumber is ignored if mainlineLinux is set to no.
48  Linux Stuff / Linux distributions / Re: Reinstallation problem - PLEASE HELP on: June 28, 2009, 06:24:16 PM
LV,

Sounds like you're in the same place as me. IT boots using the CE (Cloud Engines) uboot but doesn't boot with the Marvell uboot. You may notice that the CE uboot doesn't have any USB commands. I'd be interested to hear if you get a Marvel Uboot to work and how you do it.

Regards,
Ian
49  Hardware and U-Boot firmware / U-Boot stuff / Re: Update u-boot and boot hangs at "done, booting the kernel" on: June 23, 2009, 01:37:05 PM
@Prafulla,
Did you get a chance to look at the log I attached?
Was it what you needed?
Any ideas what would cause the boot to hang?
Thanks,
Ian
50  Hardware and U-Boot firmware / U-Boot stuff / Re: Update u-boot and boot hangs at "done, booting the kernel" on: June 21, 2009, 07:55:04 PM
Prafulla,

Thanks for your interest and reply.

I have attached a log file from PuTTY..

It starts with a reboot to the CE uboot, followed by a printenv then a boot from the kernel in nand and ubuntu filesystem on USB. Log in and then cat /var/log/kern.log.

Reboot back to  CE uboot, bubt u-boot-rd88f6281Sheevaplug_400db_nand.bin, reset to marvell uboot, printenv, then the same boot from the kernel in nand and ubuntu filesystem on USB. It hangs on 'done, booting the kernel"

Power cycle reset to marvell uboot, bubt ce_uboot_v1.0.bin, reset back to the CE uboot, followed by a printenv then a boot from the kernel in nand and ubuntu filesystem on USB. Log in and then cat /var/log/kern.log.

End of the log.

Thanks for looking.
51  Linux Stuff / General Linux questions / Re: DHCP is not working after removing supersede on: June 20, 2009, 06:51:42 PM
Check this out

http://www.openplug.org/plugwiki/index.php/Frequently_Asked_Questions#Why_can.27t_it_resolve_hostnames.3F
52  General Category / General Discussion / Re: Some Sheeva performance numbers on: June 20, 2009, 11:26:20 AM
Quote
*Can anyone please change the black background?  I can't see all of the text on my laptop.
Select the Profile tab near the top then:
Look and Layout Preferences / Current Theme / Change / SMF Default Theme
53  General Category / General Discussion / Re: Sheevaplug installer - alpha-6 release - Testers needed on: June 16, 2009, 12:18:07 PM
The Marvell website shows a page with:
Marvell Plug Computing Partners
    * Axentra       
    * Cloud Engines, Inc.       
    * CTERA       
    * Eyecon Technologies       
    * GlobalScale Technologies, Inc.       
    * Ionics EMS       
    * Prosyst       
    * Tonido       
    * WebTView

Only GlobalScale and Cloud Engines has a "Buy" button so far. Right now I'm guessing we, the experimenters, are their main clientele. Product availability still seems to be a problem even in ones and twos.
54  Hardware and U-Boot firmware / U-Boot stuff / Update u-boot and boot hangs at "done, booting the kernel" on: June 16, 2009, 11:41:33 AM
I have a pogoplug that I would like to update u-boot for the additional features.

To boot from nand my bootargs and bootcmd are:
Code:
console=console=ttyS0,115200
bootargs_root=root=/dev/mtdblock2 ro
bootargs_mtdparts=mtdparts=nand_mtd:0x100000@0(u-boot)ro,0x00200000@0x100000(uImage)ro,0x02000000@0x00300000(root)ro,0x1DD00000@0x02300000(data)ro,0x00000033@0x00000200(NAND 16MiB 1,8V 8-bit)ro
bootcmd_nand_mtd=nand read 0x2000000 0x100000 0x200000; setenv bootargs $(console) $(bootargs_root) $(bootargs_mtdparts); bootm 0x2000000
I use
Code:
run bootcmd_nand_mtd
to boot.

When I boot this using the pogoplug uboot http://www.pogoplugged.com/download/11607/ce_uboot_v1.0.bin/ everything works fine.

When I update uboot using the original sheeva uboot:
Code:
bubt u-boot-rd88f6281Sheevaplug_400db_nand.bin
and answer n to the question
Code:
Override Env parameters? (y/n)
reset and boot as before, the kernel hangs at "done, booting the kernel"

When I bubt the uboot back to the pogoplug image and again do not override the env parameters, the kernel boots again.

The Cloud Engines uboot reports itself as
Code:
U-Boot 1.1.4 (Mar 18 2009 - 16:11:55) Cloud Engines (3.4.16)
The Marvell uboot reports itself as:
Code:
U-Boot 1.1.4 (Mar  2 2009 - 12:16:00) Marvell version: 3.4.16

I have the mtdparts set up correctly for the pogoplug although mtd3 is not used by pogoplug and mtd4 makes no sense to me but it is what the kernel reports if mtdparts is not defined.

The environment variables are the same, the kernel is the same, the root filesystem is the same, the only thing changed is the uboot image and that even reports itself as the same version.

Anyone have any guesses as to what would cause the kernel to hang?

 
55  General Category / General Discussion / Re: Sheevaplug installer - alpha-6 release - Testers needed on: June 16, 2009, 06:48:10 AM
The idea of the installer is to be able to recover a bricked plug. A bricked plug is one that is no longer able to boot or communicate over the serial port.

The runme.sh script running on your linux box calls an application openOCD also on your linux box. OpenOCD uses the jtag interface available through the miniusb port to control the bricked plug. The jtag interface is able to read and write directly to the nand and access the hardware e.g. an attached usb memory stick.

The runme.sh uses openOCD to erase the nand flash on the plug, then read the images from the usb stick attached to the plug and write those images into the nand, restoring the plug to it's original state.

Hope that description helps.
56  Hardware and U-Boot firmware / U-Boot stuff / Re: Save console environment variable? on: June 15, 2009, 08:08:37 PM
oops, made a mistake. It does save ok.
57  Hardware and U-Boot firmware / U-Boot stuff / Save console environment variable? on: June 15, 2009, 01:52:56 PM
I've tried changing the console environment variable and then using saveenv to save it but after I reboot it returns to it's original value.

Anyone else noticed this?
58  Linux Stuff / General Linux questions / Re: Trouble following "Boot USB" wiki on: June 10, 2009, 02:20:45 PM
Your bootcmd line has 0x800000 (800 thousand) but should be 0x8000000 (8 million) according to http://computingplugs.com/index.php/Booting_entirely_off_an_external_USB_device
59  General Category / General Discussion / Re: USB Flash Recovery from U-Boot Rev 1.2 ? on: June 09, 2009, 07:41:27 PM
I've got it working again, but I still don't really understand the problem.

Some additional information.
The device is a Pogoplug and not a sheeva plug development kit.
The kernel booting started failing immediately after I upgraded the uboot image using bubt.
The kernel booting was fixed as soon as I restored the Pogoplug uboot image.

The Pogoplug uboot default environment is very different from the marvell uboot default environment. Even when answering N to the question override environment, the environment changes enough that the kernel won't boot. I'm guessing that the default partitions are different.
60  General Category / General Discussion / USB Flash Recovery from U-Boot Rev 1.2 ? on: June 09, 2009, 06:32:06 AM
Somehow I've managed to get to a place where booting always hangs at:
Code:
Uncompressing Linux... done, booting the kernel.

I decided to try the USB Flash Recovery from U-Boot Rev 1.2. I followed the instructions and put the 4 files on an ext2 formatted USB drive, bubt, etc. But it still hangs at done booting kernel. I compared the log with appendix A in the instructions and almost all of it matches exactly. Any help would be appreciated.

Here is the log:
Code:
Marvell>> bubt u-boot-rd88f6281Sheevaplug_400db_nand.bin
Using egiga0 device
TFTP from server 192.168.2.41; our IP address is 192.168.2.29
Filename 'u-boot-rd88f6281Sheevaplug_400db_nand.bin'.
Load address: 0x2000000
Loading: #################################################################
         ###########################
done
Bytes transferred = 470808 (72f18 hex)

**Warning**
If U-Boot Endiannes is going to change (LE->BE or BE->LE), Then Env parameters s                                                                                                                                  hould be overriden..
Override Env parameters? (y/n) n
Erase 0 - 655360 ...
Copy to Nand Flash...
done
Marvell>> set loadaddr 0x2000000
Marvell>> set mtd1Size 0x400000
Marvell>> set filesize 0x44ad000
Marvell>> saveenv
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done
Marvell>> reset

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (Mar  2 2009 - 12:16:00) Marvell version: 3.4.16

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CEE60

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0
Marvell>> rcvr
USB:   scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Trying to load image from USB flash drive using FAT FS
reading /flashware.img

** Unable to read "/flashware.img" from usb 0:1 **
Trying to load image from USB flash drive using ext2 FS partition 0
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - usb 0:0 **
Trying to load image from USB flash drive using ext2 FS partition 1
....................................................................................                                               

clip

................................................................

72011776 bytes read
Update bootcmd

bootcmd: setenv bootargs $(console) root=/dev/ram0 rootfstype=squashfs initrd=0x                                                                                                                                  2200000,0x41ad000 ramdisk_size=67252 recovery=usb serverip=0.0.0.0; bootm 0x2000                                                                                                                                  000;
Booting the image (@ 0x2000000)...
## Booting image at 02000000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2009-03-30  15:30:26 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2148292 Bytes =  2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel
Pages: 1 2 3 [4] 5