• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1] 2 3
1  Hardware and U-Boot firmware / Hardware / Re: New Sheevaplug image available on: March 25, 2015, 08:07:24 AM
Thanks for the info.

Browing http://globalscaletechnologies.com/download/ shows that Sheeva-Debian7-SW.rar is 360.838.856 bytes while sheevaplug_env.tar.rar is 226.624.239 bytes: Will both fit into the Sheevaplug's 512MB NAND, or should some of it be moved to an SD card?
2  Linux Stuff / General Linux questions / Re: Replaced PSU: Debian no longer boots on: November 18, 2013, 03:45:19 PM
In case someone else has the same problem, reinstalling Debian on an SD card solved the issue:
3  Linux Stuff / General Linux questions / Replaced PSU: Debian no longer boots on: November 07, 2013, 08:26:17 AM

After replacing the blown PSU with a new one from NewIT, the Debian6 that I use to upgrade from the original Ubuntu 9.04 no longer boots.

I'm no Linux expert, and have no idea what to try.

Thanks for any help.

Here's the output from the micro-USB port as seen by Putty in Windows:
Marvell>> reset
resetting ...

U-Boot 2011.12 (Mar 11 2012 - 18:59:46)
Marvell-Sheevaplug - eSATA - SD/MMC

SoC:   Kirkwood 88F6281_A0
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  512 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0
Marvell>> boot
Creating 1 MTD partitions on "nand0":
0x000000500000-0x000020000000 : "mtd=2"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=2"
UBI: MTD device size:            507 MiB
UBI: number of good PEBs:        4056
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 4056
UBI: number of PEBs reserved for bad PEB handling: 40
UBI: max/mean erase counter: 23/4
UBIFS: recovery needed
UBIFS error (pid 0): ubifs_recover_leb: LEB 24 scanning failed
Error reading superblock on volume 'ubi:rootfs'!
UBIFS not mounted, use ubifs mount to mount volume first!
UBIFS not mounted, use ubifs mount to mount volume first!
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Marvell>> print
bootargs=console=ttyS0,115200 ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
bootargs_ubi=console=ttyS0,115200 ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
bootcmd=setenv bootargs $(bootargs_ubi); run bootcmd_ubi; bootm 0x00800000 0x01100000
bootcmd_ubi=ubi part nand0,2; ubifsmount rootfs; ubifsload 0x1100000 /boot/uInitrd; ubifsload 0x800000 /boot/uImage
x_bootargs=console=ttyS0,115200 mtdparts=orion_nand:512k(uboot),4m@1m(kernel),507m@5m(rootfs) rw
x_bootargs_root=ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
x_bootcmd_kernel=nand read 0x6400000 0x100000 0x400000
x_bootcmd_sata=ide reset;
x_bootcmd_usb=usb start;

Environment size: 944/131068 bytes
4  Hardware and U-Boot firmware / Hardware / Re: Is my sheevaplug dead ??? on: October 26, 2013, 10:16:38 AM
I went through the threads on the subject, and since it requires some knowledge of electronics, which I don't have, I just ordered a new PSU from NewIt, although 10 + 10 is a bit high if it just means replacing one or two caps :-/
5  Hardware and U-Boot firmware / Hardware / Re: Is my sheevaplug dead ??? on: October 26, 2013, 03:57:22 AM
Thanks for the infos. I attached a picture of my dead SP.

Is there a precise, newbie-accessible HOWTO on what component to order and how to perform the operation, including how to use a multimeter?
6  Hardware and U-Boot firmware / Hardware / Re: Is my sheevaplug dead ??? on: September 05, 2013, 04:47:37 PM

I bought a Sheevaplug a couple of years ago, but have only been using it the past few months. I don't know when it stopped working, but it's no longer reachable through SSH/serial, and the blue LED is no longer lit while the green LED lights up every second or so, along with the the green and yellow LEDs next to the Ethernet plug.

Knowing nothing about electronics, I simply opened the outer case but didn't dare opening the aluminum case because of those warnings from Superpat and SunnyJim about capacitors.

Since the warranty is long gone, NewIT, which sells the SheevaPlug in Europe, simply expects users to buy a new unit.
Before I shell out the $120 or so for a new unit + shipping, I was wondering if I could safely open the aluminum case to take a picture to check with you guys, and bring it to an electronics store to check what components I need to change to possibly get it up and running again.

Or is it just too dangerous and I should just get a new one?

Thank you.

PS: I saw J-Tag mentioned a few times. Where is that connector located? Is it the one next to the connector that says "UART" on the PCB?
7  Linux Stuff / General Linux questions / Re: Cross-compiling applications for the SheevaPlug? on: April 11, 2013, 05:01:24 AM
For the benefit of other newbies struggling to cross-compile applications on a Linux PC for the SheevaPlug, I made two mistakes in the post above:

1. The Plug_Host_SWsupportPackageLinuxHost.zip contains two compiled file: gcc.tar.bz2 is indeed a Bz2 file, but "Linux Host Filesystem - rootfs.tar.bz2" is actually a gzip file. I ran this:
mv "Linux Host Filesystem - rootfs.tar.bz2" rootfs.tar.gz ; tar xzvf rootfs.tar.gz

2. To compile a basic app like "Hello, world", cd to LinuxHost/gcc/bin, and run "arm-none-linux-gnueabi-gcc -o hello hello.c", which will create a binary that uses shared libraries.

At this point, I'm surprised it works although I didn't specify neither the path to the C library nor its name. Maybe Marvell's toolchain is hard-linked to figure this out by itself by reading files from LinuxHost/rootfsv1.0.
8  Linux Stuff / General Linux questions / Re: Cross-compiling applications for the SheevaPlug? on: April 08, 2013, 06:41:39 AM
Also, I notice a discrepancy between the Linux version (3.5.0-17, 2.6.14, 2.6.32-5-kirkwood): Does it mean that the Marvell toolchain was compiled with Linux 2.6.14?

ubuntu.host# uname -a
Linux Aspire-3810T 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:32:08 UTC 2012 i686 i686 i686 GNU/Linux

sheeva# file hello
hello: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.14, not stripped

sheeva# uname -a
Linux debian 2.6.32-5-kirkwood #1 Mon Feb 25 13:55:40 UTC 2013 armv5tel GNU/Linux
9  Linux Stuff / General Linux questions / Re: Cross-compiling applications for the SheevaPlug? on: April 08, 2013, 06:38:09 AM
I successfully compiled and ran "Hello, world!" thusly:

1. Unzip Marvell's Plug_Host_SWsupportPackageLinuxHost.zip
2. cd LinuxHost/gcc/bin
3. Create "Hello, World!" file, and save as hello.c
4. gcc -o hello hello.c
5. Copy binary to embedded host
6. chmod +x hello
7. Run hello

But to compile real applications, I assume I must configure the host so it knows where to find the include files and the libraries, provided the application doesn't need some files not provided by the Marvell file.
10  Linux Stuff / General Linux questions / Re: Cross-compiling applications for the SheevaPlug? on: April 08, 2013, 05:27:38 AM
I downloaded and unzipped the "Host SW Support Package For Linux" file from the Downloads section, but don't know what to do next:

drwxr-xr-x 11 fred fred     4096 Feb 26  2008 gcc/
drwxr-xr-x 10 root root     4096 Feb 25  2009 rootfsv1.0/

The gcc/ directory contains no information on how to set things up to cross-compile applications.
11  General Category / General Discussion / Re: Which ARM toolchain ? on: April 08, 2013, 04:19:17 AM

The cross-compiler for the SheevaPlus seems available here:

"Host SW Support Package For Linux"

I have a couple of questions:
1. Will this cross-compiler run on any Linux host, or is it restricted to a specific distro?
2. How to set it up? After unzipping the file, there are two directories: gcc/ and rootfsv1.0/. How do we go from this to a running binary of "Hello,world!"?

Thank you.
12  General Category / General Discussion / Re: Cross compiling FFMPEG on: April 07, 2013, 03:19:42 PM

What toolchain did you use to cross-compile ffmpeg for the SheevaPlug?

Thank you.
13  Linux Stuff / General Linux questions / Cross-compiling applications for the SheevaPlug? on: April 05, 2013, 07:00:52 AM

I checked the Documentation section on the Plug Computer site, but didn't find how to set up a cross-compiler on a PC running Linux, and compile an application for the SheevaPlug (armv5tel processor: Feroceon 88FR131 rev 1 (v5l)).

After upgrading the SheevaPlug from its stock Ubuntu 9.04 to Debian 6, I noticed that the latest release of Nginx is 0.7.67, while support for the uwsgi protocol requires release 0.8.40 or newer.

Is there a good tutorial on how to cross-compile on Linux for the SheevaPlug?

Thank you.
14  Hardware and U-Boot firmware / U-Boot stuff / Re: Latest Uboot? on: March 22, 2013, 04:11:02 PM
Thank you. I'll stick to something that is known to work flawlessly :-)
15  Linux Stuff / General Linux questions / [Debian 6.0] Which services can I safely remove? on: March 22, 2013, 04:03:22 PM

I'm no expert, so would rather check with you before possibly breaking things.

Apparently, Debian relies on symlinks in /etc/rc3.d/ to load services, and it says this:
lrwxrwxrwx  1 root root   18 Mar 22  2013 S01bootlogs -> ../init.d/bootlogs*
lrwxrwxrwx  1 root root   17 Mar 22  2013 S13portmap -> ../init.d/portmap*
lrwxrwxrwx  1 root root   20 Mar 22  2013 S14nfs-common -> ../init.d/nfs-common*
lrwxrwxrwx  1 root root   17 Mar 22  2013 S16rsyslog -> ../init.d/rsyslog*
lrwxrwxrwx  1 root root   13 Mar 22  2013 S17atd -> ../init.d/atd*
lrwxrwxrwx  1 root root   14 Mar 22  2013 S17cron -> ../init.d/cron*
lrwxrwxrwx  1 root root   15 Mar 22  2013 S17exim4 -> ../init.d/exim4*
lrwxrwxrwx  1 root root   18 Mar 22  2013 S18rc.local -> ../init.d/rc.local*
lrwxrwxrwx  1 root root   19 Mar 22  2013 S18rmnologin -> ../init.d/rmnologin*
lrwxrwxrwx  1 root root   23 Mar 22  2013 S18stop-bootlogd -> ../init.d/stop-bootlogd*

I have no need for NFS, so I guess I can remove portmap and nfs-common. Like, I don't need an SMTP server, so I could remove exim. What about the rest?

Thank you.
Pages: [1] 2 3