• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  Hardware and U-Boot firmware / Hardware / Re: Help with GuruPlug JTAG connection on: May 22, 2010, 01:13:16 PM
> What do you mean by serial output? Seeing the plug boot and being able to give commands?

Exactly: when connected to the console serial port via the optional JTAG box, there is no output -- only input.  I *can* give it commands.  If I hit return a few times after applying power, the plug stays in the uboot command area and does not boot into the blinking WiFi LED stage.  If I don't hit returns after power on, the plug boots all the way. 

After the plug boots, even though I don't get any response from the plug when I type, I know it is doing what I am asking: I can log in by typing the root user name and default root password, and then if I type a 'reboot' command, the plug reboots.

I have a SheevaPlug too, and it works perfectly over the jtag serial console interface.  It's only my guruplug that seems to be JTAG output-challenged.
I'm just a newbie in the plugworld, but is JTAG-communication defined by specific pins for in and output? Otherwise I'd say your JTAG is defective. I just was really surprised how deep it's pushed in the plug, the whole connector disappears into the housing so to say...
2  Hardware and U-Boot firmware / Hardware / Re: Help with GuruPlug JTAG connection on: May 22, 2010, 12:42:21 PM
> Edit: Actually you might want to check out this thread: http://plugcomputer.org/plugforum/index.php?topic=1679.0

OK, I tried that: no change; still no serial output.
What do you mean by serial output? Seeing the plug boot and being able to give commands?
I noticed that you need to stick the cables in really deep, if your problem is getting no output from the plug check your connection, I put the cable in place and pushed it gently in with a screwdriver(short nails Wink).
3  Hardware and U-Boot firmware / Hardware / Re: guru plus wired ethernet hang on: May 22, 2010, 12:37:46 PM
guru plus received, connected via wireless network as an access point.  When connecting wired ethernet, system hangs, will reboot.
Thought it migh be swap space, seems not to be.  Also, the USB thumbdrive mounted in usb0 has a fried directory.  Not sure if the two
issues are related.  Ethernet devices are loaded, indicated in kernel message queue (dmesg).  Checking logs, nothing found so far.

Ideas welcome.

Several messages here on the forum seem to indicate it's a problem with some Gbit routers and swtiches but not all. I solved it by connecting to a fast ethernet connection and also tested by switching back to 100Mbit via mii-ttool or ethtool.
It seems software, after switching to 100Mbit it didn't crash once, even when compiling and having 100% load(it did get really warm though Wink)
4  Hardware and U-Boot firmware / Hardware / Re: guruplug server plus arrived but died on: May 21, 2010, 05:06:27 AM
I don't think this is related to temperature, because the reset happens immediately when I connect to a gigabit device. I hope this is a driver problem and someone comes up with a solution!

BTW: My supplier (dureg) confirmed that this is a known problem and they are working with GlobalScale to solve it.

In the meantime: What would be a good place to call ethtool (or mii-tool)? I could call it early in /etc/rcS.d, but then I still had to pull the cable before reboot. Does anyone know if (and how) I can pass an option to the mv643xx_eth module to limit autonegotiation?

eth-tool can be called from /etc/network/interfaces as far as I can tell(saw a nice link yesterdat, but now unable to find it again, most examples cover redhat.

In this case it would be something like this:
auto eth0
iface eth0 inet dhcp
     pre-up [ -f /etc/network/call_to_eth_tool_with_appropiate_parameters.script]

I'm no debian-master so I might be wrong, but this seems like the best place because it seems to be run when the adapter is brought up...
Pages: [1]