Welcome! Log In Create A New Profile

Advanced

Pogoplug mobile, usb port problem

Posted by Tbd6 
Pogoplug mobile, usb port problem
March 08, 2025 08:19AM
Hi all
I flashed 2017 uboot for pogoplug v4 and 2016 envs.
Made rootfs on usb stick but uboot does not detect usb sticks, tried sandisk and kingston sticks.
However led light on usb stick turns on.
Usb info shows ehci host controller only
Can someone help me figure this?
Re: Pogoplug mobile, usb port problem
March 08, 2025 09:48AM
Tbd6,

> I flashed 2017 uboot for pogoplug v4 and 2016
> envs.
> Made rootfs on usb stick but uboot does not detect
> usb sticks, tried sandisk and kingston sticks.
> However led light on usb stick turns on.

> Usb info shows ehci host controller only

The Pogo Mobile has USB 2.0 only. So seing only EHCI controller is normal. What type of USB stick? USB 2.0 or 3.0?

Please post the entire serial boot log.

printenv
usb reset

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Pogoplug mobile, usb port problem
March 08, 2025 12:27PM
I tried Sandisk ultra fit 2.0 and 3.0 , Kingston 3.0 and OCZ 2.0.
Sandisk flashes Led briefly when inserted, OCZ lights led all time, same as on PC.
Kingston has no Led.

Here goes. Probably hardware, huh?
I shoud say in original Pogoplug OS could not mount usb stick either.
I had to back up original uboot to tmp and then scp to PC.

Pogov4> usb reset
usb reset
resetting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Pogov4> version
version

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700)
Pogoplug V4
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28
Pogov4> printenv
printenv
arcNumber=3960
bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtb
ethact=egiga0
ethaddr=00:25:31:84:b3:7d
if_netconsole=ping $serverip
init_ide=ide reset
init_mmc=mmc rescan
init_usb=usb start
ipaddr=192.168.1.60
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
machid=f78
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
nc_ready=1
ncip=192.168.1.40
partition=nand0,2
preboot=run preboot_nc
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
scan_ide=ide reset
scan_mmc=mmc rescan
scan_usb=usb start
serverip=192.168.1.40
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_loaded=0
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_ready_retry=15

Environment size: 3315/131068 bytes

Pogov4> usb info
usb info
1: Hub,  USB Revision 2.0
 - u-boot EHCI Host Controller 
 - Class: Hub
 - PacketSize: 64  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
Re: Pogoplug mobile, usb port problem
March 08, 2025 09:48PM
Tbd6,

> I tried Sandisk ultra fit 2.0 and 3.0 , Kingston
> 3.0 and OCZ 2.0.

The Sandisk Ultra Fit is 3.0. The Sandisk Fit (not Ultra) is 2.0.

> Here goes. Probably hardware, huh?
> I shoud say in original Pogoplug OS could not
> mount usb stick either.

Do you have the Pogo Mobile or the Pogo V4? The Pogo V4 has 2 USB 3.0 ports in the back and when you open the top cover, it exposes a HDD slot and USB 2.0 slot.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Pogoplug mobile, usb port problem
March 09, 2025 10:24AM
Thank you for answering,
Yeah Sandisk 2.0 version is actually called Cruzer Fit SDCZ33 , it is little smaller from 3.0 Ultra fit.

On the bottom says "Model: Pogo-V4-A1-01 Product:Pogoplug mobile", has blueish logo on front.
I flashed uboot for pogo v4, is it correct one?
Top part seems fixed, does not open, there is only one usb port on back aside ethernet and power jack.
And there is sd card slot on side which i used to run Debian and openwrt from ram per other thread instructions.
I then flashed openwrt , neither debian nor openwrt show anything in dmesg when i plug usb stick.

Can you tell how to mount under debian, ubi partition with openwrt ?
I must have messed someting in openwrt config, wanted repair without connecting serial again.

Other question, is it posiible to sysupgrade openwrt runing from ubi, without booting openwrt uimage to ram?
Re: Pogoplug mobile, usb port problem
March 09, 2025 11:22PM
> On the bottom says "Model: Pogo-V4-A1-01
> Product:Pogoplug mobile", has blueish logo on
> front.
> I flashed uboot for pogo v4, is it correct one?
> Top part seems fixed, does not open, there is
> only one usb port on back aside ethernet and power
> jack.

Yes u-boot is the same for Pogo V4 and Pogo Mobile.

> And there is sd card slot on side which i used
> to run Debian and openwrt from ram per other
> thread instructions.
> I then flashed openwrt , neither debian nor
> openwrt show anything in dmesg when i plug usb
> stick.

If dmesg does not show anything when the USB 2.0 stick is inserted, then the port is dead.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Pogoplug mobile, usb port problem
March 10, 2025 04:25PM
Could be default environment issue, that prevents port working?
Default env seems for E02 pogoplug, herebelow quotes are from 1st thread https://forum.doozan.com/read.php?3,12381

Quote

Note: for boxes such as Pogo V4 and Zyxel NSA3xx, the mtd partition definition are kept the same as stock definition


Quote

e.2 Box specific envs:

Then for all boxes, restore these 2 envs using the saved envs text in step c (replace xxx with the real saved values)
fw_setenv mtdparts 'xxxxxxxxx'
fw_setenv ethaddr 'xx:xx:xx:xx:xx:xx'

fw_setenv mtdparts 'xxxxxxxxx'
fw_setenv ethaddr 'xx:xx:xx:xx:xx:xx'

e.3 uEnv.txt envs correction (optional


For Pogoplug mobile original stock uboot had no mtdparts defined, I missed that and after flashing 2017 uboot, rebooted pogoplug mobile with mtdparts as defined for E02.
Re: Pogoplug mobile, usb port problem
March 10, 2025 11:54PM
Tbd6,

> Could be default environment issue, that prevents
> port working?

No. In the 2017.07 u-boot, the default envs have notthing to do with the USB port.

The Cruzer Fit is a good USB thumbdrive for this plug. I never see it fail to spin up in this Pogo Mobile. And that was both in u-boot and Linux. Especially in Linux, if the drive is not showing up in Linux, chance is great that the port has problem. Try remove the Cruzer Fit and reattach it a few times.

Also try cold start (unplug/plug power cord), interrupt u-boot countdown and
usb reset
If it does not spin up, repeat "usb reset" a few times.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: