Supported USB drives? - Marvell MACCHIATObin

This topic has 8 replies, 4 voices, and was last updated 4 years, 7 months ago by bb.

Viewing 9 posts - 1 through 9 (of 9 total)

Author

Posts

July 17, 2017 at 5:13 pm #415

Participant

Where can I find a list of supported USB 3.0 drives?

I have tried two Sandisk CZ48 128GB so far, and cannot get sane ext4ls output.

July 20, 2017 at 7:20 pm #417

nanasi

Participant

Insane output?

July 20, 2017 at 9:22 pm #418

Participant

If I mount the USB drive on another Linux machine I can see all the files. But, they do not show in the ext4ls on the Macchiatobin board:


Marvell>> usb reset
(Re)start USB...
USB0:   Register 2000120 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
       scanning usb for ethernet devices... 0 Ethernet Device(s) found
Marvell>> ext4ls usb 0:1 /
<DIR>       4096 .
<DIR>       4096 ..
<DIR>      16384 lost+found
<DIR>       4096 boot
<DIR>       4096 run
<DIR>       4096 sbin
<DIR>          0 tmp
<DIR>          0 media
<DIR>          0 root
<DIR>          0 home
<DIR>          0 dev
<DIR>          0 etc
<DIR>          0 bin
<DIR>          0 mnt
<DIR>          0 sys
<DIR>       4096 lib
<DIR>          0 opt
<DIR>       4096 proc
<DIR>          0 var
<DIR>          0 srv
<DIR>       4096 usr
Marvell>> ext4ls usb 0:1 /boot
<DIR>       4096 .
<DIR>       4096 ..
Marvell>>

Console output from initial power on:


Marvell>>
BootROM - 2.03
Starting CP-1 IOROM 1.07
Booting from SPI NOR flash 1 (0x32)
Found valid image at boot postion 0x000
lNOTICE:  Starting binary extension
NOTICE:  Gathering DRAM information
mv_ddr: mv_ddr-armada-17.02.0-g42da6da (Mar  9 2017 - 12:02:05)
mv_ddr: completed successfully
Booting Trusted Firmware
BL1: v1.2(release):armada-17.02.0:2017.02-218-g1558a93
BL1: Built : 12:02:06, Mar  9 2017
NOTICE:  BL1: Booting BL2
lNOTICE:  BL2: v1.2(release):armada-17.02.0:2017.02-218-g1558a93
NOTICE:  BL2: Built : 12:02:06, Mar  9 2017
NOTICE:  BL1: Booting BL31
lNOTICE:  BL31: v1.2(release):armada-17.02.0:2017.02-218-g1558a93
NOTICE:  BL31: Built : 12:02:06, Mar  9 2017
l

U-Boot 2015.01-armada-17.02.0 (Mar 09 2017 - 12:01:25)

I2C:   ready
DRAM:  3.8 GiB
Board: MACCHIATOBin-8040
Clock:  CPU     1300 [MHz]
        DDR     800  [MHz]
        FABRIC  800  [MHz]
        MSS     200  [MHz]
        DDR 64 Bit width
        LLC Enabled (Exclusive Mode)
Comphy chip #0:
Comphy-0: PEX0
Comphy-1: PEX0
Comphy-2: PEX0
Comphy-3: PEX0
Comphy-4: KR
Comphy-5: SATA1
Comphy chip #1:
Comphy-0: SGMII1        1.25 Gbps
Comphy-1: SATA0
Comphy-2: USB3_HOST0
Comphy-3: SATA1
Comphy-4: KR
Comphy-5: SGMII2        1.25 Gbps

ERROR: UTMI PHY port type is invalid

at drivers/phy/comphy_cp110.c:1498/comphy_dedicated_phys_init()

ERROR: UTMI PHY port type is invalid

at drivers/phy/comphy_cp110.c:1498/comphy_dedicated_phys_init()

ERROR: UTMI PHY port type is invalid

at drivers/phy/comphy_cp110.c:1498/comphy_dedicated_phys_init()
UTMI PHY 0 initialized to USB Host255
UTMI PHY 1 initialized to USB Host255
UTMI PHY 2 initialized to USB Host255
Now running in RAM - U-Boot at: 3ff0a000
U-Boot DT blob at : 000000003f9f4548
NAND:  0 MiB
MMC:   XENON-SDHCI: 0, XENON-SDHCI: 1
SF: Detected W25Q32BV with page size 256 Bytes, erase size 4 KiB, total 4 MiB
PCIE-0: Link down
SCSI:  SATA link 0 timeout.
SATA link 1 timeout.
AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
flags: 64bit ncq led only pmp fbss pio slum part sxs
SATA link 0 timeout.
SATA link 1 timeout.
AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
flags: 64bit ncq led only pmp fbss pio slum part sxs
Net:   Skipping disabled port egiga1
Skipping disabled port egiga2
egiga0 [PRIME], egiga1
Warning: egiga1 MAC addresses don't match:
Address in SROM is         00:00:00:00:51:81
Address in environment is  00:00:00:00:51:82
, egiga2, egiga3
Error: egiga3 address not set.

Hit any key to stop autoboot:  0

July 20, 2017 at 9:25 pm #419

Participant

Could this be a known issue for 17.02 version?

July 22, 2017 at 1:09 pm #420

nanasi

Participant

I have tested Sandisk SDCZ80-064G and Kingston DTHX30/64GB.
U-boot: https://wiki.solid-run.com/lib/exe/fetch.php?media=products:a8040:software:os:flash-image.bin.gz


BootROM - 2.03
Starting CP-0 IOROM 1.07
Booting from SD 0 (0x29)
Found valid image at boot postion 0x000
lNOTICE:  Starting binary extension
NOTICE:  Gathering DRAM information
mv_ddr: mv_ddr-armada-17.02.0-g42da6da (Mar  6 2017 - 21:24:03)
mv_ddr: completed successfully
Booting Trusted Firmware
BL1: v1.2(release):armada-17.02.0:2017.02-218-g1558a93
BL1: Built : 21:24:04, Mar  6 2017
NOTICE:  BL1: Booting BL2
lNOTICE:  BL2: v1.2(release):armada-17.02.0:2017.02-218-g1558a93
NOTICE:  BL2: Built : 21:24:04, Mar  6 2017
NOTICE:  BL1: Booting BL31
lNOTICE:  BL31: v1.2(release):armada-17.02.0:2017.02-218-g1558a93
NOTICE:  BL31: Built : 21:24:05, Mar  6 2017
l

U-Boot 2015.01-armada-17.02.0 (Mar 06 2017 - 21:17:26)

I2C:   ready
DRAM:  3.8 GiB
Board: MACCHIATOBin-8040
Clock:  CPU     2000 [MHz]
        DDR     1200 [MHz]
        FABRIC  1200 [MHz]
        MSS     200  [MHz]
        DDR 64 Bit width
        LLC Enabled (Exclusive Mode)
Comphy chip #0:
Comphy-0: PEX0
Comphy-1: PEX0
Comphy-2: PEX0
Comphy-3: PEX0
Comphy-4: KR
Comphy-5: SATA1
Comphy chip #1:
Comphy-0: SGMII1        1.25 Gbps
Comphy-1: SATA0
Comphy-2: USB3_HOST0
Comphy-3: SATA1
Comphy-4: KR
Comphy-5: SGMII2        1.25 Gbps

ERROR: UTMI PHY port type is invalid

at drivers/phy/comphy_cp110.c:1498/comphy_dedicated_phys_init()

ERROR: UTMI PHY port type is invalid

at drivers/phy/comphy_cp110.c:1498/comphy_dedicated_phys_init()

ERROR: UTMI PHY port type is invalid

at drivers/phy/comphy_cp110.c:1498/comphy_dedicated_phys_init()
UTMI PHY 0 initialized to USB Host255
UTMI PHY 1 initialized to USB Host255
UTMI PHY 2 initialized to USB Host255
Now running in RAM - U-Boot at: 3ff0a000
U-Boot DT blob at : 000000003f9f4548
NAND:  0 MiB
MMC:   XENON-SDHCI: 0, XENON-SDHCI: 1
PCIE-0: Link up (Gen2-x1, Bus0)
SCSI:  SATA link 0 timeout.
SATA link 1 timeout.
AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
flags: 64bit ncq led only pmp fbss pio slum part sxs
SATA link 0 timeout.
SATA link 1 timeout.
AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
flags: 64bit ncq led only pmp fbss pio slum part sxs
Net:   Skipping disabled port egiga1
Skipping disabled port egiga2
egiga0, egiga1
Warning: egiga1 MAC addresses don't match:
Address in SROM is         00:00:00:00:51:81
Address in environment is  00:00:00:00:51:82
, egiga2 [PRIME], egiga3
Error: egiga3 address not set.

Hit any key to stop autoboot:  0
Marvell>>
Marvell>> version

U-Boot 2015.01-armada-17.02.0 (Mar 06 2017 - 21:17:26)
aarch64-buildroot-linux-gnu-gcc.br_real (Buildroot 2017.05-git-00218-g1558a93) 5.4.0
GNU ld (GNU Binutils) 2.26.1

Marvell>> usb start
(Re)start USB...
USB0:   Register 2000120 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
       scanning usb for ethernet devices... 0 Ethernet Device(s) found
Marvell>>


Marvell>>  usb info
1: Hub,  USB Revision 3.0
 - u-boot XHCI Host Controller
 - Class: Hub
 - PacketSize: 9  Configurations: 1
 - Vendor: 0x0000  Product 0x0000 Version 1.0
   Configuration: 1
   - Interfaces: 1 Self Powered 0mA
     Interface: 0
     - Alternate Setting 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

2: Mass Storage,  USB Revision 3.0
 - SanDisk Extreme AA010901120XXXXXXXXX
 - Class: (from Interface) Mass Storage
 - PacketSize: 9  Configurations: 1
 - Vendor: 0x0781  Product 0x5580 Version 0.16
   Configuration: 1
   - Interfaces: 1 Bus Powered 100mA
     Interface: 0
     - Alternate Setting 0, Endpoints: 2
     - Class Mass Storage, Transp. SCSI, Bulk only
     - Endpoint 1 In Bulk MaxPacket 1024
     - Endpoint 2 Out Bulk MaxPacket 1024

Marvell>>  usb storage
  Device 0: Vendor: SanDisk  Rev: 0001 Prod: Extreme
            Type: Removable Hard Disk
            Capacity: 61057.3 MB = 59.6 GB (125045424 x 512)

Marvell>> usb part

Partition Map for USB device 0  --   Partition Type: EFI

Part    Start LBA       End LBA         Name
        Attributes
        Type GUID
        Partition GUID
  1     0x002cb000      0x002d1fff      "STATE"
        attrs:  0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   fc875410-39fa-c244-9d69-0f3036caae33
  2     0x00005000      0x0000cfff      "KERN-A"
        attrs:  0x01ff000000000000
        type:   fe3a2a5d-4f32-41a7-b725-accc3285a309
        guid:   6dc7a2b5-9be5-b946-826c-aa959d265496
  3     0x00046000      0x002cafff      "ROOT-A"
        attrs:  0x0000000000000000
        type:   3cb8e202-3b7e-47dd-8a3c-7ff2a13cfcec
        guid:   e90d1848-9a1a-8447-a25a-b1c4b882f347
  4     0x0000d000      0x00014fff      "KERN-B"
        attrs:  0x0000000000000000
        type:   fe3a2a5d-4f32-41a7-b725-accc3285a309
        guid:   9825c24f-f975-cf41-8885-62604f99d8e6
<snip>

Marvell>> ext4ls usb 0:1
<DIR>       4096 .
<DIR>       4096 ..
<DIR>      16384 lost+found
<DIR>       4096 unencrypted
           65536 vmlinuz_hd.vblock

Marvell>> ext4ls usb 0:3
<DIR>       4096 .
<DIR>       4096 ..
<DIR>      16384 lost+found
<DIR>       4096 mnt
<DIR>       4096 usr
<DIR>       4096 var
<DIR>       4096 lib
<DIR>       4096 sbin
<DIR>       4096 tmp
<DIR>       4096 bin
<DIR>       4096 etc
<DIR>       4096 dev
<DIR>       4096 run
<DIR>       4096 opt
<SYM>         26 postinst
<DIR>       4096 root
<DIR>       4096 home
<DIR>       4096 debugd
<DIR>       4096 media
<DIR>       4096 proc
<DIR>       4096 sys
Marvell>>


Marvell>> printenv
baudrate=115200
bootcmd=run get_images; run set_bootargs; booti $kernel_addr $ramfs_addr $fdt_addr
bootdelay=3
console=console=ttyS0,115200
eth1addr=00:00:00:00:51:82
eth2addr=00:00:00:00:51:83
ethact=egiga2
ethaddr=00:00:00:00:51:81
ethprime=egiga2
fdt_addr=0x1000000
fdt_high=0xffffffffffffffff
fdt_name=fdt.dtb
gatewayip=10.4.50.254
get_images=tftp $kernel_addr $image_name; tftp $fdt_addr $fdt_name; run get_ramfs
get_ramfs=if test "${ramfs_name}" != "-"; then setenv ramfs_addr 0x3000000; tftp $ramfs_addr $ramfs_name; else setenv ramfs_addr -;fi
hostname=marvell
image_name=Image
initrd_addr=0xa00000
initrd_size=0x2000000
ipaddr=0.0.0.0
kernel_addr=0x2000000
loadaddr=0x2000000
loads_echo=0
netdev=eth0
netmask=255.255.255.0
ramfs_addr=0x3000000
ramfs_name=-
root=root=/dev/nfs rw
rootpath=/srv/nfs/
serverip=0.0.0.0
set_bootargs=setenv bootargs $console $root ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:none nfsroot=$serverip:$rootpath $extra_params
stderr=serial
stdin=serial
stdout=serial

Environment size: 1084/65532 bytes

October 13, 2017 at 6:57 pm #493

Participant

I got the same thing as bb that ext4ls shows many folders are empty.
I used SanDisk Cruzer Fit 8G. Looks like loader did not recognize the partition.

Marvell>> usb part 0

Partition Map for USB device 0 — Partition Type: DOS

Part Start Sector Num Sectors UUID Type
1 2 15633406 00000000-01 0b

Marvell>> usb info
1: Hub, USB Revision 3.0
– u-boot XHCI Host Controller +—————————–+
– Class: Hub | |
– PacketSize: 9 Configurations: 1 | Cannot open /dev/ttyUSB0! |
– Vendor: 0x0000 Product 0x0000 Version 1.0 | |
Configuration: 1 +—————————–+
– Interfaces: 1 Self Powered 0mA
Interface: 0
– Alternate Setting 0, Endpoints: 1
– Class Hub
– Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

2: Mass Storage, USB Revision 2.0
– SanDisk Cruzer Fit 4C530009320625113201
– Class: (from Interface) Mass Storage
– PacketSize: 64 Configurations: 1
– Vendor: 0x0781 Product 0x5571 Version 1.39
Configuration: 1
– Interfaces: 1 Bus Powered 200mA
Interface: 0
– Alternate Setting 0, Endpoints: 2
– Class Mass Storage, Transp. SCSI, Bulk only
– Endpoint 1 In Bulk MaxPacket 512
– Endpoint 2 Out Bulk MaxPacket 512

Marvell>> usb dev

USB device 0: Vendor: SanDisk Rev: 1.27 Prod: Cruzer Fit
Type: Removable Hard Disk
Capacity: 7633.5 MB = 7.4 GB (15633408 x 512)
Marvell>> usb storage
Device 0: Vendor: SanDisk Rev: 1.27 Prod: Cruzer Fit
Type: Removable Hard Disk
Capacity: 7633.5 MB = 7.4 GB (15633408 x 512)

October 13, 2017 at 8:12 pm #494

Participant

BootROM – 2.03
Starting CP-1 IOROM 1.07
Booting from SPI NOR flash 1 (0x32)
Found valid image at boot postion 0x000
lNOTICE: Starting binary extension
NOTICE: Gathering DRAM information
mv_ddr: mv_ddr-armada-17.02.0-g42da6da (Mar 9 2017 – 12:02:05)
mv_ddr: completed successfully
Booting Trusted Firmware
BL1: v1.2(release):armada-17.02.0:2017.02-218-g1558a93
BL1: Built : 12:02:06, Mar 9 2017
NOTICE: BL1: Booting BL2
lNOTICE: BL2: v1.2(release):armada-17.02.0:2017.02-218-g1558a93
NOTICE: BL2: Built : 12:02:06, Mar 9 2017
NOTICE: BL1: Booting BL31
lNOTICE: BL31: v1.2(release):armada-17.02.0:2017.02-218-g1558a93
NOTICE: BL31: Built : 12:02:06, Mar 9 2017
l

U-Boot 2015.01-armada-17.02.0 (Mar 09 2017 – 12:01:25)

January 14, 2018 at 8:40 pm #1513

spencer

Participant

I spent a few days trying to figure this problem out with uSD cards. My solution, suggested a kernel geek friend, is to format the rootfs with ext3 rather than ext4 as suggested. That allowed ext4ls to actually see the content of /boot and the card will actually boot off the uSD card.

I am not sure if this is a problem with a bug with uBoot version or some sort of interaction problem with uSD card speed.

January 15, 2018 at 2:34 am #1517

Participant

tl;dr – use a USB 2.0 stick

I tried four USB sticks before I found one that worked. A researcher mentioned that drivers in U-Boot may be limited, and that I should check the USB version of the device that worked. Sure enough, the working device supported USB 2.0 and the non-working devices were using USB 3.0. A quick way to tell is to look at the male side of the connector; if the plastic inside of the cage is blue it’s USB 3.0.

Author

Posts

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.