uboot screen not response after using JTAG to flash uboot

Hi Guys ,

I'm new to the forum and just follow the step to flash the uboot .

I'm using Pogoplug E02 (Pink) , and I first successfully installed ArchLinux and frankly i don't much command in ArchLinux comparing to Debian , so i want to update my Pogoplug to Debian but i accidentally erased uboot and of course it's bricked .

Then I get the buspirate to flash the Pogoplug via JTAG ,

Flashing process seems working as I have uboot screen showing in other terminal but the thing is it doesn't respond , it hangs at "CE>" and I cant type to write the nand again , so i have to use JTAG to flash again .

I don't know that I do something wrong or not , because sometimes the uboot screen is responding and sometimes it doesn't .

The command i use in buspirate is

dockstar_init
nand probe 0
load_image uboot.bin 0x800000
resume 0x800200

then after "resume 0x800200" , uboot screen comes up , and i press "Enter" many times , but it doesn't respond at all .

Is there anything I can do to solve this problem and make my pogoplug install DEbian successfully again .

Hope you guys have some ideas to share with me .

Thank you very much in Advance.

Cheers,
Penny

Are you interacting with uboot over serial console? I have no experience with JTAG on Pogoplug but for the dockstar, you need the bus pirate JTAG to flash uboot and a separate serial console connection for uboot

Hi dpffan ,

Yeah , I used the serial cable (DKU-5). And I use JTAG to flash uboot first , and it is successfully flashed but after the uboot show in the serial terminal , it just stop responding after it shows the prompt "CE>" . Which is weird .

IF you have some ideas , please share.

Thank you .
Cheers,
Penny

Here is my JTAG flash log .
It's successfully flashed.

> halt
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
> dockstar_init
> nand probe 0
NAND flash device 'NAND 128MiB 3.3V 8-bit (Samsung)' found
> load_image uboot-original-mtd0.kwb 0x800000
524288 bytes written at address 0x00800000
downloaded 524288 bytes in 218.830505s (2.340 KiB/s)
> resume 0x800200
>

Now when i press after "resume 0x800200" command , uboot process shows at the serial console ,
I don't know that there's something wrong with the uboot or not , it looks fine to me , but it just hangs at "CE>>"

here's the log

U-Boot 1.1.4 (Jul 16 2009 - 21:02:16) Cloud Engines (3.4.16)

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

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

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


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

Streaming disabled
Write allocate disabled


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



IS there anything I have to do or can i erase the whole nand thing and do it all over again ?
Anyone has the command to erase all from the jtag ?

Thank you very much .

Cheers,
Penny

http://forum.doozan.com/read.php?3,6965,7073#msg-7073

nand erase 0x0 0x80000

You have to look up the syntax for PogoPlug E02 uboot as I have no idea what is the address range to also erase E02's uboot environment

Hi dpffan ,

On that command , I cannot just run it yet , as i told you then it hangs after it shows the "CE>>" prompt .
That command will be run after this , so right now my problem is that i cannot type anything in the prompt yet .
That's why the command will not work for now .

I don't know what's wrong with my E02 :(

Cheers,
Penny

nand erase command is available from openocd too

Hi dpffan ,

Here's the result running in openocd

> nand erase 0x0 0x80000
nand erase bank_id [offset length]
in procedure 'nand'


but for

> nand erase 0 0x0 0x80000
erased blocks 0 to 3 on NAND flash device #0 'NAND 128MiB 3.3V 8-bit'


so i don't know that i point to the correct location or not .
or do you know whether there's location that i can erase everything?

Cheers,
Penny

This was used for the dockstar: http://archlinuxarm.org/forum/viewtopic.php?f=18&t=195&start=130#p5606

AFAIK Pogoplug E02 has less NAND than dockstar. davygravy knows all these uboot stuff very well. You probably have better luck if he replies

Hi dpffan ,

Ok i hope that davygravy might come and see this post and provide some guidance then .
I really have no idea what's wrong with my pogoplug , because i used to be able to flash from openocd and type anything on the uboot , but now it just hangs at the command prompt , and i can't go further .

Thank you very much Anyway dpffan .

Hi all ,

After trying with so many new serial cable , i think i found the problem .

I think the "TX" pin of my pogoplug is broken . It doesn't seem to response with any cable at all .

So is anyone having a way to get over this , I think if i can just flash via openocd and make it able to configure through SSH it will be ok .

IF anyone can help , really appreciate this .

Thank you very much .
Penny

Looks like uboot environment is corrupted from this output

NAND:128 MB 
*** Warning - bad CRC or NAND, using default environment

You can try the mkenvimage tool gnexus posted: http://forum.doozan.com/read.php?3,8579 to prepare a good uboot environment with a working netconsole and flash that to nand with openocd. Once netconsole is working, the need for a working serial console lessens. SSH won't work until Linux boots but netconsole is a good substitute.

I'm unable to provide more details as I don't have the Pogoplug. Good luck.