Bug#934974: u-boot: usb start fails on sheevaplug in u-boot 2019.01
I have a sheevaplug that has been on the shelf for a couple years because it appeared to be bricked. I decided to try to unbrick it to see if I could help with these tests. Unfortunately when I plug it in and connect it to a PC running Debian Buster with the micro-USB cable, there is no device /dev/ttyUSB* . I've tried the same thing with an OpenRD box and the device appears as expected then. If I ignore that problem and try to connect with opencd, I get the following error messages: $ openocd -f /usr/share/openocd/scripts/board/sheevaplug.cfg -s /usr/share/openocd/scripts Open On-Chip Debugger 0.10.0 Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select '. trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst adapter_nsrst_delay: 200 jtag_ntrst_delay: 200 adapter speed: 2000 kHz dcc downloads are enabled Warn : use 'feroceon.cpu' as target identifier, not '0' sheevaplug_load_uboot Error: no device found Error: unable to open ftdi device with vid 9e88, pid 9e8f, description 'SheevaPlug JTAGKey FT2232D B', serial '*' at bus location '*' Can anybody help me figure out what to do next? Thanks! Rick > On Sep 5, 2019, at 10:58 AM, Jan Hahne wrote: > > I was able to unbrick mine with these instructions: > https://www.newit.co.uk/forum/index.php/topic,2835.0.html > https://tadeubento.com/2018/sheevaplug-2018-unbrick/ >
Bug#934974: u-boot: usb start fails on sheevaplug in u-boot 2019.01
Am Do., 5. Sept. 2019 um 18:20 Uhr schrieb Vagrant Cascadian < vagr...@debian.org>: > Any chance people could also test the 2019.07 packages in experimental? > I can also try to prepare some 2019.10~rc+ packages which I hope to > upload soon. Thanks for helping test! > > I installed U-Boot 2019.07+dfsg-1 from https://packages.debian.org/experimental/u-boot on my SheevaPlug and the installed Debian still boots. `version` prints: U-Boot 2019.07+dfsg-1 (Jul 08 2019 - 23:41:40 +) Marvell-Sheevaplug The USB stick was detected correctly, `fatls` could access it. So in my opinion, 2019.07 works fine! Bye, Flo
Bug#934974: u-boot: usb start fails on sheevaplug in u-boot 2019.01
Thanks for your tips, now I have a working Debian Buster on my SheevaPlug! https://tadeubento.com/2018/sheevaplug-2018-unbrick/ and OpenOCD helped me out starting the original u-boot and then installing the u-boot version of Debian Stretch as Michael suggested and updated in his docs. I even got this working under macOS, but I had to edit /share/openocd/scripts/interface/ftdi/sheevaplug.cfg: [...] interface ftdi # ftdi_device_desc "SheevaPlug JTAGKey FT2232D B" # ftdi_vid_pid 0x9e88 0x9e8f ftdi_vid_pid 0x0403 0x6010 # ftdi_channel 1 ftdi_channel 0 […] Thanks again for your qualified and fast responses! Florian
Bug#934974: u-boot: usb start fails on sheevaplug in u-boot 2019.01
Am 05.09.2019 um 18:20 schrieb Vagrant Cascadian: On 2019-09-04, Martin Michlmayr wrote: * Jan Hahne [2019-08-17 16:27]: But the command "usb start" gave me these errors: EHCI timed out on TD - token=0x80008d80 EHCI timed out on TD - token=0x80008c80 ERROR: NOT USB_CONFIG_DESC 8f 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found You mention USB problems. We just got a report that said that MMC and TFTP (network) didn't work either: https://lists.debian.org/debian-arm/2019/09/msg2.html Did you try those? If so, I assume those failed for you as well? Yes, I also tried TFTP and MMC. Same behaviour as described by Florian: TFTP and MMC fail. @Florian: I don't think that your SheevaPlug is bricked. I was able to unbrick mine with these instructions: https://www.newit.co.uk/forum/index.php/topic,2835.0.html https://tadeubento.com/2018/sheevaplug-2018-unbrick/ Then I followed the instructions by Martin Michlmayr http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/ to install an older U-Boot Version (2016.11). The timestamp of this U-Boot-binary was 2018/11/07. I downloaded it from an older version of Martin's page. I just saw that Martin already has updated his page so you can download an older working U-Boot from there - Thanks a lot, Martin! @Florian: Good look with the unbricking procedure. It is a bit cumbersome but worked for me. Greetings to all of you Jan Really unfortunate to hear that it's not working in a stable released version... Thanks for the report. There are no records of successful u-boot tests on sheevaplug on the status page: https://wiki.debian.org/U-boot/Status So I have no idea how long any of these features have been broken. I don't have either the hardware or time to test every "supported" board in Debian's u-boot packages. Any chance people could also test the 2019.07 packages in experimental? I can also try to prepare some 2019.10~rc+ packages which I hope to upload soon. Thanks for helping test! live well, vagrant
Bug#934974: u-boot: usb start fails on sheevaplug in u-boot 2019.01
On 2019-09-04, Martin Michlmayr wrote: > * Jan Hahne [2019-08-17 16:27]: >> But the command "usb start" gave me these errors: >> EHCI timed out on TD - token=0x80008d80 >> EHCI timed out on TD - token=0x80008c80 >> ERROR: NOT USB_CONFIG_DESC 8f >> 2 USB Device(s) found >> scanning usb for storage devices... 0 Storage Device(s) found > > You mention USB problems. We just got a report that said that > MMC and TFTP (network) didn't work either: > https://lists.debian.org/debian-arm/2019/09/msg2.html > > Did you try those? If so, I assume those failed for you as well? Really unfortunate to hear that it's not working in a stable released version... Thanks for the report. There are no records of successful u-boot tests on sheevaplug on the status page: https://wiki.debian.org/U-boot/Status So I have no idea how long any of these features have been broken. I don't have either the hardware or time to test every "supported" board in Debian's u-boot packages. Any chance people could also test the 2019.07 packages in experimental? I can also try to prepare some 2019.10~rc+ packages which I hope to upload soon. Thanks for helping test! live well, vagrant signature.asc Description: PGP signature
Bug#934974: u-boot: usb start fails on sheevaplug in u-boot 2019.01
* Jan Hahne [2019-08-17 16:27]: > But the command "usb start" gave me these errors: > EHCI timed out on TD - token=0x80008d80 > EHCI timed out on TD - token=0x80008c80 > ERROR: NOT USB_CONFIG_DESC 8f > 2 USB Device(s) found > scanning usb for storage devices... 0 Storage Device(s) found You mention USB problems. We just got a report that said that MMC and TFTP (network) didn't work either: https://lists.debian.org/debian-arm/2019/09/msg2.html Did you try those? If so, I assume those failed for you as well? -- Martin Michlmayr https://www.cyrius.com/
Bug#934974: u-boot: usb start fails on sheevaplug in u-boot 2019.01
Source: u-boot Version: 2019.01 Severity: important Dear Maintainer, I have a SheevaPlug (Original Version From NewIT). I installed u-boot (version 2019.01) as described here: http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/ After the installation I wanted to run the installer from an USB stick: http://www.cyrius.com/debian/kirkwood/sheevaplug/install/ But the command "usb start" gave me these errors: EHCI timed out on TD - token=0x80008d80 EHCI timed out on TD - token=0x80008c80 ERROR: NOT USB_CONFIG_DESC 8f 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found I was able to get the SheevaPlug working again using this guide: https://tadeubento.com/2018/sheevaplug-2018-unbrick/ I installed a previous u-boot version 2016.11. With this versíon everything was OK. I was able to run the actual Debian installer and the installation was successfull without any errors. So I think there is a bug in u-boot, version 2019.01 -- System Information: Debian Release: 10.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armel (armv5tel) Kernel: Linux 4.19.0-5-marvell Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
