Welcome! Log In Create A New Profile

Advanced

UART Boot DNS-320 B1 with broken NAND

Posted by Ironaxe 
Re: UART Boot DNS-320 B1 with broken NAND
March 07, 2019 02:49AM
Ok. Then "unfortunately" it is right :(
Re: UART Boot DNS-320 B1 with broken NAND
March 07, 2019 02:57AM
May be you should try the compress air again on this NAND :)

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: UART Boot DNS-320 B1 with broken NAND
March 07, 2019 03:05AM
Ironaxe Wrote:
-------------------------------------------------------
> Thats a little too high for me ^^
> But 101 = 5 is right *lol*
>
> But does the 6182 equals the 6702 ?
> According to the "so called" Datasheet it aint got
> SPI but the LaCie Cloud Box has SPI Flash with
> this CPU

No it is not equal. That's why I raised the question about the SPI flash. Some 6281 boxes have both NAND and SPI, or either.

However, the 6702 and 6192 are the same and the 6192 also has the same SatR layout for boot device as the 6281.

Bits[14:12] = Boot device.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: UART Boot DNS-320 B1 with broken NAND
March 07, 2019 03:12AM
bodhi Wrote:
-------------------------------------------------------
> May be you should try the compress air again on
> this NAND :)

Tried that without luck ^^
Re: UART Boot DNS-320 B1 with broken NAND
March 07, 2019 03:22AM
I forgot that this is 6702 for a moment :)

However, that SAR register and boot device are identical for 6218 and 6192/6702.

I think we are back to my conclusion: could be that the NAND flash controller failed to read NAND device during bootROM.

Or may be the reset pins were damaged when you replace NAND so it default to SPI?

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 2 time(s). Last edit at 03/07/2019 03:27AM by bodhi.
Re: UART Boot DNS-320 B1 with broken NAND
March 07, 2019 03:31AM
bodhi Wrote:
-------------------------------------------------------
> Or may be the reset pins were damaged when you
> replace NAND so it default to SPI?

When ive put back in the Original NAND it booted up ( with the freezing ) so i would guess its possibly not that.
Re: UART Boot DNS-320 B1 with broken NAND
March 07, 2019 03:51AM
Im just trying to check my mtd0.dns-320 File against the Data found in the
88F6192 Functional Diagram ( 24.2.4.1Main Header Format )
Re: UART Boot DNS-320 B1 with broken NAND
March 07, 2019 03:52AM
> When ive put back in the Original NAND it booted
> up ( with the freezing ) so i would guess its
> possibly not that.

Ah. Then the all register settings are correct already.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: UART Boot DNS-320 B1 with broken NAND
March 07, 2019 03:56AM
Ironaxe Wrote:
-------------------------------------------------------
> Im just trying to check my mtd0.dns-320 File
> against the Data found in the
> 88F6192 Functional Diagram ( 24.2.4.1Main Header
> Format )

That's a another good thing to check! But since you dump that from the good box, that header should be OK.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: UART Boot DNS-320 B1 with broken NAND
March 07, 2019 04:01AM
Maybe i should disable ECC to try.

Ok. Not nessessary.

The bootROM tries to boot from four types of NAND flash devices four times (a total of 16 times). 
The first eight trials are performed with ECC calculation and the last eight trials are performed 
skipping ECC correction. 
A NAND flash reset (using the command 0xFF) is performed before each boot trial.

Maybe could it be helpful to get to the Command Line Debug Mode ?

Boot from UART0

As previously indicated, boot from UART0 is not a sample at reset configuration option, but is performed before every type of boot through sensing the Rx side of the UART0 interface on both MPP options.
If the debug pattern (0xDD 0x11 0x22 0x33 0x44 0x55 0x66 0x77) was received, 
the bootROM enters the command line debug mode. 
Otherwise, if the boot sequence (0xBB 0x11 0x22 0x33 0x44 0x55 0x66 0x77) was received, 
the bootROM enters the Boot from UART routine, which starts receiving the boot image using the Xmodem protocol (i.e., it starts receiving chunks of 128 bytes, each with an 8-bit checksum).
The boot image must be a continuous image, which includes a main header 
and an extension header (extended header is mandatory in this case, 
since the DDR must be initialized).The main header, extension header, 
and source image must contain valid checksum values.
According to the boot sequence described above, this boot method: 
1.Executes the registers configuration in the extended header.
2.Downloads the source image to DDR. 
3.Executes it in the DDR.



Edited 3 time(s). Last edit at 03/07/2019 05:27AM by Ironaxe.
Re: UART Boot DNS-320 B1 with broken NAND
March 07, 2019 12:44PM
Ironaxe,

I use the BootROM debug mode all the time on the NAS326. The NAS326 has a quirk that if you connect serial console, it get stuck there waiting for UART. So the debug mode cause BootROM to wait for data, and eventually timeout and boot normally.


Quote
https://forum.doozan.com/read.php?2,32146
A2. Installation

.....

1. Start kwboot on the serial console host

For ARM32 kwboot:
./kwboot -t -B 115200 /dev/ttyUSB0 -d

Ah, another idea. Start the kwboot in debug mode and let it sit there to see if the timeout occur the same way, and perhaps it will spit out something.

Nobody really knows what we can do other a couple commands with BootROM. I am sure Marvell engineers know, but they never disclosed how. I don't recall what those are (been quite a while since I looked).

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 03/07/2019 12:45PM by bodhi.
Re: UART Boot DNS-320 B1 with broken NAND
March 08, 2019 03:58AM
No timeout after 15 Minutes ^^
Just the input Prompt.

root@debian:/dns-320l# kwboot -t -B 115200 /dev/ttyUSB0 -d
Sending debug message. Please reboot the target.../
[Type Ctrl-\ + c to quit]
>
Re: UART Boot DNS-320 B1 with broken NAND
March 08, 2019 04:24AM
Ironaxe Wrote:
-------------------------------------------------------
> No timeout after 15 Minutes ^^
> Just the input Prompt.
>
>
> root@debian:/dns-320l# kwboot -t -B 115200
> /dev/ttyUSB0 -d
> Sending debug message. Please reboot the
> target.../
> [Type Ctrl-\ + c to quit]
> >
>

I recall trying 2 commands. But it was too long ago, so I forgot what they were. Apparently they were not useful enough for me to put them in my notes :) I guess googling will turn up some commands.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: UART Boot DNS-320 B1 with broken NAND
March 08, 2019 05:16AM
Schematics would bei nice ^^
Would love to replace the Nand with SPI Flash.
Re: UART Boot DNS-320 B1 with broken NAND
March 08, 2019 06:44PM
Ironaxe,

> Schematics would bei nice ^^
> Would love to replace the Nand with SPI Flash.

I have never seen a schematic for any of these Kirkwood SoCs or boxes. I only go by what's in their Reference Manuals and GPL source. FWIW, I don't have any NDA so not privy to their protected IPs :)

Don't know if it is possible to use SPI flash for this box.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: UART Boot DNS-320 B1 with broken NAND
March 11, 2019 11:51AM
So. Do we have any more options?
Re: UART Boot DNS-320 B1 with broken NAND
March 11, 2019 04:00PM
Ironaxe,

> > May be you should try the compress air again on
> > this NAND :)
>
> Tried that without luck ^^

I think the bootROM did not recognize the NAND chip. But you can search for Marvell BootROM commands to see if you can find anything.

-bodhi
===========================
Forum Wiki
bodhi's corner
reostatic
Re: UART Boot DNS-320 B1 with broken NAND
April 03, 2019 12:15AM
Hi, I have the same problem with this nas. I have to frezze nas to work. Is there a solution to this problem?
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: