well I'll chalk this pogoplug up to experience.
Maybe I'll get adventurous and buy a serial cable and try to JTAG it. I'll probably just buy another instead.
I tried to explore a bit on the ssh myself and have some how gotten myself out of the -bash command and do not know how to get myself back. Even if I did, it looks like the pogoplug isn't cooperating with the ssh commands anyway.
Thanks for your help, looks like my pogoplug didn't want to cooperate.
Black pogo that is labled E02 problems
25 posts
• Page 2 of 3 • 1, 2, 3
Re: Black pogo that is labled E02 problems
by kransbox » Sun Oct 21, 2012 6:01 pm
- kransbox
- Posts: 13
- Joined: Sat Oct 20, 2012 9:52 pm
Re: Black pogo that is labled E02 problems
by pepedog » Sun Oct 21, 2012 6:08 pm
Nothing to lose, run this one more time, I couldn't see if you removed when you did --no-uboot-check
$this->bbcode_second_pass_code('', './install_uboot_mtd0.sh --no-uboot-check')
$this->bbcode_second_pass_code('', './install_uboot_mtd0.sh --no-uboot-check')
- pepedog
- Developer
- Posts: 2431
- Joined: Mon Jun 07, 2010 3:30 pm
- Location: London UK
Re: Black pogo that is labled E02 problems
by kransbox » Sun Oct 21, 2012 6:15 pm
I cannot figure out how to bring up the -bash command again to run this.
I never rebooted the device or turned it off but I "googled ssh commands" and tried to figure out how to make a backup of the thing it was telling me to - big mistake on my end. Here is my code. If you can bring me back to -bash then I'll continue, otherwise I think I'm screwed.
$this->bbcode_second_pass_code('', '## VERIFICATION FAILED!
##
## uBoot was not properly installed to mtd0.
##
##
## YOUR DEVICE MAY BE IN AN UNUSABLE STATE.
## DO NOT REBOOT OR POWER OFF YOUR DEVICE
##
##
## Make a backup of /tmp/uboot-mtd0-dump someplace safe and
## then re-run this installer.
-bash-3.2# Select all
-bash: Select: command not found
-bash-3.2# mv /boot/uImage /boot/uImage.old
mv: cannot rename '/boot/uImage': No such file or directory
-bash-3.2# select all
> Select all
-bash: syntax error near unexpected token `Select'
-bash-3.2# mv /boot/uImage /boot/uImage.old
mv: cannot rename '/boot/uImage': No such file or directory
-bash-3.2#
-bash-3.2# ?
-bash: ?: command not found
-bash-3.2# ,
-bash: ,: command not found
-bash-3.2# cd /tmp
-bash-3.2# tar zcvf
tar: option requires an argument -- f
BusyBox v1.7.0 (2008-02-26 19:25:17 IST) multi-call binary
Usage: tar -[czjaZxtvO] [-X FILE] [-f TARFILE] [-C DIR] [FILE(s)] ...
Create, extract, or list files from a tar file
Options:
c Create
x Extract
t List
Archive format selection:
z Filter the archive through gzip
j Filter the archive through bzip2
a Filter the archive through lzma
Z Filter the archive through compress
File selection:
f Name of TARFILE or "-" for stdin
O Extract to stdout
exclude File to exclude
X File with names to exclude
C Change to directory DIR before operation
v Verbose
-bash-3.2# cd /tmp
-bash-3.2# cd /uboot-mtd0-dump
-bash: cd: /uboot-mtd0-dump: No such file or directory
-bash-3.2# cd /uboot
-bash: cd: /uboot: No such file or directory
-bash-3.2# ct /tmp
-bash: ct: command not found
-bash-3.2# cd /tmp
-bash-3.2# uboot-mtd0
-bash: uboot-mtd0: command not found
-bash-3.2# dir
-bash: dir: command not found
-bash-3.2# cd /tmp
-bash-3.2# t
-bash: t: command not found
-bash-3.2# tar -t
'
-bash
-bash-3.2#
;laksdjfa;sfkj
tar
ssh
cd..
cd..
uname -a
bash
cd /bash
cd -bash
./install_uboot_mtd0.sh --no-uboot-check
')
lol, thats what I get for exploring.....
I never rebooted the device or turned it off but I "googled ssh commands" and tried to figure out how to make a backup of the thing it was telling me to - big mistake on my end. Here is my code. If you can bring me back to -bash then I'll continue, otherwise I think I'm screwed.
$this->bbcode_second_pass_code('', '## VERIFICATION FAILED!
##
## uBoot was not properly installed to mtd0.
##
##
## YOUR DEVICE MAY BE IN AN UNUSABLE STATE.
## DO NOT REBOOT OR POWER OFF YOUR DEVICE
##
##
## Make a backup of /tmp/uboot-mtd0-dump someplace safe and
## then re-run this installer.
-bash-3.2# Select all
-bash: Select: command not found
-bash-3.2# mv /boot/uImage /boot/uImage.old
mv: cannot rename '/boot/uImage': No such file or directory
-bash-3.2# select all
> Select all
-bash: syntax error near unexpected token `Select'
-bash-3.2# mv /boot/uImage /boot/uImage.old
mv: cannot rename '/boot/uImage': No such file or directory
-bash-3.2#
-bash-3.2# ?
-bash: ?: command not found
-bash-3.2# ,
-bash: ,: command not found
-bash-3.2# cd /tmp
-bash-3.2# tar zcvf
tar: option requires an argument -- f
BusyBox v1.7.0 (2008-02-26 19:25:17 IST) multi-call binary
Usage: tar -[czjaZxtvO] [-X FILE] [-f TARFILE] [-C DIR] [FILE(s)] ...
Create, extract, or list files from a tar file
Options:
c Create
x Extract
t List
Archive format selection:
z Filter the archive through gzip
j Filter the archive through bzip2
a Filter the archive through lzma
Z Filter the archive through compress
File selection:
f Name of TARFILE or "-" for stdin
O Extract to stdout
exclude File to exclude
X File with names to exclude
C Change to directory DIR before operation
v Verbose
-bash-3.2# cd /tmp
-bash-3.2# cd /uboot-mtd0-dump
-bash: cd: /uboot-mtd0-dump: No such file or directory
-bash-3.2# cd /uboot
-bash: cd: /uboot: No such file or directory
-bash-3.2# ct /tmp
-bash: ct: command not found
-bash-3.2# cd /tmp
-bash-3.2# uboot-mtd0
-bash: uboot-mtd0: command not found
-bash-3.2# dir
-bash: dir: command not found
-bash-3.2# cd /tmp
-bash-3.2# t
-bash: t: command not found
-bash-3.2# tar -t
'
-bash
-bash-3.2#
;laksdjfa;sfkj
tar
ssh
cd..
cd..
uname -a
bash
cd /bash
cd -bash
./install_uboot_mtd0.sh --no-uboot-check
')
lol, thats what I get for exploring.....
- kransbox
- Posts: 13
- Joined: Sat Oct 20, 2012 9:52 pm
Re: Black pogo that is labled E02 problems
by karog » Sun Oct 21, 2012 6:52 pm
Can you start a brand new shell ie ssh to the E02 again from your main machine without giving up the first one in case this does not work?
Also, on the first shell, I can't tell for sure but it looks like you might have typed a single quote in there. Try typing a single quote again to end if that is the case.
Also, on the first shell, I can't tell for sure but it looks like you might have typed a single quote in there. Try typing a single quote again to end if that is the case.
- karog
- Posts: 305
- Joined: Thu Jan 05, 2012 7:55 pm
Re: Black pogo that is labled E02 problems
by kransbox » Sun Oct 21, 2012 7:11 pm
okay I did that (ran another console)
I get this code now, still no bash
$this->bbcode_second_pass_code('', 'login as: root
root@99.99.99.148's password:
Pogoplug:~$
')
I went ahead with this ssh and tried again. Here is the code. Same thing
$this->bbcode_second_pass_code('', 'Pogoplug:~$ ./install_uboot_mtd0.sh --no-uboot-check
!!!!!! DANGER DANGER DANGER DANGER DANGER DANGER !!!!!!
If you lose power to your device while running this script,
it could be left in an unusable state.
This script will replace the bootloader on /dev/mtd0.
This installer will only work on the following devices:
Seagate Dockstar
Seagate GoFlex Net
Seagate GoFlex Home
Pogoplug v1
Pogoplug Pink (v2)
Do not run this installer on any other device.
By typing ok, you agree to assume all liabilities and risks
associated with running this installer.
If you agree, type 'ok' and press ENTER to continue: ok
# checking for /usr/sbin/nandwrite...
# checking for /usr/sbin/nanddump...
# checking for /usr/sbin/flash_erase...
# checking for /usr/sbin/fw_printenv...
# checking for /etc/fw_env.config...
# Validating existing uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to jeff.doozan.com (50.116.34.13:80)
valid-uboot.md5 100% |*******************************| 1133 --:--:-- ETA
## Unknown uBoot detected on mtd0: b74593c126cdd5dba303e5dea85c6bca
##
## --no-uboot-check flag detected, continuing installation
############################################
Your device could not be auto-detected.
You must be using a device listed below to run this installer.
What device are you using? Type the number of your device and press ENTER.
1 - Seagate Dockstar
2 - Seagate GoFlex Net
3 - Seagate GoFlex Home
4 - Pogoplug v1
5 - Pogoplug v2 - Pink
6 - Other
5
Selected Pogoplug v2 - Pink
# Installing uBoot
## Installing pinkpogo davygravy-2012-02-20
Connecting to download.doozan.com (50.116.34.13:80)
uboot.mtd0.kwb.md5 100% |*******************************| 32 --:--:-- ETA
Connecting to download.doozan.com (50.116.34.13:80)
uboot.mtd0.kwb 100% |*******************************| 512k --:--:-- ETA
Erase Total 4 Units
Performing Flash Erase of length 131072 at offset 0x40000
MTD Erase failure: Input/output error
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Bad block at 40000, 1 block(s) from 40000 will be skipped
Writing data to block 3 at offset 0x60000
Writing data to block 4 at offset 0x80000
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
## Verifying new uBoot...
Connecting to download.doozan.com (50.116.34.13:80)
uboot.mtd0.kwb.md5 100% |*******************************| 32 --:--:-- ETA
##
##
## VERIFICATION FAILED!
##
## uBoot was not properly installed to mtd0.
##
##
## YOUR DEVICE MAY BE IN AN UNUSABLE STATE.
## DO NOT REBOOT OR POWER OFF YOUR DEVICE
##
##
## Make a backup of /tmp/uboot-mtd0-dump someplace safe and
## then re-run this installer.
')
anyone have a way for me to try to reflash the original pogoplug OS on this thing before I pull the plug on its comatose state?
I get this code now, still no bash
$this->bbcode_second_pass_code('', 'login as: root
root@99.99.99.148's password:
Pogoplug:~$
')
I went ahead with this ssh and tried again. Here is the code. Same thing
$this->bbcode_second_pass_code('', 'Pogoplug:~$ ./install_uboot_mtd0.sh --no-uboot-check
!!!!!! DANGER DANGER DANGER DANGER DANGER DANGER !!!!!!
If you lose power to your device while running this script,
it could be left in an unusable state.
This script will replace the bootloader on /dev/mtd0.
This installer will only work on the following devices:
Seagate Dockstar
Seagate GoFlex Net
Seagate GoFlex Home
Pogoplug v1
Pogoplug Pink (v2)
Do not run this installer on any other device.
By typing ok, you agree to assume all liabilities and risks
associated with running this installer.
If you agree, type 'ok' and press ENTER to continue: ok
# checking for /usr/sbin/nandwrite...
# checking for /usr/sbin/nanddump...
# checking for /usr/sbin/flash_erase...
# checking for /usr/sbin/fw_printenv...
# checking for /etc/fw_env.config...
# Validating existing uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to jeff.doozan.com (50.116.34.13:80)
valid-uboot.md5 100% |*******************************| 1133 --:--:-- ETA
## Unknown uBoot detected on mtd0: b74593c126cdd5dba303e5dea85c6bca
##
## --no-uboot-check flag detected, continuing installation
############################################
Your device could not be auto-detected.
You must be using a device listed below to run this installer.
What device are you using? Type the number of your device and press ENTER.
1 - Seagate Dockstar
2 - Seagate GoFlex Net
3 - Seagate GoFlex Home
4 - Pogoplug v1
5 - Pogoplug v2 - Pink
6 - Other
5
Selected Pogoplug v2 - Pink
# Installing uBoot
## Installing pinkpogo davygravy-2012-02-20
Connecting to download.doozan.com (50.116.34.13:80)
uboot.mtd0.kwb.md5 100% |*******************************| 32 --:--:-- ETA
Connecting to download.doozan.com (50.116.34.13:80)
uboot.mtd0.kwb 100% |*******************************| 512k --:--:-- ETA
Erase Total 4 Units
Performing Flash Erase of length 131072 at offset 0x40000
MTD Erase failure: Input/output error
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Bad block at 40000, 1 block(s) from 40000 will be skipped
Writing data to block 3 at offset 0x60000
Writing data to block 4 at offset 0x80000
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
## Verifying new uBoot...
Connecting to download.doozan.com (50.116.34.13:80)
uboot.mtd0.kwb.md5 100% |*******************************| 32 --:--:-- ETA
##
##
## VERIFICATION FAILED!
##
## uBoot was not properly installed to mtd0.
##
##
## YOUR DEVICE MAY BE IN AN UNUSABLE STATE.
## DO NOT REBOOT OR POWER OFF YOUR DEVICE
##
##
## Make a backup of /tmp/uboot-mtd0-dump someplace safe and
## then re-run this installer.
')
anyone have a way for me to try to reflash the original pogoplug OS on this thing before I pull the plug on its comatose state?
- kransbox
- Posts: 13
- Joined: Sat Oct 20, 2012 9:52 pm
Re: Black pogo that is labled E02 problems
by moonman » Mon Oct 22, 2012 6:09 am
You have a bad block that's why it can't verify it properly. Your u-boot should be flashed fine as it skipped the bad block (block 1 will reference block 3 instead of 2 now), however your u-boot environemnt is probably not set because it should be set after verification and verification fails (and fails because it doesn't know the block was skipped). I am not an expert, but this is what I think happened. You may be able to edit jeff's script and remove the part where it verifies u-boot so that environemnt is flashed as well. This is very dangerous though and as I am not completely sure about what I just said you may wind up with a brick if you restart.
If you want to be on the safe(r) side, contact Jeff - creator of the script and U-Boot itself, he may have a solution for you.
Register at http://forum.doozan.com and send a PM to Jeff : http://forum.doozan.com/profile.php?4,1
PS. For Jtag you need a jtag board (buspirate?), serial is different and only works if you have a working u-boot.
If you want to be on the safe(r) side, contact Jeff - creator of the script and U-Boot itself, he may have a solution for you.
Register at http://forum.doozan.com and send a PM to Jeff : http://forum.doozan.com/profile.php?4,1
PS. For Jtag you need a jtag board (buspirate?), serial is different and only works if you have a working u-boot.
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
- moonman
- Developer
- Posts: 3388
- Joined: Sat Jan 15, 2011 3:36 am
Re: Black pogo that is labled E02 problems
by moonman » Mon Oct 22, 2012 6:54 am
Actually this thread confirms what I just said: http://forum.doozan.com/read.php?3,5728,5770
So, it should work as it worked for the guy in that thread:
Do the following:
$this->bbcode_second_pass_code('', 'cd /tmp
wget -O /tmp/uboot.environment http://jeff.doozan.com/debian/uboot/files/environment/uboot.environment
')
$this->bbcode_second_pass_code('', '/usr/sbin/flash_erase /dev/mtd0 0xc0000 1')
$this->bbcode_second_pass_code('', '/usr/sbin/nandwrite -s 786432 /dev/mtd0 /tmp/uboot.environment')
Check if it was flashed correctly by running:
$this->bbcode_second_pass_code('', '/usr/sbin/fw_printenv')
Now add netconsole to the environment:
$this->bbcode_second_pass_code('', '/usr/sbin/fw_setenv ipaddr '10.0.10.6'
/usr/sbin/fw_setenv ncip '10.10.10.5'
/usr/sbin/fw_setenv ncipk '10.10.10.4'
/usr/sbin/fw_setenv serverip '10.10.10.3'
/usr/sbin/fw_setenv preboot 'run nc_test nc_start'
/usr/sbin/fw_setenv nc_test 'ping $ncip'
/usr/sbin/fw_setenv nc_start 'setenv stdin nc; setenv stdout nc; setenv stderr nc; version'
/usr/sbin/fw_setenv usb_custom_params 'loglevel=6 netconsole=6665@10.10.10.3/eth0,6666@10.10.10.4/'')
Again check if it was written to the environemnt:
$this->bbcode_second_pass_code('', '/usr/sbin/fw_printenv')
Sutup nc on your pc so that you can watch U-Boot doing its things. http://archlinuxarm.org/platforms/armv5 ... s-ui-tabs3. Cross your fingers and reboot.
If you get something in the netconsole windows then you have a working U-Boot. Now you just need to setup archlinuxarm on a flashdrive/hard drive. You can follow the link my signature.
So, it should work as it worked for the guy in that thread:
Do the following:
$this->bbcode_second_pass_code('', 'cd /tmp
wget -O /tmp/uboot.environment http://jeff.doozan.com/debian/uboot/files/environment/uboot.environment
')
$this->bbcode_second_pass_code('', '/usr/sbin/flash_erase /dev/mtd0 0xc0000 1')
$this->bbcode_second_pass_code('', '/usr/sbin/nandwrite -s 786432 /dev/mtd0 /tmp/uboot.environment')
Check if it was flashed correctly by running:
$this->bbcode_second_pass_code('', '/usr/sbin/fw_printenv')
Now add netconsole to the environment:
$this->bbcode_second_pass_code('', '/usr/sbin/fw_setenv ipaddr '10.0.10.6'
/usr/sbin/fw_setenv ncip '10.10.10.5'
/usr/sbin/fw_setenv ncipk '10.10.10.4'
/usr/sbin/fw_setenv serverip '10.10.10.3'
/usr/sbin/fw_setenv preboot 'run nc_test nc_start'
/usr/sbin/fw_setenv nc_test 'ping $ncip'
/usr/sbin/fw_setenv nc_start 'setenv stdin nc; setenv stdout nc; setenv stderr nc; version'
/usr/sbin/fw_setenv usb_custom_params 'loglevel=6 netconsole=6665@10.10.10.3/eth0,6666@10.10.10.4/'')
Again check if it was written to the environemnt:
$this->bbcode_second_pass_code('', '/usr/sbin/fw_printenv')
Sutup nc on your pc so that you can watch U-Boot doing its things. http://archlinuxarm.org/platforms/armv5 ... s-ui-tabs3. Cross your fingers and reboot.
If you get something in the netconsole windows then you have a working U-Boot. Now you just need to setup archlinuxarm on a flashdrive/hard drive. You can follow the link my signature.
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
- moonman
- Developer
- Posts: 3388
- Joined: Sat Jan 15, 2011 3:36 am
Re: Black pogo that is labled E02 problems
by kransbox » Mon Oct 22, 2012 8:18 pm
This is what I get after I've done all of your steps before doing the netconsole code:
$this->bbcode_second_pass_code('', 'Pogoplug:/tmp$ /usr/sbin/flash_erase /dev/mtd0 0xc0000 1
Erase Total 1 Units
Performing Flash Erase of length 131072 at offset 0xc0000 done
<n/nandwrite -s 786432 /dev/mtd0 /tmp/uboot.environment
Writing data to block 6 at offset 0xc0000
Pogoplug:/tmp$ /usr/sbin/fw_printenv
ethact=egiga0
bootdelay=3
baudrate=115200
arcNumber=2097
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
Pogoplug:/tmp$')
Look good?
This is what I get after doing the netconsole
$this->bbcode_second_pass_code('', 'Pogoplug:/tmp$ /usr/sbin/fw_setenv ipaddr '10.0.10.6'
Pogoplug:/tmp$ /usr/sbin/fw_setenv ncip '10.10.10.5'
Pogoplug:/tmp$ /usr/sbin/fw_setenv ncipk '10.10.10.4'
Pogoplug:/tmp$ /usr/sbin/fw_setenv serverip '10.10.10.3'
Pogoplug:/tmp$ /usr/sbin/fw_setenv preboot 'run nc_test nc_start'
Pogoplug:/tmp$ /usr/sbin/fw_setenv nc_test 'ping $ncip'
<tdin nc; setenv stdout nc; setenv stderr nc; version'
<'loglevel=6 netconsole=6665@10.10.10.3/eth0,6666@10.10.10.4/'
Pogoplug:/tmp$ /usr/sbin/fw_printenv
ethact=egiga0
bootdelay=3
baudrate=115200
arcNumber=2097
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
ipaddr=10.0.10.6
ncip=10.10.10.5
ncipk=10.10.10.4
serverip=10.10.10.3
preboot=run nc_test nc_start
nc_test=ping $ncip
nc_start=setenv stdin nc; setenv stdout nc; setenv stderr nc; version
usb_custom_params=loglevel=6 netconsole=6665@10.10.10.3/eth0,6666@10.10.10.4/
Pogoplug:/tmp$
')
thanks for your help really!
In regards to this: "Sutup nc on your pc so that you can watch U-Boot doing its things. http://archlinuxarm.org/platforms/armv5 ... s-ui-tabs3. Cross your fingers and reboot." I have no idea how to setup nc on my PC. I've viewed that link before, but I don't know quite what it is presenting. I'm on a WINDOWS 7 pc using PuTTy to ssh.
last thing. In regards to this:
$this->bbcode_second_pass_quote('', 'I')f you get something in the netconsole windows then you have a working U-Boot. Now you just need to setup archlinuxarm on a flashdrive/hard drive. You can follow the link my signature.
$this->bbcode_second_pass_code('', 'Pogoplug:/tmp$ /usr/sbin/flash_erase /dev/mtd0 0xc0000 1
Erase Total 1 Units
Performing Flash Erase of length 131072 at offset 0xc0000 done
<n/nandwrite -s 786432 /dev/mtd0 /tmp/uboot.environment
Writing data to block 6 at offset 0xc0000
Pogoplug:/tmp$ /usr/sbin/fw_printenv
ethact=egiga0
bootdelay=3
baudrate=115200
arcNumber=2097
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
Pogoplug:/tmp$')
Look good?
This is what I get after doing the netconsole
$this->bbcode_second_pass_code('', 'Pogoplug:/tmp$ /usr/sbin/fw_setenv ipaddr '10.0.10.6'
Pogoplug:/tmp$ /usr/sbin/fw_setenv ncip '10.10.10.5'
Pogoplug:/tmp$ /usr/sbin/fw_setenv ncipk '10.10.10.4'
Pogoplug:/tmp$ /usr/sbin/fw_setenv serverip '10.10.10.3'
Pogoplug:/tmp$ /usr/sbin/fw_setenv preboot 'run nc_test nc_start'
Pogoplug:/tmp$ /usr/sbin/fw_setenv nc_test 'ping $ncip'
<tdin nc; setenv stdout nc; setenv stderr nc; version'
<'loglevel=6 netconsole=6665@10.10.10.3/eth0,6666@10.10.10.4/'
Pogoplug:/tmp$ /usr/sbin/fw_printenv
ethact=egiga0
bootdelay=3
baudrate=115200
arcNumber=2097
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
ipaddr=10.0.10.6
ncip=10.10.10.5
ncipk=10.10.10.4
serverip=10.10.10.3
preboot=run nc_test nc_start
nc_test=ping $ncip
nc_start=setenv stdin nc; setenv stdout nc; setenv stderr nc; version
usb_custom_params=loglevel=6 netconsole=6665@10.10.10.3/eth0,6666@10.10.10.4/
Pogoplug:/tmp$
')
thanks for your help really!
In regards to this: "Sutup nc on your pc so that you can watch U-Boot doing its things. http://archlinuxarm.org/platforms/armv5 ... s-ui-tabs3. Cross your fingers and reboot." I have no idea how to setup nc on my PC. I've viewed that link before, but I don't know quite what it is presenting. I'm on a WINDOWS 7 pc using PuTTy to ssh.
last thing. In regards to this:
$this->bbcode_second_pass_quote('', 'I')f you get something in the netconsole windows then you have a working U-Boot. Now you just need to setup archlinuxarm on a flashdrive/hard drive. You can follow the link my signature.
can I not just finish the tutorial in my original post and install archlinux on my usb through that instead of your method, or do I HAVE to do your method? I already have archlinux installed on my usb (I believe) going through the original method outlined in the original tutorial that I followed.
- kransbox
- Posts: 13
- Joined: Sat Oct 20, 2012 9:52 pm
Re: Black pogo that is labled E02 problems
by pepedog » Mon Oct 22, 2012 8:33 pm
I hope you didn't paste whole chunks via putty into uBoot environment? It's not like Linux where it all gets buffe red.
I really think you need to check line by line
I really think you need to check line by line
- pepedog
- Developer
- Posts: 2431
- Joined: Mon Jun 07, 2010 3:30 pm
- Location: London UK
Re: Black pogo that is labled E02 problems
by kransbox » Mon Oct 22, 2012 10:22 pm
No, I posted it line by line
- kransbox
- Posts: 13
- Joined: Sat Oct 20, 2012 9:52 pm
25 posts
• Page 2 of 3 • 1, 2, 3
Who is online
Users browsing this forum: No registered users and 2 guests