Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bricked Sheevaplug
235 views
Skip to first unread message
Andrew M.A. Cater
Feb 9, 2012, 10:40:02 AM2/9/12
to
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 isn't working.
Have one green light - serial plug, reset are facing you as the plug lies with mains on right had side, Ethernet on left: this is the right hand one of the two green LEDs opposite the SD card.
There is Ethernet activity.
Reset button has no apparent effect.
Nmap doesn't show it at least at 192.168.1.0/24
Any ideas?
This is the third or fourth attempt: I've another working Sheevaplug installed last week, but without serial console to this one I can't get any further.
All best
AndyC
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2012020913...@galactic.demon.co.uk
Aborted the install part way through.
Now can't get back into the plug via U-boot : screen /dev/ttyUSB0 115200 isn't working.
Have one green light - serial plug, reset are facing you as the plug lies with mains on right had side, Ethernet on left: this is the right hand one of the two green LEDs opposite the SD card.
There is Ethernet activity.
Reset button has no apparent effect.
Nmap doesn't show it at least at 192.168.1.0/24
Any ideas?
This is the third or fourth attempt: I've another working Sheevaplug installed last week, but without serial console to this one I can't get any further.
All best
AndyC
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2012020913...@galactic.demon.co.uk
DrEagle
Feb 9, 2012, 11:50:02 AM2/9/12
to
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 <amac...@galactic.demon.co.uk>
Env: jeudi 9 février 2012 14:45
À: debia...@lists.debian.org
Objet: Bricked Sheevaplug
Archive: http://lists.debian.org/2012020916460...@milenium.gk2.net
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 <amac...@galactic.demon.co.uk>
Env: jeudi 9 février 2012 14:45
À: debia...@lists.debian.org
Objet: Bricked Sheevaplug
Andrew M.A. Cater
Feb 9, 2012, 12:40:03 PM2/9/12
to
blinking lights - but I can't get any further.
AndyC
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Marcin Juszkiewicz
Feb 9, 2012, 1:10:01 PM2/9/12
to
W dniu 09.02.2012 09:39, Andrew M.A. Cater pisze:
u-boot binary and then go with sheevaplug_reflash_uboot procedure. It is
not rocket science.
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/4F340A79...@linaro.org
> 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 I can't get any further.
Connect usb console cable, install openocd on host system, grab working
> 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 I can't get any further.
u-boot binary and then go with sheevaplug_reflash_uboot procedure. It is
not rocket science.
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
DrEagle
Feb 9, 2012, 1:20:02 PM2/9/12
to
Hello,
You can try to reflash uboot binary with openocd.
You need to keep reset switch while power up your plug.
You'll then have to send openocd reflash command in the next few seconds.
I'll try to give exact command and a ready to use config file later.
For now I'm still far from my computer...
Regards,
Env: jeudi 9 février 2012 18:39
À: debia...@lists.debian.org
Objet: Re: Bricked Sheevaplug
On Thu, Feb 09, 2012 at 05:45:03PM +0100, DrEagle wrote:
>
> All best
>
> AndyC
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2012020917...@galactic.demon.co.uk
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2012020918163...@milenium.gk2.net
You can try to reflash uboot binary with openocd.
You need to keep reset switch while power up your plug.
You'll then have to send openocd reflash command in the next few seconds.
I'll try to give exact command and a ready to use config file later.
For now I'm still far from my computer...
Regards,
Env: jeudi 9 février 2012 18:39
À: debia...@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 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 <amac...@galactic.demon.co.uk>
> Env: jeudi 9 février 2012 14:45
> À: debia...@lists.debian.org
> Objet: Bricked Sheevaplug
>
> 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 isn't working.
>
> Have one green light - serial plug, reset are facing you as the plug lies with mains on right had side, Ethernet on left: this is the right hand one of the two green LEDs opposite the SD card.
>
> There is Ethernet activity.
>
> Reset button has no apparent effect.
>
> Nmap doesn't show it at least at 192.168.1.0/24
>
> Any ideas?
>
> This is the third or fourth attempt: I've another working Sheevaplug installed last week, but without serial console to this one I can't get any further.
>
> 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 <amac...@galactic.demon.co.uk>
> Env: jeudi 9 février 2012 14:45
> À: debia...@lists.debian.org
> Objet: Bricked Sheevaplug
>
> 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 isn't working.
>
> Have one green light - serial plug, reset are facing you as the plug lies with mains on right had side, Ethernet on left: this is the right hand one of the two green LEDs opposite the SD card.
>
> There is Ethernet activity.
>
> Reset button has no apparent effect.
>
> Nmap doesn't show it at least at 192.168.1.0/24
>
> Any ideas?
>
>
> All best
>
> AndyC
>
>
> --
> To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
> Archive: http://lists.debian.org/2012020913...@galactic.demon.co.uk
>
> --
> To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
>
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 I can't get any further.
AndyC
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 I can't get any further.
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Andrew M.A. Cater
Feb 9, 2012, 2:40:01 PM2/9/12
to
lead supplied - doesn't work very reliably on two of the machines I tried it on. On the laptop, it worked immediately and I was
able to see that it was attempting to boot a kernel and hanging. Reset: interrupted U-Boot successfully, and am now attempting a
reinstall.
Thanks to all who have offered help: sorry to have caused the noise.
All the very best,
AndyC
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
David Given
Feb 9, 2012, 4:10:01 PM2/9/12
to
On 09/02/12 19:31, Andrew M.A. Cater wrote:
[...]
dodgy USB leads: sporadic USB errors on an external hard drive (which
would then cause the root file system to vanish. Very nasty), USB
console not showing up, the SheevaPlug spontaneously rebooting when
attaching or detaching the USB console... in all cases, replacing the
lead with a different one fixed the problem.
I hear a rumour that Marvell's USB chipset isn't terribly robust, and it
may well be more sensitive to sub-par USB leads than other hardware.
Whether it is or not I'd strongly recommend that anyone who's having
problems with their device try a different (more expensive) USB cable
and seeing what happens.
--
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ─────
│
│ "Never attribute to malice what can be adequately explained by
│ stupidity." --- Nick Diamos (Hanlon's Razor)
[...]
> 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 immediately and I was
> able to see that it was attempting to boot a kernel and hanging. Reset: interrupted U-Boot successfully, and am now attempting a
> reinstall.
Incidentally, I've been having endless trouble with my SheevaPlug with
> lead supplied - doesn't work very reliably on two of the machines I tried it on. On the laptop, it worked immediately and I was
> able to see that it was attempting to boot a kernel and hanging. Reset: interrupted U-Boot successfully, and am now attempting a
> reinstall.
dodgy USB leads: sporadic USB errors on an external hard drive (which
would then cause the root file system to vanish. Very nasty), USB
console not showing up, the SheevaPlug spontaneously rebooting when
attaching or detaching the USB console... in all cases, replacing the
lead with a different one fixed the problem.
I hear a rumour that Marvell's USB chipset isn't terribly robust, and it
may well be more sensitive to sub-par USB leads than other hardware.
Whether it is or not I'd strongly recommend that anyone who's having
problems with their device try a different (more expensive) USB cable
and seeing what happens.
--
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ─────
│
│ "Never attribute to malice what can be adequately explained by
│ stupidity." --- Nick Diamos (Hanlon's Razor)
Andrew M.A. Cater
Feb 10, 2012, 3:30:02 PM2/10/12
to
On Thu, Feb 09, 2012 at 08:00:36PM +0000, 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 reliably on two of the machines I tried it on. On the laptop, it worked immediately and I was
> > able to see that it was attempting to boot a kernel and hanging. Reset: interrupted U-Boot successfully, and am now attempting a
> > reinstall.
>
> Incidentally, I've been having endless trouble with my SheevaPlug with
> dodgy USB leads: sporadic USB errors on an external hard drive (which
> would then cause the root file system to vanish. Very nasty), USB
> console not showing up, the SheevaPlug spontaneously rebooting when
> attaching or detaching the USB console... in all cases, replacing the
> lead with a different one fixed the problem.
>
I'm using a good quality camera lead and it worked very well finally
> 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 immediately and I was
> > able to see that it was attempting to boot a kernel and hanging. Reset: interrupted U-Boot successfully, and am now attempting a
> > reinstall.
>
> Incidentally, I've been having endless trouble with my SheevaPlug with
> dodgy USB leads: sporadic USB errors on an external hard drive (which
> would then cause the root file system to vanish. Very nasty), USB
> console not showing up, the SheevaPlug spontaneously rebooting when
> attaching or detaching the USB console... in all cases, replacing the
> lead with a different one fixed the problem.
>
allowing me to install well _once_ I could see the console :)
> I hear a rumour that Marvell's USB chipset isn't terribly robust, and it
> may well be more sensitive to sub-par USB leads than other hardware.
> Whether it is or not I'd strongly recommend that anyone who's having
> problems with their device try a different (more expensive) USB cable
> and seeing what happens.
>
AndyC
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
bestztlights
Apr 6, 2012, 11:00:01 PM4/6/12
to
http://www.ztlights.com/LED-Tube-Light.html LED Tube Light
Comparing with traditional fluorescent tubes, our
http://www.ztlights.com/LED-Tube-Light.html LED Tube can save over 60%
electricity cost. For
example, the 8W, 16W, 21W http://www.ztlights.com/LED-Tube-
Light.html LED Tube Lights can replace
corresponding 16W, 32W and 40W traditional ones.LED tubes do not need
ballast or starter.Benefits are as follow:
1.Work without ballast and starter. Save over 60% electricity cost in
total.
2.T5 , T8, T9, T10,tubes are all available.
3.100-277V AC
4.Over 30,000 hours lifespan.
5.Input voltage can be 24V DC, 85-140/200-260V AC.
6.Eco-friendly
http://www.ztlights.com/ http://www.ztlights.com/
email:jin...@ztlights.com
--
View this message in context: http://old.nabble.com/Bricked-Sheevaplug-tp33294033p33647252.html
Sent from the debian-arm mailing list archive at Nabble.com.
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
DrEagle
Apr 7, 2012, 3:00:01 AM4/7/12
to
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 isn't working.
>
> Have one green light - serial plug, reset are facing you as the plug lies with mains on right had side, Ethernet on left: this is the right hand one of the two green LEDs opposite the SD card.
>
> There is Ethernet activity.
>
> Reset button has no apparent effect.
>
> Nmap doesn't show it at least at 192.168.1.0/24
>
> Any ideas?
>
> This is the third or fourth attempt: I've another working Sheevaplug installed last week, but without serial console to this one I can't get any further.
Use you usb/serial as a JTag (it works also as a jtag).
You can reflash yoyr uboot usng openocd [1].
FYI, then only sheevaplugs bricked were because of power supply
faulty... ;-)
[1]https://doukki.net/doku.php?id=wiki:tutoriels:uboot.howto
---
Gk2
:-]
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/4F7FE347...@doukki.net
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 isn't working.
>
> Have one green light - serial plug, reset are facing you as the plug lies with mains on right had side, Ethernet on left: this is the right hand one of the two green LEDs opposite the SD card.
>
> There is Ethernet activity.
>
> Reset button has no apparent effect.
>
> Nmap doesn't show it at least at 192.168.1.0/24
>
> Any ideas?
>
> This is the third or fourth attempt: I've another working Sheevaplug installed last week, but without serial console to this one I can't get any further.
You can reflash yoyr uboot usng openocd [1].
FYI, then only sheevaplugs bricked were because of power supply
faulty... ;-)
[1]https://doukki.net/doku.php?id=wiki:tutoriels:uboot.howto
---
Gk2
:-]
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Roger Barraud
Apr 7, 2012, 5:10:02 PM4/7/12
to
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 : screen /dev/ttyUSB0 115200 isn't working.
>>
>> Have one green light - serial plug, reset are facing you as the plug lies with mains on right had side, Ethernet on left: this is the right hand one of the two green LEDs opposite the SD card.
>>
>> There is Ethernet activity.
>>
>> Reset button has no apparent effect.
>>
>> Nmap doesn't show it at least at 192.168.1.0/24
>>
>> Any ideas?
>>
>> This is the third or fourth attempt: I've another working Sheevaplug installed last week, but without serial console to this one I can't get any further.
> Use you usb/serial as a JTag (it works also as a jtag).
> You can reflash yoyr uboot usng openocd [1].
>
> FYI, then only sheevaplugs bricked were because of power supply
> faulty... ;-)
>
> [1]https://doukki.net/doku.php?id=wiki:tutoriels:uboot.howto
> ---
> Gk2
> :-]
>
>
Does this also work with GuruPlug?
> 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 isn't working.
>>
>> Have one green light - serial plug, reset are facing you as the plug lies with mains on right had side, Ethernet on left: this is the right hand one of the two green LEDs opposite the SD card.
>>
>> There is Ethernet activity.
>>
>> Reset button has no apparent effect.
>>
>> Nmap doesn't show it at least at 192.168.1.0/24
>>
>> Any ideas?
>>
>> This is the third or fourth attempt: I've another working Sheevaplug installed last week, but without serial console to this one I can't get any further.
> Use you usb/serial as a JTag (it works also as a jtag).
> You can reflash yoyr uboot usng openocd [1].
>
> FYI, then only sheevaplugs bricked were because of power supply
> faulty... ;-)
>
> [1]https://doukki.net/doku.php?id=wiki:tutoriels:uboot.howto
> ---
> Gk2
> :-]
>
>
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
DrEagle
Apr 8, 2012, 4:50:01 AM4/8/12
to
You only need a specific adapter for serial/jtag on the guruplug.
Regards,
---
Gk2
:-]
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Herman Swartz
Nov 28, 2012, 12:00:02 AM11/28/12
to
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
Hello,
Regards,
Gérald
AndyC
Archive: http://lists.debian.org/1354078574.151...@web39301.mail.mud.yahoo.com
DrEagle
Nov 28, 2012, 4:20:02 AM11/28/12
to
Hi Herman,
On 28.11.2012 05:56, Herman Swartz wrote:
> 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.
https://doukki.net/doku.php?id=wiki:tutoriels:uboot.howto#use_openocd
I'm not at home, if you need a preconfigured configuration file or more
information on how to use, feel free to ask, I will update the wiki
page. ;-)
Gérald
Archive: http://lists.debian.org/88ca2fbd283134b7...@gk2.net
On 28.11.2012 05:56, Herman Swartz wrote:
> 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.
I'm not at home, if you need a preconfigured configuration file or more
information on how to use, feel free to ask, I will update the wiki
page. ;-)
Gérald
Clint Adams
Nov 28, 2012, 10:30:03 AM11/28/12
to
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
> 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/interface/sheevaplug.cfg
are in the Debian openocd package.
Note that I have encountered two different varieties of SheevaPlug in
the wild, and had to use a modified config for one of them.
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
DrEagle
Nov 29, 2012, 3:00:01 AM11/29/12
to
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/interface/sheevaplug.cfg
>
> are in the Debian openocd package.
>
> Note that I have encountered two different varieties of SheevaPlug in
> the wild, and had to use a modified config for one of them.
Sometime, if the flash do not work, I have tested that changing
> 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 Debian openocd package.
>
> Note that I have encountered two different varieties of SheevaPlug in
> the wild, and had to use a modified config for one of them.
"-work-area-phys 0x10000000 \" to "-work-area-phys 0x100000 \" can help
to resolve the flash.
Sometime, it may also be needed to quickly reset while openocd is
launched :
1. reset / switch on the plug
2. enter the openocd command to flash
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Herman Swartz
Nov 29, 2012, 8:00:02 AM11/29/12
to
Here is the results of running the openocd command on another Debian box. The USB cable connects to this box and the mini USB end of the cable connects to the PLUG.
I can find a lot of hits on this message but no explanations.
openocd -f /usr/share/openocd/scripts/board/sheevaplug.cfg
Open On-Chip Debugger 0.3.1 (2009-11-25-12:22)
$URL$
For bug reports, read
http://openocd.berlios.de/doc/doxygen/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'
Segmentation fault
----- Original Message -----
From: DrEagle <dre...@doukki.net>
Archive: http://lists.debian.org/1354193503.319...@web39306.mail.mud.yahoo.com
DrEagle
Nov 29, 2012, 9:40:03 AM11/29/12
to
Have you verified and configured your USB/JTAG driver ?
You may need to modify
/usr/share/openocd/scripts/interface/sheevaplug.cfg according to what
lsusb shows for your sheevaplug.
Do you have ftdi_sio driver loaded ?
Archive: http://lists.debian.org/fe8ee42e6e57c5ec...@gk2.net
You may need to modify
/usr/share/openocd/scripts/interface/sheevaplug.cfg according to what
lsusb shows for your sheevaplug.
Do you have ftdi_sio driver loaded ?
Dimax
Nov 29, 2012, 2:40:02 PM11/29/12
to
I have unbricked SheevaPlug on Windows XP machine.
If you are interested I can help.
Archive: http://lists.debian.org/CAF9kqNGtG0o1bk4-+F35Ug-4...@mail.gmail.com
If you are interested I can help.
Herman Swartz
Nov 29, 2012, 4:10:02 PM11/29/12
to
Either way would be fine. An OCD will need to be installed on my Windows XP machine to.
I have the FTDI USB driver for Windows installed and used it to configure the PLUG when the Sheeva Uboot was installed. I moved to the open source, DENX, uboot using Martin Michmayer's article located at http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade.html at the time there was a problem with the USB hard drive booting Debian OS. After upgrading to DENX uboot I have an issue reaching the PLUG through the console port from the Windows box. While watching the Windows device manager screen the virtual com port comes and goes in the port display.
Hope what I have described above all makes sense. :-)
Archive: http://lists.debian.org/1354222802.904...@web39301.mail.mud.yahoo.com
Dimax
Nov 30, 2012, 5:40:02 AM11/30/12
to
HI,
Here are the notes I left for myself a few time ago.
I.I. (Just in Case) How to Un-brick SheevaPlug
----------------------------------------------
1. Download and extract 'sheevaplug-installer-v1.0'
2. Install OpenOCD-0.2.0 (Only this version works with installer)
3. Replace content of the
sheevaplug-installer-v1.0/uboot/openocd
with
OpenOCD/0.2.0/bin/*
4. Connect USB and run
sheevaplug-installer-v1.0> ./runme.exe nand
The big picture is here:
http://plugcomputer.org/plugforum/index.php?topic=3680.0
Archive: http://lists.debian.org/CAF9kqNH9SLHpBeAGnvBTf4DW...@mail.gmail.com
Here are the notes I left for myself a few time ago.
I.I. (Just in Case) How to Un-brick SheevaPlug
----------------------------------------------
1. Download and extract 'sheevaplug-installer-v1.0'
2. Install OpenOCD-0.2.0 (Only this version works with installer)
3. Replace content of the
sheevaplug-installer-v1.0/uboot/openocd
with
OpenOCD/0.2.0/bin/*
4. Connect USB and run
sheevaplug-installer-v1.0> ./runme.exe nand
The big picture is here:
http://plugcomputer.org/plugforum/index.php?topic=3680.0
Herman Swartz
Dec 3, 2012, 10:10:03 AM12/3/12
to
No, I do not. Have been searching for a package for the USB/JTAG driver. I have been searching for the driver. Plethora of hits to wade through to find a fit.
No, ftdi_sio driver not loaded.
The Windows driver that came with the Sheeva Devel Kit did work until I upgraded the Uboot to a generic open source version. After the upgrade serial port access worked at times but after a few hours stopped working all together.
I have a PC with Debian Squeeze and a Raspberry Pi with latest version of Rasperian. Trying to use openocd to unbrick the PLUG if I could only get the proper FTDI driver 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.
Archive: http://lists.debian.org/1354547097.969...@web39301.mail.mud.yahoo.com
DrEagle
Dec 3, 2012, 1:30:01 PM12/3/12
to
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 searching for the driver. Plethora of hits to wade through to find a fit.
You need libftdi1 from debian repositories :
# sudo apt-get install libftdi1
Make a lsusb after pluggin and power up the sheevaplug to get the correct USB device information for your JTAG :
# lsusb
Bus 001 Device 008: ID 9e88:9e8f
Verify driver status :
# dmesg
[22605.988095] usb 1-6.4: new full-speed USB device number 8 using ehci_hcd
[22606.086953] usb 1-6.4: New USB device found, idVendor=9e88, idProduct=9e8f
[22606.086957] usb 1-6.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[22606.086960] usb 1-6.4: Product: SheevaPlug JTAGKey FT2232D B
[22606.086962] usb 1-6.4: Manufacturer: FTDI
[22606.086964] usb 1-6.4: SerialNumber: FTSY7LXO
[22606.116910] usbcore: registered new interface driver usbserial
[22606.116925] USB Serial support registered for generic
[22606.116971] usbcore: registered new interface driver usbserial_generic
[22606.116973] usbserial: USB Serial Driver core
[22606.119212] USB Serial support registered for FTDI USB Serial Device
[22606.119342] usb 1-6.4: Ignoring serial port reserved for JTAG
[22606.119376] ftdi_sio 1-6.4:1.1: FTDI USB Serial Device converter detected
[22606.119423] usb 1-6.4: Detected FT2232C
[22606.119425] usb 1-6.4: Number of endpoints 2
[22606.119428] usb 1-6.4: Endpoint 1 MaxPacketSize 64
[22606.119430] usb 1-6.4: Endpoint 2 MaxPacketSize 64
[22606.119432] usb 1-6.4: Setting MaxPacketSize 64
[22606.119806] usb 1-6.4: FTDI USB Serial Device converter now attached to ttyUSB0
[22606.119832] usbcore: registered new interface driver ftdi_sio
[22606.119834] ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver
Then modify your /usr/share/openocd/scripts/interface/sheevaplug.cfg
#
# Marvel SheevaPlug Development Kit
#
# http://www.marvell.com/products/embedded_processors/developer/kirkwood/sheevaplug.jsp
#
interface ft2232
ft2232_layout sheevaplug
ft2232_vid_pid 0x9e88 0x9e8f
ft2232_device_desc "SheevaPlug JTAGKey FT2232D B"
adapter_khz 2000
You can now communicate with your sheevaplug by JTAG with 2 terminals :
- In the first terminal launch openocd JTAG debugger with :
# sudo openocd -s /usr/share/openocd/scripts/ -f interface/sheevaplug.cfg -f board/sheevaplug.cfg -c init
Open On-Chip Debugger 0.5.0 (2011-08-09-08:45)
Licensed under GNU GPL v2
Info : only one transport option; autoselect 'jtag'
2000 kHz
Warn : Interface already configured, ignoring
Error: already specified ft2232_layout sheevaplug
Info : clock speed 2000 kHz
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
Info : Embedded ICE version 0
Info : feroceon.cpu: hardware has 1 breakpoint/watchpoint unit
Then in a secondary terminal you can communicate with :
# telnet localhost 4444
First terminal will show :
Info : accepting 'telnet' connection from 4444
And the second (telnet) one will give you a prompt :
Trying ::1...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Open On-Chip Debugger
>
The must is that you can open a *third* terminal with cu to communicate directly with the sheevaplug :
# cu -s 115200 -l /dev/ttyUSB0
Connected.
Try to follow me :
#1 DEBBUGER
#2 JTAG COMMANDS
#3 SHEEVAPLUG TERMINAL ACCESS
just make a reset on the #2 to verify all works fine :
> reset
JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
>
#1 will show the command received :
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
The last terminal (#3) will go through a reset (like with the switch) and make a power boot up cycle :
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** MARVELL BOARD: SHEEVA PLUG LE
U-Boot 1.1.4 (Dec 27 2009 - 22:03:21) Marvell version: 3.4.27
U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CFEE0
Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz
DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 256MB
DRAM CS[1] base 0x10000000 size 256MB
DRAM Total size 512MB 16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB
Flash: 0 kB
CPU : Marvell Feroceon (Rev 1)
Streaming disabled
Write allocate disabled
USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0 [PRIME]
Hit any key to stop autoboot: 0
Marvell>>
Intterupt by a keypress on the #3...
Then hack your sheevaplug.
If you need a complete uboot reset by jtag with openocd, copy your uboot.kwb into a folder from where you execute the sessions renaming it into uboot.bin.
Execute a flash with command into #2 :
> init
> sheevaplug_reflash_uboot
when it is finished make a reset
> reset
If you only want to load the uboot without flashing it copy uboot.elf in the sessions folder.
The same as for flashing but with another command :
> init
> sheevaplug_load_uboot
when it is finished it start the new loaded uboot.
> No, ftdi_sio driver not loaded.
>
> The Windows driver that came with the Sheeva Devel Kit did work until I upgraded the Uboot to a generic open source version. After the upgrade serial port access worked at times but after a few hours stopped working all together.
From windows and I have no idea and never tried the procedure...
> I have a PC with Debian Squeeze and a Raspberry Pi with latest version of Rasperian. Trying to use openocd to unbrick the PLUG if I could only get the proper FTDI driver loaded and the USB support for it.
You can also get a VBox with a Debian installation from you windows.
The USB can be attached from 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 !
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 searching for the driver. Plethora of hits to wade through to find a fit.
# sudo apt-get install libftdi1
Make a lsusb after pluggin and power up the sheevaplug to get the correct USB device information for your JTAG :
# lsusb
Bus 001 Device 008: ID 9e88:9e8f
Verify driver status :
# dmesg
[22605.988095] usb 1-6.4: new full-speed USB device number 8 using ehci_hcd
[22606.086953] usb 1-6.4: New USB device found, idVendor=9e88, idProduct=9e8f
[22606.086957] usb 1-6.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[22606.086960] usb 1-6.4: Product: SheevaPlug JTAGKey FT2232D B
[22606.086962] usb 1-6.4: Manufacturer: FTDI
[22606.086964] usb 1-6.4: SerialNumber: FTSY7LXO
[22606.116910] usbcore: registered new interface driver usbserial
[22606.116925] USB Serial support registered for generic
[22606.116971] usbcore: registered new interface driver usbserial_generic
[22606.116973] usbserial: USB Serial Driver core
[22606.119212] USB Serial support registered for FTDI USB Serial Device
[22606.119342] usb 1-6.4: Ignoring serial port reserved for JTAG
[22606.119376] ftdi_sio 1-6.4:1.1: FTDI USB Serial Device converter detected
[22606.119423] usb 1-6.4: Detected FT2232C
[22606.119425] usb 1-6.4: Number of endpoints 2
[22606.119428] usb 1-6.4: Endpoint 1 MaxPacketSize 64
[22606.119430] usb 1-6.4: Endpoint 2 MaxPacketSize 64
[22606.119432] usb 1-6.4: Setting MaxPacketSize 64
[22606.119806] usb 1-6.4: FTDI USB Serial Device converter now attached to ttyUSB0
[22606.119832] usbcore: registered new interface driver ftdi_sio
[22606.119834] ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver
Then modify your /usr/share/openocd/scripts/interface/sheevaplug.cfg
#
# Marvel SheevaPlug Development Kit
#
# http://www.marvell.com/products/embedded_processors/developer/kirkwood/sheevaplug.jsp
#
interface ft2232
ft2232_layout sheevaplug
ft2232_vid_pid 0x9e88 0x9e8f
ft2232_device_desc "SheevaPlug JTAGKey FT2232D B"
adapter_khz 2000
You can now communicate with your sheevaplug by JTAG with 2 terminals :
- In the first terminal launch openocd JTAG debugger with :
# sudo openocd -s /usr/share/openocd/scripts/ -f interface/sheevaplug.cfg -f board/sheevaplug.cfg -c init
Open On-Chip Debugger 0.5.0 (2011-08-09-08:45)
Licensed under GNU GPL v2
Info : only one transport option; autoselect 'jtag'
2000 kHz
Warn : Interface already configured, ignoring
Error: already specified ft2232_layout sheevaplug
2000 kHz
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
adapter_nsrst_delay: 200
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
jtag_ntrst_delay: 200
dcc downloads are enabled
Warn : use 'feroceon.cpu' as target identifier, not '0'
sheevaplug_load_uboot
dcc downloads are enabled
Warn : use 'feroceon.cpu' as target identifier, not '0'
Info : clock speed 2000 kHz
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
Info : Embedded ICE version 0
Info : feroceon.cpu: hardware has 1 breakpoint/watchpoint unit
Then in a secondary terminal you can communicate with :
# telnet localhost 4444
First terminal will show :
Info : accepting 'telnet' connection from 4444
And the second (telnet) one will give you a prompt :
Trying ::1...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Open On-Chip Debugger
>
The must is that you can open a *third* terminal with cu to communicate directly with the sheevaplug :
# cu -s 115200 -l /dev/ttyUSB0
Connected.
Try to follow me :
#1 DEBBUGER
#2 JTAG COMMANDS
#3 SHEEVAPLUG TERMINAL ACCESS
just make a reset on the #2 to verify all works fine :
> reset
JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
>
#1 will show the command received :
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
The last terminal (#3) will go through a reset (like with the switch) and make a power boot up cycle :
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** MARVELL BOARD: SHEEVA PLUG LE
U-Boot 1.1.4 (Dec 27 2009 - 22:03:21) Marvell version: 3.4.27
U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CFEE0
Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz
DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 256MB
DRAM CS[1] base 0x10000000 size 256MB
DRAM Total size 512MB 16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB
Flash: 0 kB
CPU : Marvell Feroceon (Rev 1)
Streaming disabled
Write allocate disabled
USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0 [PRIME]
Hit any key to stop autoboot: 0
Marvell>>
Intterupt by a keypress on the #3...
Then hack your sheevaplug.
If you need a complete uboot reset by jtag with openocd, copy your uboot.kwb into a folder from where you execute the sessions renaming it into uboot.bin.
Execute a flash with command into #2 :
> init
> sheevaplug_reflash_uboot
when it is finished make a reset
> reset
If you only want to load the uboot without flashing it copy uboot.elf in the sessions folder.
The same as for flashing but with another command :
> init
> sheevaplug_load_uboot
when it is finished it start the new loaded uboot.
> No, ftdi_sio driver not loaded.
>
> The Windows driver that came with the Sheeva Devel Kit did work until I upgraded the Uboot to a generic open source version. After the upgrade serial port access worked at times but after a few hours stopped working all together.
> I have a PC with Debian Squeeze and a Raspberry Pi with latest version of Rasperian. Trying to use openocd to unbrick the PLUG if I could only get the proper FTDI driver loaded and the USB support for it.
The USB can be attached from 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.
Herman Swartz
Dec 4, 2012, 12:10:02 AM12/4/12
to
DrEagle
Your posting is very busy.
Your posting is very busy.
you show a dmesg output showing the boot up log for the host having a USB connection to the Sheeva PLUG, is that correct? Nothing like the output you show in your example can be seen on the console host.
Are you expecting the dmesg output to show a USB port 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 <dre...@doukki.net>
To: Herman Swartz <herman...@yahoo.com>
Cc: "debia...@lists.debian.org" <debia...@lists.debian.org>
Sent: Monday, December 3, 2012 1:19 PM
Subject: Re: Bricked Sheevaplug
Archive: http://lists.debian.org/1354597492.303...@web39306.mail.mud.yahoo.com
Herman Swartz
Dec 5, 2012, 5:10:02 PM12/5/12
to
I did following command,
modprobe ftdi_sio vendor=0x9e88 product=ox9e8f
modprobe ftdi_sio vendor=0x9e88 product=ox9e8f
Then
lsmod |grep -A2 ftdi_sio
Result
ftdi_sio 28991 0
usbserial 22100 1 ftdi_sio
usbcore 99426 6 ftdi_sio,usbserial,usb_storge,uhci_hed,ehci_hcd
Then
lsusb
Result
Nothing
Then
ls /dev/ttyUSB*
Result
Nothing
----- Original Message -----
From: DrEagle <dre...@doukki.net>
To: Herman Swartz <herman...@yahoo.com>
Cc: "debia...@lists.debian.org" <debia...@lists.debian.org>
Sent: Monday, December 3, 2012 1:19 PM
Subject: Re: Bricked Sheevaplug
Archive: http://lists.debian.org/1354744775.662...@web39302.mail.mud.yahoo.com
Herman Swartz
Dec 5, 2012, 11:20:01 PM12/5/12
to
Did the same commands as listed in previous email, this time from a Raspberry PI running Debian.
The modules in this version of openocd on the RPI must be improved. Instead of a segment fault result running openocd from a Dell laptop with Debian Squeeze this run came back with a more appropriate message.
I am wondering if the replacement of the small Alkaline button battery (the old one was leaking) has anything to do with the problems experienced with even seeing the JTAG port on the SheevaPlug???
root@raspberrypi:/home/pi# openocd -s /usr/share/openocd/scripts/ -f interface/sheevaplug.cfg -f board/sheevaplug.cfg -c init
Open On-Chip Debugger 0.5.0 (2012-05-23-17:50)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
2000 kHz
Warn : Interface already configured, ignoring
Error: already specified ft2232_layout sheevaplug
2000 kHz
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
adapter_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Warn : use 'feroceon.cpu' as target identifier, not '0'
sheevaplug_load_uboot
Error: unable to open ftdi device: device not found
in procedure 'init'
----- Original Message -----
From: DrEagle <dre...@doukki.net>
To: Herman Swartz <herman...@yahoo.com>
Cc: "debia...@lists.debian.org" <debia...@lists.debian.org>
Sent: Monday, December 3, 2012 1:19 PM
Subject: Re: Bricked Sheevaplug
Archive: http://lists.debian.org/1354767458.725...@web39302.mail.mud.yahoo.com
DrEagle
Dec 6, 2012, 1:30:02 AM12/6/12
to
Hi,
Please try to no TOFU, the messages comes more and more un-readable.
I know that some buggy product do not allow it, but if you can, avoid top posting.
Le 05/12/2012 22:59, Herman Swartz a écrit :
> I did following command,
> modprobe ftdi_sio vendor=0x9e88 product=ox9e8f
try just
# modprobe ftdi_sio
instead
Mine works just by pluggin, may be your udev rules are incorrect.
> Then
> lsmod |grep -A2 ftdi_sio
> Result
> ftdi_sio 28991 0
> usbserial 22100 1 ftdi_sio
> usbcore 99426 6 ftdi_sio,usbserial,usb_storge,uhci_hed,ehci_hcd
my wheezy box show
ftdi_sio 38270 0
usbserial 32061 1 ftdi_sio
usbcore 128498 9 ehci_hcd,uhci_hcd,uas,usb_storage,usbhid,usbserial,ftdi_sio
> Then
> lsusb
> Result
> Nothing
You mean notinh about jtag or nothing at all ?
Mine is correct
Bus 001 Device 006: ID 9e88:9e8f
> Then
> ls /dev/ttyUSB*
> Result
> Nothing
# ls /dev/ttyUSB* -l
crw-rw---T 1 root dialout 188, 0 déc. 6 07:10 /dev/ttyUSB0
You ma try to :
add you user to the dialout group
verify openoce rules (/lib/udev/rules.d/60-openocd.rules)
---%<---
# Marvell Sheevaplug
ATTRS{idVendor}=="9e88", ATTRS{idProduct}=="9e8f", MODE="664", GROUP="plugdev"
---%<---
Must be present !
Please try to no TOFU, the messages comes more and more un-readable.
I know that some buggy product do not allow it, but if you can, avoid top posting.
Le 05/12/2012 22:59, Herman Swartz a écrit :
> I did following command,
> modprobe ftdi_sio vendor=0x9e88 product=ox9e8f
# modprobe ftdi_sio
instead
Mine works just by pluggin, may be your udev rules are incorrect.
> Then
> lsmod |grep -A2 ftdi_sio
> Result
> ftdi_sio 28991 0
> usbserial 22100 1 ftdi_sio
> usbcore 99426 6 ftdi_sio,usbserial,usb_storge,uhci_hed,ehci_hcd
ftdi_sio 38270 0
usbserial 32061 1 ftdi_sio
usbcore 128498 9 ehci_hcd,uhci_hcd,uas,usb_storage,usbhid,usbserial,ftdi_sio
> Then
> lsusb
> Result
> Nothing
You mean notinh about jtag or nothing at all ?
Mine is correct
Bus 001 Device 006: ID 9e88:9e8f
> Then
> ls /dev/ttyUSB*
> Result
> Nothing
crw-rw---T 1 root dialout 188, 0 déc. 6 07:10 /dev/ttyUSB0
You ma try to :
add you user to the dialout group
verify openoce rules (/lib/udev/rules.d/60-openocd.rules)
---%<---
# Marvell Sheevaplug
ATTRS{idVendor}=="9e88", ATTRS{idProduct}=="9e8f", MODE="664", GROUP="plugdev"
---%<---
Must be present !
Herman Swartz
Dec 6, 2012, 6:50:02 AM12/6/12
to
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 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
You ma try to :
add you user to the dialout group
Herman: Using as root
verify openoce rules (/lib/udev/rules.d/60-openocd.rules)
---%<---
# Marvell Sheevaplug
ATTRS{idVendor}=="9e88", ATTRS{idProduct}=="9e8f", MODE="664", GROUP="plugdev"
---%<---
Must be present !
Herman: Verified this line is in openocd rules.
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/1354794154.631...@web39306.mail.mud.yahoo.com
0 new messages