Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD December 18, 2019 10:19PM |
Admin Registered: 13 years ago Posts: 18,821 |
Quote
So anyway, I then switched the JTAG cable back to the bricked Pogoplug. Nada. I think that this unit had a hardware failure. The JTAG on it used to work but now it does not work anymore.
Quote
daviddyer
These machines are pretty solid, but the power supplies are not. Maybe you need to get a good power supply and try again.
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD January 04, 2020 03:04PM |
Registered: 11 years ago Posts: 18 |
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD January 06, 2020 04:37AM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD May 30, 2020 11:14AM |
Registered: 11 years ago Posts: 55 |
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD May 30, 2020 04:35PM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD May 30, 2020 05:27PM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD May 30, 2020 05:32PM |
Registered: 11 years ago Posts: 55 |
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD May 30, 2020 05:34PM |
Admin Registered: 13 years ago Posts: 18,821 |
Quote
First thank you for prompt reply. I have tried the followings:
0. connect usb cable to serial console of the NSA320s; lsusb shows:
Bus 003 Device 010: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
1. turned on NSA320s by pressing button;
2. run 'kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa310s.mtd0.kwb -p' command from a Linux laptop.
Sending boot message. Please reboot the target...-^C
and wait but nothing happens ... I had to ^C to return to prompt.
Can I do any other checks ?
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD November 26, 2020 05:30PM |
Registered: 3 years ago Posts: 28 |
pi@raspberrypi:~ $ sudo openocd -f pogo.cfg Open On-Chip Debugger 0.10.0+dev-01514-ga8edbd020-dirty (2020-11-26-10:55) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html DEPRECATED! use 'adapter driver' not 'interface' DEPRECATED! use 'adapter speed' not 'adapter_khz' Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'. 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 : clock speed 200 kHz Error: JTAG scan chain interrogation failed: all zeroes Error: Check JTAG interface, timings, target power, etc. Error: Trying to use configured scan chain anyway... Error: feroceon.cpu: IR capture error; saw 0x00 not 0x01 Warn : Bypassing JTAG setup events due to errors Info : Embedded ICE version 0 Info : feroceon.cpu: hardware has 1 breakpoint/watchpoint unit Error: unexpected Feroceon EICE version signature Info : starting gdb server for feroceon.cpu on 3333 Info : Listening on port 3333 for gdb connections pogp_init pogo_init soft_reset_halt nand probe 0 ^Cshutdown command invoked pi@raspberrypi:~ $
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD November 26, 2020 10:59PM |
Registered: 3 years ago Posts: 28 |
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD November 26, 2020 11:53PM |
Registered: 7 years ago Posts: 369 |
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD November 27, 2020 06:32AM |
Registered: 3 years ago Posts: 28 |
pi@raspberrypi:~ $ telnet 127.0.0.1 4444 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. Open On-Chip Debugger > pogo_init DEPRECATED! use 'adapter [de]assert' not 'jtag_reset' unexpected Feroceon EICE version signature DEPRECATED! use 'adapter [de]assert' not 'jtag_reset' Halt timed out, wake up GDB. timed out while waiting for target halted > soft_reset_halt requesting target halt and executing a soft reset Failed to halt CPU after 1 sec Halt timed out, wake up GDB. > pogo_init DEPRECATED! use 'adapter [de]assert' not 'jtag_reset' unexpected Feroceon EICE version signature DEPRECATED! use 'adapter [de]assert' not 'jtag_reset' Halt timed out, wake up GDB. timed out while waiting for target halted > soft_reset_halt requesting target halt and executing a soft reset Failed to halt CPU after 1 sec Halt timed out, wake up GDB. > nand probe 0 NAND flash access requires halted target NAND flash access requires halted target NAND flash access requires halted target NAND flash access requires halted target NAND flash access requires halted target NAND flash access requires halted target unknown NAND flash device found, manufacturer id: 0x00 device id: 0x00 > pogo_init DEPRECATED! use 'adapter [de]assert' not 'jtag_reset' unexpected Feroceon EICE version signature DEPRECATED! use 'adapter [de]assert' not 'jtag_reset' Halt timed out, wake up GDB. timed out while waiting for target halted
jtag_reset 0 1 feroceon.cpu arp_examine halt 0 jtag_reset 0 0
# jtag_reset 0 1 adapter assert srst feroceon.cpu arp_examine halt 0 # jtag_reset 0 0 adapter deassert srst
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD November 27, 2020 09:56PM |
Registered: 3 years ago Posts: 28 |
Setting up openocd (0.8.0-4+deb7u1) ... pi@raspberrypi:~ $ sudo openocd -f pogo.cfgOpen On-Chip Debugger 0.8.0 (2018-01-22-05:24) Licensed under GNU GPL v2 For bug reports, read http://openocd.sourceforge.net/doc/doxygen/bugs.html Info : only one transport option; autoselect 'jtag' Runtime Error: /usr/share/openocd/scripts/interface/raspberrypi123-native.cfg:18: invalid command name "bcm2835gpio_peripheral_base" in procedure 'script' at file "embedded:startup.tcl", line 58 at file "pogo.cfg", line 10 at file "/usr/share/openocd/scripts/interface/raspberrypi123-native.cfg", line 18 pi@raspberrypi:~ $ sudo nano /usr/share/openocd/scripts/board/pogo.cfgpi@raspberrypi:~ $ sudo nano /usr/share/openocd/scripts/board/pogo.cfg pi@raspberrypi:~ $ sudo nano /usr/share/openocd/scripts/interface/raspberrypi123-native.cfg pi@raspberrypi:~ $ sudo openocd -f pogo.cfgOpen On-Chip Debugger 0.8.0 (2018-01-22-05:24) Licensed under GNU GPL v2 For bug reports, read http://openocd.sourceforge.net/doc/doxygen/bugs.html Info : only one transport option; autoselect 'jtag' BCM2835 GPIO config: tck = 11, tms = 25, tdi = 10, tdi = 9 Runtime Error: /usr/share/openocd/scripts/interface/raspberrypi123-native.cfg:45: invalid command name "bcm2835gpio_swd_nums" in procedure 'script' at file "embedded:startup.tcl", line 58 at file "pogo.cfg", line 10 at file "/usr/share/openocd/scripts/interface/raspberrypi123-native.cfg", line 45 pi@raspberrypi:~ $ sudo nano /usr/share/openocd/scripts/interface/raspberrypi123-native.cfg pi@raspberrypi:~ $ sudo openocd -f pogo.cfgOpen On-Chip Debugger 0.8.0 (2018-01-22-05:24) Licensed under GNU GPL v2 For bug reports, read http://openocd.sourceforge.net/doc/doxygen/bugs.html Info : only one transport option; autoselect 'jtag' BCM2835 GPIO config: tck = 11, tms = 25, tdi = 10, tdi = 9 BCM2835 GPIO config: trst = 7 trst_only separate trst_push_pull adapter speed: 200 kHz 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 : clock speed 200 kHz Error: JTAG scan chain interrogation failed: all ones Error: Check JTAG interface, timings, target power, etc. Error: Trying to use configured scan chain anyway... Error: feroceon.cpu: IR capture error; saw 0x0f not 0x01 Warn : Bypassing JTAG setup events due to errors Info : Embedded ICE version 15 Info : feroceon.cpu: hardware has 1 breakpoint/watchpoint unit Error: unexpected Feroceon EICE version signature Warn : ThumbEE -- incomplete support Info : accepting 'telnet' connection from 4444 Error: unexpected Feroceon EICE version signature requesting target halt and executing a soft reset Error: Jazelle state handling is BROKEN! target state: halted target halted in Jazelle state due to debug-request, current mode: Supervisor cpsr: 0xffffffd3 pc: 0x00000000 MMU: disabled, D-Cache: disabled, I-Cache: disabled Error: unknown NAND flash device found, manufacturer id: 0xff device id: 0xff in procedure 'nand' Error: unexpected Feroceon EICE version signature Error: unknown NAND flash device found, manufacturer id: 0xff device id: 0xff in procedure 'nand' requesting target halt and executing a soft reset Error: Jazelle state handling is BROKEN! target state: halted target halted in Jazelle state due to debug-request, current mode: Supervisor cpsr: 0xffffffd3 pc: 0x00000000 MMU: disabled, D-Cache: disabled, I-Cache: disabled
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD December 07, 2020 03:43PM |
Registered: 10 years ago Posts: 94 |
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD December 09, 2020 06:14PM |
Registered: 3 years ago Posts: 28 |
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD April 03, 2021 04:02PM |
Registered: 3 years ago Posts: 25 |
sudo openocd -f /usr/share/openocd/scripts/board/wspace.cfgand got the output
Open On-Chip Debugger 0.10.0 Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html none separate 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_push_pull connect_deassert_srst adapter_nsrst_delay: 200 jtag_ntrst_delay: 200 adapter speed: 2000 kHz dcc downloads are enabled Warn : use 'feroceon.cpu' as target identifier, not '0' sheevaplug_load_uboot Info : clock speed 2000 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
telnet 127.0.0.1 4444
Open On-Chip Debugger 0.10.0 Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html none separate 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_push_pull connect_deassert_srst adapter_nsrst_delay: 200 jtag_ntrst_delay: 200 adapter speed: 2000 kHz dcc downloads are enabled Warn : use 'feroceon.cpu' as target identifier, not '0' sheevaplug_load_uboot Info : clock speed 2000 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 : accepting 'telnet' connection on tcp/4444 invalid command name "scan_chain\" TapName Enabled IdCode Expected IrLen IrCap IrMask -- ------------------- -------- ---------- ---------- ----- ----- ------ 0 feroceon.cpu Y 0x20a023d3 0x20a023d3 4 0x01 0x0f Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: unknown NAND flash device found, manufacturer id: 0x02 device id: 0x02 invalid command name "monitor" target halted in ARM state due to debug-request, current mode: Supervisor cpsr: 0x000000d3 pc: 0xffff0000 MMU: disabled, D-Cache: disabled, I-Cache: disabled TapName Enabled IdCode Expected IrLen IrCap IrMask -- ------------------- -------- ---------- ---------- ----- ----- ------ 0 feroceon.cpu Y 0x20a023d3 0x20a023d3 4 0x01 0x0f NAND flash device 'NAND 128MiB 3.3V 8-bit (Samsung)' found #0: NAND 128MiB 3.3V 8-bit (Samsung) pagesize: 2048, buswidth: 8, blocksize: 131072, blocks: 1024
Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. Open On-Chip Debugger > scan_chain\ invalid command name "scan_chain\" > scan_chain TapName Enabled IdCode Expected IrLen IrCap IrMask -- ------------------- -------- ---------- ---------- ----- ----- ------ 0 feroceon.cpu Y 0x20a023d3 0x20a023d3 4 0x01 0x0f > nand probe 0 NAND flash access requires halted target NAND flash access requires halted target NAND flash access requires halted target NAND flash access requires halted target NAND flash access requires halted target NAND flash access requires halted target unknown NAND flash device found, manufacturer id: 0x02 device id: 0x02 > monitor flash probe 0 invalid command name "monitor" > sheevaplug_init target halted in ARM state due to debug-request, current mode: Supervisor cpsr: 0x000000d3 pc: 0xffff0000 MMU: disabled, D-Cache: disabled, I-Cache: disabled > scan_chain TapName Enabled IdCode Expected IrLen IrCap IrMask -- ------------------- -------- ---------- ---------- ----- ----- ------ 0 feroceon.cpu Y 0x20a023d3 0x20a023d3 4 0x01 0x0f > nand probe 0 NAND flash device 'NAND 128MiB 3.3V 8-bit (Samsung)' found > nand list #0: NAND 128MiB 3.3V 8-bit (Samsung) pagesize: 2048, buswidth: 8, blocksize: 131072, blocks: 1024 >
nand dump 0 "first4.bin" 0 65536 dumped 65536 bytes in 32.075588s (1.995 KiB/s)Is this correct... it means I created a copy of the first 64 kbytes of flash? That can be written back to it in case of bricking?
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD April 03, 2021 04:51PM |
Registered: 11 years ago Posts: 18 |
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD April 05, 2021 01:07AM |
Registered: 10 years ago Posts: 94 |
================================================================================ ## uboot layout (mtd0) ## ================================================================================ offset Block 0 (128K) 0x0 ------------| | Block 1 (128K) 0x20000 | | Block 2 (128K) 0x40000 uboot | size 0x80000 | Block 3 (128K) 0x60000 | | Block 4 (128K) 0x80000 -----------|--> uboot 4 Blocks with 128K Block 5 (128K) 0xa0000 Block 6 (128K) 0xc0000 -----------| size 0x20000 uboot env | Block 7 (128K) 0xe0000 -----------|--> uboot env 1 Block with 128K 128K x 8 = 1024K = 1M to 0x100000 1M = 8 Blocks (0-7) ================================================================================
# Terminal2 We clear the first 512kB: > nand erase 0 0x0 0xa0000 # erased blocks 0 to 5 on NAND flash device #0 'NAND 128MiB 3.3V 8-bit' # Terminal2 Then we write the nand file uboot: # be careful and take the matching one !! # Files we use: pogo.cfg, and Symlinks we created before # uboot.2017.07-tld-1.pogo_e02.mtd0.kwb ----> uboot.kwb > nand write 0 uboot.kwb 0 oob_softecc_kw # Finished
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD April 05, 2021 11:12AM |
Registered: 3 years ago Posts: 25 |
telnet localhost 4444
>sheevaplug_init target halted in ARM state due to debug-request, current mode: Supervisor cpsr: 0x000000d3 pc: 0xffff0000 MMU: disabled, D-Cache: disabled, I-Cache: disabled > nand probe 0 NAND flash device 'NAND 128MiB 3.3V 8-bit (Samsung)' found > nand list 0 #0: NAND 128MiB 3.3V 8-bit (Samsung) pagesize: 2048, buswidth: 8, blocksize: 131072, blocks: 1024 >nand dump 0 "u-boot.printenv.bin" 0 786432 dumped 786432 bytes in 386.816040s (1.985 KiB/s) > nand erase 0 0 786432 erased blocks 0 to 5 on NAND flash device #0 'NAND 128MiB 3.3V 8-bit'
> nand write 0 u-boot.printenv.bin 0 wrote file u-boot.printenv.bin to NAND flash 0 up to offset 0x000c0000 in 23.302645s (32.958 KiB/s)
nand erase 0 erased blocks 0 to 1023 on NAND flash device #0 'NAND 128MiB 3.3V 8-bit' > nand write 0 flash.bin 0
nand dump 0 "flash.bin" 0 134217728 dumped 134217728 bytes in 63788.855469s (2.055 KiB/s)
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD April 06, 2021 02:35AM |
Registered: 3 years ago Posts: 25 |
> ================================================================================ > ## uboot layout (mtd0) ## > ================================================================================ > offset > Block 0 (128K) 0x0 ------------| > > | > Block 1 (128K) 0x20000 | > | > Block 2 (128K) 0x40000 uboot | size > 0x80000 > | > Block 3 (128K) 0x60000 | > | > Block 4 (128K) 0x80000 -----------|--> > uboot 4 Blocks with 128K > > Block 5 (128K) 0xa0000 > > Block 6 (128K) 0xc0000 -----------| size > 0x20000 > uboot env | > Block 7 (128K) 0xe0000 -----------|--> > uboot env 1 Block with 128K > > 128K x 8 = 1024K = 1M > to 0x100000 > 1M = 8 Blocks (0-7) > > ================================================================================ > >>
> # Terminal2 We clear the first 512kB: > > nand erase 0 0x0 0xa0000 > # erased blocks 0 to 5 on NAND flash device #0 > 'NAND 128MiB 3.3V 8-bit' > > # Terminal2 Then we write the nand file uboot: > # be careful and take the matching one !! > # Files we use: pogo.cfg, and Symlinks we created > before > # uboot.2017.07-tld-1.pogo_e02.mtd0.kwb ----> > uboot.kwb > > > nand write 0 uboot.kwb 0 oob_softecc_kw > > > # Finished > >
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD April 06, 2021 04:54AM |
Registered: 10 years ago Posts: 94 |
This print error is known - you should take this config here:Quote
fratzicu
Some bumps along the way:
> nand write 0 flash.bin 0
DCC write failed, expected end address 0x00100814 got 0x5a
For this to work I needed to change the openocd board script wspace.cfg to -work-area-phys 0x10000000 to 0x10000 (I saw it on a blog, don't know the signifficance but it works)
$_TARGETNAME configure \ -work-area-phys 0x100000 \ -work-area-size 65536 \ -work-area-backup 0see discription on first page.
>nand dump 0 "u-boot.printenv.bin" 0 786432 dumped 786432 bytes in 386.816040s (1.985 KiB/s) > nand erase 0 0 786432 erased blocks 0 to 5 on NAND flash device #0 'NAND 128MiB 3.3V 8-bit' After restart device is dead / bricked. > nand write 0 u-boot.printenv.bin 0 wrote file u-boot.printenv.bin to NAND flash 0 up to offset 0x000c0000 in 23.302645s (32.958 KiB/s) now again back to life but after decompressing.... booting the kernel it does not boot. So I restore now the whole flashBut take care, the uboot envs should always match the options of the uboot and the location where uboot will seek them (especially dtb - configuration, loaded intern or external = new methode). In other words: newer uboots can handle some more options in uboot-envs than older one can do!
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD April 06, 2021 10:18AM |
Registered: 3 years ago Posts: 25 |
DCC write failed, expected end address 0x00100814 got 0x5ais caused by some ram conflict. would setting
$_TARGETNAME configure \ -work-area-phys 0x100000 \ -work-area-size 65536 \ -work-area-backup 0be correct for my device? (very similar with sheevaplug, seagate dockstar?) Is there a source for correct finding of those parameters or they are just guessed? I'll read the page on this error (edit: I didn't find the page with this information). I'm a beginner but I really want to understand those things from A to Z.
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD April 07, 2021 03:30AM |
Registered: 10 years ago Posts: 94 |
Quote
The LaCie stock U-Boot comes with a huge limitation: at reset, U-Boot reinitialize the boot environment variables (stored in Flash) with some built-in values. This includes the boot commands sequence. As a consequence, the LaCie system layout (or partition map) can't be changed. By default, U-Boot will load the Linux kernel from partition 10 (update) or from partition 6 as a fallback (default).
Save flash size (a LaCie U-Boot image size is ~450KB against ~230KB for a mainline one).
Boot reliably from USB.
Some command line enhancements: history, completion, scripting …
Be able to add a new feature.
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD April 10, 2021 03:54PM |
Registered: 3 years ago Posts: 25 |
U-Boot 2013.04-00574-gfbf87b182 (Mar 20 2021 - 19:21:55) Wireless Space SoC: Kirkwood 88F6281_A1 DRAM: 256 MiB WARNING: Caches not enabled NAND: 128 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: egiga0 88E6161 Initialized on egiga0 BOOTP broadcast 1 BOOTP broadcast 2 *** Unhandled DHCP Option in OFFER/ACK: 44 *** Unhandled DHCP Option in OFFER/ACK: 44 DHCP client bound to address 192.168.23.64 Hit any key to stop autoboot: 0 (Re)start USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 3 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found reading /boot/uImage
5316528 bytes read in 387 ms (13.1 MiB/s) ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-5.10.7-kirkwood-tld-1 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 5316464 Bytes = 5.1 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image ...
| | __ _ / ___(_) ___ | | / _` | | | |/ _ \ | |___ (_| | |___| | __/ |_____\__,_|\____|_|\___| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__| ** MARVELL BOARD: ASTON_WS_GN3 REV: 2 LE Hold rear button - long : FAIL U-Boot 1.1.4 (Jul 27 2011 - 17:43:51) Marvell version: 3.4.16 LaCie 1.5.22 256MB U-Boot code: 06000000 -> 0607FFF0 BSS: -> 060CE600 Soc: MV88F6281 Rev 3 (DDR2) CPU running @ 800Mhz L2 running @ 400Mhz SysClock = 200Mhz , TClock = 166Mhz DRAM CAS Latency = 3 tRP = 3 tRAS = 9 tRCD=3 DRAM CS[0] base 0x00000000 size 256MB DRAM Total size 256MB 16bit width Flash: 0 kB Addresses 98M - 0M are saved for the U-Boot usage. Mem malloc Initialization (98M - 97M): Done NAND:128 MB *** Warning - bad CRC or NAND, using default environment CPU : Marvell Feroceon (Rev 1) Streaming disabled Write allocate disabled Module 0 is MII USB 0: host mode PCI 0: PCI Express Root Complex Interface PEX interface detected Link X1 Net: egiga0 [PRIME], egiga1 Waiting for LUMP (3) no lump receive; continuing Hit any key to stop autoboot: 0 Reset IDE: Marvell Serial ATA Adapter Integrated Sata device found ** Bad partition 1 ** ## Checking Image at 00800000 ... Bad Magic Number NAND read: device 0 offset 0x100000, size 0x300000 reading NAND page at offset 0x100000 failed 3145728 bytes read: ERROR ** Bad partition 1 ** ## Checking Image at 01200000 ... Bad Magic Number NAND read: device 0 offset 0x400000, size 0x400000 reading NAND page at offset 0x400000 failed 4194304 bytes read: ERROR ## Booting image at 00800000 ... Bad Magic Number Waiting for LUMP (0)
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD April 10, 2021 05:22PM |
Admin Registered: 13 years ago Posts: 18,821 |
> 5316528 bytes read in 387 ms (13.1 MiB/s) > ## Booting kernel from Legacy Image at 00800000 > ... > Image Name: Linux-5.10.7-kirkwood-tld-1 > Image Type: ARM Linux Kernel Image > (uncompressed) > Data Size: 5316464 Bytes = 5.1 MiB > Load Address: 00008000 > Entry Point: 00008000 > Verifying Checksum ... OK > Loading Kernel Image ... >
Quote
Updated 14 Apr 2018:
Kernel linux-4.16.1-kirkwood-tld-1 package has been uploaded. The following features were added/updated:
- Add GENERIC_CPU_VULNERABILITIES config to track mainline future security reports.
Latest Linux kernel 4.x general release information can be found at:
LinuxChanges log
Download at Dropbox:
linux-4.16.1-kirkwood-tld-1-bodhi.tar.bz2
md5:
ac1aff7c9848ff949dfa081cf5ac094c
sha256:
8779493bf8319b712b2f8ed3519305e61abee9e2bcc9630fc28d7c6d1d420bb8
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD April 10, 2021 06:19PM |
Registered: 3 years ago Posts: 25 |
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD April 10, 2021 06:52PM |
Admin Registered: 13 years ago Posts: 18,821 |
0x100000 in decimaland divide by 1024 to get KB.... so on.
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD April 11, 2021 05:32AM |
Registered: 3 years ago Posts: 25 |
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD April 11, 2021 06:19AM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: HOW2: Repair Pogo E02 with Raspberry PI (1,2 or 3) JTAG and OpenOCD April 11, 2021 06:32AM |
Registered: 3 years ago Posts: 25 |