• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1] 2 3
Author Topic: SheevaPlug Installer with updated kernel, uboot, distro ?  (Read 13584 times)
mhtsaras
Newbie
*

Karma: 0
Posts: 43


View Profile
« on: January 08, 2010, 08:14:14 AM »

I have my plug for some weeks up and running with the installer 1  provided kernel 2.6.30.2 , ubuntu, and uboot, and I can multiboot from nand, sd card or usb.
Now I want to install debian squeeze, the latest kernel and the latest uboot, and considering that for the installer 1 you need from the readme:
5.  Copy the following to the USB stick root directory:
      a. Root file-system (packed into rootfs.tar.gz)
      b. Kernel (named uImage)
      c. Kernel modules (packed into modules.tar.gz)
      d. Init ramdisk (uImage.initrd)
    If you do not have all, you can download from:
      a. http://plugcomputer.org/index.php/us/resources/downloads (distro, kernel(LSP), uboot)
      b. http://plugcomputer.org/plugwiki/index.php/Main_Page     (distrio,uboot)
      c. http://sheeva.with-linux.com/sheeva                      (mainline kernel+modules)


can i just replace the above files with the updated ones provided by some developers/members of the forum ?
rootfs.tar.gz   from  http://www.mediafire.com/sheeva-with-debian provided by mgillespie this post]http://plugcomputer.org/plugforum/index.php?topic=878.0]this post
kernel  from http://sheeva.with-linux.com/sheeva/  provided by cbxbiker61
and uboot from rooster  http://plugcomputer.org/plugforum/index.php?topic=1134.0 (see attached file uboot.bin )
and then follow the installer's steps to reflash my plug with all the new stuff?
and if that can be done what is the proper way to do this all together and not one by one?
Logged

mgillespie
Full Member
***

Karma: 8
Posts: 239



View Profile
« Reply #1 on: January 08, 2010, 03:11:11 PM »

In theory, you should be able to.   Last time I tried, it failed to boot with a ramdisk size problem, however I believe that has since been fixed
See here:

http://plugcomputer.org/plugforum/index.php?topic=717.msg5416#msg5416

And the possible fix which are in cxbikers newer kernels (untested) here:

http://plugcomputer.org/plugforum/index.php?topic=933.msg6429#msg6429

So yes, I think it should work.   Let us know how you get on!!!

I would use uboot 3.4.27-pingtoo-01, as it fixed a small problem in 3.4.27 that some may come across..

http://plugcomputer.org/plugforum/index.php?topic=1134.msg7028#msg7028

Logged

pingtoo
Sr. Member
****

Karma: 15
Posts: 318


View Profile
« Reply #2 on: January 08, 2010, 03:26:53 PM »

In theory, you should be able to.   Last time I tried, it failed to boot with a ramdisk size problem, however I believe that has since been fixed
See here:

http://plugcomputer.org/plugforum/index.php?topic=717.msg5416#msg5416

And the possible fix which are in cxbikers newer kernels (untested) here:

http://plugcomputer.org/plugforum/index.php?topic=933.msg6429#msg6429

So yes, I think it should work.   Let us know how you get on!!!

I would use uboot 3.4.27-pingtoo-01, as it fixed a small problem in 3.4.27 that some may come across..

http://plugcomputer.org/plugforum/index.php?topic=1134.msg7028#msg7028


Small update, the link above for the u-boot 3.4.27-pingtoo-01 patch is source code, so unless you want to compile your u-boot, I suggest use this one http://plugcomputer.org/plugforum/index.php?topic=1134.msg7016#msg7016
Logged

Good Luck Smiley

mhtsaras
Newbie
*

Karma: 0
Posts: 43


View Profile
« Reply #3 on: January 10, 2010, 04:23:00 AM »

It would be nice if the moderators/administrators of the forum and wiki, take all the above mentioned updated images of kernel, uboot, distribution and update the installer's files and configuration with all the new stuff and after testing it with the help of the members that provided them, post them online
And award the contributors/anonymous members with a generous discount on the next plugcomputer model.
Today I decided to do all the dirty work by my self and debug the all process with the help of the forum members, but after reading this post -->
http://plugcomputer.org/plugforum/index.php?topic=1134.msg7362#msg7362
I changed my mind and decided to wait for a bit, because this year I didn't received any present from santa ... yet!  Roll Eyes
Logged

mgillespie
Full Member
***

Karma: 8
Posts: 239



View Profile
« Reply #4 on: January 10, 2010, 11:37:21 AM »

I have pulled all the relevent stuff together, and built an "unofficial sheeva-with-debian" installer 1.01.

It's based on the Ubuntu Sheevainstaller 1.0 with the following changes:

  • Debian Squeeze (mine)
  • Updated Kernel (cxbiker 2.6.32.3)
  • Updated uboot (3.4.27 - pingtoo patch.01)
  • Statically linked Linux OpenOCD
  • Rootdelay for NAND booting set to 5seconds (to help cure HDD not mounting at boot)
  • Cleaned up some of the the errors and possible confusion in the instructions

The file is available here:
http://www.mediafire.com/?sharekey=04c9dc1dbf3b7c15ab1eab3e9fa335caff81ba820fb48529

It's currently totally untested, as I only have the one plug, and I don't want to upset my perfectly setup system to test it.  Looking for guinea pigs to try it out!!!
« Last Edit: January 10, 2010, 01:08:54 PM by mgillespie » Logged

mgillespie
Full Member
***

Karma: 8
Posts: 239



View Profile
« Reply #5 on: January 11, 2010, 11:23:10 AM »

9 Downloads, anyone tried it out?Huh
Logged

superpat
Full Member
***

Karma: 15
Posts: 141


View Profile
« Reply #6 on: January 12, 2010, 03:47:04 AM »

Hi,

I have downloaded it, but I want to sort out my problem with using a Rfxcom receiver, (see post re only one ttyusb), before I blow my "standard" set-up away

Thank you for your  efforts in creating the new installer.

cheers

Patrick
Logged

superpat
Full Member
***

Karma: 15
Posts: 141


View Profile
« Reply #7 on: January 12, 2010, 04:33:24 AM »

@mgillespie

I thought I should give it a try.


Unfortunately it finishes up with a Bad Magic Number

Here is my Installer x86  m/c output
Quote
debsilch:/home/patrick/sheevaplug-installer-v1.01# php runme.php nand

 ****   exec(modprobe ftdi_sio vendor=0x9e88 product=0x9e8f)
 ****   Preparing environment variables file ...
reading uboot/uboot-env/uboot-dflt.txt
uboot/uboot-env/fw_setenv baudrate 115200
CRC read error on uboot-env.bin: Success
uboot/uboot-env/fw_setenv loads_echo 0
uboot/uboot-env/fw_setenv ipaddr 10.4.50.165
uboot/uboot-env/fw_setenv serverip 10.4.50.5
uboot/uboot-env/fw_setenv rootpath /mnt/ARM_FS/
uboot/uboot-env/fw_setenv netmask 255.255.255.0
uboot/uboot-env/fw_setenv stdin serial
uboot/uboot-env/fw_setenv stdout serial
uboot/uboot-env/fw_setenv stderr serial
uboot/uboot-env/fw_setenv console console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0\(uboot\)ro,0x1ff00000@0x100000\(root\)
uboot/uboot-env/fw_setenv mainlineLinux no
uboot/uboot-env/fw_setenv CASset min
uboot/uboot-env/fw_setenv enaMonExt no
uboot/uboot-env/fw_setenv enaCpuStream no
uboot/uboot-env/fw_setenv enaWrAllo no
uboot/uboot-env/fw_setenv pexMode RC
uboot/uboot-env/fw_setenv disL2Cache no
uboot/uboot-env/fw_setenv setL2CacheWT yes
uboot/uboot-env/fw_setenv disL2Prefetch yes
uboot/uboot-env/fw_setenv enaICPref yes
uboot/uboot-env/fw_setenv enaDCPref yes
uboot/uboot-env/fw_setenv sata_dma_mode yes
uboot/uboot-env/fw_setenv MALLOC_len 1
uboot/uboot-env/fw_setenv ethprime egiga0
uboot/uboot-env/fw_setenv netbsd_en no
uboot/uboot-env/fw_setenv vxworks_en no
uboot/uboot-env/fw_setenv bootargs_root root=/dev/nfs rw
uboot/uboot-env/fw_setenv bootargs_end :::DB88FXX81:eth0:none
uboot/uboot-env/fw_setenv image_name uImage
uboot/uboot-env/fw_setenv bootcmd tftpboot 0x2000000 \$\(image_name\)\;setenv bootargs \$\(console\) \$\(bootargs_root\) nfsroot=\$\(serverip\):\$\(rootpath\) ip=\$\(ipaddr\):\$\(serverip\)\$\(bootargs_end\) \$\(mvNetConfig\) \$\(mvPhoneConfig\)\;  bootm 0x2000000\;
uboot/uboot-env/fw_setenv standalone fsload 0x2000000 \$\(image_name\)\;setenv bootargs \$\(console\) root=/dev/mtdblock0 rw ip=\$\(ipaddr\):\$\(serverip\)\$\(bootargs_end\) \$\(mvPhoneConfig\)\; bootm 0x2000000\;
uboot/uboot-env/fw_setenv bootdelay 3
uboot/uboot-env/fw_setenv disaMvPnp no
uboot/uboot-env/fw_setenv ethaddr 00:50:43:4e:2a:14
uboot/uboot-env/fw_setenv ethmtu 1500
uboot/uboot-env/fw_setenv mvPhoneConfig mv_phone_config=dev0:fxs,dev1:fxs
uboot/uboot-env/fw_setenv mvNetConfig mv_net_config=\(00:11:88:0f:62:81,0:1:2:3\),mtu=1500
uboot/uboot-env/fw_setenv usb0Mode host
uboot/uboot-env/fw_setenv yuk_ethaddr 00:00:00:EE:51:81
uboot/uboot-env/fw_setenv nandEcc 1bit
uboot/uboot-env/fw_setenv netretry no
uboot/uboot-env/fw_setenv rcvrip 169.254.100.100
uboot/uboot-env/fw_setenv loadaddr 0x02000000
uboot/uboot-env/fw_setenv autoload no
uboot/uboot-env/fw_setenv enaAutoRecovery yes
uboot/uboot-env/fw_setenv ethact egiga0
reading uboot/uboot-env/uboot-nand-custom.txt
uboot/uboot-env/fw_setenv bootargs_root ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs rootdelay=5
uboot/uboot-env/fw_setenv mtdpartitions mtdparts=orion_mtd:0x400000@0x100000\(uImage\),0x1fb00000@0x500000\(rootfs\)
uboot/uboot-env/fw_setenv ethaddr 00:50:43:01:c1:e6
uboot/uboot-env/fw_setenv real_bootcmd setenv bootargs \$\(bootargs_console\) \$\(mtdpartitions\) \$\(bootargs_root\)\; nand read.e 0x00800000 0x00100000 0x00400000\; bootm 0x00800000
uboot/uboot-env/fw_setenv bootargs_console console=ttyS0,115200
uboot/uboot-env/fw_setenv bootcmd run recover1
uboot/uboot-env/fw_setenv recover1 setenv mainlineLinux yes\; setenv arcNumber 2097\; setenv bootcmd run recover2\; saveenv\; reset
uboot/uboot-env/fw_setenv recover2 run recover3\; setenv bootcmd \$\(real_bootcmd\)\; saveenv\; setenv bootargs \$\(bootargs_console\) \$\(mtdpartitions\) root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand\; bootm 0x00800000 0x01100000
uboot/uboot-env/fw_setenv recover3 run recover4\; nand erase clean 0x00100000 0x00400000\; nand write.e 0x00800000 0x00100000 0x00400000
uboot/uboot-env/fw_setenv recover4 usb start\; fatload usb 0 0x00800000 uImage\; fatload usb 0 0x01100000 initrd

 ****   Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0 (2009-09-16-09:13) Release
$URL: http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openocd.c $
For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
2000 kHz
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
Info : JTAG Tap/device matched
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078
NAND flash device 'NAND 512MiB 3,3V 8-bit' found
successfully erased blocks 5 to 6 on NAND flash device 'NAND 512MiB 3,3V 8-bit'
wrote file uboot-env.bin to NAND flash 0 up to offset 0x000c0000 in 18.110443s
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078
NAND flash device 'NAND 512MiB 3,3V 8-bit' found
successfully erased blocks 0 to 4 on NAND flash device 'NAND 512MiB 3,3V 8-bit'
wrote file uboot.bin to NAND flash 0 up to offset 0x00074000 in 66.042610s

 ****   U-boot should be up and running now. Open your console ...

I have attached the putty.log as a file (its a bit long to insert in line!)

A small quibble,  I seem to have a hybrid Sheevaplug.  It is a V1.3, but it still has the V1.0 ftdi addresses, so I did not have to edit the config as in the readme.

I tried it 3 times and got the same result each time.

cheers

Patrick

* putty.log (40.16 KB - downloaded 233 times.)
Logged

mgillespie
Full Member
***

Karma: 8
Posts: 239



View Profile
« Reply #8 on: January 12, 2010, 04:38:03 AM »

Can you change the line back in uboot-nand-custom.txt to orion_nand?

I changed it because the notes said:

# NAND flash partitions. If using kernel >= 2.6.30 then replace orion_nand with orion_mtd
Logged

superpat
Full Member
***

Karma: 15
Posts: 141


View Profile
« Reply #9 on: January 12, 2010, 05:32:36 AM »

@mgillespie

Hi,

I changed the line back in uboot-nand-custom.txt to orion_nand

Then I ran the runme again,  The plug new kernel took an exception. I tried the complete install twice.

Again I have attached the putty.log as a file as it is long!

* putty.log (459.83 KB - downloaded 203 times.)
« Last Edit: January 12, 2010, 05:42:18 AM by superpat » Logged

mgillespie
Full Member
***

Karma: 8
Posts: 239



View Profile
« Reply #10 on: January 12, 2010, 06:31:47 AM »

Looks like we have found the same problem as being discussed here:

http://plugcomputer.org/plugforum/index.php?topic=717.msg7359#msg7359

Can you try it out with an older uboot to try and eliminate what is going on? (try it with both orion_nand and orion_mtd)
Logged

pingtoo
Sr. Member
****

Karma: 15
Posts: 318


View Profile
« Reply #11 on: January 12, 2010, 07:27:13 AM »

@superpat,

Thanks for the putty output, I been try to figure this one for sometime.

This is not a u-boot issue, this is linux kernel issue.

It looks like you will need to use orion_nand in order for the MTD(NAND) being recognize by kernel, this is evidently in you second putty.log output. I have never really pay attention to which word to use and how it affect the kernel. I will take a look at the code to see if I can find something.

In the mean time. please try older kernel, before .32 will be a good start.
Logged

Good Luck Smiley

Kamikaze321
Newbie
*

Karma: 0
Posts: 19


View Profile
« Reply #12 on: January 12, 2010, 01:18:07 PM »

Holly sh..  Grin Grin Grin Grin Grin Grin Grin Grin Grin

orion_nand instead of orion_mtd solved all problems, I got my Debian now, thank you guys, especially pingtoo for spending so much time solving this problem.
Logged

pingtoo
Sr. Member
****

Karma: 15
Posts: 318


View Profile
« Reply #13 on: January 12, 2010, 01:39:38 PM »

Holly sh..  Grin Grin Grin Grin Grin Grin Grin Grin Grin

orion_nand instead of orion_mtd solved all problems, I got my Debian now, thank you guys, especially pingtoo for spending so much time solving this problem.
You are welcome, I was plan to go home check you log files I downloaded to verify before I let you know. Now you got it figure out  Wink
Logged

Good Luck Smiley

mgillespie
Full Member
***

Karma: 8
Posts: 239



View Profile
« Reply #14 on: January 12, 2010, 02:41:01 PM »

Hmm, so regardless of what kernel is used, it's orion_nand.   The note the txt file is wrong.

Does this explain why superpat could not get this to work?  Any ideas how to progress this is a fully working, updated debian installer pack?  I'm lost....
Logged

Pages: [1] 2 3
Print
Jump to: