• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  Hardware and U-Boot firmware / Hardware / Re: Fried SheevaPlug !!! on: May 25, 2010, 07:20:58 AM
Hi doublecheese ,
I had the same problem with my meteohub system running on the sheeva.
I solved it within 20 minutes by replacing the defect power supply  with a 5V 3A wall wart  power plug.
Everything was running well again.

All is described as already mentioned in http://plugcomputer.org/plugforum/index.php?topic=1318.0.
Cheers and have fun with your Meteohub.
2  Linux Stuff / Linux distributions / Re: USB port turns off when starting kernel on: November 20, 2009, 10:17:18 AM
I had a similar problem, I solved it by sending my plug back to NewIT.
I didn't get any useful messages with dmesg and lsusb.
I got a new one within 4 days. Very good support from NewIT

With the new one no more any problem with the usb port. Smiley
3  Linux Stuff / General Linux questions / Re: SD card problems on cold boot on: November 01, 2009, 03:24:05 AM
I think this is the known problem on a power-on boot up!

So far the only thing that has worked is to have two mmcinit; commands.

See  MMC/SD support in u-boot

Posts: 23

Re: MMC/SD support in u-boot
« Reply #50 on: September 20, 2009, 10:24:44 AM »
   Reply with quoteQuote
Quote from: CqCn 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.
CqCn -

I'm not sure I found your solution.  I tried adding rootdelay=10 to my bootargs_root.  It didn't make a difference.  So far the only thing that has worked is to have two mmcinit; commands.  On a power-on boot up, the first one fails, and the second one works.  On a reboot they both work.
4  Linux Stuff / Linux distributions / Re: Debian installer for SheevaPlug available now on: October 30, 2009, 08:14:53 AM
Today I got a replaced new Plug from NewIT.
And again the same issue, uncorrect date and time!
Thats why I installed firstly Ubuntu to my 4GB SD-Card with sheevaplug-installer-v1.0 and setup Date with ntpdate pool.ntp.org and hwclock --systohc.
Afterwards I started the Debian queeze installation with the debian installer according
http://www.cyrius.com/debian/kirkwood/sheevaplug/install.html

And as expected, the installer was running perfectly   ! Smiley

There was only the known problem that sheeva was not booting from power on.
I solved this by inserting a second mmcinit in -->
setenv bootcmd_mmc 'mmcinit; mmcinit; ext2load mmc 0 0x0800000 /uInitrd; ext2load mmc 0 0x400000 /uImage'

Thanks all for your help and good ideas!
5  Linux Stuff / Linux distributions / Re: Debian installer for SheevaPlug available now on: October 28, 2009, 06:13:02 AM
Hi jimjack,
have a lock to post 7, the installer also dies on installing busybox and there was also an
uncorrect date.
This was also my second Plug ant it was from NewIt too.
At least I sended it back due to the brocken USB.
Could it be that there is something wrong with those NewIt Plugs?

I'll get a new one in the next days and will test it then.
6  Linux Stuff / Linux distributions / Re: Debian installer for SheevaPlug available now on: October 26, 2009, 08:28:25 AM
Hi TBM just a feedback regarding my Sheevaplug not working with Debian installer.
This sheevaplug has got a defect and I reshipped it to NewIt.

Thus I cannot investigate my problem with debian installer at the moment.
Hopefully the new one will run without any problems.

Thanks for yor help.
7  Linux Stuff / Linux distributions / Re: Debian installer for SheevaPlug available now on: October 25, 2009, 02:16:47 AM
TBM after tail -n 100 /var/log/syslog  | more

I got this.
Code:
~ # tail -n 100 /var/log/syslog  | more
Sep 10 16:01:51 in-target: Reading package lists...
Sep 10 16:01:51 in-target:
Sep 10 16:01:51 in-target: Building dependency tree...
Sep 10 16:01:52 in-target:
Sep 10 16:01:53 in-target: The following NEW packages will be installed:
Sep 10 16:01:53 in-target:   locales
Sep 10 16:01:53 in-target: 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Sep 10 16:01:53 in-target: Need to get 4664kB of archives.
Sep 10 16:01:53 in-target: After this operation, 12.6MB of additional disk space will be used.
Sep 10 16:01:53 in-target: WARNING: The following packages cannot be authenticated!
Sep 10 16:01:53 in-target:   locales
Sep 10 16:01:53 in-target: E:
Sep 10 16:01:53 in-target: There are problems and -y was used without --force-yes
Sep 10 16:01:53 in-target:
Sep 10 16:01:53 localechooser: error: the command 'validlocale' is not available
Sep 10 16:01:55 in-target: locale:
Sep 10 16:01:55 in-target: Cannot set LC_CTYPE to default locale
Sep 10 16:01:55 in-target: : No such file or directory
Sep 10 16:01:55 in-target:
Sep 10 16:01:55 in-target: locale:
Sep 10 16:01:55 in-target: Cannot set LC_MESSAGES to default locale
Sep 10 16:01:55 in-target: : No such file or directory
Sep 10 16:01:55 in-target:
Sep 10 16:01:55 in-target: locale:
Sep 10 16:01:55 in-target: Cannot set LC_ALL to default locale
Sep 10 16:01:55 in-target: : No such file or directory
Sep 10 16:01:55 in-target:
Sep 10 16:01:56 in-target: Reading package lists...
Sep 10 16:01:56 in-target:
Sep 10 16:01:56 in-target: Building dependency tree...
Sep 10 16:01:57 in-target:
Sep 10 16:01:58 in-target: Recommended packages:
Sep 10 16:01:58 in-target:   reportbug pciutils
Sep 10 16:01:58 in-target: The following NEW packages will be installed:
Sep 10 16:01:58 in-target:   installation-report
Sep 10 16:01:58 in-target: 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Sep 10 16:01:58 in-target: Need to get 17.0kB of archives.
Sep 10 16:01:58 in-target: After this operation, 111kB of additional disk space will be used.
Sep 10 16:01:58 in-target: WARNING: The following packages cannot be authenticated!
Sep 10 16:01:58 in-target:   installation-report
Sep 10 16:01:58 in-target: E:
Sep 10 16:01:58 in-target: There are problems and -y was used without --force-yes
Sep 10 16:01:58 in-target:
Sep 10 16:02:00 base-installer: info: kernel linux-image-versatile not usable on kirkwood
Sep 10 16:02:00 base-installer: info: kernel linux-image-orion5x not usable on kirkwood
Sep 10 16:02:00 base-installer: info: kernel linux-image-kirkwood usable on kirkwood
Sep 10 16:02:00 base-installer: info: kernel linux-image-ixp4xx not usable on kirkwood
Sep 10 16:02:00 base-installer: info: kernel linux-image-iop32x not usable on kirkwood
Sep 10 16:02:00 base-installer: info: kernel linux-image-2.6.30-2-versatile not usable on kirkwood
Sep 10 16:02:00 base-installer: info: kernel linux-image-2.6.30-2-orion5x not usable on kirkwood
Sep 10 16:02:00 base-installer: info: kernel linux-image-2.6.30-2-kirkwood usable on kirkwood
Sep 10 16:02:00 base-installer: info: kernel linux-image-2.6.30-2-ixp4xx not usable on kirkwood
Sep 10 16:02:00 base-installer: info: kernel linux-image-2.6.30-2-iop32x not usable on kirkwood
Sep 10 16:02:00 base-installer: info: kernel linux-image-2.6-versatile not usable on kirkwood
Sep 10 16:02:00 base-installer: info: kernel linux-image-2.6-orion5x not usable on kirkwood
Sep 10 16:02:00 base-installer: info: kernel linux-image-2.6-kirkwood usable on kirkwood
Sep 10 16:02:00 base-installer: info: kernel linux-image-2.6-ixp4xx not usable on kirkwood
Sep 10 16:02:00 base-installer: info: kernel linux-image-2.6-iop32x not usable on kirkwood
Sep 10 16:02:00 base-installer: info: Found kernels 'linux-image-2.6-kirkwood,linux-image-2.6.30-2-kirkwood,linux-image-kirkwood'
Sep 10 16:02:00 base-installer: info: arch_kernel candidates: linux-image-2.6-kirkwood
Sep 10 16:02:00 base-installer: info: arch_kernel: linux-image-2.6-kirkwood (present)
Sep 10 16:02:00 base-installer: info: Using kernel 'linux-image-2.6-kirkwood'
Sep 10 16:02:00 base-installer: info: Setting do_initrd='yes'.
Sep 10 16:02:01 base-installer: info: Setting link_in_boot='yes'.
Sep 10 16:02:01 base-installer: info: Available initramfs generator(s): 'initramfs-tools'
Sep 10 16:02:01 in-target: locale:
Sep 10 16:02:01 in-target: Cannot set LC_CTYPE to default locale
Sep 10 16:02:01 in-target: : No such file or directory
Sep 10 16:02:01 in-target:
Sep 10 16:02:01 in-target: locale:
Sep 10 16:02:01 in-target: Cannot set LC_MESSAGES to default locale
Sep 10 16:02:01 in-target: : No such file or directory
Sep 10 16:02:01 in-target:
Sep 10 16:02:01 in-target: locale:
Sep 10 16:02:01 in-target: Cannot set LC_ALL to default locale
Sep 10 16:02:01 in-target: : No such file or directory
Sep 10 16:02:01 in-target:
Sep 10 16:02:03 in-target: Reading package lists...
Sep 10 16:02:03 in-target:
Sep 10 16:02:03 in-target: Building dependency tree...
Sep 10 16:02:04 in-target:
Sep 10 16:02:04 in-target: The following NEW packages will be installed:
Sep 10 16:02:04 in-target:   busybox
Sep 10 16:02:04 in-target: 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Sep 10 16:02:04 in-target: Need to get 346kB of archives.
Sep 10 16:02:04 in-target: After this operation, 606kB of additional disk space will be used.
Sep 10 16:02:04 in-target: WARNING: The following packages cannot be authenticated!
Sep 10 16:02:04 in-target:   busybox
Sep 10 16:02:04 in-target: E:
Sep 10 16:02:04 in-target: There are problems and -y was used without --force-yes
Sep 10 16:02:04 in-target:
Sep 10 16:02:04 base-installer: error: exiting on error base-installer/kernel/failed-package-install
Sep 10 16:04:33 main-menu[458]: WARNING **: Configuring 'bootstrap-base' failed with error code 30
Sep 10 16:04:33 main-menu[458]: WARNING **: Menu item 'bootstrap-base' failed.
Sep 10 16:04:45 main-menu[458]: INFO: Modifying debconf priority limit from 'high' to 'medium'
Sep 10 16:04:45 debconf: Setting debconf/priority to medium
Sep 10 16:04:46 main-menu[458]: DEBUG: resolver (libgcc1): package doesn't exist (ignored)
Sep 10 16:04:56 main-menu[458]: INFO: Falling back to the package description for auto-install
Sep 10 16:04:56 main-menu[458]: INFO: Falling back to the package description for ai-choosers
Sep 10 16:04:56 main-menu[458]: INFO: Menu item 'di-utils-shell' selected


How to copy the file?
How to come back to the installer?

Thanks Billy
8  Linux Stuff / Linux distributions / Re: Debian installer for SheevaPlug available now on: October 24, 2009, 02:08:21 PM
TBM thanks

after
setenv mainlineLinux yes
setenv arcNumber 2097
saveenv
reset

the installer is running

but I get this message now


     +------------------¦ [!!] Install the base system +------------------+
     ¦                     Unable to install busybox                                         ¦
     ¦ An error was returned while trying to install the busybox package ¦
     ¦ onto the target system.                                                              ¦
     ¦                                                                                                   ¦
     ¦ Check /var/log/syslog or see virtual console 4 for the details.       ¦
     ¦                                                                                                   ¦
     ¦     <Go Back>                                       <Continue>                    ¦
     ¦                                                                                                  ¦
     +--------------------------------------------------------------------+

What to do?
9  Linux Stuff / Linux distributions / Re: Debian installer for SheevaPlug available now on: October 24, 2009, 12:00:59 AM
Debian installer not working!

As I got now my second sheeva I'd like to install debian on it.

I tried to install according Michaels how to. http://www.cyrius.com/debian/kirkwood/sheevaplug/install.html
First step Upgrading U-Boot via tftp was no problem.
Second step --> Starting the Installer doesnt work completely.

TFTP: if you want to load the installer via the network from a TFTP server, use this:

setenv serverip 192.168.1.2
setenv ipaddr 192.168.1.147
tftpboot 0x0800000 uInitrd
tftpboot 0x400000 uImage

this works fine

but after starting the installer with:

setenv bootargs console=ttyS0,115200n8 base-installer/initramfs-tools/driver-policy=most
bootm 0x400000 0x0800000

I got this and nothing more

Marvell>> bootm 0x400000 0x0800000
## Booting image at 00400000 ...
   Image Name:   Debian kernel
   Created:      2009-10-22  22:23:04 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1811896 Bytes =  1.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 00800000 ...
   Image Name:   debian-installer ramdisk
   Created:      2009-10-22  22:23:05 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    2695527 Bytes =  2.6 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

What to do? Thanks for your help
10  General Category / General Discussion / Re: Sheevaplug installer - version 1.0 on: September 28, 2009, 11:52:40 PM
Quote from: klauterbach on September 27, 2009, 06:48:01 PM
Note: Currently my plug doesn't boot properly on initial power up. However if I press the reset switch after powering up the device boots correctly. Has anyone else experienced this problem?

I solved this problem by inserting a secound mmcinit in --> uboot-mmc-custom.txt

# Bootcmd to be used after all installation is done
real_bootcmd setenv bootargs $(bootargs_console) $(bootargs_root);  mmcinit; mmcinit; ext2load mmc 0:1 0x800000 /uImage; bootm 0x00800000
11  General Category / General Discussion / Re: Sheevaplug installer - alpha-6 release - Testers needed on: August 21, 2009, 01:54:04 PM
My problem is solved. The point was "grep: installer/uboot-custom.txt: No such file or directory" .
(Due to the help of  user fragfutter I was able to find out, that this file was missing in my installer directory)
I don't know why.
After downloading and installing with a new sheevaplug-installer-alpha-6.tar.gz th plug is running now.
12  General Category / General Discussion / Re: Sheevaplug installer - alpha-6 release - Testers needed on: August 20, 2009, 12:24:55 AM
Sorry, I'm an absolute newbie. I got my Plug 2 weeks ago. Now I wanted to update it by alpha-6 installer.
When I used alpha-6 Installer  according the Install WIKI, I got the following message on my Linux system:
Code:
root@Lt-Ubuntu:~/Desktop/Sheeva# ./runme.sh
 **** Preparing environment variables file ...
grep: installer/uboot-custom.txt: No such file or directory
 **** Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
2000 kHz
dcc downloads are enabled
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (Manufacturer: 0x1e9, Part: 0x0a02, Version: 0x2)
Info : JTAG Tap/device matched
Error: unknown EmbeddedICE version (comms ctrl: 0x00000018)
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
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 20.600372s
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 0x00073000 in 73.503960s
 **** U-boot should be up and running now. Open your console ...
root@Lt-Ubuntu:~/Desktop/Sheeva#



It tells me that the install should be ok.
After connecting to the Plug I get the following message.
Code:
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (May 13 2009 - 13:10:52) Marvell version: 3.4.16
          <INTERRUPT>
Marvell>> e: 00600000 -> 0067FFF0  BSS: -> 006CF100

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
egiga0 no link
mvEgigaInit: egiga1 mvEthPortEnable failed (error)
mvEgigaInit: egiga1 failed
Using egiga0 device
TFTP from server 10.4.50.5; our IP address is 10.4.50.165
Filename 'uImage'.
Load address: 0x2000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
## Booting image at 02000000 ...
Bad Magic Number
Marvell>>



I assume, uboot is not running correctly.
What is gooing wrong? I tried it with 4 different USB sticks.
How can I test whether the stick is recognized by the Plug?
Thanks for your help.
 


Pages: [1]