Dies ist eine mobil optimierte Seite, die schnell lädt. Wenn Sie die Seite ohne Optimierung laden möchten, dann klicken Sie auf diesen Text.

Reparatur Pogo E02 mittels Raspi als Jtag

    Nobody is reading this thread right now.
AW: Reparatur Pogo E02 mittels Raspi als Jtag

iregdnwie kann ich keine verbindung mit dem ttl herstellen.
ich mach die schritte jetzt mit dem zweiten pogo. wenn ich dann mit dem ttl nicht drauf komme, liegt es an Win10.
Ich berichte
 
AW: Reparatur Pogo E02 mittels Raspi als Jtag

Du musst schauen welchen Comport dein TTY/USB Adapter in Win10 belegt und den rufst du mit putty auf. (Einstellungen beachten in Windows: 115000 /8/N/1)
Ist oft Standardmäßig auf 9600 eingestellt, da bekommst du nix raus in putty!
--joerg_999
 
AW: Reparatur Pogo E02 mittels Raspi als Jtag

​Hallo jierg_999,

der zweite pogo (pink E02) will nicht geflsht werden:
Open On-Chip Debugger> pogo_init
> soft_reset_halt
requesting target halt and executing a soft reset
feroceon.cpu: target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x600000d3 pc: 0x00000000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
> nand probe 0
NAND flash device 'NAND 128MiB 3.3V 8-bit (Hynix)' found
> nand erase 0 0x0 0xa0000
erased blocks 0 to 4 on NAND flash device #0 'NAND 128MiB 3.3V 8-bit'
> nand write 0 uboot.kwb 0 oob_softecc_kw
invalid mode value encountered 24
cpsr contains invalid mode value - communication failure
error executing hosted NAND write
Unable to write data to NAND device
failed writing file uboot.kwb to NAND flash 0 at offset 0x00032800
timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS: 0
Polling target feroceon.cpu failed, trying to reexamine
Embedded ICE version 0
feroceon.cpu: hardware has 1 breakpoint/watchpoint unit
unexpected Feroceon EICE version signature

2.versuch:
Open On-Chip Debugger> pogo_init
> soft_reset_halt
requesting target halt and executing a soft reset
feroceon.cpu: target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x600000d3 pc: 0x00000000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
> nand probe 0
NAND flash device 'NAND 128MiB 3.3V 8-bit (Hynix)' found
> nand erase 0 0x0 0xa0000
erased blocks 0 to 4 on NAND flash device #0 'NAND 128MiB 3.3V 8-bit'
> nand write 0 uboot.kwb 0 oob_softecc_kw
timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS: 0
Unable to write data to NAND device
failed writing file uboot.kwb to NAND flash 0 at offset 0x0002c000
>

3. versuch:
Open On-Chip Debugger> pogo_init
feroceon.cpu: target state: halted
target halted in Thumb state due to debug-request, current mode: Supervisor
cpsr: 0x400000f3 pc: 0xffff0a42
MMU: enabled, D-Cache: enabled, I-Cache: enabled
> pogo_init
> soft_reset_halt
requesting target halt and executing a soft reset
feroceon.cpu: target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x400000d3 pc: 0x00000000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
> nand probe 0
NAND flash device 'NAND 128MiB 3.3V 8-bit (Hynix)' found
> nand erase 0 0x0 0xa0000
erased blocks 0 to 4 on NAND flash device #0 'NAND 128MiB 3.3V 8-bit'
> nand write 0 uboot.kwb 0 oob_softecc_kw
memory read caused data abort (address: 0xd8000000, size: 0x1, count: 0x1)
timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS: 0
Unable to write data to NAND device
failed writing file uboot.kwb to NAND flash 0 at offset 0x0003c000
Ist beim Pinken Pogo irgendwas anders?
PS:Hab das TTL diesmal nicht an con 3 angeschlossen.

VG, Spyer
 
Zuletzt bearbeitet von einem Moderator:
AW: Reparatur Pogo E02 mittels Raspi als Jtag

Nein der Pink Pogo ist ein E02 sollte also passen.
Hat das flashen beim 1.Pogo geklappt? - denn dann sollten die Verkabelung, deine Rechte und die Symlinks passen.

Starte openOCD mal neu + reset vom Pogo, möglicherweise hat sich da was aufgehängt
 
Zuletzt bearbeitet:
AW: Reparatur Pogo E02 mittels Raspi als Jtag

Hallo joerg_999,

der pinke pogo hat jetzt das im letzten versuch ausgegeben:
Open On-Chip Debugger> pogo_init
feroceon.cpu: target state: halted
target halted in Thumb state due to debug-request, current mode: Supervisor
cpsr: 0x400000f3 pc: 0xffff0a42
MMU: enabled, D-Cache: enabled, I-Cache: enabled
> pogo_init
feroceon.cpu: target state: halted
target halted in Thumb state due to debug-request, current mode: Supervisor
cpsr: 0x200000f3 pc: 0xffff0880
MMU: enabled, D-Cache: enabled, I-Cache: enabled
> pogo_init
> soft_reset_halt
requesting target halt and executing a soft reset
feroceon.cpu: target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x200000d3 pc: 0x00000000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
> nand probe 0
NAND flash device 'NAND 128MiB 3.3V 8-bit (Hynix)' found
> nand erase 0 0x0 0xa0000
erased blocks 0 to 4 on NAND flash device #0 'NAND 128MiB 3.3V 8-bit'
> nand write 0 uboot.kwb 0 oob_softecc_kw
timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS: 13
error executing hosted NAND write
Unable to write OOB data to NAND device
failed writing file uboot.kwb to NAND flash 0 at offset 0x0004c800
Jazelle debug entry -- BROKEN!
invalid mode value encountered 0
ThumbEE -- incomplete support
timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS: 10
Polling target feroceon.cpu failed, trying to reexamine
Embedded ICE version 0
feroceon.cpu: hardware has 1 breakpoint/watchpoint unit
> pogo_init
feroceon.cpu: target state: halted
target halted in Thumb state due to debug-request, current mode: Undefined instruction
cpsr: 0x200000fb pc: 0xffff0a8a
MMU: enabled, D-Cache: enabled, I-Cache: enabled
> pogo_init
> soft_reset_halt
requesting target halt and executing a soft reset
feroceon.cpu: target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x200000d3 pc: 0x00000000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
> nand probe 0
NAND flash device 'NAND 128MiB 3.3V 8-bit (Hynix)' found
> nand erase 0 0x0 0xa0000
erased blocks 0 to 4 on NAND flash device #0 'NAND 128MiB 3.3V 8-bit'
> nand write 0 uboot.kwb 0 oob_softecc_kw
timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS: 0
wrote file uboot.kwb to NAND flash 0 up to offset 0x00080000 in 15.336334s (33.385 KiB/s)

Das sieht so aus als hätte der was geschrieben, aber da blinks nichts.
Ich versuche mal den "normalen" pogo mit ttl zu ereichen und mache dann morgen weiter.

Danke für deine hilfe

VG, Spyer
 
AW: Reparatur Pogo E02 mittels Raspi als Jtag

OK, gerne geschehen.
Gute Nacht

PS: wrote file uboot.kwb to NAND flash 0 up to offset 0x00080000 in 15.336334s (33.385 KiB/s) .... das sieht ja ganz gut aus.
 
AW: Reparatur Pogo E02 mittels Raspi als Jtag

kurz Rückmeldung zum "normalen pogo":
Ich habe beim ttl txd rxd vertauscht :emoticon-0138-think
U-Boot 2015.10-tld-1 (Nov 06 2015 - 15:46:25 -0800)
Pogo E02


SoC: Kirkwood 88F6281_A0
DRAM: 256 MiB (ECC not enabled)
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
Error: egiga0 address not set.


No link on egiga0
ping failed; host 192.168.1.100 is not alive
Hit any key to stop autoboot: 0

Der scheint wieder belebt zu sein. Jetzt noch der pinke und alles ist gut aber morgen erst wieder.

Edit:
Ist da jetzt der bootloader mit dem internen oder externen bootloader drauf?
PogoE02> printenvarcNumber=2097
baudrate=115200
bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
if_netconsole=ping $serverip
ipaddr=192.168.1.10
led_error=orange blinking
led_exit=green off
led_init=green blinking
machid=0x831
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then boo tm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
preboot=run if_netconsole start_netconsole
preboot_nc=run if_netconsole start_netconsole
rootdelay=10
rootfstype=ext3
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
serverip=192.168.1.100
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$root delay rootfstype=$rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$ro otdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$root delay rootfstype=$rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; se tenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
usb_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then boo tm 0x800000 0x1100000; else bootm 0x800000; fi
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1


Environment size: 2237/131068 bytes

edit2: der pinke pogo lebt auch wieder
U-Boot 2015.10-tld-1 (Nov 06 2015 - 15:46:25 -0800)Pogo E02


SoC: Kirkwood 88F6281_A0
DRAM: 256 MiB (ECC not enabled)
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
Hit any key to stop autoboot: 0
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
UBI: attaching mtd1 to ubi0
UBI: scanning is finished
UBI: empty MTD device detected
UBI: attached mtd1 (name "mtd=3", size 91 MiB) to ubi0
UBI: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 512
UBI: VID header offset: 512 (aligned 512), data offset: 2048
UBI: good PEBs: 727, bad PEBs: 1, corrupted PEBs: 0
UBI: user volume: 0, internal volumes: 1, max. volumes count: 128
UBI: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 0
UBI: available PEBs: 704, total reserved PEBs: 23, PEBs reserved for bad PEB handling: 19
Error reading superblock on volume 'rootfs' errno=-22!
ubifsmount - mount UBIFS volume


Usage:
ubifsmount <volume-name>
- mount 'volume-name' volume
** Bad device usb 0 **
** Bad device usb 1 **
** Bad device usb 2 **
** Bad device usb 3 **
** Bad device usb 0 **
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: ......... done.
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...




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 ... OK
OK


Starting kernel ...


Uncompressing Linux............................................................................................................................ done, booting the kernel.
[ 0.000000] Linux version 2.6.22.18 (bdietrich@buildman) (gcc version 4.2.1) #81 Tue Oct 19 16:05:00 PDT 2010
[ 0.000000] CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053177
[ 0.000000] Machine: Feroceon-KW
[ 0.000000] Using UBoot passing parameters structure
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] CPU0: D VIVT write-back cache
[ 0.000000] CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
[ 0.000000] CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
[ 0.000000] Built 1 zonelists. Total pages: 65024
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/mtdblock2 ro
[ 0.000000] PID hash table entries: 1024 (order: 10, 4096 bytes)
[ 0.000000] Console: colour dummy device 80x30
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.010000] Memory: 256MB 0MB 0MB 0MB = 256MB total
[ 0.010000] Memory: 255872KB available (3592K code, 253K data, 124K init)
[ 0.250000] Mount-cache hash table entries: 512
[ 0.250000] CPU: Testing write buffer coherency: ok
[ 0.250000] NET: Registered protocol family 16
[ 0.250000]
[ 0.250000] CPU Interface
[ 0.250000] -------------
[ 0.250000] SDRAM_CS0 ....base 00000000, size 256MB
[ 0.250000] SDRAM_CS1 ....disable
[ 0.250000] SDRAM_CS2 ....disable
[ 0.250000] SDRAM_CS3 ....disable
[ 0.250000] PEX0_MEM ....base e8000000, size 128MB
[ 0.250000] PEX0_IO ....base f2000000, size 1MB
[ 0.250000] INTER_REGS ....base f1000000, size 1MB
[ 0.250000] NFLASH_CS ....base fa000000, size 2MB
[ 0.250000] SPI_CS ....base f4000000, size 16MB
[ 0.250000] BOOT_ROM_CS ....no such
[ 0.250000] DEV_BOOTCS ....no such
[ 0.250000] CRYPT_ENG ....base f0000000, size 2MB
[ 0.250000]
[ 0.250000] Marvell Development Board (LSP Version KW_LSP_4.2.7_patch21_with_rx_desc_tuned)-- SHEEVA PLUG Soc: 88F6281 A0 LE
[ 0.250000]
[ 0.250000] Detected Tclk 200000000 and SysClk 400000000
[ 0.250000] MV Buttons Device Load
[ 0.250000] Marvell USB EHCI Host controller #0: c0652600
[ 0.750000] PEX0 interface detected no Link.
[ 0.750000] PCI: bus0: Fast back to back transfers enabled
[ 0.750000] SCSI subsystem initialized
[ 0.750000] usbcore: registered new interface driver usbfs
[ 0.750000] usbcore: registered new interface driver hub
[ 0.750000] usbcore: registered new device driver usb
[ 0.750000] NET: Registered protocol family 2
[ 0.760000] Time: kw_clocksource clocksource has been installed.
[ 0.850000] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.850000] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.850000] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.850000] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.850000] TCP reno registered
[ 0.880000] RTC has been updated!!!
[ 0.880000] RTC registered
[ 0.880000] Use the XOR engines (acceleration) for enhancing the following functions:
[ 0.880000] o RAID 5 Xor calculation
[ 0.880000] o kernel memcpy
[ 0.880000] o kenrel memzero
[ 0.880000] Number of XOR engines to use: 4
[ 0.880000] cesadev_init(c00117b0)
[ 0.880000] mvCesaInit: sessions=640, queue=64, pSram=f0000000
[ 0.880000] MV Buttons Driver Load
[ 0.880000] squashfs: version 3.3 (2007/10/31) Phillip Lougher
[ 0.880000] squashfs: LZMA suppport for slax.org by jro
[ 0.880000] JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.880000] io scheduler noop registered
[ 0.880000] io scheduler anticipatory registered (default)
[ 0.900000] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
[ 0.900000] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[ 0.910000] RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
[ 0.920000] Loading Marvell Ethernet Driver:
[ 0.920000] o Cached descriptors in DRAM
[ 0.920000] o DRAM SW cache-coherency
[ 0.930000] o Single RX Queue support - ETH_DEF_RXQ=0
[ 0.930000] o Single TX Queue support - ETH_DEF_TXQ=0
[ 0.940000] o TCP segmentation offload enabled
[ 0.940000] o Receive checksum offload enabled
[ 0.950000] o Transmit checksum offload enabled
[ 0.950000] o Network Fast Processing (Routing) supported
[ 0.960000] o Driver ERROR statistics enabled
[ 0.960000] o Driver INFO statistics enabled
[ 0.970000] o Proc tool API enabled
[ 0.970000] o Rx descripors: q0=128
[ 0.970000] o Tx descripors: q0=532
[ 0.980000] o Loading network interface(s):
[ 0.990000] o eth0, ifindex = 1, GbE port = 0
[ 0.990000] o eth1, ifindex = 2, GbE port = 1
[ 1.000000]
[ 1.000000] mvFpRuleDb (cfdf6000): 2048 entries, 8192 bytes
[ 1.000000] Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
[ 1.010000] Copyright (c) 1999-2006 Intel Corporation.
[ 1.020000] e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
[ 1.020000] e100: Copyright(c) 1999-2006 Intel Corporation
[ 1.030000]
[ 1.030000] Warning Sata is Powered Off
[ 1.030000] NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
[ 1.040000] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
[ 1.050000] Scanning device for bad blocks
[ 1.080000] Bad eraseblock 465 at 0x03a20000
[ 1.110000] Using static partition definition
[ 1.110000] Creating 4 MTD partitions on "nand_mtd":
[ 1.120000] 0x00000000-0x00100000 : "u-boot"
[ 1.120000] 0x00100000-0x00500000 : "uImage"
[ 1.130000] 0x00500000-0x02500000 : "root"
[ 1.130000] 0x02500000-0x08000000 : "data"
[ 1.140000] ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
[ 1.140000] ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
[ 1.180000] ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
[ 1.200000] ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[ 1.200000] usb usb1: configuration #1 chosen from 1 choice
[ 1.210000] hub 1-0:1.0: USB hub found
[ 1.210000] hub 1-0:1.0: 1 port detected
[ 1.330000] USB Universal Host Controller Interface driver v3.0
[ 1.610000] usb 1-1: new high speed USB device using ehci_marvell and address 2
[ 1.760000] usb 1-1: configuration #1 chosen from 1 choice
[ 1.760000] hub 1-1:1.0: USB hub found
[ 1.770000] hub 1-1:1.0: 4 ports detected
[ 1.880000] usbcore: registered new interface driver usblp
[ 1.880000] drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
[ 1.890000] Initializing USB Mass Storage driver...
[ 1.890000] usbcore: registered new interface driver usb-storage
[ 1.900000] USB Mass Storage support registered.
[ 1.910000] mice: PS/2 mouse device common for all mice
[ 1.910000] i2c /dev entries driver
[ 1.910000] Linux telephony interface: v1.00
[ 1.920000] md: linear personality registered for level -1
[ 1.920000] md: raid0 personality registered for level 0
[ 1.930000] md: raid1 personality registered for level 1
[ 2.100000] raid6: int32x1 97 MB/s
[ 2.270000] raid6: int32x2 114 MB/s
[ 2.440000] raid6: int32x4 122 MB/s
[ 2.610000] raid6: int32x8 110 MB/s
[ 2.610000] raid6: using algorithm int32x4 (122 MB/s)
[ 2.610000] md: raid6 personality registered for level 6
[ 2.620000] md: raid5 personality registered for level 5
[ 2.620000] md: raid4 personality registered for level 4
[ 2.630000] raid5: measuring checksumming speed
[ 2.680000] arm4regs : 1084.000 MB/sec
[ 2.730000] 8regs : 754.800 MB/sec
[ 2.780000] 32regs : 899.600 MB/sec
[ 2.780000] raid5: using function: arm4regs (1084.000 MB/sec)
[ 2.790000] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
[ 2.790000] dm_crypt using the OCF package.
[ 2.800000] sdhci: Secure Digital Host Controller Interface driver
[ 2.800000] sdhci: Copyright(c) Pierre Ossman
[ 2.810000] usbcore: registered new interface driver usbhid
[ 2.810000] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
[ 2.820000] TCP cubic registered
[ 2.820000] NET: Registered protocol family 1
[ 2.830000] NET: Registered protocol family 17
[ 2.830000] md: Autodetecting RAID arrays.
[ 2.840000] md: autorun ...
[ 2.840000] md: ... autorun DONE.
[ 4.940000] Empty flash at 0x009ac208 ends at 0x009ac800
[ 9.220000] VFS: Mounted root (jffs2 filesystem) readonly.
[ 9.230000] Freeing init memory: 124K
init started: BusyBox v1.7.0 (2008-02-26 19:25:17 IST)
starting pid 267, tty '': '/etc/init.d/rcS'
[ 11.450000] eth0: started
udhcpc (v1.7.0) started
HWADDR 00 0x25 0x31 0x04 0x8c 0x1e
PIP0 140
PIP1 30
cat: can't open '/etc/resolv.conf': No such file or directory
route: SIOCDELRT: No such process
grep: /etc/resolv.conf: No such file or directory
Sending discover...
Sending discover...
Sending discover...
HWADDR 00 0x25 0x31 0x04 0x8c 0x1e
PIP0 140
PIP1 30
No lease, forking to background
starting pid 370, tty '': '/bin/sh'
-sh-4.3#

