I just received a used pogo e02, I wanted to to convert this to a slim player device by putting debian onto it first.

I expected stock is to have been on the plug, but it seems to have corrupt is as of now, stock is not booting. No Pogo server running on ip address of device, my router identify it as "debian", can't connect with ssh, default password is failing.

I have serial console to it now, but stock OS has NO tool support it seems. cat / cd / grep all return as unknown commands.

I realize this is old device, so I tried to search first before makeing new thread, but My searches did not result in any answers to how to move from stock to debian. I only found topics asking how to switch from Aarch to Debian.

U-Boot 1.1.4 (Sep 28 2009 - 11:55:23) Cloud Engines v2.0 (3.4.16)

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 00690D60

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz 

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB 
DRAM Total size 256MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:128 MB

CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD: PPV2

Streaming disabled 
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0 
CE>> printenv
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
run_diag=yes
console=console=ttyS0,115200
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/mtdblock2 ro
ethmtu=1500
usb0Mode=host
nandEcc=1bit
ethact=egiga0
serverip=169.254.254.252
ipaddr=169.254.254.253
ethaddr=00:25:31:02:F6:64
cesvcid=UMT3AW7DWKU2HFVY33ER8VKTJ6
ceboardver=PPV2
bootcmd=nand read.e 0x800000 0x100000 0x200000; setenv bootargs $(console) $(bootargs_root);bootm 0x800000
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
bootargs=console=ttyS0,115200 root=/dev/mtdblock2 ro

Edited 1 time(s). Last edit at 11/22/2020 10:04PM by mrmazak.

I did find a post from 2014 mentioning that from serial console you can set env and command boot from usb, but it was not enough details for me I suppose. I will keep at it.

I do find a couple posts and threads that say how to run Jeff's scripts to install Debian and update uboot. Bit they start with a running device with ssh access
All I have access to at the moment is serial console.

I bought this thing off of eBay, and description said working perfectly device. Not that I wanted a device running stock, but apparently I needed to start from there to enable ssh.

Might try to get e-bay refund.
Unless I find hope in restoring it with console cmd. And usb boot.



Edited 1 time(s). Last edit at 11/23/2020 06:38AM by mrmazak.

mrmazak,

Follow the instruction in the release thread:
https://forum.doozan.com/read.php?2,12096

and create the Debian rootfs on USB using Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2. You need to do step 4, since you are booting with stock u-boot.

Plug in this USB rootfs. Power up, interrupt serial console, and

setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial'
setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd'
setenv usb_boot 'mw 0x800000 0 1; run load_uimage; if run load_uinitrd; then bootm 0x800000 0x2100000; else bootm 0x800000; fi'
setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot'
setenv bootcmd 'usb start; run usb_bootcmd; usb stop; reset'

And then,

printenv
boot

Please post the entire serial log here.

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

Here we go. You specified to do step 4 because of stock uboot. Makes me need to ask. Once I am able to flash new uboot, will I then update rootfs and undo step 4?

the 4th line , the one with the if statement was 'too many args"

CE>> 
CE>> setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=seri'
CE>> setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
CE>> setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd'
CE>> setenv usb_boot 'mw 0x800000 0 1; run load_uimage; if run load_uinitrd; then bootm 0x800000 0x2100000; else b'
** Too many args (max. 16) **
CE>> setenv usb_boot 'mw 0x800000 0 1; run load_uimage; if run load_uinitrd; then bootm 0x800000 0x2100000; else b'
** Too many args (max. 16) **
CE>> setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot'
CE>> setenv bootcmd 'usb start; run usb_bootcmd; usb stop; reset'
CE>> printenv
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
run_diag=yes
console=console=ttyS0,115200
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/mtdblock2 ro
ethmtu=1500
usb0Mode=host
nandEcc=1bit
ethact=egiga0
bootargs=console=ttyS0,115200 root=/dev/mtdblock2 ro
serverip=169.254.254.252
ipaddr=169.254.254.253
ethaddr=00:25:31:02:F6:64
cesvcid=UMT3AW7DWKU2HFVY33ER8VKTJ6
ceboardver=PPV2
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial
load_uimage=ext2load usb 0:1 0x800000 /boot/uImage
load_uinitrd=ext2load usb 0:1 0x2100000 /boot/uInitrd
usb_boot=mw 0x800000 0 1; run load_uimage; if run load_uinitrd; then bootm 0x800000 0x2100000; else
usb_bootcmd=run usb_set_bootargs; run usb_boot
bootcmd=usb start; run usb_bootcmd; usb stop; reset

Environment size: 1087/131068 bytes

seems to not recognize the 'usb' cmd in 'usb boot'

CE>> reset


U-Boot 1.1.4 (Sep 28 2009 - 11:55:23) Cloud Engines v2.0 (3.4.16)

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 00690D60

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz 

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB 
DRAM Total size 256MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:128 MB

CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD: PPV2

Streaming disabled 
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0 
CE>> setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial'
CE>> setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
CE>> setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd'
CE>> setenv usb_boot 'mw 0x800000 0 1; run load_uimage; bootm 0x800000'
CE>> setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot'
CE>> setenv bootcmd 'usb start; run usb_bootcmd; usb stop; reset'
CE>> printenv
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
run_diag=yes
console=console=ttyS0,115200
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/mtdblock2 ro
ethmtu=1500
usb0Mode=host
nandEcc=1bit
ethact=egiga0
bootargs=console=ttyS0,115200 root=/dev/mtdblock2 ro
serverip=169.254.254.252
ipaddr=169.254.254.253
ethaddr=00:25:31:02:F6:64
cesvcid=UMT3AW7DWKU2HFVY33ER8VKTJ6
ceboardver=PPV2
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial
load_uimage=ext2load usb 0:1 0x800000 /boot/uImage
load_uinitrd=ext2load usb 0:1 0x2100000 /boot/uInitrd
usb_boot=mw 0x800000 0 1; run load_uimage; bootm 0x800000
usb_bootcmd=run usb_set_bootargs; run usb_boot
bootcmd=usb start; run usb_bootcmd; usb stop; reset

Environment size: 1045/131068 bytes
CE>> boot
Unknown command 'usb' - try 'help'

** Block device usb 0 not supported
## Booting image at 00800000 ...
Bad Magic Number
Unknown command 'usb' - try 'help'


U-Boot 1.1.4 (Sep 28 2009 - 11:55:23) Cloud Engines v2.0 (3.4.16)

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 00690D60

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz 

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB 
DRAM Total size 256MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:128 MB

CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD: PPV2

Streaming disabled 
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0 

NAND read: device 0 offset 0x100000, size 0x200000

Reading data from 0x2ff800 -- 100% complete.
 2097152 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2010-10-19  23:05:02 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1979140 Bytes =  1.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC
CE>>

this bad CRC message is same as i get when internal boot is left alone, (not interupted from console)


Maybe need to change 'usb start' to 'bootext2'

CE>> help
?       - alias for 'help'
base    - print or set address offset
boot    - boot default, i.e., run 'bootcmd'
bootd   - boot default, i.e., run 'bootcmd'
bootext2    dev:boot_part1,boot_part2 addr boot_image linux_dev_name 
bootm   - boot application image from memory
bootp   - boot image via network using BootP/TFTP protocol
bubt    - Burn an image on the Boot Nand Flash.
chpart  - change active partition
cmp     - memory compare
cmpm    - Compare Memory
cp      - memory copy
cpumap - Display CPU memory mapping settings.
crc32   - checksum calculation
date    - get/set/reset date & time
dclk    - Display the MV device CLKs.
dhcp    - invoke DHCP client to obtain IP/boot params
diskboot- boot from IDE device
echo    - echo args to console
eeprom  - EEPROM sub-system
erase   - erase FLASH memory
ext2load- load binary file from a Ext2 filesystem
ext2ls  - list files in a directory (default /)
fi      - Find value in the memory.
flinfo  - print FLASH memory information
fsinfo  - print information about filesystems
fsload  - load binary file from a filesystem image
g       - start application at cached address 'addr'(default addr 0x40000)
go      - start application at address 'addr'
help    - print online help
icrc32  - checksum calculation
ide     - IDE sub-system
iloop   - infinite loop on address range
imd     - i2c memory display
imm[.b, .s, .w, .l]     - i2c memory modify (auto-incrementing)
imw     - memory write (fill)
inm     - memory modify (constant address)
iprobe  - probe to discover valid I2C chip addresses
ir      - reading and changing MV internal register values.
loop    - infinite loop on address range
ls      - list files in a directory (default /)
map     - Diasplay address decode windows
md      - memory display
me      - PCI master enable
mm      - memory modify (auto-incrementing)
mp      - map PCI BAR
mtdparts- define flash/nand partitions
mtest   - simple RAM test
mv_diag - perform board diagnostics
mw      - memory write (fill)
nand                   - NAND sub-system
nboot   - boot from NAND device
nbubt   - Burn a boot loader image on the Boot Nand Flash.
nm      - memory modify (constant address)
pci     - list and access PCI Configuration Space
phyRead - Read PCI-E Phy register
pciePhyWrite    - Write PCI-E Phy register
phyRead - Read Phy register
phyWrite        - Write Phy register
ping    - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
protect - enable or disable FLASH write protection
rarpboot- boot image via network using RARP/TFTP protocol
reset   - Perform RESET of the CPU
resetenv        - Return all environment variable to default.
run     - run commands in an environment variable
saveenv - save environment variables to persistent storage
se      - PCI Slave enable
setenv  - set environment variables
sflash  - read, write or erase the external SPI Flash.
sg      - scanning the PHYs status
sp      - Scan PCI bus.
tftpboot- boot image via network using TFTP protocol
version - print monitor version

Edited 1 time(s). Last edit at 11/23/2020 06:34PM by mrmazak.

Maybe I should try to make rootfs again. This line seems to indicate the usb stick is not recognized.

It is ext3, like Debian release thread says.

CE>> boot
Unknown command 'usb' - try 'help'

** Block device usb 0 not supported
## Booting image at 00800000 ...
Bad Magic Number
Unknown command 'usb' - try 'help'

mrmazak,

This stock u-boot version does not support USB drive. So with this Pogo E02 if you cannot login with serial console because stock FW is corrupted, then there 2 alternatives (actually 3 but I don't want to muddy the water for now).

1. Boot the kernel with tftpboot. The setenvs posted previously will be changed to a slightly diffrent set of commands.

tftpboot will require you to set up tftp server in the box that you are using for serial console. It must be a Linux box.

2. Flash new u-boot in serial console, and boot into the Debian rootfs that you've created.

Flash new u-boot does not require further set up, you are ready to do that. The Debian rootfs must be as is after creation (Step 4 should not be done, since this is new u-boot).

Let me come back and post the command to flash in serial console.

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

different usb drive with rootfs confirmed to work on my nsa320 ( i know it would not boot) gives same 'block device usb 0 not supported' message


didn't see your earlier response, ignore this post. hahaha



Edited 1 time(s). Last edit at 11/24/2020 05:25PM by mrmazak.

Quote

2. Flash new u-boot in serial console, and boot into the Debian rootfs that you've created.

On 2nd thought, flashing directly like this has some risk. If for whatever reason it does not work, then the box will be bricked. And then you will need JTAG to unbrick.

Doing tftpboot is safer, in that you don't touch u-boot envs and u-boot itself during the attempt. After you have booted into Debian on USB, then you can flash new u-boot. At this time, everything will have been checked out. And so the flashing will have minimal risk.


Think about the above and let me know.

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

Tftp method might be better option. Gives more room for recovery before needing JTAG.

I have setup tftp server and found an example on using it to boot kernel, but have not tried it yet.

Has anything from this guide need updated?

https://forum.doozan.com/read.php?3,28772,29034#msg-29034

> I have setup tftp server and found an example on
> using it to boot kernel, but have not tried it
> yet.
>
> Has anything from this guide need updated?
>
> https://forum.doozan.com/read.php?3,28772,29034#msg-29034

Right on! that's in the Wiki thread. And written specifically for the Pogo E02.

Quote

Booting Debian on Pogoplug

How to set up U-Boot for booting in multiple drives configuration
Backup and Restore NAND mtds
UART Booting HowTo for Selected Kirkwood Devices
Migrating from Arch to Debian?
How to boot new Debian rootfs using stock u-boot tftp - Pogo E02
How to boot new Debian rootfs on USB using stock u-boot - NSA325
How to boot Debian rootfs on a GPT HDD with stock u-boot (kernel files stored in HDD raw sector), 2nd HowTo post
How to boot Pogo V3 from SATA (to unbrick), 2nd How to Post
How to install U-Boot for Pogoplug V3 (OXNAS OX820) from OpenWRT

You can use the guide as is.

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

This Pogo is failing to connect to my network. I find out.

During the tftp load it just keeps trying and then stops with message
Retry count exceeded; starting again
*** ERROR: 'eth1addr' not set



So I added setenv 'eth1addr' (router ip)

This stopped the error message, but still does not load from tftp.

Router log does not show any connection to box either.......
Correction: router log does show a connection. At least after I did setenv eth1addr (to same mac addr listed in ethaddr)

So what should eth1 be set as?

I have tried to match it to ip address
Tried match it to router address
Mac address
None of these worked.



Edited 1 time(s). Last edit at 11/25/2020 06:44AM by mrmazak.

You have eth only. Don't add eth1.

ethaddr is already set.

undefine eth1

CE:> setenv eth1addr

-----------------

Make sure your tftp server is on, the files are in the correct place, make sure your serverip is the tftp server's address



Edited 3 time(s). Last edit at 11/25/2020 09:40AM by daviddyer.

When I use term on other box on network, and I do tftp $server_ip
I get the tftp prompt
Then I command 'get uImage' the file is transfered

I can only assume that the tftpboot command should have been able to connect also.

Maybe need to chown the files or something. I'll try that after work.

Thanks

Try it in a few more steps.

set serverip, ipaddr, put your usb flash drive (rootfs) to the usb port of pogo E02

then

tftp 0x800000 uImage (the one with dtb built-in)
tftp 0x1100000 uInitrd
bootm 0x800000 0x1100000

Yes, like David said. Dont use command that does not allow you to see where it failed in each step.

The box MAC address must be ethaddr (ethaddr1 is irrelevant). So your settings are already correct:

ethprime=egiga0
ethact=egiga0
ethaddr=00:25:31:02:F6:64

And you can also test the server connection before do the tftp transfer.

Assuming your router is x.x.x.1, and your tftp server box is x.x.x.y, then

ping x.x.x.1
ping x.x.x.y

And then do

setenv ipaddr x.x.x.x
setenv serverip x.x.x.y 
tftp 0x800000 uImage
tftp 0x1100000 uInitrd

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

fantastic. I of cource made a mistake.
I cp the kernel files to "tftproot" folder, and servers root is setup in "tftpboot" folder.

fixed that and kernel loaded, but is halted at "booting Kernel"

Welcome to minicom 2.7.1

OPTIONS: I18n 
Compiled on Aug 13 2017, 15:25:34.
Port /dev/ttyS0, 17:27:36

Press CTRL-A Z for help on special keys



U-Boot 1.1.4 (Sep 28 2009 - 11:55:23) Cloud Engines v2.0 (3.4.16)

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 00690D60

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz 

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB 
DRAM Total size 256MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:128 MB
*** Warning - bad CRC or NAND, using default environment


CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD (GUESSED): PP_V2

Streaming disabled 
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0 
CE>> setenv mtdids 'nand0=orion_nand'
CE>> setenv partition 'nand0,2'
CE>> setenv bootargs 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)'
CE>> setenv ipaddr 192.168.1.17
CE>> setenv serverip 192.168.1.16
CE>> tftp 0x800000 uImage
Using egiga0 device
TFTP from server 192.168.1.16; our IP address is 192.168.1.17
Filename 'uImage'.
Load address: 0x800000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##############################################################
done
Bytes transferred = 4973786 (4be4da hex)
CE>> tftp 0x1100000 uInitrd
Using egiga0 device
TFTP from server 192.168.1.16; our IP address is 192.168.1.17
Filename 'uInitrd'.
Load address: 0x1100000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #############
done
Bytes transferred = 9713936 (943910 hex)
CE>> printenv
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
run_diag=yes
stdin=serial
stdout=serial
stderr=serial
console=console=ttyS0,115200
mainlineLinux=no
CASset=min
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
MALLOC_len=1
ethprime=egiga0
netbsd_en=no
vxworks_en=no
bootargs_root=root=/dev/mtdblock2 ro
bootcmd=nand read.e 0x800000 0x100000 0x200000; setenv bootargs $(console) $(bootargs_root); bootm 0x800000
ceboardver=PP_V2
bootdelay=3
disaMvPnp=no
ethaddr=00:50:43:00:02:02
ethmtu=1500
usb0Mode=host
nandEcc=1bit
ethact=egiga0
mtdids=nand0=orion_nand
partition=nand0,2
bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
filesize=943910
fileaddr=1100000
netmask=255.255.0.0
ipaddr=192.168.1.17
serverip=192.168.1.16

Environment size: 892/131068 bytes
CE>> bootm 0x800000 0x1100000
## Booting image at 00800000 ...
   Image Name:   Linux-5.2.9-kirkwood-tld-1
   Created:      2020-11-23  23:08:18 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4973722 Bytes =  4.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000 ...
   Image Name:   initramfs-5.2.9-kirkwood-tld-1
   Created:      2019-08-25   2:22:50 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9713872 Bytes =  9.3 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

I will leave it here for little time and see if it gives any life signs.

no progress.

the console stops receiving data. maybe the kernel files are not created right.



Edited 3 time(s). Last edit at 11/25/2020 09:12PM by mrmazak.

i did bad things t this thing now.

got frustrated and did

tftpboot 0x800000 pogo.kwb(short name I put for 2017 bootloader)

nand erase 0x0 0xa4fff

nand write.e 0x800000 0x0 0x80000

addresses found on openwrt flashing directions site. Then did reset. Now I get no response on serial console.

now i wil just stop, as i thin there is more more to do??? Maybe jtag, but that still needs console output i thought.

mrmazak,

> addresses found on openwrt flashing directions
> site.

Really bad move. You should have asked how to do the number 2 on my list

Quote

mrmazak,

This stock u-boot version does not support USB drive. So with this Pogo E02 if you cannot login with serial console because stock FW is corrupted, then there 2 alternatives (actually 3 but I don't want to muddy the water for now).

1. Boot the kernel with tftpboot. The setenvs posted previously will be changed to a slightly diffrent set of commands.

tftpboot will require you to set up tftp server in the box that you are using for serial console. It must be a Linux box.

2. Flash new u-boot in serial console, and boot into the Debian rootfs that you've created.

Flash new u-boot does not require further set up, you are ready to do that. The Debian rootfs must be as is after creation (Step 4 should not be done, since this is new u-boot).

Let me come back and post the command to flash in serial console.

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



Edited 1 time(s). Last edit at 11/25/2020 10:39PM by bodhi.

Power down (pull out the power cord). And power up again. Does it now show any sign of life?

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

Yes, there is one quick flash of the LED when plugged in. Not from the big led(led4), from the lan port lights and one on the board(led3)

Lan port also has lights while connected



Edited 2 time(s). Last edit at 11/26/2020 05:48AM by mrmazak.

Too bad! you were very close to successful booting Debian in this post

CE>> bootm 0x800000 0x1100000
## Booting image at 00800000 ...
   Image Name:   Linux-5.2.9-kirkwood-tld-1
   Created:      2020-11-23  23:08:18 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4973722 Bytes =  4.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000 ...
   Image Name:   initramfs-5.2.9-kirkwood-tld-1
   Created:      2019-08-25   2:22:50 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9713872 Bytes =  9.3 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Quote

Yes, there is one quick flash of the LED when plugged in. Not from the big led(led4), from the lan port lights and one on the board(led3)

u-boot was corrupted in NAND. So now it is JTAG time.

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

Yeah, I got ahead of my knowledge of this device.

I did setup jtag as the guide says.

https://forum.doozan.com/read.php?3,21789,page=1

But planed to do it from the pi itself. So I think 2 terminal sessions is correct?. Not three. So telnet step would not be relevant?


I don't have a 8 pin plug for the connection . And to buy the ones I found on amazon would be same cost as this device was $8.

So I am thinking about just soldering to the pins.


I did. Dry run the setup, and I got some errors in terminal about depricated settings. I aought to post them here and ask if it would be ok to continue.

Yes, post in that thread so joerg can help you.

https://forum.doozan.com/read.php?3,21789,page=1

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