• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 2 [3]
31  Linux Stuff / General Linux questions / Re: Tottaly Newbie on: November 10, 2009, 09:46:23 PM
Dear all,

I am sorry but I am new at Linux and at Sheeva, it just arrived, I have pluged it in, and have found it in my network. So, letīs start the questions:

I am using Putty software to loggin in in Sheeva, so there is any default login and pass to enter??


Hello alexgondim,

Does your Sheevaplug (SDK) comes with a development CD? Maybe a little browsing on the documents could help you start faster...  Smiley


Just my 2 cents.

32  Hardware and U-Boot firmware / U-Boot stuff / Re: Completely Blank Console on: October 23, 2009, 02:32:26 AM

Any thoughts would be GRATEFULLY received! I've completely run out of ideas!


Maybe this could help you, based on how I do it in the "windows" version of the sheevaplug-installer. I know you are already familiar with the basic instructions but I just added some things.

Please, also take note that I am using Teraterm as the serial console.
I have also installed the USBtoSerial JTAG driver (FTDI) on my windows PC.


1. Connect the USB stick (preloaded with installer) into the Plugcomputer.
2. Attach the JTAG into the plugcomputer and connect it to the PC using USB cable.
3. Supply power to the plugcomputer unit.
*4. When the plugcomputer boots up, disconnect and reconnect the USB cable of the JTAG.
5. Execute "runme.exe | nand" on the command prompt, this will format the NAND flash.
*6. After the nand is formatted through open ocd, close the CMD prompt. Disconnect and reconnect the USB cable of the JTAG.
7. Open teraterm and select the appropriate serial port. Configure Baud rate to 115200.
8. Wait until the rootfilesystem is flashed into the NAND and the system reboots.


Oftentimes, I have to disconnect and reconnect the usb cable of the JTAG board just to make it work on windows.  Grin


Hope this could help.
33  General Category / General Discussion / Re: Boycott Global Scale Technologies on: October 21, 2009, 01:08:07 AM

As for the Ionics plug suggested by Snake:

I'd like to get a couple from them as they are much smaller than the GS version and black. Sweet. But, they seem even more disorganised in my opinion than GS as they at first answered my initial enquiries, and now they aren't responding at all to my requests for purchase. Their website is poor. There's no way to contact them (that I can see) other than their one supplied email address.

Has anyone actually successfully purchased any plugs from them? If so, whom can I contact please?

Hi badcam,

Have you ever tried clicking on the "CONTACT US" link?  Grin
Or if you really like direct links try this.... http://www.ionics-ems.com/contact.html

There are 3 main SDK distributors I think: GlobalScale, NEW IT, and IONICS and you can certainly choose any of them, but do not expect that these companies could always reply to your inquiries since they could be busy processing bulk orders....

Just my 2 cents.
34  General Category / General Discussion / Re: Boycott Global Scale Technologies on: October 19, 2009, 12:00:19 AM

If you have a problem with Globalscale, report it to Marvell. If Marvell receive enough complaints (that they themselves aren't the real cause of) then they might consider switching distributer, or at least slapping Globalscale until their customer service improves. Or, they might ask Globalscale to expedite your order. Either way, you stand a chance of getting the results you want.


Hmm.. I am not really sure whether Marvell has the power to "slap" Globalscale... I think, Marvell is a chip designer and Globalscale is a manufacturer who orders chips from them. And though they have this link, they are completely different companies with different management.

If you really dislike GlobalScale you could use the net to surf for other manufacturers who also create plugcomputers using the Marvell chip...

for example:

http://www.ionics-ems.com/plugcomputer.html


Just a suggestion of course.

35  Hardware and U-Boot firmware / Hardware / Re: Controlling green LED. on: October 14, 2009, 10:03:20 PM
That`s pretty simple, actually.
Check arch/arm/mach-kirkwood/sheevaplug-setup.c
I think all you have to do is adding a new entry to sheevaplug_led_pins[].
You'll also need to know the right GPIO pin.

(That`s also the place to change the name of plug:green:health to anything you want)

Thanks for this information...  It helped me to control the individual colors in the tricolor LED mounted on my plugcomputer... Cheesy
36  Hardware and U-Boot firmware / Hardware / Re: success to control green led and red led which belong to pogoplug on: October 13, 2009, 08:14:22 PM
Hello Victor,

I'm also interested in controlling additional LED's in the sheevaplug platform.

I think your post is very helpful but I just have one question though, are the files that you have attached (ledapp.tar.gz and led_drv.tar.gz) should be compiled inside the plug?

Hope you could provide help on how you were able to do it.

Thank you.
37  Linux Stuff / Kernel / Re: Need kernel headers for 2.6.30.2 [SOLVED] on: October 06, 2009, 06:58:04 PM
sorry for re-opening the thread, but could someone explain to me how to install the headers from sheeva.with-linux?

I also updated to the 2.6.30.6 in order to have the ability to make some drivers I need, but I cant figure out how to install the headers from the tar.gz files from the site. When I extract them I get a usr directory with many subdirectories.
Do I need to copy the directory somewhere? forgive my ignorance but the only ways Ive done headers is by installing them through apt-get or by .deb files.

Thanks in advance


Hello Manic, I am also having the same problem... have you already managed to figure out how to install these headers so that we could "make" drivers from sources? Could you kindly share this knowledge?

I tried crazy ideas like replacing the link of "/lib/modules/2.6.30-rc6/build" that is pointing to "/home/kelly/src/Sheevaplug_LSP/Sources/linux-2.6.30-rc6-work" (which is actually a dead link) to "/usr/include/linux" after decompressing the tar.gz header files to "/' directory... but still no luck.

Any help would be appreciated.
Pages: 1 2 [3]