mick
> *To:* Herman Swartz
> *Cc:* DrEagle ; "debian-arm@lists.debian.org"
>
> *Sent:* Sunday, December 9, 2012 10:21 AM
> *Subject:* Re: Bricked Sheevaplug
>
> On Sun, 9 Dec 2012 06:04:39 -0800 (PST)
> Herman Swartz mailto:herman_swa...@yahoo.com>>
>
Cc: DrEagle ; "debian-arm@lists.debian.org"
Sent: Sunday, December 9, 2012 10:21 AM
Subject: Re: Bricked Sheevaplug
On Sun, 9 Dec 2012 06:04:39 -0800 (PST)
Herman Swartz allegedly wrote:
>
> When I ordered the PLUG from Globalscale they sent me the Power PLUG,
> v1.3 of the or
On Sun, 9 Dec 2012 06:04:39 -0800 (PST)
Herman Swartz allegedly wrote:
>
> When I ordered the PLUG from Globalscale they sent me the Power PLUG,
> v1.3 of the original PLUG. Globalscale did NOT provide the proper
> documentation, they included the doc for the original PLUG. The two
> are signific
. 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 may had same problem with android mail.
I do not see another test to do.
May be a quick reset after power on could help.
I had one of my sheevaplugs with issues like yours.
The only way to get able to talk to it was something like undocumented failsafe
recovery.
I just remember playing with
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
endor}=="9e88", ATTRS{idProduct}=="9e8f", MODE="664", GROUP="plugdev"
---%<---
Must be present !
> - Original Message -
> From: DrEagle
> To: Herman Swartz
> Cc: "debian-arm@lists.debian.org"
> Sent: Monday, December 3, 20
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
uot;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 for a package for the USB/JTAG driver. I
> have been sea
om the windows host to the virtualized debian.
> There was a Raspberry Pi drive full issue I needed to resolve before picking
> back up with it.
Enjoy and good hacking !
> - Original Message -
> From: DrEagle
> To: Herman Swartz
> Cc: debian-arm@lists.debian.org
>
loads are enabled
> Warn : use 'feroceon.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:
bugs.html
>>> 2000 kHz
>>> trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
>>> jtag_nsrst_delay: 200
>>> jtag_ntrst_delay: 200
>>> dcc downloads are enabled
>>> Warn : use 'feroceon.cpu' as target identifier, not '0'
>>>
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
roceon.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
er, 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 08:56:14PM -0800, Herman Swartz wrote:
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
On 28.11.2012 16:21, Clint Adams wrote:
On Tue, Nov 27, 2012 at 08:56:14PM -0800, Herman Swartz wrote:
Do you have info or links to instruction on how to use openocd with
Sheeva PLUG? A cfg file for PLUG would help.
/usr/share/openocd/scripts/board/sheevaplug.cfg
/usr/share/openocd/scripts/int
On Tue, Nov 27, 2012 at 08:56:14PM -0800, Herman Swartz wrote:
> Do you have info or links to instruction on how to use openocd with Sheeva
> PLUG? A cfg file for PLUG would help.
/usr/share/openocd/scripts/board/sheevaplug.cfg
/usr/share/openocd/scripts/interface/sheevaplug.cfg
are in the Debia
;m still far from my computer...
Regards,
Gérald
- Message d'origine -
De: Andrew M.A. Cater
Env: jeudi 9 février 2012 18:39
À: debian-arm@lists.debian.org
Objet: Re: Bricked Sheevaplug
On Thu, Feb 09, 2012 at 05:45:03PM +0100, DrEagle wrote:
Hello,
It is really hard to brick a sh
x27;m still far from my computer...
Regards,
Gérald
- Message d'origine -
De: Andrew M.A. Cater
Env: jeudi 9 février 2012 18:39
À: debian-arm@lists.debian.org
Objet: Re: Bricked Sheevaplug
On Thu, Feb 09, 2012 at 05:45:03PM +0100, DrEagle wrote:
> Hello,
>
> It is reall
Le 07/04/2012 23:03, Roger Barraud a écrit :
> On 07/04/12 18:48, DrEagle wrote:
>> Hi Andrew,
>>
>> Just a clue,
>>
>> Le 09/02/2012 14:45, Andrew M.A. Cater a écrit :
>>> Upated to lastest DENX U-boot and went to install Debian as per
>>> Martin's excellent instructions.
>>>
>>> Aborted the insta
On 07/04/12 18:48, DrEagle wrote:
Hi Andrew,
Just a clue,
Le 09/02/2012 14:45, Andrew M.A. Cater a écrit :
Upated to lastest DENX U-boot and went to install Debian as per Martin's
excellent instructions.
Aborted the install part way through.
Now can't get back into the plug via U-boot : scr
Hi Andrew,
Just a clue,
Le 09/02/2012 14:45, Andrew M.A. Cater a écrit :
> Upated to lastest DENX U-boot and went to install Debian as per Martin's
> excellent instructions.
>
> Aborted the install part way through.
>
> Now can't get back into the plug via U-boot : screen /dev/ttyUSB0 115200
On Thu, Feb 09, 2012 at 08:00:36PM +, David Given wrote:
> On 09/02/12 19:31, Andrew M.A. Cater wrote:
> [...]
> > Thanks for all - and thank you for the tip about openocd. It turns out that
> > the lead I'm using - which is better quality than the
> > lead supplied - doesn't work very reliabl
On 09/02/12 19:31, Andrew M.A. Cater wrote:
[...]
> Thanks for all - and thank you for the tip about openocd. It turns out that
> the lead I'm using - which is better quality than the
> lead supplied - doesn't work very reliably on two of the machines I tried it
> on. On the laptop, it worked imm
try to give exact command and a ready to use config file later.
> For now I'm still far from my computer...
>
> Regards,
> Gérald
>
> - Message d'origine -
> De: Andrew M.A. Cater
> Env: jeudi 9 février 2012 18:39
> À: debian-arm@lists.debian.org
>
rom my computer...
Regards,
Gérald
- Message d'origine -
De: Andrew M.A. Cater
Env: jeudi 9 février 2012 18:39
À: debian-arm@lists.debian.org
Objet: Re: Bricked Sheevaplug
On Thu, Feb 09, 2012 at 05:45:03PM +0100, DrEagle wrote:
> Hello,
>
> It is really hard to brick a shee
W dniu 09.02.2012 09:39, Andrew M.A. Cater pisze:
On Thu, Feb 09, 2012 at 05:45:03PM +0100, DrEagle wrote:
This is precisely the problem: it is _NOT_ coming up with serial console and
there's no obvious record of it on the network. I see some activity on hard
reset from
blinking lights - but
On Thu, Feb 09, 2012 at 05:45:03PM +0100, DrEagle wrote:
> Hello,
>
> It is really hard to brick a sheeva plug.
> You always can use usb console as jtag and flash a new uboot with openocd.
>
> I have not my notes with me to give more help for now.
>
> Gérald
>
> - Message d'origine -
>
Hello,
It is really hard to brick a sheeva plug.
You always can use usb console as jtag and flash a new uboot with openocd.
I have not my notes with me to give more help for now.
Gérald
- Message d'origine -
De: Andrew M.A. Cater
Env: jeudi 9 février 2012 14:45
À: debian-arm@lists.debi
* Mark Brown [2009-08-02 13:18]:
> > Filename 'uImage'.
> > Load address: 0x200
> > Loading: T T T T T T T T T T
> > Retry count exceeded; starting again
> > ## Booting image at 0200 ...
> > Bad Magic Number
> > Unknown command '' - try 'help'
> > Marvell>>
>
> That doesn't look bricked?
On Sat, Aug 01, 2009 at 08:19:37PM +0100, Andrew M.A. Cater wrote:
> USB 0: host mode
> PEX 0: interface detected no Link.
> Net: egiga0 [PRIME], egiga1
> Hit any key to stop autoboot: 0
> Using egiga0 device
> TFTP from server 10.4.50.5; our IP address is 10.4.50.165
> Filename 'uImage'.
> Loa
34 matches
Mail list logo
