[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bricked Sheevaplug



I have unbricked SheevaPlug on Windows XP machine.
If you are interested I can help.


On Thu, Nov 29, 2012 at 4:29 PM, DrEagle <dreagle@doukki.net> wrote:
> 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 ?
>
>
> On 29.11.2012 13:51, Herman Swartz wrote:
>>
>> 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 <dreagle@doukki.net>
>> 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:
>>>>
>>>> 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
>> "-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-arm-REQUEST@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact
>> listmaster@lists.debian.org
>> Archive: 339fde8d401a1ba7dac20946ab5e6995@gk2.net">http://lists.debian.org/339fde8d401a1ba7dac20946ab5e6995@gk2.net
>
>
>
> --
> To UNSUBSCRIBE, email to debian-arm-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
> Archive: fe8ee42e6e57c5ec6f8922041685bc27@gk2.net">http://lists.debian.org/fe8ee42e6e57c5ec6f8922041685bc27@gk2.net
>


Reply to: