Welcome! Log In Create A New Profile

Advanced

Bricked or not, that is the question :/

Posted by alonetrio 
Forum List Message List New Topic
alonetrio
Bricked or not, that is the question :/
November 08, 2018 10:18AM
hi all,

i recently flashed my stora with the latest uboot from https://forum.doozan.com/read.php?3,12381,12381#msg-12381

all was ok, netconsole was working ok, etc.... But ( as i am a noob :=0 ) i have done a "env default -a" i directly loose my netconsole, and the only choice was a reboot. Since this day, it seem i have a brick....

is there something to do/test to make it alive ?

ps: for an unknown reason i never had serial output/access even with stock uboot...

thx all.
Reply Quote
bodhi
Re: Bricked or not, that is the question :/
November 08, 2018 04:47PM
alonetrio,

> i recently flashed my stora with the latest uboot from https://forum.doozan.com/read.php?3,12381,12381#msg-12381

> i have done a "env default
> -a" i directly loose my netconsole, and the only
> choice was a reboot. Since this day, it seem i
> have a brick....

>
> is there something to do/test to make it alive ?

It is very far from bricked :) Even without serial console, you can still fix this with uEnv.txt.

Do you keep the log of your u-boot flashing session? it would be good to have in case I need to ask question.

Let find my instruction post for this or write a new one.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
bodhi
Re: Bricked or not, that is the question :/
November 08, 2018 05:01PM
Here is how you restore the u-boot envs to default values during boot.


Booting with the default envs using uEnv.txt loading capability using uboot.2016.05-tld-1.environment (the content of the default envs in text format).

This assumes that you have install my latest u-boot release. The uboot.2016.05-tld-1.environment file is in the downloaded tarball.

This assumes that you have the rootfs on USB drive. If your rootfs is on HDD and you cannot take it out of the box, then create a new USB rootfs using Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2. Basically, you need to access this drive to copy the envs file to the rootfs.


1. Copy the default envs in text format to the rootfs on USB. Assuming the USB rootfs is mounted on another Linux box as /media/sdb1.

Become root and copy the default envs to uEnv.txt: 
su -
cp -a uboot.2016.05-tld-1.environment /media/sdb1/boot/uEnv.txt

2. Modify the uEnv.txt for your box specifics to replace the 2 envs devices and dtb_file as following: 

devices=usb ide
dtb_file=/boot/dts/kirkwood-netgear_stora_ms2000.dtb

Note:

- The devices env above indicates that u-boot will attempt to boot with the USB first, if it is not present then it will try to boot HDD.
- The dtb_file above indicates that you are booting the Netgear Stora box. This instruction is applicable to all Kirkwood boxes, just change the corresponding DTB file name if you booting other boxes.

3. and then sync and unmount the USB 

sync
umount /media/sdb1


4. Plug in this USB rootfs to the box, and power up.

You should find your box again in the nextwork and log in your usuall way as before.

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



Edited 1 time(s). Last edit at 11/08/2018 05:04PM by bodhi.
Reply Quote
alonetrio
Re: Bricked or not, that is the question :/
November 11, 2018 12:24PM
hi,
and thx for your answer.

i tried with 2 differents usb key, with ext3, ext4 and nothing. it do not even try to access the key. Any other voodoo tricks i can try ?
Reply Quote
bodhi
Re: Bricked or not, that is the question :/
November 11, 2018 05:06PM
alonetrio,

> i tried with 2 differents usb key, with ext3, ext4
> and nothing. it do not even try to access the key.
> Any other voodoo tricks i can try ?

Which exact version of new u-boot that you have flashed to NAND? do you keep the log of what you did to flash?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
alonetrio
Re: Bricked or not, that is the question :/
November 12, 2018 07:11AM
hi,

i didn't have log of the session when i burned:

uboot.2017.07-tld-1.netgear_ms2110.bodhi.tar
md5
1b09317e896ad928104a1edce459a9f5
sha256
8f5e8b5b33e3979b05698a09a92f99cd41ed04121993058f9b2469122fd280a7

but be sure that all was ok, i had my linux working, etc...

i installed netconsole with env var, and all was ok but net console gave me prompt instead of counting from 10 to 0 to boot.

i just clear the preboot env var thinking that will force it to boot normaly.

i'm pretty sure it stall at a uboot prompt. but without any serial i cani't investage more.

it smell that this time you will tell it's bricked.... argggg :/

aloneTrio
Reply Quote
bodhi
Re: Bricked or not, that is the question :/
November 12, 2018 04:16PM
aloneTrio,

> uboot.2017.07-tld-1.netgear_ms2110.bodhi.tar
> md5
> 1b09317e896ad928104a1edce459a9f5
> sha256
> 8f5e8b5b33e3979b05698a09a92f99cd41ed04121993058f9b2469122fd280a7
>
>
> but be sure that all was ok, i had my linux
> working, etc...

So it was flashed successful. u-boot is OK on NAND mtd0. You have not done anything to change it if you just wiped out the envs.

>
> i installed netconsole with env var, and all was
> ok but net console gave me prompt instead of
> counting from 10 to 0 to boot.

There was some wrong setting in your netconsole set up. So you could have fixed this issue at the netconsole prompt.

>
> i just clear the preboot env var thinking that
> will force it to boot normaly.
>
> i'm pretty sure it stall at a uboot prompt. but
> without any serial i cani't investage more.

>
> it smell that this time you will tell it's
> bricked.... argggg :/
>

No. It is not bricked. The envs are just messed up, so you can't boot the kernel. uboot.2017.07-tld-1.netgear_ms2110 should be able to read the uEnv.txt and correct that.

If you can connect serial console then this problem can be solved very quickly. So if you can do this, then we will wait until you boot with serial console.

------

If you can't connect serial console (for whatever reason) then we just have to work on the rootfs and make sure that it is good and have the uEnv.txt in /boot. Without console visibilty, we need to rely on the LEDs to guess where the booting process is at.

1. I assume you were booting with SATA rootfs, no USB? can you take it offline and mount it on another Linux box?

2. If you can do number 1, then do this to make sure your rootfs is OK. Assuming it is mounted at /media/sdb1 

ls -lart /media/sdb1/boot
ls -lart /media/sdb1/boot.dts/kirkwood-netgear_stora_ms2000.dtb
e2label /dev/sdb1

Please post the output of these 3 commands above.

3. Put the uEnv.txt in /media/sdb1/boot/. And modify the content as 

devices=ide
dtb_file=/boot/dts/kirkwood-netgear_stora_ms2000.dtb

If you'd like, post the content here for confirmation: 

cat /media/sdb1/boot/uEnv.txt

------

After we've verified that the rootfs is OK. Do a sync and then umount 

sync
unmount /dev/sdb1

Take it back to the Stora. Power up. And observe the HDD lights or feel the drive to see if it was accessed during you power up. And then observe and record the LEDs behavior.

See if it gets you to boot successfuly.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
alonetrio
Re: Bricked or not, that is the question :/
November 21, 2018 08:27AM
hi bodhi !

still nothing :/ i tested with a sata and usb, perhaps i missed something ? 

root@AlonUX:/mnt# ls -lart diskstora/boot
total 36264
drwxr-xr-x 21 root root    4096 févr. 17  2015 ..
drwxr-xr-x  2 root root    4096 juil. 16  2017 dts
-rw-r--r--  1 root root  153501 juil. 16  2017 config-4.12.1-kirkwood-tld-1
-rwxr-xr-x  1 root root 3821528 juil. 16  2017 zImage-4.12.1-kirkwood-tld-1
-rw-------  1 root root 3821528 juil. 16  2017 vmlinuz-4.12.1-kirkwood-tld-1
-rw-------  1 root root 2504031 juil. 16  2017 System.map-4.12.1-kirkwood-tld-1
-rw-r--r--  1 root root 8435004 juil. 16  2017 linux-headers-4.12.1-kirkwood-tld-1_1.0_armel.deb
-rw-r--r--  1 root root 3821592 juil. 20  2017 uImage
-rw-r--r--  1 root root 7245632 juil. 24  2017 initrd.img-4.12.1-kirkwood-tld-1
-rw-r--r--  1 root root 7245696 juil. 24  2017 uInitrd
-rw-r--r--  1 root root    2777 nov.  21 15:20 uEnv.txt
drwxr-xr-x  3 root root    4096 nov.  21 15:20 .




root@AlonUX:/mnt# ls -lart diskstora/boot/dts/kirkwood-netgear_stora_ms2000.dtb
-rw-r--r-- 1 root root 11869 juil. 16  2017 diskstora/boot/dts/kirkwood-netgear_stora_ms2000.dtb





root@AlonUX:/mnt# e2label /dev/sdd1 
rootfs



root@AlonUX:/mnt# cat diskstora/boot/uEnv.txt 
arcNumber=2097
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
device=0:1
devices=ide
disks=0 1 2 3
ethact=egiga0
ethaddr=52:3b:20:9c:11:51
if_netconsole=ping $serverip
ipaddr=192.168.0.231
led_error=orange blinking
led_exit=green off
led_init=green blinking
dtb_file=/boot/dts/kirkwood-netgear_stora_ms2000.dtb
load_dtb_addr=0x1c00000
load_initrd_addr=0x1100000
load_uimage_addr=0x800000
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
machid=0x831
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
serverip=192.168.0.220
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
usb_ready_retry=15

thx you.
Reply Quote
bodhi
Re: Bricked or not, that is the question :/
November 21, 2018 08:37PM
alonetrio,

Did you ping this IP address while the box is powering up?

On another Linux box, execute the ping 
ping 192.168.0.231
And then power up the Stora.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
bodhi
Re: Bricked or not, that is the question :/
November 21, 2018 08:44PM
alonetrio,

Also, when you did this:

Quote

i have done a "env default -a"

Did you also run saveenv command like this? 

saveenv

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
alonetrio
Re: Bricked or not, that is the question :/
November 22, 2018 08:33AM
bodhi,

still nothing new. no ping.

yes, env default -a, perhaps cleared the bootcmd env var, then saveenv.

i tried something :
for now, when i plugged the power cord, the stora power on automatically, i decided to remove the battery ( i don't know what it save, clock, something else ? ), replace the battery, now i need to press the power button to get it powered on. Still same effect on the boot side, but it's now a bit different.

AloneTrio.
Reply Quote
bodhi
Re: Bricked or not, that is the question :/
November 22, 2018 05:26PM
AloneTrio ,

> yes, env default -a, perhaps cleared the bootcmd
> env var, then saveenv.

You did not report the whole story before. But clearing the bootcmd and then saveenv is why it cannot be recover with uEnv.txt.

Now I declare that it is bricked :) Sorry, you need serial console to receover.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
alonetrio
Re: Bricked or not, that is the question :/
November 22, 2018 05:28PM
Bodhi,

grrr ;)
jtag is the only option ? ok, is there a jtag pinout somewhere ?

regards,

AloneTrio
Reply Quote
bodhi
Re: Bricked or not, that is the question :/
November 22, 2018 05:34PM
AloneTrio,

Not JTAG. Serial console is easier and cheaper. Open the box and find serial console header for this box.

The pinout info is in this forum before in some thread that I forgot to save the link.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
alonetrio
Re: Bricked or not, that is the question :/
November 22, 2018 05:37PM
Bodhi,

as i said, and i don't know why, i never had any outpout from the serial port of the stora, not even with the stock uboot, or yours when it was working ;)

so no choice...

AloneTrio.
Reply Quote
bodhi
Re: Bricked or not, that is the question :/
November 22, 2018 05:38PM
Perhaps in this thread:

https://forum.doozan.com/read.php?3,49404,57349#msg-57349

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
bodhi
Re: Bricked or not, that is the question :/
November 22, 2018 05:40PM
> as i said, and i don't know why, i never had any
> outpout from the serial port of the stora, not
> even with the stock uboot, or yours when it was
> working ;)

May be just wrong connections (Tx/Rx)... things like that. People has connected serial console successfully before on the Stora.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
alonetrio
Re: Bricked or not, that is the question :/
November 22, 2018 05:47PM
i just ordered another usb to ttl "dongle" FTDI powered, and hope to see a serial output ;)

will i have to use kwboot to boot, and reflash from what i understand ?

AloneTrio.
Reply Quote
bodhi
Re: Bricked or not, that is the question :/
November 22, 2018 06:12PM
> will i have to use kwboot to boot, and reflash
> from what i understand ?

Yes. kwboot to boot the latest Stora u-boot, which should boot your current rootfs right away. After logged into Debian, do the flashing again in command line as before.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
alonetrio
Re: Bricked or not, that is the question :/
November 22, 2018 06:13PM
thx,

i will let you know my progress.

thx for all.

AloneTrio.
Reply Quote
alonetrio
Re: Bricked or not, that is the question :/
November 23, 2018 09:26PM
so nothing with serial :/

so i soldered jtag, and seems ok using openocd : 


root@raspberrypi:~# openocd -f pogo.cfg                                    
Open On-Chip Debugger 0.10.0+dev-00581-g1b864d6e (2018-11-24-00:25)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
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
adapter_nsrst_delay: 500
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
dcc downloads are enabled
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
Info : accepting 'telnet' connection on tcp/4444
Info : Halt timed out, wake up GDB.
Error: timed out while waiting for target halted

i can't halt it :/ and without it i can't acces nand...


without knowing what i'm doing i use this conf:
perhaps some address are not good. 

# Pogoplug E02                                                                                                                  
 # modification joerg_999 14.03.2016                                                                                            
 # use this pogo.cfg taken from sheevaplug to use with Raspi direct or Buspirate jtag adapter                                   
 # use raspberrypi-native mode                                                                                                  
 # we use the Pins from SPI Interface (violett) 19,21,23,26 and 22, + 20 for GND                                                
 # see GPIO schematic Raspi Raspi GPIO                                                                                          
                                                                                                                                
 # source [find interface/buspirate.cfg]                                                                                        
 # source [find interface/sysfsgpio-raspberrypi.cfg]                                                                            
 source [find interface/raspberrypi123-native.cfg]                                                                              
 source [find target/feroceon.cfg]                                                                                              
                                                                                                                                
$_TARGETNAME configure \                                                                                                        
-work-area-phys 0x10000000 \                                                                                                    
-work-area-size 65536 \                                                                                                         
-work-area-backup 0                                                                                                             
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 pogo_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 ;# DDR SDRAM Configuration Register
 mww 0xD0001404 0x39543000 ;# Dunit Control Low Register
 mww 0xD0001408 0x22125451 ;# DDR SDRAM Timing (Low) Register
 mww 0xD000140C 0x00000833 ;# DDR SDRAM Timing (High) Register
 mww 0xD0001410 0x000000CC ;# DDR SDRAM Address Control Register
 mww 0xD0001414 0x00000000 ;# DDR SDRAM Open Pages Control Register
 mww 0xD0001418 0x00000000 ;# DDR SDRAM Operation Register
 mww 0xD000141C 0x00000C52 ;# DDR SDRAM Mode Register
 mww 0xD0001420 0x00000042 ;# DDR SDRAM Extended Mode Register
 mww 0xD0001424 0x0000F17F ;# Dunit Control High Register
 mww 0xD0001428 0x00085520 ;# Dunit Control High Register
 mww 0xD000147c 0x00008552 ;# Dunit Control High Register
 mww 0xD0001504 0x0FFFFFF1 ;# CS0n Size Register
 mww 0xD0001508 0x10000000 ;# CS1n Base Register
 mww 0xD000150C 0x0FFFFFF5 ;# CS1n Size Register
 mww 0xD0001514 0x00000000 ;# CS2n Size Register
 mww 0xD000151C 0x00000000 ;# CS3n Size Register
 mww 0xD0001494 0x003C0000 ;# DDR2 SDRAM ODT Control (Low) Register
 mww 0xD0001498 0x00000000 ;# DDR2 SDRAM ODT Control (High) REgister
 mww 0xD000149C 0x0000F80F ;# DDR2 Dunit ODT Control Register
 mww 0xD0001480 0x00000001 ;# DDR SDRAM Initialization Control Register
 mww 0xD0020204 0x00000000 ;# Main IRQ Interrupt Mask Register
 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 ;# MPP 0 to 7
 mww 0xD0010004 0x11113322 ;# MPP 8 to 15
 mww 0xD0010008 0x00001111 ;# MPP 16 to 23
 mww 0xD0010418 0x003E07CF ;# NAND Read Parameters REgister
 mww 0xD001041C 0x000F0F0F ;# NAND Write Parameters Register
 mww 0xD0010470 0x01C7D943 ;# NAND Flash Control Register
 }
 proc pogo_reflash_uboot { } {
 # reflash the u-Boot binary and reboot into it
 pogo_init
 nand probe 0
 nand erase 0 0x0 0xa0000
 nand write 0 uboot.kwb 0 oob_softecc_kw
 resume
 }
 proc pogo_reflash_uboot_env { } {
 # reflash the u-Boot environment variables area
 pogo_init
 nand probe 0
 nand erase 0 0xc0000 0x20000
 nand write 0 uboot-env.bin 0xc0000 oob_softecc_kw
 resume
 }
 proc pogo_load_uboot { } {
 # load u-Boot into RAM and execute it
 pogo_init
 load_image uboot.kwb
 verify_image uboot.kwb
 resume 0x800200
 }
Reply Quote
bodhi
Re: Bricked or not, that is the question :/
November 24, 2018 12:09AM
alonetrio,

>
> so i soldered jtag, and seems ok using openocd :
>
>
> 
> root@raspberrypi:~# openocd -f pogo.cfg           
>                         
> Open On-Chip Debugger 0.10.0+dev-00581-g1b864d6e
> (2018-11-24-00:25)
> Licensed under GNU GPL v2
> For bug reports, read
>         http://openocd.org/doc/doxygen/bugs.html
> 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
> adapter_nsrst_delay: 500
> 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
> dcc downloads are enabled
> 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
> Info : accepting 'telnet' connection on tcp/4444
> Info : Halt timed out, wake up GDB.
> Error: timed out while waiting for target halted
>
>
> i can't halt it :/ and without it i can't acces
> nand...
>
>
> without knowing what i'm doing i use this conf:
> perhaps some address are not good.
>
> 
> # Pogoplug E02                                    
>                                                   
>                           
>  # modification joerg_999 14.03.2016              
>                                                   
>                           
>  # use this pogo.cfg taken from sheevaplug to use
> with Raspi direct or Buspirate jtag adapter       
>                            
>  # use raspberrypi-native mode                    
>                                                   
>                           
>  # we use the Pins from SPI Interface (violett)
> 19,21,23,26 and 22, + 20 for GND                  
>                              
>  # see GPIO schematic Raspi Raspi GPIO            
>                                                   
>                           
>                                                   
>                                                   
>                           
>  # source [find interface/buspirate.cfg]          
>                                                   
>                           
>  # source [find
> interface/sysfsgpio-raspberrypi.cfg]              
>                                                   
>           
>  source [find interface/raspberrypi123-native.cfg]
>                                                   
>                           
>  source [find target/feroceon.cfg]                
>                                                   
>                           
>                                                   
>                                                   
>                           
> $_TARGETNAME configure \                          
>                                                   
>                           
> -work-area-phys 0x10000000 \                      
>                                                   
>                           
> -work-area-size 65536 \                           
>                                                   
>                           
> -work-area-backup 0                               
>                                                   
>                           
> 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 pogo_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 ;# DDR SDRAM
> Configuration Register
>  mww 0xD0001404 0x39543000 ;# Dunit Control Low
> Register
>  mww 0xD0001408 0x22125451 ;# DDR SDRAM Timing
> (Low) Register
>  mww 0xD000140C 0x00000833 ;# DDR SDRAM Timing
> (High) Register
>  mww 0xD0001410 0x000000CC ;# DDR SDRAM Address
> Control Register
>  mww 0xD0001414 0x00000000 ;# DDR SDRAM Open Pages
> Control Register
>  mww 0xD0001418 0x00000000 ;# DDR SDRAM Operation
> Register
>  mww 0xD000141C 0x00000C52 ;# DDR SDRAM Mode
> Register
>  mww 0xD0001420 0x00000042 ;# DDR SDRAM Extended
> Mode Register
>  mww 0xD0001424 0x0000F17F ;# Dunit Control High
> Register
>  mww 0xD0001428 0x00085520 ;# Dunit Control High
> Register
>  mww 0xD000147c 0x00008552 ;# Dunit Control High
> Register
>  mww 0xD0001504 0x0FFFFFF1 ;# CS0n Size Register
>  mww 0xD0001508 0x10000000 ;# CS1n Base Register
>  mww 0xD000150C 0x0FFFFFF5 ;# CS1n Size Register
>  mww 0xD0001514 0x00000000 ;# CS2n Size Register
>  mww 0xD000151C 0x00000000 ;# CS3n Size Register
>  mww 0xD0001494 0x003C0000 ;# DDR2 SDRAM ODT
> Control (Low) Register
>  mww 0xD0001498 0x00000000 ;# DDR2 SDRAM ODT
> Control (High) REgister
>  mww 0xD000149C 0x0000F80F ;# DDR2 Dunit ODT
> Control Register
>  mww 0xD0001480 0x00000001 ;# DDR SDRAM
> Initialization Control Register
>  mww 0xD0020204 0x00000000 ;# Main IRQ Interrupt
> Mask Register
>  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 ;# MPP 0 to 7
>  mww 0xD0010004 0x11113322 ;# MPP 8 to 15
>  mww 0xD0010008 0x00001111 ;# MPP 16 to 23
>  mww 0xD0010418 0x003E07CF ;# NAND Read Parameters
> REgister
>  mww 0xD001041C 0x000F0F0F ;# NAND Write
> Parameters Register
>  mww 0xD0010470 0x01C7D943 ;# NAND Flash Control
> Register
>  }
>  proc pogo_reflash_uboot { } {
>  # reflash the u-Boot binary and reboot into it
>  pogo_init
>  nand probe 0
>  nand erase 0 0x0 0xa0000
>  nand write 0 uboot.kwb 0 oob_softecc_kw
>  resume
>  }
>  proc pogo_reflash_uboot_env { } {
>  # reflash the u-Boot environment variables area
>  pogo_init
>  nand probe 0
>  nand erase 0 0xc0000 0x20000
>  nand write 0 uboot-env.bin 0xc0000
> oob_softecc_kw
>  resume
>  }
>  proc pogo_load_uboot { } {
>  # load u-Boot into RAM and execute it
>  pogo_init
>  load_image uboot.kwb
>  verify_image uboot.kwb
>  resume 0x800200
>  }
> 
>

Please repost this in joerg's JTAG thread:

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

I'll comment on your questions after that.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
alonetrio
Re: Bricked or not, that is the question :/
November 24, 2018 04:09AM
ok !! done ! ;)
Reply Quote
Newer Topic Older Topic
Author:

Your Email:


Subject:
Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: