• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  General Category / General Discussion / Re: Replacement power supplies from Globalscale? In stock or not? on: October 27, 2010, 09:57:24 PM
Yes, my original SheevaPlug order from April 2009 *also* shows "not yet shipped" even though I got it a few months after that. 

I got an email from Globalscale this afternoon (in response to my customer service request through their web site) saying that my PSUs should ship by Friday, and "thank you for [my] patience."  I'll believe it when I see the tracking number.

But my SparkFun DC-DC converter order did arrive this afternoon, and I now have a SheevaPlug that runs off of 12VDC instead of AC mains.  http://www.sparkfun.com/commerce/product_info.php?products_id=9948.  So far, it's running well, and is running quite cool.  Since I'm using my SheevaPlug primarily with my ham radio stuff, 12VDC is all over my bench, so this really made a lot of sense for me anyway.

I'm going to keep the replacement AC supplies (when they finally get here) just in case something goes wrong with the DC-DC solution.
2  General Category / General Discussion / Replacement power supplies from Globalscale? In stock or not? on: October 25, 2010, 05:03:39 PM
Globalscale lists a $10 replacement power supply for the Sheevaplug, and the web site has no caveat about limited supply and long waits as it does for the various plugs themselves.

When my Sheevaplug PSU fried (bad caps) 10 days ago, I went ahead and ordered 2 replacement PSUs immediately.

Naturally, I assumed they'd ship in something approximating finite time.  Naturally, Globalscale's not done that.  They charged my card within a few hours, and now the order is just sitting there unfilled.  I've gotta wonder if it's just bad service, or if those, too, are in shorter supply than demand.

I managed to order a 5V, 3A DC-DC converter from SparkFun  on Friday, and I intend to use instead, since my Sheevaplug is in fact sitting in a spot with lots of 12V DC power anyway, and I bet the 12V-5V switching supply will run a lot cooler, too.  SparkFun filled the order in less than 2 business days, so I should have my DC-DC solution in hand before Globalscale even gets around to shipping the other two.

Still, it would be nice to know if anyone has had a positive experience ordering a replacement PSU from globalscale, since dead power supplies seem to be epidemic.
3  General Category / Success stories / SheevaPlug as a Ham Radio/Packet Radio server on: June 22, 2009, 02:15:20 PM
My primary interest in the SheevaPlug was to use it as a server for the Amateur Packet Reporting System (APRS).  Last week I got it all working.

The first step was getting kernel AX.25 networking built into my kernel.  I started from a kernel.org 2.6.30 tarball, applied the patches that cbxbiker61 posted at http://sheeva.with-linux.com/sheeva/, and built it with  this config file copied to ".config" in the kernel source directory.  I built directly on the plug, not cross-compiled, since I'm running on a 40GB USB disk drive rather than NAND Flash, and it was easy to do.  I followed the instructions on pushbx's web site, http://www.computingplugs.com/index.php/Main_Page, for building my kernel.

Once I had the kernel with AX.25 networking enabled, it was just a matter of following the set-up instructions at http://www.xastir.org/wiki/index.php/HowTo:AX.25 to connect the ax.25 network interface to a serial KISS TNC through a USB<->Serial adapter.  Sharing the TNC across the network was a little harder to figure out, but in the end I managed it using the latest version of SOCAT and some trickery with "kissnetd" and pseudo-ttys.  (Socat needs to be built from source, not installed via the Ubuntu repositories, because the repository version is too old and doesn't support the ability to tie raw network interfaces together.)

In addition to just having the TNC shared across the LAN, I also have javAPRSSrvr running on the SheevaPlug.  This required only a little more than installing the default java jre --- the ax25 component of javAPRSSrvr also requires a platform-specific shared library to be built, so I also had to install default-jdk to get that job done, since the shared library is currently only available for x86 in binary form.

Details of my set-up are described on my blog (also running on the SheevaPlug), http://www.bogodyn.org/blog/, where I also walk through the configuration and build instructions a little bit.

With this set-up, I can run multiple APRS programs on different machines on my LAN, using only one TNC connected to the SheevaPlug, and also run the plug as an APRS<->Internet gateway.  There's one more piece of software I can't yet run on the SheevaPlug because its author hasn't yet released source, but when he does it should simplify the sharing considerably.

As a lark, I also installed X11, VNC, and a few other libraries and development headers, and was even able  to build Xastir for the SheevaPlug, and connect it up to the ax.25 interface.  But that still requires that I display the vncviewer on my desktop, where I already have Xastir running --- so this was mostly just a proof-of-principle that the SheevaPlug would support that sort of operation.
4  Hardware and U-Boot firmware / Hardware / Re: Alternative power supplies on: June 17, 2009, 09:26:48 AM
I'm very curious about what 5V regulator you're using that can handle the current draw of the Sheeva and the USB dongles you've got on it.

I'm not so much interested in powering the sheevaplug with solar, but my primary use for the SheevaPlug will be to handle some of my amateur radio applications --- which means it's working in an area where I have lots of 12V supplies available including some batteries.  It would be nice to power the Sheeva from the 12V athat's all over the shack rather than AC.

So far, all the DC/DC converters I've seen that can do 12V-5V at the current levels needed are almost as expensive as the SheevaPlug itself.
5  Linux Stuff / Kernel / Re: [SOLVED] Internal error: Oops: 5 from 2.6.22.18 #1 on: June 11, 2009, 02:17:08 PM
My "solution" was simply to go with a newer kernel, which I needed anyway for the modules to support the hardware I have since added.

Thanks,

Charles

Thank you for this post, Charles.

I also had this problem with hald while following pushbx's instructions for installing X11 with VNC because icewm-gnome installes hal and that is broken.  Your "solution" is clearly the reason that pushbx didn't have the problem, because he is certainly running with a 2.6.30 kernel (as am I, now).  I've been gunshy about trying to install anything that might install hal ever since, but I'm glad to know that 2.6.30 fixes it.
6  Linux Stuff / Kernel / Re: 2.6.30-rc8 new release on: June 09, 2009, 07:52:47 AM

[...]

But I'm thinking this probably means my NAND flash is not set up properly to receive the uImage that is downloaded here.  What do I need to do to set it up right?  I assume it's something related to the first couple of steps in the USB recovery document:
Code:
   Marvell>> set loadaddr 0x20000000
   Marvell>> set mtd1Size 0x300000
SO what should "mtd1Size" actually be if not what the recovery document says?

I assume that if I change that, I'll also have to reflash the filesystem, too, because the start of mtd2 will need to be shifted.  Yes?  So what exactly (in painfully detailed steps) would I need to do here.
[...]

Answering my own question, looks like I need to completely redo the USB reflash with:

Code:
  Marvell>> set loadaddr 0x2000000
  Marvell>> set mtd1Size 0x400000
  Marvell>> set filesize 0x44ad000
  Marvell>> saveenv
  Marvell>> reset

followed by the reflash from USB drive and a new bootcmd and bootargs of:
Code:
setenv bootcmd 'nand read.e 0x800000 0x100000 0x400000; bootm 0x800000'
setenv bootargs 'console=ttyS0,115200
mtdparts=nand_mtd:0x100000@0x00000(uboot),
0x400000@0x100000(uImage)ro,0x1fb00000@0x500000(rootfs)rw
root=/dev/mtdblock2'

to get back to the original size of mtd1 and the original kernel, at which point I should be able to reflash with the 2.6.30-rc8. 

These commands differ from the ones in the  most recent USB recovery document ( SheevaPlug Development Kit - USB Flash Recovery from U-Boot-Rev1.2.pdf) in that they all set the mtd1 partition to 0x400000 instead of 0x300000.  It is a pity that the 1.2 revision of that is in the most recent documentation package has this choice of mtd1 partition size, since as far as I can tell that is *NOT* how the unit is shipped (according to http://www.computingplugs.com/index.php/Default_software which shows all the mtd1 variables at 0x400000.

 
7  Linux Stuff / Kernel / Re: 2.6.30-rc8 new release on: June 09, 2009, 12:42:26 AM
I just got my SheevaPlug and tried to use your README to reflash with the new kernel (I want the modules).  It ended with the following:
Code:
Image 2599688 bytes, NAND page 2048 bytes, OOB area 2048 bytes, devices size 2097152 bytes
Input file does not fit into device: Success
Data was only partially written due to error
: Success
Despite the "Success" claims, this doesn't look good.  Rather than test it out, I just reflashed the original uImage (by following the USB recovery instructions) and got a working device back.

But I'm thinking this probably means my NAND flash is not set up properly to receive the uImage that is downloaded here.  What do I need to do to set it up right?  I assume it's something related to the first couple of steps in the USB recovery document:
Code:
   Marvell>> set loadaddr 0x20000000
   Marvell>> set mtd1Size 0x300000
SO what should "mtd1Size" actually be if not what the recovery document says?

I assume that if I change that, I'll also have to reflash the filesystem, too, because the start of mtd2 will need to be shifted.  Yes?  So what exactly (in painfully detailed steps) would I need to do here.

I have already successfully reflashed my device using the USB recovery after having hosed it following some other instructions that left me with a corrupted "hal" package that couldn't be unwedged, so at least I know how to get it back to its original state.  But I'd rather like not to have to keep doing that  Smiley.

Pages: [1]