Hier läd der aber ein weiteres image, was der "normale" pogo nicht macht.
hmmm...
 
Zuletzt bearbeitet von einem Moderator:
AW: Reparatur Pogo E02 mittels Raspi als Jtag

Das ist möglicherweise noch das original Pogo Betriebssystem drauf und das lädt er (soweit kein USB Stick angesteckt ist):
U-Boot 1.1.4 (Sep 28 2009 - 11:55:23) Cloud Engines v2.0 (3.4.16)
Das ist eine Funktion die geht bei den neuesten uboots......

Beim anderen Pogo ist das original OS gelöscht oder möglicherweise durch ein Rescuesystem ersetzt welches aber erst mit den richtigen Startparametern (envs) hochkommt.


Zu deiner Frage: Die neuen envs sind dafür ausgelegt um die aktuellen vorgefertigten Filesysteme vom doozan Forum (also wie in meiner Anleitung) zu booten.
Wenn du was älteres booten möchtest musst du zumindestens machid und arcNumber und möglicherweise ein paar andere Dinge anpassen.

Du meinst hier nicht externer bootloader sondern extern geladenes dtb File oder im Kernel integriertes dtb file.
Lies dir dazu nochmals entweder meine Beschreibungen oder die original Threads im doozan Forum durch.
h**p://forum.doozan.com/read.php?2,12096 ab Punkt 4

Noch etwas:
Wenn du den Pogo mit dem Originalsystem sichern möchtest gehst du folgendermaßen vor:
# How To backup mtd0 to mtd3.

First verify:
fw_printenv mtdparts
# expected output
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
cat /proc/mtd
# expected output
dev: size erasesize name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 02000000 00020000 "rootfs"
mtd3: 05b00000 00020000 "data"
# and then nanddump:
# Beispiel:
# nanddump --noecc --omitoob -l 0x80000 -f /tmp/mtd0-dump /dev/mtd0
nanddump --noecc --omitoob -f mtd0 /dev/mtd0
nanddump --noecc --omitoob -f mtd1 /dev/mtd1
nanddump --noecc --omitoob -f mtd2 /dev/mtd2
nanddump --noecc --omitoob -f mtd3 /dev/mtd3

# How To restore mtd1 to mtd3.

# Prerequisite:
# Check for bad blocks. There should be none shown from the following command:
dmesg | grep -i bad
# Flash mtd1 mtd2 mtd3:
nandwrite --noecc /dev/mtd1 mtd1
# Expected output
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000
...
Writing data to block 30 at offset 0x3c0000
Writing data to block 31 at offset 0x3e0000
nandwrite --noecc /dev/mtd2 mtd2
# Expected output
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000
...
Writing data to block 254 at offset 0x1fc0000
Writing data to block 255 at offset 0x1fe0000
nandwrite --noecc /dev/mtd3 mtd3
# Expected output
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000
...
Writing data to block 726 at offset 0x5ac0000
Writing data to block 727 at offset 0x5ae0000
# There should be no error occurred


--joerg_999
 
Zuletzt bearbeitet von einem Moderator:
Hallo, funktioniert die Raspi Lösung als Jtag auch mit einer Seagate Dockstar?
Falls ja, welche Änderungen am Aufbau müssen vorgenommen werden?

Danke im voraus.
 
Aber sicher, wurde bereits auch schon durchgeführt.
Die Pinbelegung muss an die Dockstar angepasst werden und man benötigt die dockstar.cfg
Code: 
================================================================================
##    JTAG connector - Dockstar, GoflexNet, GoflexHome                        ##
================================================================================

Dockstar plug J1 10 pin, Serial Link/JTAG (Pin counting pairwise, and original)
function               name pin org   pin name function color RS232
output                 VCC  1   1 10  2   GND           blk
Test Reset, active low TRST 3   2  9  4   TxD  3.3 V    blu
Test Data Input        TDI  5   3  8  6   RxD  3.3 V    wht
Test Mode Select       TMS  7   4  7  8   SRST System Reset, active low
Test Clock             TCK  9   5  6 10   TDO  Test Data Output
--------------------------------------------------------------------------------
Code: 
pi@raspberrypi ~ $ cat /usr/share/openocd/scripts/board/dockstar.cfg
# Marvell SheevaPlug

# I'm using a wiggler compatible cable
source [find interface/sysfsgpio-raspberrypi.cfg]
source [find target/feroceon.cfg]
adapter_khz 200
adapter_nsrst_delay 500

$_TARGETNAME configure \
    -work-area-phys 0x100000 \
    -work-area-size 65536 \
    -work-area-backup 0

# Disabled for the dockstar 
#arm7_9 dcc_downloads enable

# this assumes the hardware default peripherals location before u-Boot moves it
set _FLASHNAME $_CHIPNAME.flash
nand device $_FLASHNAME orion 0 0xd8000000

proc dockstar_init { } {

    # We need to assert DBGRQ while holding nSRST down.
    # However DBGACK will be set only when nSRST is released.
    # Furthermore, the JTAG interface doesn't respond at all when
    # the CPU is in the WFI (wait for interrupts) state, so it is
    # possible that initial tap examination failed.  So let's
    # re-examine the target again here when nSRST is asserted which
    # should then succeed.
    jtag_reset 0 1
    feroceon.cpu arp_examine
    halt 0
    jtag_reset 0 0
    wait_halt

    arm mcr 15 0 0 1 0 0x00052078

    mww 0xD0001400 0x43000C30
    mww 0xD0001404 0x39543000
    mww 0xD0001408 0x22125451
    mww 0xD000140C 0x00000833
    mww 0xD0001410 0x000000CC
    mww 0xD0001414 0x00000000
    mww 0xD0001418 0x00000000
    mww 0xD000141C 0x00000C52
    mww 0xD0001420 0x00000042
    mww 0xD0001424 0x0000F17F
    mww 0xD0001428 0x00085520
    mww 0xD000147c 0x00008552

    # 1st bank is 128 MB
    mww 0xD0001504 0x07FFFFF1
    # 2nd bank of DRAM is not used
    mww 0xD0001508 0x00000000
    mww 0xD000150C 0x00000000
    # Commented the 3 following    lines
    #mww 0xD0001504 0x0FFFFFF1
    #mww 0xD0001508 0x10000000
    #mww 0xD000150C 0x0FFFFFF5
    mww 0xD0001514 0x00000000
    mww 0xD000151C 0x00000000
    mww 0xD0001494 0x003C0000
    mww 0xD0001498 0x00000000
    mww 0xD000149C 0x0000F80F
    mww 0xD0001480 0x00000001
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000
    mww 0xD0020204 0x00000000

    mww 0xD0010000 0x01111111
    mww 0xD0010004 0x11113322
    mww 0xD0010008 0x00001111

    mww 0xD0010418 0x003E07CF
    mww 0xD001041C 0x000F0F0F
    mww 0xD0010470 0x01C7D943

}

proc sheevaplug_reflash_uboot { } {

    # reflash the u-Boot binary and reboot into it
    sheevaplug_init
    nand probe 0
    nand erase 0 0x0 0xa0000
    nand write 0 uboot.bin 0 oob_softecc_kw
    resume

}

proc sheevaplug_reflash_uboot_env { } {

    # reflash the u-Boot environment variables area
    sheevaplug_init
    nand probe 0
    nand erase 0 0xa0000 0x40000
    nand write 0 uboot-env.bin 0xa0000 oob_softecc_kw
    resume

}

proc sheevaplug_load_uboot { } {

    # load u-Boot into RAM and execute it
    sheevaplug_init
    #load_image uboot.elf
    #verify_image uboot.elf
    load_image u-boot
    verify_image u-boot
    resume 0x00600000

}

proc dockstar_reset_cpu { } {

#    System and User mode registers
#          r0: 00000000       r1: 00000000       r2: 00000000       r3: 00000000
#          r4: 00000000       r5: 00000000       r6: 00000000       r7: 00000000
#          r8: 00000000       r9: 00000000      r10: 00000000      r11: 00000000
#         r12: 00000000   sp_usr: 7dddee86   lr_usr: dffebe46       pc: ffff0a42
#        cpsr: 400000f3

    reg r1 0
    reg r2 0
    reg r3 0
    reg r4 0
    reg r5 0
    reg r6 0
    reg r7 0
    reg r8 0
    reg r9 0
    reg r10 0
    reg r11 0
    reg r12 0
    reg sp_usr 0
    reg lr_usr 0
    reg pc 0
    # Set the CPU in Supervisor mode
    reg cpsr 0x13

#    FIQ mode shadow registers
#      r8_fiq: fbcfff64   r9_fiq: d7dfafd6  r10_fiq: 1fff6d2e  r11_fiq: 1db65df4
#     r12_fiq: ff5a6de4   sp_fiq: 745fe7d5   lr_fiq: 89f7ae3e spsr_fiq: 00000000

    reg r8_fiq 0
    reg r9_fiq 0
    reg r10_fiq 0
    reg r11_fiq 0
    reg r12_fiq 0
    reg sp_fiq 0
    reg lr_fiq 0
    reg spsr_fiq 0

#    Supervisor mode shadow registers
#      sp_svc: fffeff84   lr_svc: ffff0a43 spsr_svc: 00000000

    reg sp_svc 0
    reg lr_svc 0
    reg spsr_svc 0

#    Abort mode shadow registers
#      sp_abt: 51fe66f7   lr_abt: d7abaef7 spsr_abt: 00000000

    reg sp_abt 0
    reg lr_abt 0
    reg spsr_abt 0

#    IRQ mode shadow registers
#      sp_irq: 7fdb4ed5   lr_irq: 6d41122e spsr_irq: 00000000

    reg sp_irq 0
    reg lr_irq 0
    reg spsr_irq 0
   
#    Undefined instruction mode shadow registers
#      sp_und: 75ffef7e   lr_und: d75b6cd1 spsr_und: 00000000

    reg sp_und 0
    reg lr_und 0
    reg spsr_und 0
   
}
 
Zuletzt bearbeitet:
Hallo joerg_999

irgendwie geht gerade nichts bei mir so richtig.
Kabel sind mit Raspberry und TTL Converter verbunden

über Putty habe ich auf dem Raspberry "openocd" gestartet, siehe Ausgabe
aber bei Telnet Terminal2
Windows 10 telnet 192.168.178.3 4444
Verbindungsaufbau zu 192.168.178.3...Es konnte keine Verbindung mit dem Host hergestellt werden, auf Port 4444: Verbindungsfehler
bekomme ich keine Verbindung zum Host

sudo openocd -f pogo.cfg
Open On-Chip Debugger 0.10.0+dev-00399-g09076d10 (2018-04-11-12:15)
Licensed under GNU GPL v2
For bug reports, read
Sie müssen registriert sein, um Links zu sehen.

BCM2835 GPIO config: tck = 11, tms = 25, tdi = 10, tdo = 9
BCM2835 GPIO nums: swclk = 25, swdio = 24
BCM2835 GPIO config: trst = 7
trst_only separate trst_push_pull
adapter speed: 200 kHz
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
adapter_nsrst_delay: 200
jtag_ntrst_delay: 200
Warn : use 'feroceon.cpu' as target identifier, not '0'
pogo_load_uboot
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : BCM2835 GPIO JTAG/SWD bitbang driver
Info : JTAG and SWD modes enabled
Info : clock speed 200 kHz
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9 (Marvell Semiconductors), part: 0x0a02, ver: 0x2)
Info : Embedded ICE version 0
Info : feroceon.cpu: hardware has 1 breakpoint/watchpoint unit
Info : Listening on port 3333 for gdb connections
 
Zuletzt bearbeitet:
so ich hab es mit picocom versucht, geht auch nicht...

Kabel sind ok, durchgemessen und Pin geprüft.

Pogo im Himmel

pi@raspberrypi:~ $ picocom 4444
picocom v1.7

port is : 4444
flowcontrol : none
baudrate is : 9600
parity is : none
databits are : 8
escape is : C-a
local echo is : no
noinit is : no
noreset is : no
nolock is : no
send_cmd is : sz -vv
receive_cmd is : rz -vv
imap is :
omap is :
emap is : crcrlf,delbs,


FATAL: cannot open 4444: No such file or directory
 
Zuletzt bearbeitet:
Baudrate (9600) ist falsch --> richtig: 115200 8 N 1
probiere mal das, bin momentan unterwegs kann erst am Wochenende drüber schauen.

Vorgangsweise:
1.) zuerst OpenOCD starten
2.) in zweiten Putty Fenster Terminal auf telnet stellen und mit IP des Raspis:4444 starten
schon sollte es funktionieren.

PS: Pogo ist nie im Himmel und kann immer wiederbelebt werden....(außer du fährst mit dem Auto drüber ,-)

LG
joerg_999
 
Zuletzt bearbeitet:
so habe ich es gemacht
pi@raspberrypi:~ $ sudo openocd -f pogo.cfg
Open On-Chip Debugger 0.10.0+dev-00399-g09076d1 (2018-04-12-17:46)
Licensed under GNU GPL v2
For bug reports, read
Sie müssen registriert sein, um Links zu sehen.

BCM2835 GPIO config: tck = 11, tms = 25, tdi = 10, tdo = 9
BCM2835 GPIO nums: swclk = 25, swdio = 24
BCM2835 GPIO config: trst = 7
trst_only separate trst_push_pull
adapter speed: 200 kHz
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
adapter_nsrst_delay: 200
jtag_ntrst_delay: 200
Warn : use 'feroceon.cpu' as target identifier, not '0'
pogo_load_uboot
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : BCM2835 GPIO JTAG/SWD bitbang driver
Info : JTAG and SWD modes enabled
Info : clock speed 200 kHz
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9 (Marvell Semiconductors), part: 0x0a02, ver: 0x2)
Info : Embedded ICE version 0
Info : feroceon.cpu: hardware has 1 breakpoint/watchpoint unit
Info : Listening on port 3333 for gdb connections

pi@raspberrypi:~ $ picocom -b 115200 -r -l 4444
picocom v1.7

port is : 4444
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
escape is : C-a
local echo is : no
noinit is : no
noreset is : yes
nolock is : yes
send_cmd is : sz -vv
receive_cmd is : rz -vv
imap is :
omap is :
emap is : crcrlf,delbs,


FATAL: cannot open 4444: No such file or directory

Microsoft Windows [Version 10.0.16299.371]
(c) 2017 Microsoft Corporation. Alle Rechte vorbehalten.

C:\WINDOWS\system32>cd ..

C:\Windows>cd..

C:\>telnet 192.168.178.3 4444
Verbindungsaufbau zu 192.168.178.3...Es konnte keine Verbindung mit dem Host hergestellt werden, auf Port 4444: Verbindungsfehler

C:\>

EDIT: geht nicht, machen wir am WE
 
Zuletzt bearbeitet:
zu Punkt 2 und 3 .. warum plagst du dich so herum?? installiere dir Putty auf deinem WIN PC und gut ist es.
Von da rufst du Putty 3x auf (die Einstellung ob ssh telnet oder seriell brauchst du hier nur anklicken!)
1.) ssh Session auf Port 22
2.) telnet Session auf Port 4444
3.) serial Session auf den COM Port deines TTY/USB Adapters (wobei du die Portgeschwindigkeit schon mal unter WIN auf 115200 einstellen solltest und dann nochmals in Putty, 1.) und 2.) immer auf die Adresse deines RASPis)

In der Beschreibung Seite 1 steht: Spoiler 1 (der Start von OpenOCD) sieht ja schon mal gut aus....
 
Zuletzt bearbeitet:
Du musst dich einloggen oder registrieren, um hier zu antworten.

Ähnliche Themen

G
FFMPEG HWACCEL Transcoding
Antworten
1
Aufrufe
3K
franky64
F
  • Angepinnt
Pogo E02 debian 9.2 (stretch mit kernel 4.14.1)+IPC
Antworten
5
Aufrufe
3K
kalle1984
Pogoplug E02 neues image mit Kernel 4.10.9 (Jessie 8.9) + IPC 11.6
Antworten
7
Aufrufe
4K
joerg_999
  • Angepinnt
Installation von OpenWRT-18.06.x auf Pogoplug E02
9 10 11
Antworten
152
Aufrufe
22K
teufel
Pogo E02 Neues Filesystem und Kernelupdate in einem Durchgang
2
Antworten
21
Aufrufe
5K
joerg_999
Menü
Anmelden
Registrieren
Für die Nutzung dieser Website sind Cookies erforderlich. Du musst diese akzeptieren, um die Website weiter nutzen zu können. Erfahre mehr…