Testing u-boot targets for buster!

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Testing u-boot targets for buster!

Vagrant Cascadian-4
Hello fine u-boot testers. You were one of the gracious people who
offered to test one or more u-boot targets from the debian
packages. Thanks!

  https://salsa.debian.org/debian/u-boot/blob/master/debian/targets

Since we're in the process of freezing Buster, at the very least I would
like to get positive confirmation that each platform is still
working. Please test your boards and update:

  https://wiki.debian.org/U-boot/Status

There have been a variety of regressions in u-boot versions over time,
and I would really hate to release Buster for any platform with a broken
u-boot.

I've tested a few myself, but I can't possibly test them all.

If you're unable to continue to test a particular platform in the
future, please let me know that as well, and I'll update the file
accordingly.


live well,
  vagrant

signature.asc (233 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Testing u-boot targets for buster!

Leigh Brown
Hello Vagrant,

On 2019-02-20 18:25, Vagrant Cascadian wrote:

> Hello fine u-boot testers. You were one of the gracious people who
> offered to test one or more u-boot targets from the debian
> packages. Thanks!
>
>   https://salsa.debian.org/debian/u-boot/blob/master/debian/targets
>
> Since we're in the process of freezing Buster, at the very least I
> would
> like to get positive confirmation that each platform is still
> working. Please test your boards and update:
>
>   https://wiki.debian.org/U-boot/Status
>
> There have been a variety of regressions in u-boot versions over time,
> and I would really hate to release Buster for any platform with a
> broken
> u-boot.
>
> I've tested a few myself, but I can't possibly test them all.
>
> If you're unable to continue to test a particular platform in the
> future, please let me know that as well, and I'll update the file
> accordingly.
>
>
> live well,
>   vagrant

I tested u-boot 2019.01+dfsg-1 on my Globalscale Dreamplug and it
doesn't work:

U-Boot 2019.01+dfsg-1 (Jan 15 2019 - 00:36:19 +0000)
Marvell-DreamPlug

SoC:   Kirkwood 88F6281_A1
DRAM:  512 MiB
Loading Environment from SPI Flash... Invalid bus 0 (err=-19)
*** Warning - spi_flash_probe_bus_cs() failed, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Error: egiga0 address not set.
, egiga1
Error: egiga1 address not set.

88E1116 Initialized on egiga0
88E1116 Initialized on egiga1
IDE:   ide_preinit failed
Hit any key to stop autoboot:  0
=> usb start
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008c80
EHCI timed out on TD - token=0x80008c80
EHCI timed out on TD - token=0x80008c80
  ERROR: NOT USB_CONFIG_DESC a3
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008c80
EHCI timed out on TD - token=0x80008c80
2 USB Device(s) found
        scanning usb for storage devices... 0 Storage Device(s) found

So it cannot detect USB or SPI Flash.

Regards,

Leigh.

Reply | Threaded
Open this post in threaded view
|

Dreamplug fails to detect SPI and USB

Vagrant Cascadian-4
On 2019-02-26, Leigh Brown wrote:

> I tested u-boot 2019.01+dfsg-1 on my Globalscale Dreamplug and it
> doesn't work:
>
> U-Boot 2019.01+dfsg-1 (Jan 15 2019 - 00:36:19 +0000)
> Marvell-DreamPlug
>
> SoC:   Kirkwood 88F6281_A1
> DRAM:  512 MiB
> Loading Environment from SPI Flash... Invalid bus 0 (err=-19)
> *** Warning - spi_flash_probe_bus_cs() failed, using default environment
>
> In:    serial
> Out:   serial
> Err:   serial
> Net:   egiga0
> Error: egiga0 address not set.
> , egiga1
> Error: egiga1 address not set.
>
> 88E1116 Initialized on egiga0
> 88E1116 Initialized on egiga1
> IDE:   ide_preinit failed
> Hit any key to stop autoboot:  0
> => usb start
> starting USB...
> USB0:   USB EHCI 1.00
> scanning bus 0 for devices... EHCI timed out on TD - token=0x80008d80
> EHCI timed out on TD - token=0x80008c80
> EHCI timed out on TD - token=0x80008c80
> EHCI timed out on TD - token=0x80008c80
>   ERROR: NOT USB_CONFIG_DESC a3
> EHCI timed out on TD - token=0x80008d80
> EHCI timed out on TD - token=0x80008c80
> EHCI timed out on TD - token=0x80008c80
> 2 USB Device(s) found
>         scanning usb for storage devices... 0 Storage Device(s) found
>
> So it cannot detect USB or SPI Flash.
I don't think Debian carries any particular patches that would affect
the dreamplug target and I'm not seeing any obvious changes in
upstream's master branch since v2019.01.

It would be good to find out the last known working version, if
possible:

  https://snapshot.debian.org/package/u-boot/


Please file a bug in the Debian bug tracker so I can keep track of this
issue in Debian:

  https://www.debian.org/Bugs/Reporting


live well,
  vagrant

signature.asc (233 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Testing u-boot targets for buster!

Leigh Brown
In reply to this post by Leigh Brown
Hello,

FYI I have installed u-boot 2019.01+dfsg-3 on my Dreamplug running
Buster, and all is now well.

U-Boot 2019.01+dfsg-3 (Mar 01 2019 - 04:42:31 +0000)
Marvell-DreamPlug

SoC:   Kirkwood 88F6281_A1
DRAM:  512 MiB
Loading Environment from SPI Flash... SF: Detected mx25l1605d with page
size 256 Bytes, erase size 64 KiB, total 2 MiB
OK
In:    serial
Out:   serial
Err:   serial
Net:   egiga0, egiga1
88E1116 Initialized on egiga0
88E1116 Initialized on egiga1
IDE:   ide_preinit failed
Hit any key to stop autoboot:  0
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 4 USB Device(s) found
        scanning usb for storage devices... Device NOT ready
    Request Sense returned 02 3A 00
1 Storage Device(s) found
2038528 bytes read in 115 ms (16.9 MiB/s)
9949 bytes read in 27 ms (359.4 KiB/s)
4015832 bytes read in 211 ms (18.2 MiB/s)
## Booting kernel from Legacy Image at 06000000 ...
    Image Name:   uImage-4.19.0-2-marvell
    Created:      2019-02-26  14:27:36 UTC
    Image Type:   ARM Linux Kernel Image (uncompressed)
    Data Size:    2038464 Bytes = 1.9 MiB
    Load Address: 00008000
    Entry Point:  00008000
    Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 06600000 ...
    Image Name:   uInitrd-4.19.0-2-marvell
    Created:      2019-02-26  14:28:44 UTC
    Image Type:   ARM Linux RAMDisk Image (uncompressed)
    Data Size:    4015768 Bytes = 3.8 MiB
    Load Address: 00000000
    Entry Point:  00000000
    Verifying Checksum ... OK
## Flattened Device Tree blob at 06400000
    Booting using the fdt blob at 0x6400000
    Loading Kernel Image ... OK
    Loading Ramdisk to 0fc2b000, end 0ffff698 ... OK
    Loading Device Tree to 0fc25000, end 0fc2a6dc ... OK

Starting kernel ...

[    0.011113] [Firmware Info]:
/ocp@f1000000/ethernet-controller@72000/ethernet0-port@0:
local-mac-address is not set
[    0.011214] [Firmware Info]:
/ocp@f1000000/ethernet-controller@76000/ethernet1-port@0:
local-mac-address is not set
[    4.734090] sd 0:0:0:0: [sda] No Caching mode page found
[    4.739468] sd 0:0:0:0: [sda] Assuming drive cache: write through
dproot: clean, 42790/241920 files, 317370/967168 blocks
INIT: version 2.93 booting
[info] Using makefile-style concurrent boot in runlevel S.
[ ok ] Starting hotplug events dispatcher: systemd-udevd.
[ ok ] Synthesizing the initial hotplug events (subsystems)...done.
[ ok ] Synthesizing the initial hotplug events (devices)...done.
[ ok ] Waiting for /dev to be fully populated...done.
[ ok ] Activating swap...done.
[....] Checking file systems...fsck from util-linux 2.33.1
done.
[ ok ] Cleaning up temporary files... /tmp.
[ ok ] Mounting local filesystems...done.
[ ok ] Activating swapfile swap...done.
[ ok ] Cleaning up temporary files....
[ ok ] Starting Setting kernel variables: sysctl.
[ ok ] Configuring network interfaces...done.
[ ok ] Cleaning up temporary files....
INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
[....] Starting busybox' syslogd implementation : syslogdStarting
/sbin/syslogd...
1146 (syslogd)
. ok
[....] Starting busybox' klogd implementation : klogdStarting
/sbin/klogd...
1174 (klogd)
. ok
[ ok ] Starting periodic command scheduler: cron.
[ ok ] Starting system message bus: dbus.
[ ok ] Starting bluetooth: bluetoothd.
Starting Dropbear SSH server: dropbear.
[ ok ] Starting NTP server: ntpd.
Starting very small Busybox based DHCP server: Starting
/usr/sbin/udhcpd...
udhcpd.

Debian GNU/Linux buster/sid iron ttyS0

iron login: