• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1] 2 3 ... 22
1  Linux Stuff / Kernel / Re: new kernel available on: June 30, 2011, 04:38:01 AM
Have you tried setup your environment with systemd yet? if you do how does it feel?

2  Hardware and U-Boot firmware / U-Boot stuff / Re: Boot rootfs from 32GB microsd? on: June 22, 2011, 05:32:00 AM
You may have lost some files but the system seems to be intact. I guess you can give it a try to see if you can load this time.

The only thing I think is more of my fault is I want too see how many partition your have. the command "fdisk -l /dev/sdf1" should have been "fdisk -l /dev/sdf" without the "1" at the end. but that is ok. you have show me the sdf1 is the root disk and you were mounting from partition 1.

I think the article you follow given wrong instruction. To copy a live (mounted) file system using "cp" is wrong. should have been command like "cpio" or "tar" even "rsync" could do a better job. also the live file system require all in memory info flush down first before copy.
3  Hardware and U-Boot firmware / U-Boot stuff / Re: Boot rootfs from 32GB microsd? on: June 21, 2011, 06:04:06 AM
The file system is dirty. You need to clean it up first before using it. Take the SD to another linux computer, run "fsck -y /dev/your_sd_device". while you at this linux computer do following commands and post the output so we can see if there any other anomaly.
fdisk -l /dev/your_sd_device
ls -l /
ls -l /dev/{console,null}

4  Hardware and U-Boot firmware / U-Boot stuff / Re: Dreamplug/openocd on: June 16, 2011, 08:40:13 AM
Please see this post http://plugcomputer.org/plugforum/index.php?topic=5848.msg18954#msg18954
5  Hardware and U-Boot firmware / U-Boot stuff / Re: Dreamplug esata boot on: June 15, 2011, 09:06:30 PM

Attached are two u-boot files for dreamplug, one is used for testing/load, the other is bootable version.

The code is still in development, so little bit of debug information but it does very little impact on performance.

The kernel can be used by this u-boot need to have guruplug machine type or else you will get the silent treatment.

The kernel also must not probe NAND or else you will get stuck at "loop: module loaded" line.

Now how to setup the u-boot. There are three major step/phase.
1. save existing environment by boot to normal u-boot prompt and use the "printenv" command the select/cut/paste the result to a file.

2. load the first u-boot.bin to have a runtime version. NOTE, this u-boot.bin is not bootable, do not flash this one. commands,
2.1 open serial windows, i.e. putty /dev/ttyUSB0 (not the right command, just to illustrate the idea.)
2.2 At you unix host, using openocd to connect then on second windows do telnet localhost 4444 to get openocd prompt. as follow,
openocd -f plug_openocd.script
, second windows,
telnet localhost 4444
your will see this
Connected to localhost.
Escape character is '^]'.
Open On-Chip Debugger
, do following,
Connected to localhost.
Escape character is '^]'.
Open On-Chip Debugger
> init
> kirkwood_init
> load_image /path/to/u-boot-base0x800000.bin bin 0x800000 bin
> resume 0x800000
Now at your serial tty window, interupt the auto boot sequence. you should be at "Marvell>> " prompt. At this point you can play around, nothing have damaged your existing environment, a reset command will bring you back to factory shipped u-boot. (Note, you may lost the u-boot env, this is to be expected, because I use a different address offset on the NOR)
3. flash the bootable u-boot.
3.1 copy the "u-boot.kwb" to a media that can later plugin to dreamplug. (FAT or EXT2)
3.2 At serial tty windows, do (use media SD card as example)
Marvell>> usb reset
Marvell>> ext2load usb 1 0x6400000 /u-boot.kwb
Marvell>> sf probe 0
Marvell>> sf erase 0x0 0x100000
Marvell>> sf write 0x6400000 0x0 0x100000
# Now retype your u-boot env ... (example)
Marvell>> setenv ethaddr 00:11:22:33:44:55
Marvell>> setenv eth1addr 00:11:22:33:44:56
Marvell>> setenv bootargs console=ttyS0,152000 rdinit=/bin/sh
Marvell>> setenv ...
Marvell>> saveenv
Marvell>> reset

All done. new u-boot looks like this
U-Boot 2011.03-00012-g1a93b51-dirty-pingtoo-v1.2 (Jun 15 2011 - 22:44:57)

SoC:   Kirkwood 88F6281_A1
DRAM:  512 MiB
SF: Got idcodes
00000000: c2 20 15 c2 20    . ..
SF: Detected MX25L1605D with page size 256, total 2 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0, egiga1
88E1121 Initialized on egiga0
88E1121 Initialized on egiga1
Hit any key to stop autoboot:  0

6  General Category / General Discussion / Re: Cannot flash new SPO S/N Sheevaplug on: June 13, 2011, 11:00:59 AM
So you just want a quick way to flash. here is a trick, as long as you can flash u-boot you can do this,

1. Prepare a blank file size at most 512MB (but only need to be large enough to hold u-boot/env/rootfs.
dd if=/dev/zero of=blankfile bs=1m count=512

2. Write stuff you want in NAND to the blank file first.
dd if=/path/to/u-boot of=/path/to/blankfile conv=notrunc
dd if=/path/to/u-boot-env.bin of=/path/to/blankfile conv=notrunc skip=1280
dd if=/path/to/kernel of=/path/to/blankfile conv=notrunc skip=2048
dd if=/path/to/rootfs of=/path/to/blankfile conv=notrunc skip=10240

3. Flash the blankfile to NAND
openocd -f /path/to/sheevaplug.cfg
On a seperated terminal session,
telnet localhost 4444
nand probe 0
nand erase 0 0x0 [expr 512*1024*1024]
nand write 0 /path/to/blankfile 0 oob_softecc_kw

Above code is just right off my head, have not been tested, but it should give you a general direction on what to work on. Be very careful about the nand erase part, once it started you lost your u-boot on NAND.

Good luck Smiley
7  General Category / General Discussion / Re: Cannot flash new SPO S/N Sheevaplug on: June 13, 2011, 06:27:21 AM
The problem is the rootfs on the NAND is jffs2 and your kernel command line specify using UBI, they are not compatible, so you boot failed.

As far as I can tell from your posts, you have not successfully flash rootfs to NAND. However I cannot tell if you were able to load kernel from SD. IF you do then there always have a way to manually load rootfs/kernel to NAND. so let us know if you were able to go on to u-boot prompt to load kernel from SD and we can work from there.

Good Luck Smiley
8  General Category / General Discussion / Re: Ethernet Mixup on: June 10, 2011, 11:49:41 AM
This is udev issue, nothing to do with hardware. the udev was design to maintenance MAC to name rule. so the very first time udev detect the ethernet interface it create a rule to map the NIC's MAC to eth0. Once you have second NIC it will map to eth1 because eth0 already exist in the rule file. since you clone the file system the rule file also get copy to second plug. And since your second plug have different NIC/MAC it will give it a name "eth1".

9  Hardware and U-Boot firmware / U-Boot stuff / Re: Dreamplug esata boot on: June 09, 2011, 06:24:15 AM
Yes, it is possible to replace u-boot. I have a version in test, if you want to take the risk I can send it to you. I finish the build but have not have time to test it complete. I know it work because I load it in to memory and played with usb, and ide. however this version will erase environment variables in NOR, you will need to re-enter them manually.
10  Hardware and U-Boot firmware / U-Boot stuff / Re: Dreamplug esata boot on: June 07, 2011, 09:39:27 AM
Sorry, I did not notice the default u-boot for dreamplug does not have 'ide' subsystem.

Using kernel from one device and rootfs from another device is a goos solution too.

Good luck Smiley
11  Hardware and U-Boot firmware / U-Boot stuff / Re: Dreamplug esata boot on: June 06, 2011, 10:30:13 AM
Since the default uboot does not support ext2, you will need to use fat.

make sure your kernel on the fat parition then do

ide start

fatload ide 0:2 /kernel
12  Hardware and U-Boot firmware / U-Boot stuff / Re: Dreamplug/openocd on: June 02, 2011, 06:23:52 AM
At this time, openocd does not have support for the dreamplug's SPI/NOR so it cannot be done. however you can use openocd to halt the dreamplug, transfer your uboot into memory, resume and flash with existing command.

Warning, do not flash just any u-boot code you got. your u-boot code need to be able to boot from SPI so use "mkimage -l -u-boot-filename" to check it is bootable from SPI.

Good luck Smiley
13  Hardware and U-Boot firmware / U-Boot stuff / Re: NET: Registered protocol family 10 on: April 27, 2011, 07:07:30 AM
Once you got into single user mode you are root and can change anything you want.

I am not 100% sure I understand your situation, you said "Yes, I have not change the /etc/fstab", so if you have not change /etc/fstab than my analysis is wrong and you do not need to go into single user mode to change anything.

Anyway, if you want to use SD as your rootfs then change your "bootargs_root" to have "root=/dev/sdc[partition number where your rootfs is] rootwait". This should let you boot from SD.

Having kernel on SD allow you to upgrade kernel easier, I think you are using debian alike distro. I think it have some simple upgrade script to upgrade kernel.

Good Luck Smiley
14  Linux Stuff / Kernel / Re: Kernel hangs after upgrade. on: April 27, 2011, 06:12:17 AM
So I guess you went back to an older kernel, please see this thread http://plugcomputer.org/plugforum/index.php?topic=2002.0

Good luck Smiley
15  Hardware and U-Boot firmware / U-Boot stuff / Re: NET: Registered protocol family 10 on: April 27, 2011, 06:06:16 AM
You did a good job to preserve the system condition this make debug much easier Wink

First you need to clarify your intention, you said you want to "boot from SD", do you mean you want the rootfs load from SD or you want u-boot load kernel from SD? To me "boot from SD" mean make uboot load kernel from SD which is not happening for you base on the info you provided. however you are already load and boot from NAND as is now.

currently your setting use NAND partition 2 for rootfs and the file system is "ubifs" and you were successfully boot up but you may have mis-configured your rootfs where in its /etc/fstab it may be looking stuff from SD, your problem is because the SD is on USB which is slow to come up so it throw off the boot sequence since it can not get all the essential directories need for linux system.

If my analysis is correct then you can try to boot into single user mode by modify your "bootargs_root" append word "single". this should let you boot to shell prompt at which point you can correct your /etc/fstab and start again.

BTW, the "NET: Registered protocol family 10" is refer to IPV6, so it most likely it load the module but missing something in /etc so it stuck in there.

Good luck Smiley
Pages: [1] 2 3 ... 22