• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 2 [3] 4 5 ... 22
31  Hardware and U-Boot firmware / Hardware / Re: Is this a Sympton of a dying SD-Card? on: April 05, 2011, 07:54:48 PM
4G should be enough to fix a 2G file system. may be something I have not thought about yet.
32  Hardware and U-Boot firmware / Hardware / Re: Is this a Sympton of a dying SD-Card? on: April 05, 2011, 09:24:54 AM
Usually when fsck failed with not enough memory that mean swap is not set. fsck require large amount of memory because it does all the correction in memory before it write back to storage. simply setup a swap space usually will address fsck not enough memory problem.

Good luck Smiley
33  Hardware and U-Boot firmware / Hardware / Re: Is this a Sympton of a dying SD-Card? on: April 05, 2011, 06:01:26 AM
I'll say it is probably dying if not at lease the filesystem on it is dirty. take the SD card to another PC have the filesystem repaired first. And while you have the SD card on the PC, make backup of it after filesystem repair.

Good luck Smiley
34  Hardware and U-Boot firmware / U-Boot stuff / Re: Choosing uboot/uImage for Guru Server on: April 05, 2011, 05:54:38 AM
Please wait, the u-boot.bin is not bootable. the address is wrong.

You can get source code and compile you self or I can upload a new one after I got home.

Good luck Smiley
35  Hardware and U-Boot firmware / U-Boot stuff / Re: Choosing uboot/uImage for Guru Server on: April 04, 2011, 03:36:05 PM
OK, this version load at 0x800000.

To verify, md5sum for u-boot.bin is
Code:
94d521fda4bd905831b8e292ac93049b  u-boot.bin

In your u-boot prompt do
Code:
Marvell>> mw 0x800000 0 0x60000
Marvell>> tftp 0x800000 /path/to/u-boot.bin
Marvell>> crc32 0x800000 0x60000
CRC32 for 00800000 ... 0085ffff ==> 7ae0f097
Marvell>> md 0x844688
00844688: 6f422d55 3220746f 2e313130 702d3330    U-Boot 2011.03-p
00844698: 74676e69 742d6f6f 2d747365 28203176    ingtoo-test-v1 (
008446a8: 20727041 32203430 20313130 3831202d    Apr 04 2011 - 18
008446b8: 3a35313a 0a293735 7672614d 2d6c6c65    :15:57).Marvell-
008446c8: 75727547 67756c50 00000000 00847910    GuruPlug.....y..
Marvell>>
Marvell>> go 0x800000
## Starting application at 0x00800000 ...


U-Boot 2011.03-pingtoo-test-v1 (Apr 04 2011 - 18:15:57)
Marvell-GuruPlug

SoC:   Kirkwood 88F6281_A1
DRAM:  512 MiB
NAND:  512 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0 [PRIME], egiga1
88E1121 Initialized on egiga0
88E1121 Initialized on egiga1
Hit any key to stop autoboot:  0
36  Hardware and U-Boot firmware / U-Boot stuff / Re: Choosing uboot/uImage for Guru Server on: April 04, 2011, 11:25:38 AM
hum, I just realize you said you load it in 0x80000, this will not work, it have to be at 0x600000. Th code was compile to that specific address.

I have one time run in to this tftp freeze problem because the cpu cache was wrong. so check you u-boot with "help" command, does it have "icache" and/or "dcache" command? if it have them run the commands without and argument, one should be "off" and the other should be "on". as which should be "on/off" I need to go home to check on my plug.

Good luck Smiley
37  Hardware and U-Boot firmware / U-Boot stuff / Re: Choosing uboot/uImage for Guru Server on: April 04, 2011, 11:17:17 AM
Sorry, once you load it, ue the "go" command. as in
Code:
go 0x60000
38  Hardware and U-Boot firmware / U-Boot stuff / Re: Choosing uboot/uImage for Guru Server on: April 01, 2011, 12:45:30 PM
I am so dumb Sad, I should let you know you can tftp the u-boot.bin as well. no need to use openocd. just make sure you load it in to 0x600000.

I think my openocd is v0.3 or something there about.

Good luck Smiley
39  Hardware and U-Boot firmware / U-Boot stuff / Re: Choosing uboot/uImage for Guru Server on: April 01, 2011, 06:59:05 AM
If guruplug_init did not work then the rest will not work.

you will need to go back to the openocd windows to see if openocd can get successfully sync, some where in the openocd message must have this line
Quote
"Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)"
the important part "found: 0x20a023d3" or something similar. only you got that message then you can proceed to the other window do the rest.

One more thing, do not flash the uboot.bin to NAND, it is not bootable, I want to make sure we got a working version before burn it in.

Good luck Smiley
40  Hardware and U-Boot firmware / U-Boot stuff / Re: Choosing uboot/uImage for Guru Server on: March 30, 2011, 08:04:30 PM
Hi crunch, hope you are still working on this problem. anyway I have something for you to test. a u-boot at 2010-12 with a lots of options enabled, a linxe kernel-2.6.32-r7-unionfs, a initramfs of my custom build and a simple u-boot environment setup image file.

you will needd to use openocd to load uboot to memeory and place kernel,initrams and envsrc.uimg to the tftp server following my instruction we shold be good to go.

1. load u-boot, at command prompt: openocd -f /path/to/board/guruplug.cfg -s /path/to/board/..
Quote
   # I am using guruplug -installer directory structure. lets say your guruplug-installer is
   # at /tmp/guruplug-installer/, under /tmp/guruplug-install there should be a "openocd" dir
   # so for example you can, cd /tmp/guruplug-install,
   # openocd -f ./board/guruplug.cfg -s ./openocd.
2, on second windows do
Code:
telnet localhost 4444
3. at prompt do,    ######### you should have third window ready connect to /dev/ttyUSB0
Code:
guruplug_init
load_image /path/to/where/you/save/u-boot.bin 0x600000 #You must use full path.
resume 0x600000
4. at the window that connect to ttyUSB0, interrupt autoboot.
Code:
U-Boot 2010.12-dirty (Mar 28 2011 - 18:39:13)
Marvell-GuruPlug

SoC:   Kirkwood 88F6281_A1
DRAM:  512 MiB
NAND:  512 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0 [PRIME], egiga1
88E1121 Initialized on egiga0
88E1121 Initialized on egiga1
Hit any key to stop autoboot:  0
5. At the third windows with Marvell>> we need to setup for network transfer, so if you have dhcp environment handy then you can simply run "dhcp" this will setup "ipaddr" and "serverip" hopefully,
6 or you can manually setup network,
Code:
Marvell>> setenv ipaddr xxx.xxx.xxx.xxx(your plug ip address)
Marvell>> setenv serverip xxx.xxx.xxx.xxx(your tftp server address)
7 now first load the u-boot environment variables image file,
Code:
Marvell>> tftp 0x800000 /path/to/envsrc.uImg
Marvell>> imi 0x800000

## Checking Image at 00800000 ...
   Legacy image found
   Image Name:   u-boot env
   Image Type:   ARM U-Boot Script (uncompressed)
   Data Size:    647 Bytes = 647 Bytes
   Load Address: 00000000
   Entry Point:  00000000
   Contents:
      Image 0: 639 Bytes = 639 Bytes
   Verifying Checksum ... OK

Marvell>> env default -f
Marvell>> source 0x800000
8. the envsrc.uImg setup some assumuption for location of kernel and initramfs file. so if they don't match your setup you can change by
Code:
Marvell>> setenv tftpinitrdfile /path/to/guru-initramfs.uImg
Marvell>> setenv tftpkernelfile /path/to/guru-uImage
9. if you are sure the "tftpinitrdfile" and "tftpkernelfile" are correct match you setup then we are read to load them to memory,
Code:
Marvell>> run tftp_load_ki
10. after load successful we verify that we have good images in memory by,
Code:
Marvell>> imi ${k}
## Checking Image at 02000000 ...
   Legacy image found
   Image Name:   Linux-2.6.32-gentoo-r7
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1222036 Bytes = 1.2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK

Marvell>> imi ${i}
## Checking Image at 01100000 ...
   Legacy image found
   Image Name:   Guruplug initramfs 20100529
   Image Type:   ARM Linux RAMDisk Image (lzma compressed)
   Data Size:    2820877 Bytes = 2.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

11. if everything looks ok, we are ready to boot, if you have a UBI based rootfs and your rootfs volumne is "rootfs" then you can try to run
Code:
Marvell>> run bootmki_ubi
or else you can boot into initramfs by
Code:
Marvell>> run bootmki_interactive
12. if everything went will, you should see all the normal kernel boot up messages. if not then post what ever happen and we will work from there.

Good luck :-)
41  Hardware and U-Boot firmware / Hardware / Re: I just received a new Dreamplug today on: March 29, 2011, 02:58:28 PM
Hey, I am in same boat as you are!  I am going to get GST to change mine too.

Thank you very much for dig in to find out what is going on.
42  Hardware and U-Boot firmware / Hardware / Re: I just received a new Dreamplug today on: March 29, 2011, 09:48:54 AM
You can use any kernel that is compile support guruplug. the archnumber used in u-boot is target to guruplug machine type. I think without replace the rootfs you need kernel and modules. so as long as you can get module files then dump them in to /lib/modules/`uname r-`/ you are good to go.

Good luck Smiley
43  Hardware and U-Boot firmware / U-Boot stuff / Re: Choosing uboot/uImage for Guru Server on: March 25, 2011, 07:22:34 PM
Reflashing my box with stock Guruplug images is really what I'm trying to do - the OS images hosted with the installer don't work for me. What I suspect is that my plug is from an "in-between lot" which was built in a slightly different way from the normal gurus. For example, I noticed that when I tried to update my plug, the apt repo was on an unreachable local IP subnet, probably somewhere deep in globalscale-land. There were a few other things laying around that suggested the box was built hastily and/or in a one-off manner - backup files, extra wireless firmware, and some sloppy init scripts. This doesn't bother me particularly, but it does indicate that my box might've been built in a custom manner. I can't really think of anything that would cause this behavior however. I did notice that when I loaded Debian uImages (from their nightly kirkwood build repository), I got an "unsupported device" error message.

Perhaps I should nand erase the entire flash, reinstall uBoot, and build up the plug from nothing? I might be able to set up debugging via openocd/gdb, which could help.

pingtoo, I'd be happy to try out some of your uboot and/or kernel builds. I'm fine with learning more about these devices while I'm busy unbricking... Eventually I should probably set up USB booting so I don't wear out the NAND.

Are you comfortable loading u-boot from openocd? I am having problem setup u-boot from tftp for guruplug+.
44  Hardware and U-Boot firmware / U-Boot stuff / Re: Choosing uboot/uImage for Guru Server on: March 24, 2011, 08:36:33 PM
OK, let me try to make u-boot so we can test. I only have guruplug-plus. it make take me a few try before I can get openocd sync to test my u-boot.
45  Hardware and U-Boot firmware / U-Boot stuff / Re: Choosing uboot/uImage for Guru Server on: March 24, 2011, 01:13:20 PM
I see two options, one we continue debug. start from beginning. the other option replace your u-boot to more recent version and start from there. I am currently develop my dreamplug system. if you interest I can produce a u-boot and/or kernel too see if it will help. if you choose second option you will need to be patient, I can produce u-boot right away but the kernel is where I am develop at the moment, I am building my initramfs to support multiple root fs option.
Pages: 1 2 [3] 4 5 ... 22