All, except for one file with some chip wiring, are for the original Sheeva
PLUG. My guess is they went on to Guru PLUG and didn't follow up on assembling
a package of documentation like was done on the original PLUG.
From: mick
To: Herman Swartz
. The two are significantly different. I
have not been able to find documentation for the v1.3 Power PLUG.
Herman
From: DrEagle
To: Herman Swartz
Cc: "debian-arm@lists.debian.org"
Sent: Thursday, December 6, 2012 11:13 AM
Subject: RE : R
about the PLUG, but Linux to.
Herman
From: DrEagle
To: Herman Swartz
Cc: "debian-arm@lists.debian.org"
Sent: Thursday, December 6, 2012 11:13 AM
Subject: RE : Re: Bricked Sheevaplug
I may had same problem with android mail.
I do not see another
I am using Yahoo mail. Do not see any way to stop TOFU.
try just
# modprobe ftdi_sio
instead
Herman: No difference
You mean notinh about jtag or nothing at all ?
Herman:
root@raspberrypi:/lib/udev/rules.d# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device
ad_uboot
Error: unable to open ftdi device: device not found
in procedure 'init'
- Original Message -
From: DrEagle
To: Herman Swartz
Cc: "debian-arm@lists.debian.org"
Sent: Monday, December 3, 2012 1:19 PM
Subject: Re: Bricked Sheevaplug
Sorry for the delay, I
- Original Message -
From: DrEagle
To: Herman Swartz
Cc: "debian-arm@lists.debian.org"
Sent: Monday, December 3, 2012 1:19 PM
Subject: Re: Bricked Sheevaplug
Sorry for the delay, I just come back home !
Le 03/12/2012 16:04, Herman Swartz a écrit :
> No, I do not. Have been searching
on the console host to
the Sheeva PLUG coming active with a connection?
lsusb command being executed on the console host doesn't show anything
different from execution of the command before the PLUG cold boot.
Herman
- Original Message -
From: DrEagle
To: Herman Swartz
Cc: &q
loaded and the USB support for it.
There was a Raspberry Pi drive full issue I needed to resolve before picking
back up with it.
- Original Message -
From: DrEagle
To: Herman Swartz
Cc: debian-arm@lists.debian.org
Sent: Thursday, November 29, 2012 9:29 AM
Subject: Re: Bricked
nager screen the
virtual com port comes and goes in the port display.
Hope what I have described above all makes sense. :-)
- Original Message -
From: Dimax
To: DrEagle
Cc: Herman Swartz ; debian-arm@lists.debian.org
Sent: Thursday, November 29, 2012 2:35 PM
Subject: Re: Bricked Sheevapl
n.cpu' as target identifier, not '0'
Segmentation fault
- Original Message -
From: DrEagle
To: debian-arm@lists.debian.org
Cc:
Sent: Thursday, November 29, 2012 2:51 AM
Subject: Re: Bricked Sheevaplug
On 28.11.2012 16:21, Clint Adams wrote:
> On Tue, Nov 27, 2012 at 0
Hi Gerald,
Do you have info or links to instruction on how to use openocd with Sheeva
PLUG? A cfg file for PLUG would help.
Thanks
Herman
- Original Message -
From: DrEagle
To: Andrew M.A. Cater ;
debian-arm@lists.debian.org
Cc:
Sent: Thursday, February 9, 2012 1:16 PM
Subject: RE:
Thanks for your feedback Rainer.
Herman
- Original Message -
From: Rainer H. Rauschenberg
To: "debian-arm@lists.debian.org"
Cc:
Sent: Monday, November 26, 2012 3:37 PM
Subject: Re: System crashes on USB connection
On Mon, 26 Nov 2012, Herman Swartz wrote:
> I have a Sh
Sent: Monday, November 26, 2012 11:30 AM
Subject: Re: System crashes on USB connection
Herman Swartz wrote:
[...]
> I have a Sheeva PLUG dev kit with Debian Linux release and the USB port is
> not able to handle having a second USB device connected simultaineously. I
> tried connecting
Hi Christoph,
I have a Sheeva PLUG dev kit with Debian Linux release and the USB port is not
able to handle having a second USB device connected simultaineously. I tried
connecting a USB hub into the single USB of the Sheeva PLUG and then plugging a
hard drive into the hub. The PLUG is able to
the library
files??
What do you think?
Thanks
Herman
- Original Message
From: Daniel Kahn Gillmor
To: Xan
Cc: debian-arm@lists.debian.org; Herman Swartz
Sent: Thu, June 10, 2010 3:50:24 PM
Subject: Re: Context Switching is Broken
On 06/10/2010 11:34 AM, Xan wrote:
> Maybe you r
Context switching is broken. The man page for context is example code that
doesn't work, but should.
Does a bug report need to be submitted?
Thanks
Herman
--
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lis
I have Sheeva PLUG running Debian Squeeze.
While compiling JNOS program several error messages are returned regarding
errors in modules calling get, set, make and swap context functions not being
implemented.
The JNOS developer directed me to ARM Architecture threads.
Do you have any idea w
17 matches
Mail list logo
