Hello,
I picked up a new old stock Pogoplug Series 4 (V4-A03-01) recently after coming across this hackaday article.
I then watched the youtube uploads from Films by Kris.
This then lead me to Kris's "show notes" he posted on paste bin.
Hopefully adding the links and keywords will help others find this.
These are the commands I tried while following Kris's example (copied from pastebin):
Questions:
Why does does my original Pogoplug printenv look so much different than the others I've seen posted here?
The lines with tabs seem to be unusual:
I thought I would check in and see what the more experienced people here thought I should do next. This device has never had ethernet connected. Is there a copy of the complete stock pre-internet connected image somewhere already?
Is it possible to recover the original OS at this point? Do I dump the NAND with the original memory display command in uboot, decompress it somehow and try to modify it, or is there some other way to recover?
Thanks for taking the time to read this.
-Jake
Restating questions for easier unpacking:
1. Why does does my original Pogoplug printenv look so much different than the others I've seen posted here?
2. Is there a copy of this stock pre-internet-connected image somewhere already?
3. Is it possible to recover the original OS at this point?
4. Do I dump the NAND with the original memory display command in uboot, decompress it somehow and try to modify it, or is there some other way to recover?
+5. What other questions should I be asking in order to learn more about embedded Linux and apply this experience to other devices?
I picked up a new old stock Pogoplug Series 4 (V4-A03-01) recently after coming across this hackaday article.
I then watched the youtube uploads from Films by Kris.
This then lead me to Kris's "show notes" he posted on paste bin.
Hopefully adding the links and keywords will help others find this.
These are the commands I tried while following Kris's example (copied from pastebin):
The busybox install looked straight forward. I used an USB drive to transfer the busybox binary and everything seemed to be working. With the new busybox binary mounted to /tmp, I tested several new commands and everything seemed to work. So I copied /bin/busybox to a USB drive, and replaced the original binary with the new one. Kris lists the command he used to link everything on PB:Quote
#connect
screen /dev/ttyUSB0 115200,cs8,-parenb,-cstopb,-hupcl
#list partition
cat /proc/partitions
cat /proc/mtd
#remount / (root) as read/write
mount -o remount,rw /
#change root password
passwd root
#start telnetd or ssh server (both are already there)
#startup script can be found here
#(might want to enable dropbear and telnet and disable pogo services 'hbmgr.sh'):
vi /etc/init.d/rcS
#mount sdcard
mkdir /mnt/sdcard
mknod /dev/mmcblk0 b 179 0
mknod /dev/mmcblk0p1 b 179 1
mount /dev/mmcblk0p1 /mnt/sdcard
#mount USB drive
mkdir /mnt/usb
mknod /dev/sda b 8 0
mknod /dev/sda1 b 8 1
mount /dev/sda1 /mnt/usb
#add these lines to /etc/fstab
/dev/sda1 /mnt/usb vfat defaults 0 0
/dev/mmcblk0p1 /mnt/sdcard vfat defaults 0 0
This is where things went south for me. I got a bunch of warnings about each command with a message (IIRC) calling something about each one illegal. This ended with an infinitely repeating "#" prompt. I let it sit for a few hours, but nothing changed and not knowing what else to do, I rebooted, then got kernel panic (my bootlog is attached to this post along with results of several other uboot commands and the kwboot versions too).Quote
busybox --list|while read c;do echo $c;ln -s /bin/busybox $c;done
Questions:
Why does does my original Pogoplug printenv look so much different than the others I've seen posted here?
The lines with tabs seem to be unusual:
Quote
baudrate=115200
----bootargs=console=ttyS0,115200 root=ubi0:rootfs ubi.mtd=4,2048 rootfstype=ubifs
----boot=bootm 0x800000
bootcmd=run boot_nand
bootdelay=1
----boot_nand=run load_nand boot || run load_nand2 boot
----CASset=min
----ceboardver=PPV4A3
----disaMvPnp=no
----disL2Cache=no
----disL2Prefetch=yes
----enaCpuStream=no
----enaDCPref=yes
----enaICPref=yes
----enaMonExt=no
----enaWrAllo=no
----Environment size: 801/131068 bytes
ethact=egiga0
----ethaddr=00:50:43:00:02:02
----ethmtu=1500
----ethprime=egiga0
----hddPowerCtrl=no
ipaddr=169.254.254.253
----load_nand2=nboot 0x800000 0 0x500000
----load_nand=nboot 0x800000 0 0x200000
----loads_echo=0
mainlineLinux=no
----MALLOC_len=1
----nandEcc=1bit
----netbsd_en=no
----netmask=255.255.0.0
----pcieTune=no
----pexMode=RC
----rootpath=/mnt/ARM_FS/
----run_diag=yes
----sata_dma_mode=yes
serverip=169.254.254.254
----setL2CacheWT=yes
stderr=serial
stdin=serial
stdout=serial
----usb0Mode=host
----vxworks_en=no
I thought I would check in and see what the more experienced people here thought I should do next. This device has never had ethernet connected. Is there a copy of the complete stock pre-internet connected image somewhere already?
Is it possible to recover the original OS at this point? Do I dump the NAND with the original memory display command in uboot, decompress it somehow and try to modify it, or is there some other way to recover?
Thanks for taking the time to read this.
-Jake
Restating questions for easier unpacking:
1. Why does does my original Pogoplug printenv look so much different than the others I've seen posted here?
2. Is there a copy of this stock pre-internet-connected image somewhere already?
3. Is it possible to recover the original OS at this point?
4. Do I dump the NAND with the original memory display command in uboot, decompress it somehow and try to modify it, or is there some other way to recover?
+5. What other questions should I be asking in order to learn more about embedded Linux and apply this experience to other devices?