Welcome! Log In Create A New Profile

Advanced

Debian on Netgear RN102

Posted by whitepawn 
Re: Debian on Netgear RN102
September 21, 2020 10:19AM
Bodhi,

Quote
Bodhi
Remember the previous posts above? that "living dangerously" has come back and bitten you in the rear :)
I laughed so hard, but you are right:)I am just having fun maybe i am a masochist:)
But i must admit it is a big learning curve for me so thanks again.

I have tried my original mtd0 backup with both, I think you suspected bit-flaps or something that broke crc image but it seems no effect.Same CRC error:

nandwrite --noecc /dev/mtd0 mtd0.bin
And,
nandwrite /dev/mtd0 mtd0.bin

Now i am suspected NAND configuration is not correct in U-Boot source code.But i have find some interesting findings with serial recovery from u-boot.Let me explained what i have done so far:

-Nandwrite from debian and u-boot can write and verify flash contents but when i rebooted system flash contents seems erased.I am not sure why this is happening, U-Boot initiates flash with our modified code, erases flash and writes temporarily only.This behave doesn't change with stock mtd0 backup and compiled u-boot and i think my compiled u-boot is not problem in here.
-When i flash u-boot (it doesn't matter stock one or my compiled one) and rebooted 2 times it marks block 0 and some as "bad".I have to always make nand scrub.chip and nand erase.chip before trying new things.I think this behave of bad NAND configuration.
-I have tried both sizes for u-boot(180000, 200000 and 400000(from mirabox recovery address)) in u-boot write:
nand write 0x7000000 0 0x00180000

nand write 0x7000000 0 0x00200000

nand write 0x7000000 0 0x00400000


Same behavior.
Attached tftp u-boot logs in post.

For this problem:
Quote
whitepawn
Edit2:
I just realized in u-boot nand info says:

Marvell>> nand info
Device 0: nand0, sector size 64 KiB
Page size 8192 b
OOB size 128 b
Erase size 65536 b

But in kernel:

nand: 8192 MiB, MLC, erase size: 2048 KiB, page size: 8192, OOB size: 744


Erase size and oob sizes are different.Is this relevant in our case?
I think this is the main problem so solution is either
u-boot-2011.12-armada370/drivers/mtd/nand/fsl_ifc_nand.c
or
u-boot-2011.12-armada370/include/configs/armada_370.h
according to this and this post but i don't know how to edit ifc_nand.c and armada_370.h for my flash or maybe as you said BootROM is not capable for this flash i don't know.

I will share my findings if i can find anything.

Sorry for late response, i had some things to do.

Regards



Edited 1 time(s). Last edit at 09/21/2020 10:21AM by whitepawn.
Attachments:
open | download - tftp400.log (178.5 KB)
open | download - tftp180.log (153 KB)
Re: Debian on Netgear RN102
September 21, 2020 06:30PM
whitepawn,

> Remember the previous posts above? that "living
> dangerously" has come back and bitten you in the
> rear :)
]
> I laughed so hard, but you are right:)I am just
> having fun maybe i am a masochist:)

Masochist is a friend of mine. I know Masochist. You, sir, are no masochist :)))

> But i must admit it is a big learning curve for me
> so thanks again.

No problem. I know this area is not easy to find info in one place out there.

> Now i am suspected NAND configuration is not
> correct in U-Boot source code.

I think you are close.

Now that I really think about this. I now remember vaguely that I came across some info that there is an option to specify type of NAND when you build u-boot image. Probably because all the boxes that I've built u-boot for only use regular NAND with 128K sector so I did not pay attention closely.

The BootROM will parse the header when it starts. Therefore this flash info must be inside the header.

Now I am quite positive that this can be overcome. Look at the build script, or the build log. And run that command (when the image is actually produced, either doimage or mkimage) at the command line to check the options available.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Debian on Netgear RN102
September 22, 2020 04:52AM
whitepawn,

Marvell u-boot build script uses ./tools/marvell/doimage.
doimage -T nand -D image_dest -E image_exec [-S address] -P page_size
         -L 2 -N S [other_options] image_in image_out

The option -N specify the NAND type. So to specify MLC:

doimage -T nand -D image_dest -E image_exec [-S address] -P page_size
         -L 2 -N M [other_options] image_in image_out

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Debian on Netgear RN102
September 23, 2020 11:53AM
Bodhi,
I have tried with these:
./build_rn102-nand.pl -v 2.7 -d /home/jigsaw/u-boot-2011.12-armada370/armada-370-netgear-rn102.dtb -P 8192 -L 2048 -N MLC

./build_rn102-nand.pl -v 2.5 -d /home/jigsaw/u-boot-2011.12-armada370/armada-370-netgear-rn102.dtb -P 4096 -L 128 -N MLC

./build_rn102-nand.pl -v 2.4 -d /home/jigsaw/u-boot-2011.12-armada370/armada-370-netgear-rn102.dtb -N M

But unfortunately none of them worked.
I also reviewed my steps and changed some of them:

Quote
whitepawn
I have edited nand_ids.c

{"NAND 8GiB 3,3V 16-bit Custom", 0x64, 0, 8192, 0, LP_OPTIONS16},

First it complained about 8 bit config which is LP_OPTIONS then i changed it to LP_OPTIONS16 no more complains from u-boot.
This must be only LP_OPTIONS for 8 bit which is my NAND bus width according to datasheet but u-boot doesn't like it.(Prints marvell logo constantly and doesn't detect flash chip size.)Bootloader seems working on LP_OPTIONS16 which is 16 bit, seems fishy to me but i actually don't know.
{"NAND 8GiB 3,3V 16-bit Custom",	0x64, 0, 8192, 0, LP_OPTIONS},

Another correction:
Previous mvNfc.c was:
{			/* Micron 64Gb */
	 .tADL = 0,		/* tADL, Address to write data delay */
	 .tCH = 20,		/* tCH, Enable signal hold time */
	 .tCS = 20,		/* tCS, Enable signal setup time */
	 .tWC = 90,		/* tWC, ND_nWE cycle duration */
	 .tWH = 45,		/* tWH, ND_nWE high duration */
	 .tWP = 45,		/* tWP, ND_nWE pulse time */
	 .tRC = 90,		/* tWC, ND_nRE cycle duration */
	 .tRH = 45,		/* tRH, ND_nRE high duration */
	 .tRP = 45,		/* tRP, ND_nRE pulse width */
	 .tR = 0,		/* tR = data transfer from cell to register */
	 .tWHR = 90,		/* tWHR, ND_nWE high to ND_nRE low delay for status read */
	 .tAR = 65,		/* tAR, ND_ALE low to ND_nRE low delay */
	 .tRHW = 32,		/* tRHW, ND_nRE high to ND_nWE low delay */
	 .pgPrBlk = 256,	/* Pages per block - detected */
	 .pgSz = 8192,		/* Page size */
	 .oobSz = 448,		/* Spare size */
	 .blkNum = 4096,	/* Number of blocks/sectors in the flash */
	 .id = 0x642C,		/* Device ID 0xDevice,Vendor */
	 .model = "Micron 64Gb 8bit",
	 .bb_page = 0,		/* Manufacturer Bad block marking page in block */
	 .flags = NFC_CLOCK_UPSCALE_200M
	 },

Edited this to:

{			/* Micron 64Gb */
	 .tADL = 0,		/* tADL, Address to write data delay */
	 .tCH = 20,		/* tCH, Enable signal hold time */
	 .tCS = 20,		/* tCS, Enable signal setup time */
	 .tWC = 90,		/* tWC, ND_nWE cycle duration */
	 .tWH = 45,		/* tWH, ND_nWE high duration */
	 .tWP = 45,		/* tWP, ND_nWE pulse time */
	 .tRC = 90,		/* tWC, ND_nRE cycle duration */
	 .tRH = 45,		/* tRH, ND_nRE high duration */
	 .tRP = 45,		/* tRP, ND_nRE pulse width */
	 .tR = 0,		/* tR = data transfer from cell to register */
	 .tWHR = 90,		/* tWHR, ND_nWE high to ND_nRE low delay for status read */
	 .tAR = 65,		/* tAR, ND_ALE low to ND_nRE low delay */
	 .tRHW = 32,		/* tRHW, ND_nRE high to ND_nWE low delay */
	 .pgPrBlk = 256,	/* Pages per block - detected */
	 .pgSz = 8192,		/* Page size */
	 .oobSz = 744,		/* Spare size */
	 .blkNum = 2048,	/* Number of blocks/sectors in the flash */
	 .id = 0x642C,		/* Device ID 0xDevice,Vendor */
	 .model = "Micron 64Gb 8bit",
	 .bb_page = 0,		/* Manufacturer Bad block marking page in block */
	 .flags = NFC_CLOCK_UPSCALE_200M
	 },

It didn't work either:)

Tried to port nand mtd driver from "u-boot-marvell-u-boot-2013.01-15t1" with my "0" zero software skills build failed of course:)Tried to debug it before this error but can't fix this one:

make[1]: *** No rule to make target '/home/jigsaw/u-boot-2011.12-armada370/board/mv_ebu/common/mv_hal/usibootup/usibootup.c', needed by '.depend'.  Stop.
make: *** [Makefile:466: board/mv_ebu/common/libmv_ebu.o] Error 2
make: *** Waiting for unfinished jobs....

 *** Error: Build failed


 *** Error: Build u-boot boot from NAND failed



While trying to fixing and looking some codes for hours i decide i should solder 4GB NAND because if i remember correctly there are some codes for 4096 page size and ECC sizes but no codes for 8192 in stock netgear.So i feel hopeless for 8GB (someone more intelligent and coding experienced than me can achieve this) but maybe 4GB will work easier, i will try with samsung and micron chip.
Will share results with you guys.
Regards.

EDIT:

Now things are getting interesting, when you are desperate and tired maybe sometimes good things happen.

I unsoldered 8GB NAND and soldered 4GB one which is a samsung branded.With stock Netgear U-boot it gives promising outputs even with stock bootloader:

root@whitepawnxeon:/home/jigsaw/Downloads# kwboot -t -B 115200 /dev/ttyUSB0 -b mtd0stockuboot.img -p
Sending boot message. Please reboot the target...-
Sending boot image...
  0 % [......................................................................]
  0 % [......................................................................]
  1 % [......................................................................]
  1 % [......................................................................]
  2 % [......................................................................]
  2 % [......................................................................]
  3 % [......................................................................]
  3 % [......................................................................]
  4 % [......................................................................]
  5 % [.........

General initialization - Version: 1.0.0

High speed PHY - Version: 2.1.4 (COM-PHY-V20) 
Update PEX Device ID 0x6710
High speed PHY - Ended Successfully
0000
DDR3 Training Sequence - Ver 5.7.1
DDR3 Training Sequence - Run without PBS.
DDR3 Training Sequence - Ended Successfully 
.............................................................]
  5 % [......................................................................]
  6 % [......................................................................]
  6 % [......................................................................]
  7 % [......................................................................]
  7 % [......................................................................]
  8 % [......................................................................]
  9 % [......................................................................]
  9 % [......................................................................]
 10 % [......................................................................]
 10 % [......................................................................]
 11 % [......................................................................]
 11 % [......................................................................]
 12 % [......................................................................]
 13 % [......................................................................]
 13 % [......................................................................]
 14 % [......................................................................]
 14 % [......................................................................]
 15 % [......................................................................]
 15 % [......................................................................]
 16 % [......................................................................]
 17 % [......................................................................]
 17 % [......................................................................]
 18 % [......................................................................]
 18 % [......................................................................]
 19 % [......................................................................]
 19 % [......................................................................]
 20 % [......................................................................]
 21 % [......................................................................]
 21 % [......................................................................]
 22 % [......................................................................]
 22 % [......................................................................]
 23 % [......................................................................]
 23 % [......................................................................]
 24 % [......................................................................]
 25 % [......................................................................]
 25 % [......................................................................]
 26 % [......................................................................]
 26 % [......................................................................]
 27 % [......................................................................]
 27 % [......................................................................]
 28 % [......................................................................]
 29 % [......................................................................]
 29 % [......................................................................]
 30 % [......................................................................]
 30 % [......................................................................]
 31 % [......................................................................]
 31 % [......................................................................]
 32 % [......................................................................]
 33 % [......................................................................]
 33 % [......................................................................]
 34 % [......................................................................]
 34 % [......................................................................]
 35 % [......................................................................]
 35 % [......................................................................]
 36 % [......................................................................]
 37 % [......................................................................]
 37 % [......................................................................]
 38 % [......................................................................]
 38 % [......................................................................]
 39 % [......................................................................]
 39 % [......................................................................]
 40 % [......................................................................]
 41 % [......................................................................]
 41 % [......................................................................]
 42 % [......................................................................]
 42 % [......................................................................]
 43 % [......................................................................]
 43 % [......................................................................]
 44 % [......................................................................]
 45 % [......................................................................]
 45 % [......................................................................]
 46 % [......................................................................]
 46 % [......................................................................]
 47 % [......................................................................]
 47 % [......................................................................]
 48 % [......................................................................]
 48 % [......................................................................]
 49 % [......................................................................]
 50 % [......................................................................]
 50 % [......................................................................]
 51 % [......................................................................]
 51 % [......................................................................]
 52 % [......................................................................]
 52 % [......................................................................]
 53 % [......................................................................]
 54 % [......................................................................]
 54 % [......................................................................]
 55 % [......................................................................]
 55 % [......................................................................]
 56 % [......................................................................]
 56 % [......................................................................]
 57 % [......................................................................]
 58 % [......................................................................]
 58 % [......................................................................]
 59 % [......................................................................]
 59 % [......................................................................]
 60 % [......................................................................]
 60 % [......................................................................]
 61 % [......................................................................]
 62 % [......................................................................]
 62 % [......................................................................]
 63 % [......................................................................]
 63 % [......................................................................]
 64 % [......................................................................]
 64 % [......................................................................]
 65 % [......................................................................]
 66 % [......................................................................]
 66 % [......................................................................]
 67 % [......................................................................]
 67 % [......................................................................]
 68 % [......................................................................]
 68 % [......................................................................]
 69 % [......................................................................]
 70 % [......................................................................]
 70 % [......................................................................]
 71 % [......................................................................]
 71 % [......................................................................]
 72 % [......................................................................]
 72 % [......................................................................]
 73 % [......................................................................]
 74 % [......................................................................]
 74 % [......................................................................]
 75 % [......................................................................]
 75 % [......................................................................]
 76 % [......................................................................]
 76 % [......................................................................]
 77 % [......................................................................]
 78 % [......................................................................]
 78 % [......................................................................]
 79 % [......................................................................]
 79 % [......................................................................]
 80 % [......................................................................]
 80 % [......................................................................]
 81 % [......................................................................]
 82 % [......................................................................]
 82 % [......................................................................]
 83 % [......................................................................]
 83 % [......................................................................]
 84 % [......................................................................]
 84 % [......................................................................]
 85 % [......................................................................]
 86 % [......................................................................]
 86 % [......................................................................]
 87 % [......................................................................]
 87 % [......................................................................]
 88 % [......................................................................]
 88 % [......................................................................]
 89 % [......................................................................]
 90 % [......................................................................]
 90 % [......................................................................]
 91 % [......................................................................]
 91 % [......................................................................]
 92 % [......................................................................]
 92 % [......................................................................]
 93 % [......................................................................]
 94 % [......................................................................]
 94 % [......................................................................]
 95 % [......................................................................]
 95 % [......................................................................]
 96 % [......................................................................]
 96 % [......................................................................]
 97 % [......................................................................]
 97 % [......................................................................]
 98 % [......................................................................]
 99 % [......................................................................]
 99 % [......................................]
[Type Ctrl-\ + c to quit]

 __   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_ 
        | | | |___|  _ \ / _ \ / _ \| __| 
        | |_| |___| |_) | (_) | (_) | |_ 
         \___/    |____/ \___/ \___/ \__| 
 ** LOADER **


U-Boot 2011.12-gec25d27-dirty (Oct 26 2015 - 16:53:05) Marvell version: v2011.12 2014_T2.0p1 
06/23/2015 ReadyNAS-102 V2.0

Board: DB-88F6710-BP
SoC:   MV6710 A1
CPU:   Marvell PJ4B v7 UP (Rev 1) LE
       CPU    @ 1200 [MHz]
       L2     @ 600 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 600 [MHz]
       DDR 16Bit Width, FastPath Memory Access
DRAM:  512 MiB

Map:   Code:		0x1feef000:0x1ff9ef34
       BSS:		0x1ffef0a0
       Stack:		0x1f9eeef8
       Heap:		0x1f9ef000:0x1feef000

NAND:  (ID 0xd7ec)	nand_get_flash_type: second ID read did not match ac,d7 against ec,52
No NAND device found!!!
0 MiB
MMC:   MRVL_MMC: 0
*** Warning - readenv() failed, using default environment


Initialize and scan all PCI interfaces
PEX unit.port(active IF[-first bus]):
------------------------------------------
PEX 0: Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1: Root Complex Interface, Detected Link X1, GEN 2.0
FPU not initialized
USB 0: Host Mode
USB 1: Host Mode
Shutting down unused interfaces:
       GBE0
       SDIO
       AUDIO
       TDM
Modules/Interfaces Detected:
       RGMII1 Phy
       PEX0 (Lane 0)
       PEX1 (Lane 1)
       SATA0 (Lane 2)
       SATA1 (Lane 3)
Net:   , egiga1 [PRIME]
Detect MVT/MP board...
Saving Environment to NAND...
Erasing Nand...
Attempt to erase non page aligned data
Power On!

Updating env to v3...
Saving Environment to NAND...
Erasing Nand...
Attempt to erase non page aligned data
raise: Signal # 8 caught
raise: Signal # 8 caught

 __   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_ 
        | | | |___|  _ \ / _ \ / _ \| __| 
        | |_| |___| |_) | (_) | (_) | |_ 
         \___/    |____/ \___/ \___/ \__| 
 ** LOADER **


U-Boot 2011.12-gec25d27-dirty (Oct 26 2015 - 16:53:05) Marvell version: v2011.12 2014_T2.0p1 
06/23/2015 ReadyNAS-102 V2.0

Board: DB-88F6710-BP
SoC:   MV6710 A1
CPU:   Marvell PJ4B v7 UP (Rev 1) LE
       CPU    @ 1200 [MHz]
       L2     @ 600 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 600 [MHz]
       DDR 16Bit Width, FastPath Memory Access
DRAM:  512 MiB

Map:   Code:		0x1feef000:0x1ff9ef34
       BSS:		0x1ffef0a0
       Stack:		0x1f9eeef8
       Heap:		0x1f9ef000:0x1feef000

NAND:  (ID 0xd7ec)	nand_get_flash_type: second ID read did not match ac,d7 against ec,53
No NAND device found!!!
0 MiB
MMC:   MRVL_MMC: 0
*** Warning - readenv() failed, using default environment


Initialize and scan all PCI interfaces
PEX unit.port(active IF[-first bus]):
------------------------------------------
PEX 0: Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1: Root Complex Interface, Detected Link X1, GEN 2.0
FPU not initialized
USB 0: Host Mode
USB 1: Host Mode
Shutting down unused interfaces:
       GBE0
       SDIO
       AUDIO
       TDM
Modules/Interfaces Detected:
       RGMII1 Phy
       PEX0 (Lane 0)
       PEX1 (Lane 1)
       SATA0 (Lane 2)
       SATA1 (Lane 3)
Net:   , egiga1 [PRIME]
Detect MVT/MP board...
Saving Environment to NAND...
Erasing Nand...
Attempt to erase non page aligned data
Power On!

Updating env to v3...
Saving Environment to NAND...
Erasing Nand...
Attempt to erase non page aligned data
raise: Signal # 8 caught
raise: Signal # 8 caught

 __   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_ 
        | | | |___|  _ \ / _ \ / _ \| __| 
        | |_| |___| |_) | (_) | (_) | |_ 
         \___/    |____/ \___/ \___/ \__| 
 ** LOADER **


U-Boot 2011.12-gec25d27-dirty (Oct 26 2015 - 16:53:05) Marvell version: v2011.12 2014_T2.0p1 
06/23/2015 ReadyNAS-102 V2.0

Board: DB-88F6710-BP
SoC:   MV6710 A1
CPU:   Marvell PJ4B v7 UP (Rev 1) LE
       CPU    @ 1200 [MHz]
       L2     @ 600 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 600 [MHz]
       DDR 16Bit Width, FastPath Memory Access
DRAM:  512 MiB

Map:   Code:		0x1feef000:0x1ff9ef34
       BSS:		0x1ffef0a0
       Stack:		0x1f9eeef8
       Heap:		0x1f9ef000:0x1feef000

NAND:  (ID 0xd7ec)	nand_get_flash_type: second ID read did not match ac,d7 against ec,53
No NAND device found!!!
0 MiB
MMC:   MRVL_MMC: 0
*** Warning - readenv() failed, using default environment


Initialize and scan all PCI interfaces
PEX unit.port(active IF[-first bus]):
------------------------------------------
PEX 0: Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1: Root Complex Interface, Detected Link X1, GEN 2.0
FPU not initialized
USB 0: Host Mode
USB 1: Host Mode
Shutting down unused interfaces:
       GBE0
       SDIO
       AUDIO
       TDM
Modules/Interfaces Detected:
       RGMII1 Phy
       PEX0 (Lane 0)
       PEX1 (Lane 1)
       SATA0 (Lane 2)
       SATA1 (Lane 3)
Net:   , egiga1 [PRIME]

It seems it is partially detected:

NAND:  (ID 0xd7ec)	nand_get_flash_type: second ID read did not match ac,d7 against ec,53

Now i will make a fresh start because i edit so many things on stock u-boot.
Will post results if it works.
EDIT2:

It seems no editing needed for mvNfc.c and nand_ids.c because device id is d7 manufacturer id is ec(samsung) is already there.

#ifdef CONFIG_MV_MTD_MLC_NAND_SUPPORT
	/* 32 Gigabit - wrongly detected due to changes in READ_ID decoding */
	{"NAND 4GiB 3,3V 8-bit",	0xD7, 4096, 4096, 524288, LP_OPTIONS},

{			/* Samsung 32Gb */
	 .tADL = 0,		/* tADL, Address to write data delay */
	 .tCH = 5,		/* tCH, Enable signal hold time */
	 .tCS = 20,		/* tCS, Enable signal setup time */
	 .tWC = 25,		/* tWC, ND_nWE cycle duration */
	 .tWH = 10,		/* tWH, ND_nWE high duration */
	 .tWP = 15,		/* tWP, ND_nWE pulse time */
	 .tRC = 30,		/* tWC, ND_nRE cycle duration */
	 .tRH = 15,		/* tRH, ND_nRE high duration */
	 .tRP = 15,		/* tRP, ND_nRE pulse width */
	 .tR = 60000,		/* tR = data transfer from cell to register, maximum 60,000ns */
	 .tWHR = 60,		/* tWHR, ND_nWE high to ND_nRE low delay for status read */
	 .tAR = 10,		/* tAR, ND_ALE low to ND_nRE low delay */
	 .tRHW = 48,		/* tRHW, ND_nRE high to ND_nWE low delay */
	 .pgPrBlk = 128,	/* Pages per block - detected */
	 .pgSz = 4096,		/* Page size */
	 .oobSz = 128,		/* Spare size */
	 .blkNum = 8192,	/* Number of blocks/sectors in the flash */
	 .id = 0xD7EC,		/* Device ID 0xDevice,Vendor */
	 .model = "Samsung 32Gb 8bit",
	 .bb_page = 127,	/* Manufacturer Bad block marking page in block */
	 .flags = NFC_CLOCK_UPSCALE_200M
	 },

But now i am in another trouble which is this type of flashs are have another device id which is supported by a patch to nand_base.c.I have tried to port marvell 2013.01 nand_base.c because it seems they included in it but not in my stock netgear nand_base.c
I tried to patch it but i get this error:
Building linker script for board a370, Non-secure mode
Building linker script for board a370, Secure mode
nand_base.c: In function 'nand_flash_detect_non_onfi':
nand_base.c:2532:20: error: 'id_data' undeclared (first use in this function)
nand_base.c:2532:20: note: each undeclared identifier is reported only once for each function it appears in
nand_base.c:2589:37: error: invalid storage class for function 'nand_get_flash_type'
nand_base.c: In function 'nand_get_flash_type':
nand_base.c:2595:6: error: 'dev_id' redeclared as different kind of symbol
nand_base.c:2592:27: note: previous definition of 'dev_id' was here
nand_base.c:2614:2: error: invalid type argument of unary '*' (have 'int')
nand_base.c:2635:50: error: expected ')' before ';' token
nand_base.c:2637:3: warning: format '%x' expects a matching 'unsigned int' argument [-Wformat]
nand_base.c:2637:3: warning: format '%x' expects a matching 'unsigned int' argument [-Wformat]
nand_base.c:2637:3: warning: format '%x' expects a matching 'unsigned int' argument [-Wformat]
nand_base.c:2637:3: error: expected ';' before '}' token
nand_base.c:2643:7: error: invalid type argument of unary '*' (have 'int')
nand_base.c:2649:7: error: invalid type argument of unary '*' (have 'int')
nand_base.c:2649:27: error: invalid type argument of unary '*' (have 'int')
nand_base.c:2652:24: error: invalid type argument of unary '*' (have 'int')
nand_base.c:2669:2: error: 'ret' undeclared (first use in this function)
nand_base.c:2695:10: error: invalid type argument of unary '*' (have 'int')
nand_base.c:2734:2: error: invalid type argument of unary '*' (have 'int')
nand_base.c: In function 'nand_flash_detect_non_onfi':
nand_base.c:3115:1: error: expected declaration or statement at end of input
make[1]: *** [/home/jigsaw/u-boot-2011.12-armada370/config.mk:309: nand_base.o] Error 1
make: *** [Makefile:466: drivers/mtd/nand/libnand.o] Error 2
make: *** Waiting for unfinished jobs....



Edited 4 time(s). Last edit at 09/23/2020 07:18PM by whitepawn.
Re: Debian on Netgear RN102
September 26, 2020 05:10PM
whitepawn,

Since you've edited your post, I did not notice there is new info in it (the new post indicator in red) (until now I happen to want to read it again).


Quote

I have edited nand_ids.c

{"NAND 8GiB 3,3V 16-bit Custom", 0x64, 0, 8192, 0, LP_OPTIONS16},

First it complained about 8 bit config which is LP_OPTIONS then i changed it to LP_OPTIONS16 no more complains from u-boot.

This must be only LP_OPTIONS for 8 bit which is my NAND bus width according to datasheet but u-boot doesn't like it.(Prints marvell logo constantly and doesn't detect flash chip size.)Bootloader seems working on LP_OPTIONS16 which is 16 bit, seems fishy to me but i actually don't know.


Not sure I can recall what you mean by "u-boot doesn't like it."? so using LP_OPTIONS and built OK, but when running u-boot seems to choke on detecting NAND chip? and you can build with either LP_OPTIONS16 or LP_OPTIONS?

It is fishy, because the datasheet is always right.

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



Edited 2 time(s). Last edit at 09/26/2020 05:13PM by bodhi.
Re: Debian on Netgear RN102
September 26, 2020 06:49PM
Bodhi,

Quote
Bodhi
Since you've edited your post, I did not notice there is new info in it (the new post indicator in red) (until now I happen to want to read it again).
I didn't want to spam forum thats why i just edited post.In most forums i think it is forbidden, is it possible to post before someone replies in here?

Quote
Bodhi
Not sure I can recall what you mean by "u-boot doesn't like it."? so using LP_OPTIONS and built OK, but when running u-boot seems to choke on detecting NAND chip? and you can build with either LP_OPTIONS16 or LP_OPTIONS?
When i use this:
{"NAND 8GiB 3,3V 16-bit Custom", 0x64, 0, 8192, 0, LP_OPTIONS},

and compiled u-boot it gives this error in u-boot similiar to this and this post:
NAND bus width 8 instead 16 bit
No NAND device found!!!
but when i this:
{"NAND 8GiB 3,3V 16-bit Custom", 0x64, 0, 8192, 0, LP_OPTIONS16}

no error at all.I assume u-boot cannot determine properly if flash is 8 or 16 bit.Maybe some kind of patch is required.

Another info:I investigated more about usb reset and found this post which says CONFIG_USB_EHCI_TT_NEWSCHED in kernel may solve problem then i checked your kernel config and found:
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
CONFIG_USB_EHCI_PCI=y
Is already set to "yes" so another dead end for me:)

Now i am trying to solve samsung k9gbg08u0a flash problem and this is also very hard for me to fix nand driver so i am now trying to find another types of 4gb or 2gb NAND flashes.
Regards.



Edited 1 time(s). Last edit at 09/26/2020 06:50PM by whitepawn.
Re: Debian on Netgear RN102
September 26, 2020 07:01PM
whitepawn,

Your post is not clear. Do I understand it correctly below?


Quote

and compiled u-boot it gives this compile error in u-boot similiar to this and this post:

NAND bus width 8 instead 16 bit
No NAND device found!!!


Or is it the runtime error in u-boot log?

This is the reason I always want to see the complete serial console log!

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



Edited 1 time(s). Last edit at 09/26/2020 07:04PM by bodhi.
Re: Debian on Netgear RN102
September 26, 2020 07:08PM
Ah I see it is a run time error


Quote
https://lists.denx.de/pipermail/u-boot/2010-October/078192.html

Before getting to the u-boot prompt I get the following message:

NAND: NAND device: Manufacturer ID: 0x2c, Chip ID: 0x48 (Micron NAND
2GiB 3,3V 8-bit)
NAND bus width 8 instead 16 bit

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Debian on Netgear RN102
September 26, 2020 07:14PM
Quote

I didn't want to spam forum thats why i just edited post.In most forums i think it is forbidden, is it possible to post before someone replies in here?

It is OK, if the new info is substantial then a new post is better. I usually don't read a thread again, and only visit the thread when I see the red indicator for a new post.

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



Edited 1 time(s). Last edit at 09/26/2020 07:15PM by bodhi.
Re: Debian on Netgear RN102
September 27, 2020 06:25AM
Bodhi,

Quote
Bodhi
This is the reason I always want to see the complete serial console log!

Right now samsung 4gb is soldered to box thats why i couldn't give full log for 8gb one.If it helps i can resolder 8gb one and get a full log no problem.

Yes sir compiling u-boot is fine with both "LP_OPTIONS16" and "LP_OPTIONS".
With 8gb flash and "LP_OPTIONS" and loading compiled binary with kwboot it gives nand bus error.NAND bus detection seems doesn't work properly.

It seems fixing samsung nand is easier so i have tried this so far:

For samsung 4gb code is already there i didn't modified stock u-boot code and it doesn't give nand bus error.
/* 32 Gigabit - wrongly detected due to changes in READ_ID decoding */
	{"NAND 4GiB 3,3V 8-bit",	0xD7, 4096, 4096, 524288, LP_OPTIONS},

The error with stock u-boot:
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_ 
        | | | |___|  _ \ / _ \ / _ \| __| 
        | |_| |___| |_) | (_) | (_) | |_ 
         \___/    |____/ \___/ \___/ \__| 
 ** LOADER **


U-Boot 2011.12-gec25d27-dirty (Oct 26 2015 - 16:53:05) Marvell version: v2011.12 2014_T2.0p1 
06/23/2015 ReadyNAS-102 V2.0

Board: DB-88F6710-BP
SoC:   MV6710 A1
CPU:   Marvell PJ4B v7 UP (Rev 1) LE
       CPU    @ 1200 [MHz]
       L2     @ 600 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 600 [MHz]
       DDR 16Bit Width, FastPath Memory Access
DRAM:  512 MiB

Map:   Code:		0x1feef000:0x1ff9ef34
       BSS:		0x1ffef0a0
       Stack:		0x1f9eeef8
       Heap:		0x1f9ef000:0x1feef000

NAND:  (ID 0xd7ec)	nand_get_flash_type: second ID read did not match ac,d7 against ec,53
No NAND device found!!!
0 MiB
MMC:   MRVL_MMC: 0
*** Warning - readenv() failed, using default environment


Initialize and scan all PCI interfaces
PEX unit.port(active IF[-first bus]):
------------------------------------------
PEX 0: Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1: Root Complex Interface, Detected Link X1, GEN 2.0
FPU not initialized
USB 0: Host Mode
USB 1: Host Mode
Shutting down unused interfaces:
       GBE0
       SDIO
       AUDIO
       TDM
Modules/Interfaces Detected:
       RGMII1 Phy
       PEX0 (Lane 0)
       PEX1 (Lane 1)
       SATA0 (Lane 2)
       SATA1 (Lane 3)
Net:   , egiga1 [PRIME]


For samsung 4gb (K9GBG08U0M) one the code is already written but seems old for samsung chip.
It can't read 3rd 4th 5th and 6th sub-ids which determines page size ecc size block size etc. as described here.

Quote
http://lists.infradead.org/pipermail/linux-mtd/2010-May/029882.html
Samsung K9GAG08U0M (5-byte sequence): ec d5 14 b6 74
4th byte, bits 1:0 encode the page size: 0=1KiB, 1=2KiB, 2=4KiB, 3=8KiB
4th byte, bits 5:4 encode the block size: 0=64KiB, 1=128KiB, ...
4th byte, bit 6 encodes the OOB size: 0=8B/512B, 1=16B/512B

Samsung K9GAG08U0D (6-byte sequence): ec d5 94 29 34 41
4th byte, bits 1:0 encode the page size: 0=2KiB, 1=4KiB, 3=8KiB, 4=rsvd
4th byte, bits 7;5:4 encode the block size: 0=128KiB, 1=256KiB, ...
4th byte, bits 6;3:2 encode the OOB size: 1=128B/page, 2=218B/page

This patch uses the new 6-byte scheme if the ID code wraps around
exactly at byte 6, and falls back to the old scheme otherwise.

I have compared marvell 2013 u-boot nand_base.c with my stock netgear 2011 u-boot nand_base.c, it is similiar except NAND 3-4-5-6th id determination code.I have attached diff file and screenshots of related code.I have tried to patch it but it gives this error:
jigsaw@whitepawn:~/u-boot-2011.12-armada370$ ./build_rn102-nand.pl -v 3.4 -d /home/jigsaw/u-boot-2011.12-armada370/armada-370-netgear-rn102.dtb
No secure boot option selected

**** [Cleaning Make]	*****

Configuring for armada_370_db - Board: armada_370, Options: DB_88F6710_BP

**** [Setting Macros]	*****

Boot from NAND
** Little ENDIAN ** 
Enable NAND controller NFC
Support flash: NAND 
Project: RN102 
**** [Building U-BOOT]	*****

Generating include/generated/asm-offsets.h
/home/jigsaw/u-boot-2011.12-armada370/lib/sha1.c:389:19: warning: ‘_sha1_src’ defined but not used [-Wunused-const-variable=]
  389 | static const char _sha1_src[] = "_sha1_src";
      |                   ^~~~~~~~~
In file included from aisimage.c:29:
/home/jigsaw/u-boot-2011.12-armada370/include/image.h:534:12: warning: inline function ‘fit_parse_subimage’ declared but never defined
  534 | inline int fit_parse_subimage(const char *spec, ulong addr_curr,
      |            ^~~~~~~~~~~~~~~~~~
/home/jigsaw/u-boot-2011.12-armada370/include/image.h:532:12: warning: inline function ‘fit_parse_conf’ declared but never defined
  532 | inline int fit_parse_conf(const char *spec, ulong addr_curr,
      |            ^~~~~~~~~~~~~~
In file included from fit_image.c:31:
/home/jigsaw/u-boot-2011.12-armada370/include/image.h:534:12: warning: inline function ‘fit_parse_subimage’ declared but never defined
  534 | inline int fit_parse_subimage(const char *spec, ulong addr_curr,
      |            ^~~~~~~~~~~~~~~~~~
/home/jigsaw/u-boot-2011.12-armada370/include/image.h:532:12: warning: inline function ‘fit_parse_conf’ declared but never defined
  532 | inline int fit_parse_conf(const char *spec, ulong addr_curr,
      |            ^~~~~~~~~~~~~~
In file included from default_image.c:31:
/home/jigsaw/u-boot-2011.12-armada370/include/image.h:534:12: warning: inline function ‘fit_parse_subimage’ declared but never defined
  534 | inline int fit_parse_subimage(const char *spec, ulong addr_curr,
      |            ^~~~~~~~~~~~~~~~~~
/home/jigsaw/u-boot-2011.12-armada370/include/image.h:532:12: warning: inline function ‘fit_parse_conf’ declared but never defined
  532 | inline int fit_parse_conf(const char *spec, ulong addr_curr,
      |            ^~~~~~~~~~~~~~
In file included from /home/jigsaw/u-boot-2011.12-armada370/common/image.c:73:
/home/jigsaw/u-boot-2011.12-armada370/include/image.h:534:12: warning: inline function ‘fit_parse_subimage’ declared but never defined
  534 | inline int fit_parse_subimage(const char *spec, ulong addr_curr,
      |            ^~~~~~~~~~~~~~~~~~
/home/jigsaw/u-boot-2011.12-armada370/include/image.h:532:12: warning: inline function ‘fit_parse_conf’ declared but never defined
  532 | inline int fit_parse_conf(const char *spec, ulong addr_curr,
      |            ^~~~~~~~~~~~~~
In file included from imximage.c:32:
/home/jigsaw/u-boot-2011.12-armada370/include/image.h:534:12: warning: inline function ‘fit_parse_subimage’ declared but never defined
  534 | inline int fit_parse_subimage(const char *spec, ulong addr_curr,
      |            ^~~~~~~~~~~~~~~~~~
/home/jigsaw/u-boot-2011.12-armada370/include/image.h:532:12: warning: inline function ‘fit_parse_conf’ declared but never defined
  532 | inline int fit_parse_conf(const char *spec, ulong addr_curr,
      |            ^~~~~~~~~~~~~~
In file included from kwbimage.c:29:
/home/jigsaw/u-boot-2011.12-armada370/include/image.h:534:12: warning: inline function ‘fit_parse_subimage’ declared but never defined
  534 | inline int fit_parse_subimage(const char *spec, ulong addr_curr,
      |            ^~~~~~~~~~~~~~~~~~
/home/jigsaw/u-boot-2011.12-armada370/include/image.h:532:12: warning: inline function ‘fit_parse_conf’ declared but never defined
  532 | inline int fit_parse_conf(const char *spec, ulong addr_curr,
      |            ^~~~~~~~~~~~~~
In file included from mkimage.c:25:
/home/jigsaw/u-boot-2011.12-armada370/include/image.h:534:12: warning: inline function ‘fit_parse_subimage’ declared but never defined
  534 | inline int fit_parse_subimage(const char *spec, ulong addr_curr,
      |            ^~~~~~~~~~~~~~~~~~
/home/jigsaw/u-boot-2011.12-armada370/include/image.h:532:12: warning: inline function ‘fit_parse_conf’ declared but never defined
  532 | inline int fit_parse_conf(const char *spec, ulong addr_curr,
      |            ^~~~~~~~~~~~~~
In file included from omapimage.c:37:
/home/jigsaw/u-boot-2011.12-armada370/include/image.h:534:12: warning: inline function ‘fit_parse_subimage’ declared but never defined
  534 | inline int fit_parse_subimage(const char *spec, ulong addr_curr,
      |            ^~~~~~~~~~~~~~~~~~
/home/jigsaw/u-boot-2011.12-armada370/include/image.h:532:12: warning: inline function ‘fit_parse_conf’ declared but never defined
  532 | inline int fit_parse_conf(const char *spec, ulong addr_curr,
      |            ^~~~~~~~~~~~~~
In file included from ublimage.c:36:
/home/jigsaw/u-boot-2011.12-armada370/include/image.h:534:12: warning: inline function ‘fit_parse_subimage’ declared but never defined
  534 | inline int fit_parse_subimage(const char *spec, ulong addr_curr,
      |            ^~~~~~~~~~~~~~~~~~
/home/jigsaw/u-boot-2011.12-armada370/include/image.h:532:12: warning: inline function ‘fit_parse_conf’ declared but never defined
  532 | inline int fit_parse_conf(const char *spec, ulong addr_curr,
      |            ^~~~~~~~~~~~~~
  CC    aes.c
hdrparser.c: In function ‘parse_main_header’:
hdrparser.c:195:19: warning: too many arguments for format [-Wformat-extra-args]
  195 |   fprintf(stdout, "[15:12]Source address (LBA):      0x%08X\n",
      |                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
hdrparser.c:198:19: warning: too many arguments for format [-Wformat-extra-args]
  198 |   fprintf(stdout, "[15:12]Source address:            0x%08X\n",
      |                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
hdrparser.c: In function ‘parse_bin_header’:
hdrparser.c:295:18: warning: too many arguments for format [-Wformat-extra-args]
  295 |  fprintf(stdout, "[0005:0005]Reserved:              0x%02X\n",
      |                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
hdrparser.c:297:18: warning: too many arguments for format [-Wformat-extra-args]
  297 |  fprintf(stdout, "[0007:0005]Reserved:              0x%04X\n",
      |                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  CC    arc4.c
  CC    base64.c
  CC    bignum.c
  CC    certs.c
  CC    debug.c
  CC    des.c
  CC    dhm.c
  CC    havege.c
  CC    md2.c
  CC    md4.c
  CC    md5.c
  CC    net.c
  CC    padlock.c
  CC    rsa.c
  CC    sha1.c
  CC    sha2.c
  CC    sha4.c
  CC    ssl_cli.c
  CC    ssl_srv.c
  CC    ssl_tls.c
  CC    timing.c
  CC    x509parse.c
  CC    xtea.c
  CC    camellia.c
  CC    mvMemPool.c
  AR    libpolarssl.a
ar: creating libpolarssl.a
  RL    libpolarssl.a
  CC    aes/aescrypt2.c
  CC    hash/hello.c
  CC    hash/md5sum.c
  CC    hash/sha1sum.c
  CC    hash/sha2sum.c
  CC    pkey/dh_client.c
  CC    pkey/dh_genprime.c
  CC    pkey/dh_server.c
  CC    pkey/mpi_demo.c
  CC    pkey/rsa_genkey.c
  CC    pkey/rsa_sign.c
pkey/rsa_sign.c: In function ‘main’:
pkey/rsa_sign.c:104:17: warning: implicit declaration of function ‘sha4_file’; did you mean ‘sha1_file’? [-Wimplicit-function-declaration]
  104 |     if( ( ret = sha4_file( argv[1], hash, 0 ) ) != 0 )
      |                 ^~~~~~~~~
      |                 sha1_file
  CC    pkey/rsa_verify.c
  CC    ssl/ssl_client1.c
pkey/rsa_verify.c: In function ‘main’:
pkey/rsa_verify.c:129:17: warning: implicit declaration of function ‘sha4_file’; did you mean ‘sha1_file’? [-Wimplicit-function-declaration]
  129 |     if( ( ret = sha4_file( argv[1], hash, 0 ) ) != 0 )
      |                 ^~~~~~~~~
      |                 sha1_file
  CC    ssl/ssl_client2.c
  CC    ssl/ssl_server.c
  CC    test/benchmark.c
  CC    test/selftest.c
  CC    test/ssl_test.c
test/selftest.c: In function ‘main’:
test/selftest.c:143:17: warning: implicit declaration of function ‘camellia_self_test’; did you mean ‘xtea_self_test’? [-Wimplicit-function-declaration]
  143 |     if( ( ret = camellia_self_test( v ) ) != 0 )
      |                 ^~~~~~~~~~~~~~~~~~
      |                 xtea_self_test
Building linker script for board a370, Non-secure mode
Building linker script for board a370, Secure mode
nand_base.c: In function 'nand_get_flash_type':
nand_base.c:2661:29: error: 'struct nand_chip' has no member named 'init_size'
nand_base.c:2663:14: error: 'struct nand_chip' has no member named 'init_size'
nand_base.c:2663:37: error: 'id_data' undeclared (first use in this function)
nand_base.c:2663:37: note: each undeclared identifier is reported only once for each function it appears in
make[1]: *** [/home/jigsaw/u-boot-2011.12-armada370/config.mk:309: nand_base.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:466: drivers/mtd/nand/libnand.o] Error 2
make: *** Waiting for unfinished jobs....

 *** Error: Build failed


 *** Error: Build u-boot boot from NAND failed

jigsaw@whitepawn:~/u-boot-2011.12-armada370$

So i don't know c language and couldn't figure out how to patch my stock u-boot from marvell 2013 code.
BTW:I have checked many nand_base codes online and compared all with my stock u-boot code marvell 2013 is the closest one that i found.
Regards.



Edited 4 time(s). Last edit at 09/27/2020 07:01AM by whitepawn.
Attachments:
open | download - nand_base.diff (41.2 KB)
open | download - kompare.png (381.4 KB)
open | download - kompare2.png (271.2 KB)
tme
Re: Debian on Netgear RN102
September 27, 2020 10:15AM
Hi whitepawn and bodhi,

I have ported the latest mainline U-Boot release candidate v2020.10-rc5 to Netgear ReadyNAS RN102. My starting point was U-Boot for Synology DS414 which is based on the Marvell Armada XP SoC. Of course, a major part of the port is the device tree credited to bodhi and pulled from his recent kernel. Thanks a lot!

Using UART boot to upload U-Boot to the box fails consistently, though, so I have not been able to test it yet:
$ kwboot -b ~/u-boot/build/u-boot.kwb -a -t -B 115200 /dev/ttyUSB0
Sending boot message. Please reboot the target...\
Sending boot image...
  0 % [......................................................................]
  1 % [......................................................................]
  2 % [......................................................................]
  4 % [......................................................................]
  5 % [......................................................................]
  7 % [......................................................................]
  8 % [......................................................................]
  9 % [......................................................................]
 11 % [......................................................................]
 12 % [......................................................................]
 14 % [......................................................................]
 15 % [......................................................................]
 16 % [......................................................................]
 18 % [......................................................................]
 19 % [......................................................................]
 21 % [......................................................................]
 22 % [...............................BootROM: Invalid header ID
Booting from NAND flash


General initialization - Version: 1.0.0

High speed PHY - Version: 2.1.4 (COM-PHY-V20) 
Update PEX Device ID 0x6710
High speed PHY - Ended Successfully
0000
DDR3 Training Sequence - Ver 5.7.1
DDR3 Training Sequence - Run without PBS.
DDR3 Training Sequence - Ended Successfully 
BootROM: Image checksum verification PASSED

 __   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_ 
        | | | |___|  _ \ / _ \ / _ \| __| 
        | |_| |___| |_) | (_) | (_) | |_ 
         \___/    |____/ \___/ \___/ \__| 
 ** LOADER **


U-Boot 2011.12-gec25d27-dirty (Oct 26 2015 - 16:53:05) Marvell version: v2011.12 2014_T2.0p1 
06/23/2015 ReadyNAS-102 V2.0

Board: DB-88F6710-BP
SoC:   MV6710 A1
CPU:   Marvell PJ4B v7 UP (Rev 1) LE
       CPU    @ 1200 [MHz]
       L2     @ 600 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 600 [MHz]
       DDR 16Bit Width, FastPath Memory Access
DRAM:  512 MiB

Map:   Code:		0x1feef000:0x1ff9ef34
       BSS:		0x1ffef0a0
       Stack:		0x1f9eeef8
       Heap:		0x1f9ef000:0x1feef000

NAND:  (ID 0xf1ad)	128 MiB
MMC:   MRVL_MMC: 0
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
nand_read_bbt: Bad block at 0x000001820000
nand_read_bbt: Bad block at 0x000001f00000

Initialize and scan all PCI interfaces
PEX unit.port(active IF[-first bus]):
------------------------------------------
PEX 0: Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1: Root Complex Interface, Detected Link X1, GEN 2.0
FPU not initialized
USB 0: Host Mode
USB 1: Host Mode
Shutting down unused interfaces:
       GBE0
       SDIO
       AUDIO
       TDM
Modules/Interfaces Detected:
       RGMII1 Phy
       PEX0 (Lane 0)
       PEX1 (Lane 1)
       SATA0 (Lane 2)
       SATA1 (Lane 3)
Net:   , egiga1 [PRIME]
Power On!
I believe the error message "BootROM: Invalid header ID" comes from the box and not from 'kwboot'. Both the kwb-file and my U-Boot patch are attached. Check the executable './make-all.sh' script included in the patch to see how to build 'u-boot.kwb', 'u-boot-spl.kwb' and plenty of other targets.

UART boot with an image build for Synology DS414 fails very similarly, so I suspect my image has the correct "header ID" for Armada XP rather than Armada 370. If so, uploading to, for instance, GTI Mirabox should work, but then, of course, fail to run. EDIT: No, GTI Mirabox is also Armada 370. :TIDE

In 'arch/arm/dts/armada-370.dtsi' I found:
		bootrom {
			compatible = "marvell,bootrom";
			reg = <MBUS_ID(0x01, 0xe0) 0 0x100000>;
		};
Is this 'reg' what have to be changed and, if so, to what value? Or is it more subtile?

Regards,
Trond Melen



Edited 1 time(s). Last edit at 09/28/2020 01:52AM by tme.
Attachments:
open | download - u-boot.kwb (623.1 KB)
open | download - u-boot-v2020-10-rc5-netgear-rn102-support.patch (41.3 KB)
tme
Re: Debian on Netgear RN102
September 27, 2020 10:48AM
Hi whitepawn,

We posted in parallel.

Warnings from the compiler are to be expected. Gcc has become much better since 2013 at detecting inconsistencies in the code. Ignore the warnings, turn them off with -Wno-unused-const-variable etc. Alternatively, install a Linux distribution from 2013. :-)

These are probably real errors, though:
nand_base.c:2661:29: error: 'struct nand_chip' has no member named 'init_size'
nand_base.c:2663:14: error: 'struct nand_chip' has no member named 'init_size'
nand_base.c:2663:37: error: 'id_data' undeclared (first use in this function)
I guess you get them because stock U-Boot is based on version 2011.12 while you pulled 'nand_base.c' from a 2013 version. Maybe worth investigating, but only maybe.

There are 75 patches in your diff-file, but the majority are white space formatting. Check the manual page to find out how to tell 'diff' to ignore white space.

If you want try to integrate 'nand_base.c' with stock U-Boot, start with bringing the original code under version control. It is definitely worth the initial burden to learn to use 'git'.

Regards,
Trond Melen
Re: Debian on Netgear RN102
September 27, 2020 11:20AM
Trond,
Quick post before i test:
Maybe ddr code is not working?Could you please try this. Your stock u-boot image (mtd0) you will need and you may patch it with ddr code.
I will try it and post results.
Regards.
tme
Re: Debian on Netgear RN102
September 27, 2020 12:49PM
Hi whitepawn,

Quote

Maybe ddr code is not working?

For some hours earlier today I thought so too. What is similar to your case is that the UART boot drops out early, but my error message is clearly the result of some comparison. My current hypothesis is that Armada's BootROM in both cases puts the kwb-image into SRAM until it's exhausted. Then it initializes DDR3 memory and places the rest of the image there. In both cases it's the DDR3 initialization that triggers the drop out, but for different reasons. Soon we will know!

You are using different tools, but the idea I believe is the same: Some 80 months ago, Willy Tarreau struggeled with a similar issue on his GTI Mirabox based on the Marwell Armada XP SoC. If I understand correctly, his solution was to extract Marwell's proprietary non-disclosed DDR3 training code from the stock U-Boot image, prepend it to his own 'u-boot.bin' image and then generate a kwb-file from the concatenated images. And that's just what you successfully did, right?

DDR3 training code for Armada XP is now included in U-Boot. (The symbol MV88F67XX on line 19 is defined for RN102 which hosts a Marvell 88F6710 SoC.)

Regards,
Trond Melen
Re: Debian on Netgear RN102
September 27, 2020 02:38PM
Hi Trond I am back,
Many thanks for building u-boot, i have tried your stock u-boot.kwb and i ddr patched your code both of them are loaded extremely slowly like synology or seagate bootloaders that i tried in past.
In my case your u-boot.kwb loads slow (approx 35-40 mins), Loaded 100 percent unlike yours hangs at 22 percent but it cannot boot and hangs at "[Type Ctrl-\ + c to quit]".
I also ddr patched to try it out but same case happened hangs at "[Type Ctrl-\ + c to quit]".


Quote
Tme
Warnings from the compiler are to be expected. Gcc has become much better since 2013 at detecting inconsistencies in the code. Ignore the warnings, turn them off with -Wno-unused-const-variable etc. Alternatively, install a Linux distribution from 2013. :-)
Warnings are not problem yes it can compile and output u-boot.I choose toolchain from 2013 because in netgear documentation it says:
Quote
README.NETGEAR
$ export PATH=$PATH:/opt/armv7-marvell-linux-gnueabi-softfp_i686_64K_Dev_20131002/bin/
$ export CROSS_COMPILE=arm-marvell-linux-gnueabi-
$ export CROSS_COMPILE_BH=arm-marvell-linux-gnueabi-
$ git clean -fdx
$ ./build_rn102-nand.pl -v 2.0 -d ../armada-370-netgear-rn102.dtb
$ git clean -fdx
$ ./build_rn104-nand.pl -v 2.0 -d ../armada-370-netgear-rn104.dtb
so i didn't wanted to mess things up and get unwanted trouble with new toolchain.And yes maybe retro distro will cure my u-boot problems:-)

Quote
Tme
I guess you get them because stock U-Boot is based on version 2011.12 while you pulled 'nand_base.c' from a 2013 version. Maybe worth investigating, but only maybe

Yes but i only applied differences in variables and id detection code.For example 2013 version have yaffs2 support but i didn't touch it.


Quote
Tme
If you want try to integrate 'nand_base.c' with stock U-Boot, start with bringing the original code under version control. It is definitely worth the initial burden to learn to use 'git'.

How can i do this?Could you please explain me?

Regards.
tme
Re: Debian on Netgear RN102
September 27, 2020 02:58PM
Hi whitepawn,

> both of them are loaded extremely slowly

For me the transfere takes about one minute with a HL-340 based USB-to-RS232 adapter, and not more than, say, 4 minutes by slower means. 'kwboot' is always started first. Kwb-file transfere starts within 3-10 seconds after power on.

I have also experienced what appears to be very slow transferes, but I believe this is 'kwboot' feeding the "Marvell>" promt, rather than the xmodem receiver, so nothing is actually received. Interrupt and switch to 'picocom' to confirm.

Version control? The search string "git tutorial" is one possible starting point.

Regards,
Trond Melen
Re: Debian on Netgear RN102
September 27, 2020 06:32PM
,

Quote
whitepawn
So i don't know c language and couldn't figure out how to patch my stock u-boot from marvell 2013 code.

It is quite difficult to port new code back to a much older version (a lot has changed structurally), if you are not familiar with the old version code base. Going forward is easier, but also requires that you know the new code base.

In your case, you would have to remove some new code that the old code base cannot use. But when doing that, you'll run into problem with removing too much and must retrofit some code back to the old code base!!!

So I think it is not feasible. You could end up taking a lot of trials and errors to get it built, but then there is a good chance that it will not run.


Quote
Trond
I believe the error message "BootROM: Invalid header ID" comes from the box and not from 'kwboot'.

Correct. The BootROM accepted the image and parsed the header, and it did not find what it likes there.

-bodhi
===========================
Forum Wiki
bodhi's corner
tme
Re: Debian on Netgear RN102
September 28, 2020 02:36AM
Hi whitepawn and bodhi,

One way to be able to test my RN102 port of the current mainline U-Boot would be to disassemble BootROM 1.08 to find out what "Header ID"(s) it likes.

How do I dump the BootROM content? Using 'md' at the "Marvell>" prompt? Or from inside Debian?

Regards,
Trond Melen
tme
Re: Debian on Netgear RN102
September 28, 2020 11:21AM
Hi withepawn and bodhi,

There is no need to dump the BootROM. It is well documented on page 81 to 98 in the document "88F6710, 88F6707, and 88F6W11 ARMADA ® 370 SoC Functional Specifications – Unrestricted" which is no longer available at www.marvell.com, but may be downloaded from at Arnaud Ebalard's site 'natisbad.org'. For the record, the BootROM starts at 0xFFF00000 and its size is 1 MB (Table 10, page 83).

The problem was the first byte:
$ hexdump u-boot.kwb | head -5
0000000 005a 0000 7c5c 0007 0201 4000 4000 0002
0000010 ffc0 007f 0000 0080 0000 0000 0000 f901
0000020 0102 5b2c 0002 0000 005b 0000 0068 0000
0000030 0000 0000 0000 0000 0000 0000 0000 0000
0000040 000f ea00 f014 e59f f014 e59f f014 e59f
There is a NUXI problem here so the first byte is 0x5a, which means "Boot from SPI/NOR flash" (Table 11, page 85). The simplest fix is the '-p' options to 'kwboot'. It patches this byte to 0x69 which means "Boot from UART0" and then, on the fly, recomputes the one byte checksum at 0x1f (which is 0xf9 in the kwb-file):
$ kwboot -b u-boot.kwb -p /dev/ttyUSB0
Sending boot message. Please reboot the target.../
Sending boot image...
  0 % [......................................................................]
  1 % [......................................................................]
  2 % [......................................................................]
  4 % [......................................................................]
  5 % [......................................................................]
  7 % [......................................................................]
  8 % [......................................................................]
  9 % [......................................................................]
 11 % [......................................................................]
 12 % [......................................................................]
 14 % [......................................................................]
 15 % [......................................................................]
 16 % [......................................................................]
 18 % [......................................................................]
 19 % [......................................................................]
 21 % [......................................................................]
 22 % [...............................+xmodem: Protocol error
So the error message "BootROM: Invalid header ID" disappeared.

The new error message "xmodem: Protocol error" is from 'kwboot'. The '+' in stead of '.' indicates that no acknowledge for this 132 byte block was received from the box within the timeout period of 1 s. This can be verified with the '-o' option:
$ kwboot -b u-boot.kwb -p -o 5000 /dev/ttyUSB0
Sending boot message. Please reboot the target.../
Sending boot image...
  0 % [......................................................................]
  1 % [......................................................................]
  2 % [......................................................................]
  4 % [......................................................................]
  5 % [......................................................................]
  7 % [......................................................................]
  8 % [......................................................................]
  9 % [......................................................................]
 11 % [......................................................................]
 12 % [......................................................................]
 14 % [......................................................................]
 15 % [......................................................................]
 16 % [......................................................................]
 18 % [......................................................................]
 19 % [......................................................................]
 21 % [......................................................................]
 22 % [...............................+xmodem: Protocol error
The only difference is invisible. Now took 5 s for the '+' to appear. Inserting the DDR3 training code from the stock U-Boot might work, but is not completely satisfactory.

Regards,
Trond Melen

EDIT: Typos only. :TIDE



Edited 1 time(s). Last edit at 09/28/2020 11:54AM by tme.
tme
Re: Debian on Netgear RN102
September 28, 2020 02:30PM
Hi whitepawn,

I tried inserting the DDR3 training code from the stock U-Boot using 'kwbimage' and 'mvebuimg'. It kind of works:
$ ./kwbimage -x -i backup.mtd0 -o /tmp/
$ mv /tmp/payload /tmp/payload.orig
$ ./kwbimage -x -i u-boot.bin -o /tmp/
Invalid image version 20
$ ./mvebuimg -v 1 create -b /tmp/binary.0 -o ubootmodded.bin spi /tmp/payload.orig
$ kwboot -b ubootmodded.bin -p -t /dev/ttyUSB0 
Sending boot message. Please reboot the target...|
Sending boot image...
  0 % [......................................................................]
  1 % [......................................................................]
  2 % [......................................................................]
  3 % [......................................................................]
  4 % [......................................................................]
  5 % [......................................................................]
  6 % [......................................................................]
  7 % [......................................................................]
  8 % [......................................................................]
  9 % [.........

General initialization - Version: 1.0.0

High speed PHY - Version: 2.1.4 (COM-PHY-V20) 
Update PEX Device ID 0x6710
High speed PHY - Ended Successfully
0000
DDR3 Training Sequence - Ver 5.7.1
DDR3 Training Sequence - Run without PBS.
DDR3 Training Sequence - Ended Successfully 
.............................................................]
 10 % [......................................................................]
 11 % [......................................................................]
 12 % [......................................................................]
 13 % [......................................................................]
[...]
 95 % [......................................................................]
 96 % [......................................................................]
 97 % [......................................................................]
 98 % [......................................................................]
 99 % [.............................................]
[Type Ctrl-\ + c to quit]
$
So the whole kwb-image was uploaded. It took 87 s. 'kwbimage' on 'u-boot.bin' said "Invalid image version 20". Important?

Expected behavior next is that the terminal emulator built into 'kwboot' and enabled with the '-t' option should kick in, but it didn't. I wonder why.

Regards,
Trond Melen
Re: Debian on Netgear RN102
September 29, 2020 05:34AM
Tme,

Quote
tme
So the whole kwb-image was uploaded. It took 87 s. 'kwbimage' on 'u-boot.bin' said "Invalid image version 20". Important?

I think it is not normal but i am not sure.I never get this error.
It seems u-boot is not compatible with out box because i get exactly same behavior on seagate and synology bootloaders.It hangs on:
[Type Ctrl-\ + c to quit]

@bodhi

I see so it is not possible to retrofit code.So only chance I will try to find SDIO gpio pins again.

Regards.



Edited 1 time(s). Last edit at 09/29/2020 05:36AM by whitepawn.
Re: Debian on Netgear RN102
September 29, 2020 01:58PM
Bodhi,
Out of luck with SDIO pins.Now i decided to boot debian from rear e-SATA port with e-SATA to 2.5 inch HDD cable like this.
Is this possible to boot from e-SATA via changing bootenvs?If its possible which envs i must use?
Regards.
tme
Re: Debian on Netgear RN102
September 29, 2020 03:01PM
Hi whitepawn,

Good idea!

This is my plan too, but the rear eSATA connector on Netgear ReadyNAS boxes is not eSATAp. Since you are more of a hardware guy, you may try to feed 5 V to the connector. It should preferably have its own 5 V regulator running on 12 V, but maybe there is excess power capacity on an existing 5 V rail? I think SSDs need 5 V only, while HDDs needs 12 V in addition for the spin engine, but here I am guessing.

Alternatively, you need something like this. I ordered a similar one a week ago and expect it to work with U-Boot v2020.10 when it arrives as long as the attached SSD has an 'ext3' partition labeled 'rootfs'. If you want to save both the rear USB3 connectors for other usages, you may attach the USB plug to a normal charger via an extension cable.

Stock U-Boot fails to find an SSD in slot 1, so it would come as a surprise if it's found when the SSD is attached to the eSATA connector. It could be due to timing, though, and I did not try with an HDD.

In principle, U-Boot may also be loaded from the SSD attached to the eSATA connector by changing the first byte of the U-Boot image to 0x78 which means "Boot from SATA device" and placing the "image LBA location offset (in sectors) in the hard drive used for boot" in bytes 0xC–0xF (page 85, Tabele 11). Also, the Sample at Reset Register at 0x18230 must be modified once to make the BootROM prefer SATA over NAND. This can be done from U-Boot. Cool? Yes, but not part of my plan. :-)

Regards,
Trond Melen
Re: Debian on Netgear RN102
September 29, 2020 03:46PM
Tme,

Yes it is no e-SATAp but neither standard 7 pin e-SATA.If you looked connector inside there are also some pins which i think power pins.

If it not provides 5v supply i can make a voltage regulator with LM7805 no problem.Since RN102 draws 1 amp in idle with one usb and one 2.5 inch drive attached oem psu (5v 12A) will work i think.

I have many HDD drives with USB 3.0 so i want to save them for backup purposes.

If e-SATA works i will be ok with 2 USB3.0, 1 USB2.0 and 2 Normal SATA bays:-)

Regards.
tme
Re: Debian on Netgear RN102
September 29, 2020 03:58PM
Quote

Yes, it is no e-SATAp, but neither standard 7 pin e-SATA. If you looked connector inside there are also some pins which I think are power pins.

My current understanding is that the power pins are there, but unconnected. Can you please verify?

Regards,
Trond Melen
tme
Re: Debian on Netgear RN102
September 29, 2020 04:14PM
Hi bodhi,

Just to experience the expected behavior, I decided to use 'kwboot' to upload the 'mtd0' backup from my second RN102 which still runs stock Netgear firmware:
$ kwboot -b backup.mtd0 -p -t /dev/ttyUSB0 
Sending boot message. Please reboot the target...-
Sending boot image...
  0 % [......................................................................]
  1 % [......................................................................]
  3 % [......................................................................]
  5 % [......................................................................]
  6 % [......................................................................]
  8 % [......................................................................]
 10 % [......................................................................]
 11 % [......................................................................]
 13 % [......................................................................]
 15 % [.........

General initialization - Version: 1.0.0

High speed PHY - Version: 2.1.4 (COM-PHY-V20) 
Update PEX Device ID 0x6710
High speed PHY - Ended Successfully
0000
DDR3 Training Sequence - Ver 5.7.1
DDR3 Training Sequence - Run without PBS.
DDR3 Training Sequence - Ended Successfully 
.............................................................]
 17 % [......................................................................]
 18 % [......................................................................]
 20 % [......................................................................]
 22 % [......................................................................]
[...]
 92 % [......................................................................]
 94 % [......................................................................]
 95 % [......................................................................]
 97 % [......................................................................]
 99 % [....................................]
[Type Ctrl-\ + c to quit]
Surprice! It fails the same way as the patched U-Boot v2020.10-rc5. Maybe I'm closer to getting it running than I thought?

'backup.mtd0' was created by the command
nanddump --noecc --omitoob -l 0x80000 -f backup.mtd0 /dev/mtd0
Why isn't this image suited for 'kwboot -p'?

Would it work it I flash it like this?
cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00180000 00020000 "u-boot"
mtd1: 00080000 00020000 "u-boot-env"
mtd2: 00600000 00020000 "uImage"
mtd3: 00400000 00020000 "minirootfs"
mtd4: 07400000 00020000 "ubifs"

nandwrite -help
Usage: nandwrite [OPTION] MTD_DEVICE [INPUTFILE|-]
Writes to the specified MTD device.

  -a, --autoplace         Use auto OOB layout
  -k, --skip-all-ffs      Skip pages that contain only 0xff bytes
  -m, --markbad           Mark blocks bad if write fails
  -n, --noecc             Write without ecc
  -N, --noskipbad         Write without bad block skipping
  -o, --oob               Input contains oob data
  -O, --onlyoob           Input contains oob data and only write the oob part
  -s addr, --start=addr   Set output start address (default is 0)
  -p, --pad               Pad writes to page size
  -b, --blockalign=1|2|4  Set multiple of eraseblocks to align to
      --input-skip=length Skip |length| bytes of the input file
      --input-size=length Only read |length| bytes of the input file
  -q, --quiet             Don't display progress messages
  -h, --help              Display this help and exit
  -V, --version           Output version information and exit

nandwrite /dev/mtd0 backup.mtd0
(Not tried yet.)

Regards,
Trond Melen
Re: Debian on Netgear RN102
September 29, 2020 04:45PM
Quote
whitepawn
Bodhi,
Out of luck with SDIO pins.Now i decided to boot debian from rear e-SATA port with e-SATA to 2.5 inch HDD cable like this.
Is this possible to boot from e-SATA via changing bootenvs?If its possible which envs i must use?
Regards.

Let's review yours and Trond's successful bootlogs. But perhpaps you guys can tell me, does it show eSata disk initialized if there is a disk attached?

Also in u-boot console, attached an HDD to to eSATA port, and try both of these commands, one of them should initialize all the SATA disks in the system.

ide reset
scsi reset


Quote
Trond
In principle, U-Boot may also be loaded from the SSD attached to the eSATA connector by changing the first byte of the U-Boot image to 0x78 which means "Boot from SATA device" and placing the "image LBA location offset (in sectors) in the hard drive used for boot" in bytes 0xC–0xF (page 85, Tabele 11). Also, the Sample at Reset Register at 0x18230 must be modified once to make the BootROM prefer SATA over NAND. This can be done from U-Boot. Cool? Yes, but not part of my plan. :-)

Yes it is possible, but not really a good way to run the box permanently. This should be used as a rescue mechanism, similar to UART booting.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Debian on Netgear RN102
September 29, 2020 06:58PM
@bodhi and tme,
I resoldered stock flash chip and tested it before doing below:
Since i don't have any e-SATA cable in hand and i am impaitent guy i sacrificed one of my sata cable and soldered it directly to e-SATA daughter board and feeded my HDD with external power source.(I was wrong, e-SATA port doesn't have power pins btw i have checked it but not a big deal for me)It detected my e-SATA connected HDD as shown below:


BootROM 1.08
Booting from NAND flash


General initialization - Version: 1.0.0

High speed PHY - Version: 2.1.4 (COM-PHY-V20)
Update PEX Device ID 0x6710
High speed PHY - Ended Successfully
0000
DDR3 Training Sequence - Ver 5.7.1
DDR3 Training Sequence - Run without PBS.
DDR3 Training Sequence - Ended Successfully
BootROM: Image checksum verification PASSED
l
 __   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_
        | | | |___|  _ \ / _ \ / _ \| __|
        | |_| |___| |_) | (_) | (_) | |_
         \___/    |____/ \___/ \___/ \__|
 ** LOADER **


U-Boot 2011.12-gec25d27-dirty (Oct 26 2015 - 16:53:05) Marvell version: v2011.12 2014_T2.0p1
06/23/2015 ReadyNAS-102 V2.0

Board: DB-88F6710-BP
SoC:   MV6710 A1
CPU:   Marvell PJ4B v7 UP (Rev 1) LE
       CPU    @ 1200 [MHz]
       L2     @ 600 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 600 [MHz]
       DDR 16Bit Width, FastPath Memory Access
DRAM:  512 MiB

Map:   Code:            0x1feef000:0x1ff9ef34
       BSS:             0x1ffef0a0
       Stack:           0x1f9eeef8
       Heap:            0x1f9ef000:0x1feef000

NAND:  (ID 0xf12c)      128 MiB
MMC:   MRVL_MMC: 0
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01

Initialize and scan all PCI interfaces
PEX unit.port(active IF[-first bus]):
------------------------------------------
PEX 0: Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1: Root Complex Interface, Detected Link X1, GEN 2.0
FPU not initialized
USB 0: Host Mode
USB 1: Host Mode
Shutting down unused interfaces:
       GBE0
       SDIO
       AUDIO
       TDM
Modules/Interfaces Detected:
       RGMII1 Phy
       PEX0 (Lane 0)
       PEX1 (Lane 1)
       SATA0 (Lane 2)
       SATA1 (Lane 3)
Net:   , egiga1 [PRIME]
Power On!

FDT loaded successfully
Hit any key to stop autoboot:  0
Marvell>> <INTERRUPT>
Marvell>> <INTERRUPT>
Marvell>> <INTERRUPT>
Marvell>> ide reset

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
  Device 0 @ 0 0:
Model: ST940210AS                               Firm: 3.ALC    Ser#:             5QX1VL4R
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 38154.3 MB = 37.2 GB (78140160 x 512)

Marvell>>


For testing i made rootfs on e-SATA HDD and plugged my previous rootfs and kernel loaded usb flash drive in front.It booted rootfs directly from HDD i am suprized.I think it loaded kernel from usb drive and rootfs from e-SATA drive.So if it seems ok how can i boot all kernel and rootfs from e-SATA drive?
Attached photos to post.Couldn't get full bootlog because i am so tired will add full log tomorrow.
BTW it seems HHD boots faster than USB.
Regards.
Attachments:
open | download - rsz_img_20200930_021942.jpg (717.5 KB)
open | download - rsz_img_20200930_021949.jpg (445.2 KB)
Re: Debian on Netgear RN102
September 30, 2020 12:09AM
whitepawn,


Quote

Marvell>> ide reset

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
Device 0 @ 0 0:
Model: ST940210AS Firm: 3.ALC Ser#: 5QX1VL4R
Type: Hard Disk
Supports 48-bit addressing
Capacity: 38154.3 MB = 37.2 GB (78140160 x 512)

Marvell>>

Was it with only the esATA port has this HDD attched to it? no other HDD in the slots?

Quote

For testing i made rootfs on e-SATA HDD and plugged my previous rootfs and kernel loaded usb flash drive in front.It booted rootfs directly from HDD i am suprized.I think it loaded kernel from usb drive and rootfs from e-SATA drive.

Yes. The SATA drive has the partition with label rootfs. So the kernel sees that and ignore the USB rootfs. HDD always got detected and scanned first.


Quote

So if it seems ok how can i boot all kernel and rootfs from e-SATA drive?
Attached photos to post.Couldn't get full bootlog because i am so tired will add full log tomorrow.

If the eSATA drive was detected above in u-boot , then definitely you can boot entirely with eSATA.

Quote

BTW it seems HHD boots faster than USB

Much much faster.

====

What you should do is to remove the USB drive and let it boot with the eSATA drive. But before you do that we need to change some envs. Let me revise the envs.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Debian on Netgear RN102
September 30, 2020 04:07AM
Bodhi,
Quote
Bodhi
Was it with only the esATA port has this HDD attched to it? no other HDD in the slots?
Yes only HDD attached to box is e-SATA disk.And USB flash disk to boot.Nothing else attached.

Quote
Bodhi
Yes. The SATA drive has the partition with label rootfs. So the kernel sees that and ignore the USB rootfs. HDD always got detected and scanned first.

Oh i see now.

Quote
Bodhi
If the eSATA drive was detected above in u-boot , then definitely you can boot entirely with eSATA.

Yes sir it detects.

Here is the full log

BootROM 1.08
Booting from NAND flash


General initialization - Version: 1.0.0

High speed PHY - Version: 2.1.4 (COM-PHY-V20)
Update PEX Device ID 0x6710
High speed PHY - Ended Successfully
0000
DDR3 Training Sequence - Ver 5.7.1
DDR3 Training Sequence - Run without PBS.
DDR3 Training Sequence - Ended Successfully
BootROM: Image checksum verification PASSED
l
 __   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_
        | | | |___|  _ \ / _ \ / _ \| __|
        | |_| |___| |_) | (_) | (_) | |_
         \___/    |____/ \___/ \___/ \__|
 ** LOADER **


U-Boot 2011.12-gec25d27-dirty (Oct 26 2015 - 16:53:05) Marvell version: v2011.12                                2014_T2.0p1
06/23/2015 ReadyNAS-102 V2.0

Board: DB-88F6710-BP
SoC:   MV6710 A1
CPU:   Marvell PJ4B v7 UP (Rev 1) LE
       CPU    @ 1200 [MHz]
       L2     @ 600 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 600 [MHz]
       DDR 16Bit Width, FastPath Memory Access
DRAM:  512 MiB

Map:   Code:            0x1feef000:0x1ff9ef34
       BSS:             0x1ffef0a0
       Stack:           0x1f9eeef8
       Heap:            0x1f9ef000:0x1feef000

NAND:  (ID 0xf12c)      128 MiB
MMC:   MRVL_MMC: 0
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01

Initialize and scan all PCI interfaces
PEX unit.port(active IF[-first bus]):
------------------------------------------
PEX 0: Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1: Root Complex Interface, Detected Link X1, GEN 2.0
FPU not initialized
USB 0: Host Mode
USB 1: Host Mode
Shutting down unused interfaces:
       GBE0
       SDIO
       AUDIO
       TDM
Modules/Interfaces Detected:
       RGMII1 Phy
       PEX0 (Lane 0)
       PEX1 (Lane 1)
       SATA0 (Lane 2)
       SATA1 (Lane 3)
Net:   , egiga1 [PRIME]
Power On!

FDT loaded successfully
Hit any key to stop autoboot:  0
Marvell>> <INTERRUPT>
Marvell>> <INTERRUPT>
Marvell>> <INTERRUPT>
Marvell>> <INTERRUPT>
Marvell>> ide reset

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
  Device 0 @ 0 0:
Model: ST940210AS                               Firm: 3.ALC    Ser#:                                            5QX1VL4R
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 38154.3 MB = 37.2 GB (78140160 x 512)

Marvell>> boot
(Re)start USB...
USB:   Active port:     0
Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/boot/uImage" from usb device 0:1 ()
5418806 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 ()
9576098 bytes read
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   Linux-5.8.5-mvebu-370xp-tld-1
   Created:      2020-09-09  21:14:23 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5418742 Bytes = 5.2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 03000000 ...
   Image Name:   initramfs-5.8.5-mvebu-370xp-tld-
   Created:      2020-09-09  21:45:01 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9576034 Bytes = 9.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000][    T0] Booting Linux on physical CPU 0x0
[    0.000000][    T0] Linux version 5.8.5-mvebu-370xp-tld-1 (root@tldDebianVM)                                (arm-linux-gnueabihf-gcc (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04) 7.5.0, GNU ld (GNU                                Binutils for Ubuntu) 2.30) #1.0 SMP PREEMPT Mon Aug 31 00:00:32 PDT 2020
[    0.000000][    T0] CPU: ARMv7 Processor [561f5811] revision 1 (ARMv7), cr=10                               c5387d
[    0.000000][    T0] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction                                cache
[    0.000000][    T0] OF: fdt: Machine model: NETGEAR ReadyNAS 102
[    0.000000][    T0] printk: bootconsole [earlycon0] enabled
[    0.000000][    T0] Memory policy: Data cache writeback
[    0.000000][    T0] Zone ranges:
[    0.000000][    T0]   Normal   [mem 0x0000000000000000-0x000000001fffffff]
[    0.000000][    T0]   HighMem  empty
[    0.000000][    T0] Movable zone start for each node
[    0.000000][    T0] Early memory node ranges
[    0.000000][    T0]   node   0: [mem 0x0000000000000000-0x000000001fffffff]
[    0.000000][    T0] Initmem setup node 0 [mem 0x0000000000000000-0x000000001f                               ffffff]
[    0.000000][    T0] CPU: All CPU(s) started in SVC mode.
[    0.000000][    T0] percpu: Embedded 20 pages/cpu s53068 r8192 d20660 u81920
[    0.000000][    T0] Built 1 zonelists, mobility grouping on.  Total pages: 13                               0048
[    0.000000][    T0] Kernel command line: console=ttyS0,115200 root=LABEL=root                               fs rootdelay=10 mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boo                               t-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) earlypri                               ntk=serial init=/bin/systemd mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0                               x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ub                               ifs) reason=normal bdtype=rn102
[    0.000000][    T0] Dentry cache hash table entries: 65536 (order: 6, 262144                                bytes, linear)
[    0.000000][    T0] Inode-cache hash table entries: 32768 (order: 5, 131072 b                               ytes, linear)
[    0.000000][    T0] mem auto-init: stack:off, heap alloc:on, heap free:off
[    0.000000][    T0] Memory: 493536K/524288K available (10240K kernel code, 10                               12K rwdata, 3072K rodata, 1024K init, 342K bss, 30752K reserved, 0K cma-reserved                               , 0K highmem)
[    0.000000][    T0] random: get_random_u32 called from ____cache_alloc+0x338/                               0x794 with crng_init=0
[    0.000000][    T0] rcu: Preemptible hierarchical RCU implementation.
[    0.000000][    T0] rcu:     RCU restricting CPUs from NR_CPUS=4 to nr_cpu_id                               s=1.
[    0.000000][    T0]  Trampoline variant of Tasks RCU enabled.
[    0.000000][    T0]  Rude variant of Tasks RCU enabled.
[    0.000000][    T0]  Tracing variant of Tasks RCU enabled.
[    0.000000][    T0] rcu: RCU calculated value of scheduler-enlistment delay i                               s 10 jiffies.
[    0.000000][    T0] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_id                               s=1
[    0.000000][    T0] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000][    T0] L2C: DT/platform modifies aux control register: 0x1208630                               0 -> 0x1a086302
[    0.000000][    T0] Aurora cache controller enabled, 4 ways, 256 kB
[    0.000000][    T0] Aurora: CACHE_ID 0x00000100, AUX_CTRL 0x1a086302
[    0.000000][    T0] Switching to timer-based delay loop, resolution 53ns
[    0.000006][    T0] sched_clock: 32 bits at 18MHz, resolution 53ns, wraps eve                               ry 114537122277ns
[    0.007874][    T0] clocksource: armada_370_xp_clocksource: mask: 0xffffffff                                max_cycles: 0xffffffff, max_idle_ns: 101938038664 ns
[    0.019297][    T0] Console: colour dummy device 80x30
[    0.024017][    T0] Calibrating delay loop (skipped), value calculated using                                timer frequency.. 37.49 BogoMIPS (lpj=187492)
[    0.034146][    T0] pid_max: default: 32768 minimum: 301
[    0.039211][    T0] LSM: Security Framework initializing
[    0.044158][    T0] Mount-cache hash table entries: 1024 (order: 0, 4096 byte                               s, linear)
[    0.051487][    T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096                                bytes, linear)
[    0.060284][    T0] CPU: Testing write buffer coherency: ok
[    0.065723][    T1] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[    0.072059][    T1] Setting up static identity map for 0x100000 - 0x100060
[    0.078747][    T1] mvebu-soc-id: MVEBU SoC ID=0x6710, Rev=0x1
[    0.084178][    T1] mvebu-pmsu: Initializing Power Management Service Unit
[    0.090703][    T1] rcu: Hierarchical SRCU implementation.
[    0.098528][    T1] smp: Bringing up secondary CPUs ...
[    0.103418][    T1] smp: Brought up 1 node, 1 CPU
[    0.107715][    T1] SMP: Total of 1 processors activated (37.49 BogoMIPS).
[    0.114035][    T1] CPU: All CPU(s) started in SVC mode.
[    0.119579][    T1] devtmpfs: initialized
[    0.128181][    T1] VFP support v0.3: implementor 56 architecture 2 part 20 v                               ariant 9 rev 6
[    0.137105][    T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffff                               ffff, max_idle_ns: 19112604462750000 ns
[    0.146877][    T1] futex hash table entries: 256 (order: 2, 16384 bytes, lin                               ear)
[    0.154089][    T1] xor: measuring software checksum speed
[    0.258575][    T1]    arm4regs  :  1103.200 MB/sec
[    0.358572][    T1]    8regs     :   671.200 MB/sec
[    0.458568][    T1]    32regs    :  1062.400 MB/sec
[    0.463021][    T1] xor: using function: arm4regs (1103.200 MB/sec)
[    0.468785][    T1] prandom: seed boundary self test passed
[    0.477388][    T1] prandom: 100 self tests passed
[    0.481801][    T1] pinctrl core: initialized pinctrl subsystem
[    0.488937][    T1] thermal_sys: Registered thermal governor 'step_wise'
[    0.489672][    T1] NET: Registered protocol family 16
[    0.502532][    T1] DMA: preallocated 256 KiB pool for atomic coherent alloca                               tions
[    0.510427][    T1] audit: initializing netlink subsys (disabled)
[    0.516397][   T31] audit: type=2000 audit(0.490:1): state=initialized audit_                               enabled=0 res=1
[    0.526687][    T1] cpuidle: using governor ladder
[    0.532706][    T1] cpuidle: using governor menu
[    0.537219][    T1] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.809662][    T1] raid6: int32x8  gen()   214 MB/s
[    0.978986][    T1] raid6: int32x8  xor()   135 MB/s
[    1.148653][    T1] raid6: int32x4  gen()   224 MB/s
[    1.318713][    T1] raid6: int32x4  xor()   151 MB/s
[    1.488577][    T1] raid6: int32x2  gen()   414 MB/s
[    1.658571][    T1] raid6: int32x2  xor()   217 MB/s
[    1.828605][    T1] raid6: int32x1  gen()   430 MB/s
[    1.998590][    T1] raid6: int32x1  xor()   201 MB/s
[    2.003121][    T1] raid6: using algorithm int32x1 gen() 430 MB/s
[    2.008694][    T1] raid6: .... xor() 201 MB/s, rmw enabled
[    2.013779][    T1] raid6: using intx1 recovery algorithm
[    2.020115][    T1] vgaarb: loaded
[    2.025085][    T1] SCSI subsystem initialized
[    2.030354][    T1] usbcore: registered new interface driver usbfs
[    2.036054][    T1] usbcore: registered new interface driver hub
[    2.043232][    T1] usbcore: registered new device driver usb
[    2.049955][    T1] mc: Linux media interface: v0.10
[    2.055380][    T1] videodev: Linux video capture interface: v2.00
[    2.061870][    T1] pps_core: LinuxPPS API ver. 1 registered
[    2.067039][    T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodol                               fo Giometti <giometti@linux.it>
[    2.076775][    T1] PTP clock support registered
[    2.084613][    T1] clocksource: Switched to clocksource armada_370_xp_clocks                               ource
[    3.073764][    T1] VFS: Disk quotas dquot_6.6.0
[    3.078146][    T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096                                bytes)
[    3.114256][    T1] NET: Registered protocol family 2
[    3.121014][    T1] tcp_listen_portaddr_hash hash table entries: 512 (order:                                0, 6144 bytes, linear)
[    3.129761][    T1] TCP established hash table entries: 4096 (order: 2, 16384                                bytes, linear)
[    3.137725][    T1] TCP bind hash table entries: 4096 (order: 3, 32768 bytes,                                linear)
[    3.145009][    T1] TCP: Hash tables configured (established 4096 bind 4096)
[    3.152009][    T1] UDP hash table entries: 256 (order: 1, 8192 bytes, linear                               )
[    3.158822][    T1] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, l                               inear)
[    3.166056][    T1] NET: Registered protocol family 1
[    3.171430][    T1] RPC: Registered named UNIX socket transport module.
[    3.177569][    T1] RPC: Registered udp transport module.
[    3.182498][    T1] RPC: Registered tcp transport module.
[    3.187446][    T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    3.193963][    T1] PCI: CLS 0 bytes, default 64
[    3.198580][    T1] Trying to unpack rootfs image as initramfs...
[    3.819000][    T1] Freeing initrd memory: 9352K
[    3.823527][    T1] NetWinder Floating Point Emulator V0.97 (double precision                               )
[    3.830477][    T1] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7                                counters available
[    3.841463][    T1] Initialise system trusted keyrings
[    3.848266][    T1] Key type blacklist registered
[    3.852797][    T1] workingset: timestamp_bits=30 max_order=17 bucket_order=0
[    3.859616][    T1] zbud: loaded
[    3.864207][    T1] NFS: Registering the id_resolver key type
[    3.869941][    T1] Key type id_resolver registered
[    3.874398][    T1] Key type id_legacy registered
[    3.878835][    T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering                               ...
[    3.885724][    T1] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    3.892473][    T1] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat                               , Inc.
[    3.900740][    T1] orangefs_debugfs_init: called with debug mask: :none: :0:
[    3.907693][    T1] orangefs_init: module version upstream loaded
[    3.986625][    T1] async_tx: api initialized (async)
[    3.991256][    T1] Key type asymmetric registered
[    3.995705][    T1] Asymmetric key parser 'x509' registered
[    4.001145][    T1] Block layer SCSI generic (bsg) driver version 0.4 loaded                                (major 243)
[    4.008766][    T1] io scheduler bfq registered
[    4.015884][    T1] armada-370-pinctrl d0018000.pin-ctrl: registered pinctrl                                driver
[    4.032725][    T1] mvebu-pcie soc:pcie@82000000: PCI host bridge to bus 0000                               :00
[    4.040004][    T1] pci_bus 0000:00: root bus resource [bus 00-ff]
[    4.046060][    T1] pci_bus 0000:00: root bus resource [mem 0xf8000000-0xffdf                               ffff]
[    4.052973][    T1] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    4.059654][    T1] pci 0000:00:01.0: [11ab:6710] type 01 class 0x060400
[    4.065891][    T1] pci 0000:00:01.0: reg 0x38: [mem 0x00000000-0x000007ff pr                               ef]
[    4.073232][    T1] pci 0000:00:02.0: [11ab:6710] type 01 class 0x060400
[    4.079602][    T1] pci 0000:00:02.0: reg 0x38: [mem 0x00000000-0x000007ff pr                               ef]
[    4.087917][    T1] PCI: bus0: Fast back to back transfers disabled
[    4.093653][    T1] pci 0000:00:01.0: bridge configuration invalid ([bus 00-0                               0]), reconfiguring
[    4.101846][    T1] pci 0000:00:02.0: bridge configuration invalid ([bus 00-0                               0]), reconfiguring
[    4.110287][    T1] pci 0000:01:00.0: [1b4b:9170] type 00 class 0x010601
[    4.116671][    T1] pci 0000:01:00.0: reg 0x10: [io  0xfffffff8-0xffffffff]
[    4.123037][    T1] pci 0000:01:00.0: reg 0x14: [io  0xfffffffc-0xffffffff]
[    4.129509][    T1] pci 0000:01:00.0: reg 0x18: [io  0xfffffff8-0xffffffff]
[    4.135965][    T1] pci 0000:01:00.0: reg 0x1c: [io  0xfffffffc-0xffffffff]
[    4.142330][    T1] pci 0000:01:00.0: reg 0x20: [io  0xfffffff0-0xffffffff]
[    4.148750][    T1] pci 0000:01:00.0: reg 0x24: [mem 0x40000000-0x400001ff]
[    4.155176][    T1] pci 0000:01:00.0: reg 0x30: [mem 0xd0000000-0xd000ffff pr                               ef]
[    4.161949][    T1] pci 0000:01:00.0: Enabling fixed DMA alias to 00.1
[    4.168017][    T1] pci 0000:01:00.0: PME# supported from D3hot
[    4.173874][    T1] pci 0000:00:01.0: ASPM: current common clock configuratio                               n is inconsistent, reconfiguring
[    4.205702][    T1] PCI: bus1: Fast back to back transfers disabled
[    4.211442][    T1] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to                                01
[    4.218538][    T1] pci 0000:02:00.0: [1b73:1009] type 00 class 0x0c0330
[    4.224889][    T1] pci 0000:02:00.0: reg 0x10: [mem 0x42000000-0x4200ffff 64                               bit]
[    4.231734][    T1] pci 0000:02:00.0: reg 0x18: [mem 0x42010000-0x42010fff 64                               bit]
[    4.238680][    T1] pci 0000:02:00.0: reg 0x20: [mem 0x42011000-0x42011fff 64                               bit]
[    4.245680][    T1] pci 0000:02:00.0: supports D1
[    4.249978][    T1] pci 0000:02:00.0: PME# supported from D0 D1 D3hot D3cold
[    4.256948][    T1] pci 0000:00:02.0: ASPM: current common clock configuratio                               n is inconsistent, reconfiguring
[    4.295699][    T1] PCI: bus2: Fast back to back transfers disabled
[    4.301437][    T1] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to                                02
[    4.308263][    T1] pci 0000:00:01.0: BAR 14: assigned [mem 0xf8000000-0xf80f                               ffff]
[    4.315235][    T1] pci 0000:00:02.0: BAR 14: assigned [mem 0xf8100000-0xf81f                               ffff]
[    4.322148][    T1] pci 0000:00:01.0: BAR 13: assigned [io  0x10000-0x10fff]
[    4.328635][    T1] pci 0000:00:01.0: BAR 6: assigned [mem 0xf8200000-0xf8200                               7ff pref]
[    4.335887][    T1] pci 0000:00:02.0: BAR 6: assigned [mem 0xf8300000-0xf8300                               7ff pref]
[    4.343124][    T1] pci 0000:01:00.0: BAR 6: assigned [mem 0xf8000000-0xf800f                               fff pref]
[    4.350373][    T1] pci 0000:01:00.0: BAR 5: assigned [mem 0xf8010000-0xf8010                               1ff]
[    4.357228][    T1] pci 0000:01:00.0: BAR 4: assigned [io  0x10000-0x1000f]
[    4.363588][    T1] pci 0000:01:00.0: BAR 0: assigned [io  0x10010-0x10017]
[    4.369964][    T1] pci 0000:01:00.0: BAR 2: assigned [io  0x10018-0x1001f]
[    4.376341][    T1] pci 0000:01:00.0: BAR 1: assigned [io  0x10020-0x10023]
[    4.382701][    T1] pci 0000:01:00.0: BAR 3: assigned [io  0x10024-0x10027]
[    4.389077][    T1] pci 0000:00:01.0: PCI bridge to [bus 01]
[    4.394247][    T1] pci 0000:00:01.0:   bridge window [io  0x10000-0x10fff]
[    4.400623][    T1] pci 0000:00:01.0:   bridge window [mem 0xf8000000-0xf80ff                               fff]
[    4.407482][    T1] pci 0000:02:00.0: BAR 0: assigned [mem 0xf8100000-0xf810f                               fff 64bit]
[    4.414816][    T1] pci 0000:02:00.0: BAR 2: assigned [mem 0xf8110000-0xf8110                               fff 64bit]
[    4.422132][    T1] pci 0000:02:00.0: BAR 4: assigned [mem 0xf8111000-0xf8111                               fff 64bit]
[    4.429464][    T1] pci 0000:00:02.0: PCI bridge to [bus 02]
[    4.434652][    T1] pci 0000:00:02.0:   bridge window [mem 0xf8100000-0xf81ff                               fff]
[    4.441609][    T1] pcieport 0000:00:01.0: enabling device (0140 -> 0143)
[    4.447957][    T1] pcieport 0000:00:02.0: enabling device (0140 -> 0142)
[    4.455439][    T1] mv_xor d0060800.xor: Marvell shared XOR driver
[    4.526004][    T1] mv_xor d0060800.xor: Marvell XOR (Registers Mode): ( xor                                cpy intr )
[    4.537016][    T1] mv_xor d0060900.xor: Marvell shared XOR driver
[    4.606018][    T1] mv_xor d0060900.xor: Marvell XOR (Registers Mode): ( xor                                cpy intr )
[    4.808117][    T1] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    4.818987][    T1] printk: console [ttyS0] disabled
[    4.845281][    T1] d0012000.serial: ttyS0 at MMIO 0xd0012000 (irq = 19, base                               _baud = 12500000) is a 16550A
[    4.854208][    T1] printk: console [ttyS0] enabled
[    4.854208][    T1] printk: console [ttyS0] enabled
[    4.863378][    T1] printk: bootconsole [earlycon0] disabled
[    4.863378][    T1] printk: bootconsole [earlycon0] disabled
[    4.876227][    T1] ahci 0000:01:00.0: enabling device (0146 -> 0147)
[    4.882466][    T1] ahci 0000:01:00.0: AHCI 0001.0000 32 slots 2 ports 6 Gbps                                0x3 impl SATA mode
[    4.891464][    T1] ahci 0000:01:00.0: flags: 64bit ncq sntf led only pmp fbs                                pio slum part sxs
[    4.902942][    T1] scsi host0: ahci
[    4.907616][    T1] scsi host1: ahci
[    4.911660][    T1] ata1: SATA max UDMA/133 abar m512@0xf8010000 port 0xf8010                               100 irq 42
[    4.919456][    T1] ata2: SATA max UDMA/133 abar m512@0xf8010000 port 0xf8010                               180 irq 42
[    4.928070][    T1] sata_mv d00a0000.sata: slots 32 ports 1
[    4.936508][    T1] scsi host2: sata_mv
[    4.940844][    T1] ata3: SATA max UDMA/133 irq 27
[    4.946977][    T1] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xf1
[    4.953480][    T1] nand: Micron MT29F1G08ABADAWP
[    4.958930][    T1] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048,                                OOB size: 64
[    4.967363][    T1] Bad block table found at page 65472, version 0x01
[    4.973827][    T1] Bad block table found at page 65408, version 0x01
[    4.980167][    T1] 5 cmdlinepart partitions found on MTD device pxa3xx_nand-                               0
[    4.986987][    T1] Creating 5 MTD partitions on "pxa3xx_nand-0":
[    4.992609][    T1] 0x000000000000-0x000000180000 : "u-boot"
[    5.000131][    T1] 0x000000180000-0x0000001a0000 : "u-boot-env"
[    5.008493][    T1] 0x000000200000-0x000000800000 : "uImage"
[    5.016572][    T1] 0x000000800000-0x000000c00000 : "minirootfs"
[    5.024962][    T1] 0x000000c00000-0x000008000000 : "ubifs"
[    5.034531][    T1] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com                                for information.
[    5.043722][    T1] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Ja                               son@zx2c4.com>. All Rights Reserved.
[    5.057273][    T1] libphy: Fixed MDIO Bus: probed
[    5.066828][    T1] libphy: orion_mdio_bus: probed
[    5.089362][    T1] mvneta d0074000.ethernet eth0: Using random mac address 7                               e:a5:e6:ae:62:8b
[    5.101839][    T1] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Drive                               r
[    5.109195][    T1] ehci-pci: EHCI PCI platform driver
[    5.114167][    T1] ehci-orion: EHCI orion driver
[    5.119187][    T1] orion-ehci d0050000.usb: EHCI Host Controller
[    5.125114][    T1] orion-ehci d0050000.usb: new USB bus registered, assigned                                bus number 1
[    5.132978][    T1] orion-ehci d0050000.usb: irq 25, io mem 0xd0050000
[    5.164662][    T1] orion-ehci d0050000.usb: USB 2.0 started, EHCI 1.00
[    5.171150][    T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=                               0002, bcdDevice= 5.08
[    5.179495][    T1] usb usb1: New USB device strings: Mfr=3, Product=2, Seria                               lNumber=1
[    5.186859][    T1] usb usb1: Product: EHCI Host Controller
[    5.192047][    T1] usb usb1: Manufacturer: Linux 5.8.5-mvebu-370xp-tld-1 ehc                               i_hcd
[    5.199088][    T1] usb usb1: SerialNumber: d0050000.usb
[    5.205131][    T1] hub 1-0:1.0: USB hub found
[    5.209634][    T1] hub 1-0:1.0: 1 port detected
[    5.215500][    T1] xhci_hcd 0000:02:00.0: xHCI Host Controller
[    5.221504][    T1] xhci_hcd 0000:02:00.0: new USB bus registered, assigned b                               us number 2
[    5.229970][    T1] xhci_hcd 0000:02:00.0: hcc params 0x200073a1 hci version                                0x100 quirks 0x0000000000080010
[    5.240102][    T1] usb usb2: New USB device found, idVendor=1d6b, idProduct=                               0002, bcdDevice= 5.08
[    5.248519][    T1] usb usb2: New USB device strings: Mfr=3, Product=2, Seria                               lNumber=1
[    5.255897][ T1197] ata2: SATA link down (SStatus 0 SControl 300)
[    5.261584][ T1193] ata1: SATA link down (SStatus 0 SControl 300)
[    5.267266][    T1] usb usb2: Product: xHCI Host Controller
[    5.272505][    T1] usb usb2: Manufacturer: Linux 5.8.5-mvebu-370xp-tld-1 xhc                               i-hcd
[    5.279606][    T1] usb usb2: SerialNumber: 0000:02:00.0
[    5.285560][    T1] hub 2-0:1.0: USB hub found
[    5.289991][    T1] hub 2-0:1.0: 2 ports detected
[    5.295479][    T1] xhci_hcd 0000:02:00.0: xHCI Host Controller
[    5.300970][    T1] xhci_hcd 0000:02:00.0: new USB bus registered, assigned b                               us number 3
[    5.308882][    T1] xhci_hcd 0000:02:00.0: Host supports USB 3.0 SuperSpeed
[    5.315676][    T1] usb usb3: We don't know the algorithms for LPM for this h                               ost, disabling LPM.
[    5.323968][    T1] usb usb3: New USB device found, idVendor=1d6b, idProduct=                               0003, bcdDevice= 5.08
[    5.332370][    T1] usb usb3: New USB device strings: Mfr=3, Product=2, Seria                               lNumber=1
[    5.339733][    T1] usb usb3: Product: xHCI Host Controller
[    5.344920][    T1] usb usb3: Manufacturer: Linux 5.8.5-mvebu-370xp-tld-1 xhc                               i-hcd
[    5.351896][    T1] usb usb3: SerialNumber: 0000:02:00.0
[    5.357764][    T1] hub 3-0:1.0: USB hub found
[    5.362160][    T1] hub 3-0:1.0: 2 ports detected
[    5.368323][    T1] usbcore: registered new interface driver usblp
[    5.375125][    T1] usbcore: registered new interface driver usb-storage
[    5.382124][    T1] mousedev: PS/2 mouse device common for all mice
[    5.389967][    T1] i2c /dev entries driver
[    5.398763][    T1] rtc-ds1307 0-0068: 'wakeup-source' is set, request for an                                IRQ is disabled!
[    5.412146][    T1] rtc-ds1307 0-0068: registered as rtc0
[    5.418828][    T1] rtc-ds1307 0-0068: setting system clock to 2000-01-06T21:                               08:32 UTC (947192912)
[    5.444702][ T1209] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl F300)
[    5.456279][    T1] orion_wdt: Initial timeout 229 sec
[    5.461617][ T1209] ata3.00: ATA-7: ST940210AS, 3.ALC, max UDMA/100
[    5.468672][    T1] device-mapper: uevent: version 1.0.3
[    5.473725][ T1209] ata3.00: 78140160 sectors, multi 0: LBA48 NCQ (depth 31/3                               2)
[    5.481337][    T1] device-mapper: ioctl: 4.42.0-ioctl (2020-02-27) initialis                               ed: dm-devel@redhat.com
[    5.490748][    T1] device-mapper: multipath round-robin: version 1.2.0 loade                               d
[    5.497834][    T1] device-mapper: multipath queue-length: version 0.2.0 load                               ed
[    5.505048][    T1] device-mapper: multipath service-time: version 0.3.0 load                               ed
[    5.511879][ T1209] ata3.00: configured for UDMA/100
[    5.516598][    T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[    5.522857][    T1] device-mapper: raid: Loading target version 1.15.1
[    5.536509][    T1] marvell-cesa d0090000.crypto: CESA device successfully re                               gistered
[    5.544289][ T1201] scsi 2:0:0:0: Direct-Access     ATA      ST940210AS                                      C    PQ: 0 ANSI: 5
[    5.553293][    T1] hid: raw HID events driver (C) Jiri Kosina
[    5.561124][  T183] sd 2:0:0:0: [sda] 78140160 512-byte logical blocks: (40.0                                GB/37.3 GiB)
[    5.570885][    T1] usbcore: registered new interface driver usbhid
[    5.576812][   T20] usb 1-1: new high-speed USB device number 2 using orion-e                               hci
[    5.584344][  T183] sd 2:0:0:0: [sda] Write Protect is off
[    5.589814][    T1] usbhid: USB HID core driver
[    5.594403][  T183] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabl                               ed, doesn't support DPO or FUA
[    5.604320][    T1] drop_monitor: Initializing network drop monitor service
[    5.613388][    T1] NET: Registered protocol family 10
[    5.619641][    T1] Segment Routing with IPv6
[    5.623667][    T1] RPL Segment Routing with IPv6
[    5.628228][    T1] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    5.636810][    T1] NET: Registered protocol family 17
[    5.642585][    T1] 8021q: 802.1Q VLAN Support v1.8
[    5.647305][    T1] Key type dns_resolver registered
[    5.652183][    T1] ThumbEE CPU extension supported.
[    5.656873][    T1] Registering SWP/SWPB emulation handler
[    5.662434][    T1] registered taskstats version 1
[    5.667316][    T1] Loading compiled-in X.509 certificates
[    5.672534][    T1] zswap: loaded using pool lzo/zbud
[    5.677751][    T1] Key type ._fscrypt registered
[    5.682095][    T1] Key type .fscrypt registered
[    5.686492][    T1] Key type fscrypt-provisioning registered
[    5.694753][    T1] Key type big_key registered
[    5.723710][    T1] Key type encrypted registered
[    5.732724][    T1] input: gpio-keys as /devices/platform/gpio-keys/input/inp                               ut0
[    5.773077][  T183]  sda: sda1
[    5.779889][  T183] sd 2:0:0:0: [sda] Attached SCSI disk
[    5.787421][   T20] usb 1-1: New USB device found, idVendor=0781, idProduct=5                               56b, bcdDevice= 1.26
[    5.797376][    T1] Freeing unused kernel memory: 1024K
[    5.802501][   T20] usb 1-1: New USB device strings: Mfr=1, Product=2, Serial                               Number=3
[    5.812051][    T1] Checked W+X mappings: passed, no W+X pages found
[    5.818176][    T1] Run /init as init process
[    5.824792][   T20] usb 1-1: Product: Cruzer Edge
[    5.829175][   T20] usb 1-1: Manufacturer: SanDisk
[    5.833597][   T20] usb 1-1: SerialNumber: 20053045001B529189D3
[    5.856531][   T20] usb-storage 1-1:1.0: USB Mass Storage device detected
[    5.874957][   T20] scsi host3: usb-storage 1-1:1.0
Loading, please wait...
Starting version 241
[    6.906564][  T183] scsi 3:0:0:0: Direct-Access     SanDisk  Cruzer Edge                                     1.26 PQ: 0 ANSI: 6
[    6.925769][ T1201] sd 3:0:0:0: [sdb] 15633408 512-byte logical blocks: (8.00                                GB/7.45 GiB)
[    6.950244][ T1201] sd 3:0:0:0: [sdb] Write Protect is off
[    6.966202][ T1201] sd 3:0:0:0: [sdb] Write cache: disabled, read cache: enab                               led, doesn't support DPO or FUA
[    7.026454][ T1201]  sdb: sdb1
[    7.037157][    C0] random: fast init done
[    7.043887][ T1201] sd 3:0:0:0: [sdb] Attached SCSI disk
[    8.885016][ T1485] usbcore: registered new interface driver uas
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
[   21.248622][ T1503] process '/usr/bin/fstype' started with executable stack
Begin: Will now check root file system ... fsck from util-linux 2.33.1
[/sbin/fsck.ext3 (1) -- /dev/sda1] fsck.ext3 -a -C0 /dev/sda1
rootfs: clean, 28904/488640 files, 381660/1953536 blocks
done.
[   22.051467][ T1513] EXT4-fs (sda1): mounting ext3 file system using the ext4                                subsystem
[   22.427542][ T1513] EXT4-fs (sda1): mounted filesystem with ordered data mode                               . Opts: (null)
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
[   24.855464][    T1] systemd[1]: System time before build time, advancing cloc                               k.
[   25.319091][    T1] systemd[1]: systemd 241 running in system mode. (+PAM +AU                               DIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTL                               S +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierar                               chy=hybrid)
[   25.340710][    T1] systemd[1]: Detected architecture arm.

Welcome to Debian GNU/Linux 10 (buster)!

[   25.443933][    T1] systemd[1]: Set hostname to <Neutron>.
[   27.270020][    T1] systemd[1]: File /lib/systemd/system/systemd-journald.ser                               vice:12 configures an IP firewall (IPAddressDeny=any), but the local system does                                not support BPF/cgroup based firewalling.
[   27.286734][    T1] systemd[1]: Proceeding WITHOUT firewalling in effect! (Th                               is warning is only shown for the first loaded unit using IP firewalling.)
[   28.300706][    T1] systemd[1]: /lib/systemd/system/rpc-statd.service:13: PID                               File= references path below legacy directory /var/run/, updating /var/run/rpc.st                               atd.pid → /run/rpc.statd.pid; please update the unit file accordingly.
[   28.505634][    T1] systemd[1]: /lib/systemd/system/fancontrol.service:9: PID                               File= references path below legacy directory /var/run/, updating /var/run/fancon                               trol.pid → /run/fancontrol.pid; please update the unit file accordingly.
[   28.629188][    T1] random: systemd: uninitialized urandom read (16 bytes rea                               d)
[   28.649714][    T1] random: systemd: uninitialized urandom read (16 bytes rea                               d)
[   28.657998][    T1] systemd[1]: Listening on fsck to fsckd communication Sock                               et.
[  OK  ] Listening on fsck to fsckd communication Socket.
[   28.695280][    T1] random: systemd: uninitialized urandom read (16 bytes rea                               d)
[   28.703911][    T1] systemd[1]: Listening on RPCbind Server Activation Socket                               .
[  OK  ] Listening on RPCbind Server Activation Socket.
[   28.746058][    T1] systemd[1]: Started Dispatch Password Requests to Console                                Directory Watch.
[  OK  ] Started Dispatch Password …ts to Console Directory Watch.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Reached target Swap.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Reached target Slices.
[  OK  ] Created slice system-getty.slice.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Set up automount Arbitrary…s File System Automount Point.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Listening on Journal Socket.
         Mounting POSIX Message Queue File System...
         Mounting NFSD configuration filesystem...
         Mounting RPC Pipe File System...
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started Forward Password R…uests to Wall Directory Watch.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Reached target Paths.
[   29.344727][    C0] random: crng init done
[   29.348525][    C0] random: 7 urandom warning(s) missed due to ratelimiting
         Starting Load Kernel Modules...
         Starting Remount Root and Kernel File Systems...
         Starting Create list of re…odes for the current kernel...
         Mounting Kernel Debug File System...
[  OK  ] Listening on initctl Compatibility Named Pipe.
[  OK  ] Listening on Journal Audit Socket.
         Starting Journal Service...
[  OK  ] Listening on udev Kernel Socket.
         Starting udev Coldplug all Devices...
[   29.825299][ T1547] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted NFSD configuration filesystem.
[  OK  ] Mounted RPC Pipe File System.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Started Create list of req… nodes for the current kernel.
[  OK  ] Mounted Kernel Debug File System.
         Starting Create System Users...
         Starting Load/Save Random Seed...
[   30.331791][    T1] systemd[1]: Starting Apply Kernel Variables...
         Starting Apply Kernel Variables...
[   30.481048][    T1] systemd[1]: Starting pNFS block layout mapping daemon...
         Starting pNFS block layout mapping daemon...
[   30.576143][    T1] systemd[1]: nfs-blkmap.service: Can't open PID file /run/                               blkmapd.pid (yet?) after start: No such file or directory
[   30.655796][    T1] systemd[1]: Started pNFS block layout mapping daemon.
[  OK  ] Started pNFS block layout mapping daemon.
[   30.833572][    T1] systemd[1]: Started Load/Save Random Seed.
[  OK  ] Started Load/Save Random Seed.
[   30.915559][    T1] systemd[1]: Started Create System Users.
[  OK  ] Started Create System Users.
[   30.945010][    T1] systemd[1]: Started Apply Kernel Variables.
[  OK  ] Started Apply Kernel Variables.
[   30.997166][    T1] systemd[1]: Starting Create Static Device Nodes in /dev..                               .
         Starting Create Static Device Nodes in /dev...
[   31.460203][    T1] systemd[1]: Started Create Static Device Nodes in /dev.
[  OK  ] Started Create Static Device Nodes in /dev.
[   31.516727][    T1] systemd[1]: Started Journal Service.
[  OK  ] Started Journal Service.
         Starting Flush Journal to Persistent Storage...
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /tmp...
         Starting udev Kernel Device Manager...
[  OK  ] Mounted /tmp.
[   31.986255][ T1546] systemd-journald[1546]: Received request to flush runtime                                journal from PID 1
[  OK  ] Reached target Local File Systems.
         Starting Preprocess NFS configuration...
[  OK  ] Started Flush Journal to Persistent Storage.
         Starting Create Volatile Files and Directories...
[  OK  ] Started Preprocess NFS configuration.
[  OK  ] Reached target NFS client services.
         Starting NFSv4 ID-name mapping service...
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Started NFSv4 ID-name mapping service.
[  OK  ] Started Create Volatile Files and Directories.
         Starting RPC bind portmap service...
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Started RPC bind portmap service.
[  OK  ] Reached target RPC Port Mapper.
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Reached target System Initialization.
[  OK  ] Started Daily apt download activities.
[  OK  ] Started Daily man-db regeneration.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Started Daily rotation of log files.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Started Daily apt upgrade and clean activities.
[  OK  ] Reached target Timers.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
         Starting Avahi mDNS/DNS-SD Stack...
         Starting fan speed regulator...
[  OK  ] Started D-Bus System Message Bus.
         Starting Login Service...
         Starting Helper to synchronize boot up for ifupdown...
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started Login Service.
[   36.624973][ T1565] sd 2:0:0:0: Attached scsi generic sg0 type 0
[   36.877757][ T1565] sd 3:0:0:0: Attached scsi generic sg1 type 0
[  OK  ] Started fan speed regulator.
[  OK  ] Started Helper to synchronize boot up for ifupdown.
         Starting Raise network interfaces...
[   57.409125][ T1847] mvneta d0074000.ethernet eth0: PHY [d0072004.mdio-mii:00]                                driver [Marvell 88E1318S] (irq=POLL)
[   57.419160][ T1847] mvneta d0074000.ethernet eth0: configuring for phy/rgmii-                               id link mode
[   59.545616][   T20] mvneta d0074000.ethernet eth0: Link is Up - 100Mbps/Full                                - flow control rx/tx
[   59.553843][   T20] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  OK  ] Started Raise network interfaces.
[  OK  ] Reached target Network.
         Starting /etc/rc.local Compatibility...
[  OK  ] Started Glances.
         Starting NFS Mount Daemon...
         Starting OpenBSD Secure Shell server...
         Starting Network Time Service...
[   66.383474][ T1917] Setting Persistent MAC address to 00:50:43:00:02:02
[   66.562567] rc.local[1915]: <13>Feb 14 02:12:39 root[1927]: Setting Persisten                               t MAC address to 00:50:43:00:02:02
[   67.027824] rc.local[1915]: Killed old client process
[  OK  ] Started Network Time Service.
[  OK  ] Started NFS Mount Daemon.
         Starting NFS server and services...
[  OK  ] Started OpenBSD Secure Shell server.
[   68.004392] rc.local[1915]: Internet Systems Consortium DHCP Client 4.4.1
[   68.012665] rc.local[1915]: Copyright 2004-2018 Internet Systems Consortium.
[   68.041014] rc.local[1915]: All rights reserved.
[   68.071051] rc.local[1915]: For info, please visit https://www.isc.org/softwa                               re/dhcp/
[   68.104249] rc.local[1915]: Listening on LPF/eth0/7e:a5:e6:ae:62:8b
[   68.148363] rc.local[1915]: Sending on   LPF/eth0/7e:a5:e6:ae:62:8b
[   68.183830] rc.local[1915]: Sending on   Socket/fallback
[   68.192006] rc.local[1915]: DHCPRELEASE of 192.168.2.112 on eth0 to 192.168.2                               .1 port 67
[   68.407761][   T20] mvneta d0074000.ethernet eth0: Link is Down
[   68.764202][ T1947] NFSD: Using UMH upcall client tracking operations.
[   68.778629][ T1947] NFSD: starting 90-second grace period (net f0000021)
[  OK  ] Started NFS server and services.
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Reached target Remote File Systems.
         Starting LSB: Starts syslogd...
[  OK  ] Started Regular background program processing daemon.
         Starting Permit User Sessions...
[   69.239631] rc.local[1915]: Internet Systems Consortium DHCP Client 4.4.1
[   69.291020] rc.local[1915]: Copyright 2004-2018 Internet Systems Consortium.
[   69.321038] rc.local[1915]: All rights reserved.
[   69.351027] rc.local[1915]: For info, please visit https://www.isc.org/softwa                               re/dhcp/
[  OK  ] Started Permit User [   69.611424][ T1996] mvneta d0074000.ethernet eth                               0: PHY [d0072004.mdio-mii:00] driver [Marvell 88E1318S] (irq=POLL)
Sessions.
[   69.643239][ T1996] mvneta d0074000.ethernet eth0: configuring for phy/rgmii-                               id link mode
[   69.744835] rc.local[1915]: Listening on LPF/eth0/00:50:43:00:02:02
[   69.758057] rc.local[1915]: Sending on   LPF/eth0/00:50:43:00:02:02
[   69.791226] rc.local[1915]: Sending on   Socket/fallback
[   69.820984] rc.local[1915]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 i                               nterval 4
[  OK  ] Started LSB: Starts syslogd.
         Starting LSB: Starts klogd...
[  OK  ] Started LSB: Starts klogd.
[   71.787646][   T20] mvneta d0074000.ethernet eth0: Link is Up - 100Mbps/Full                                - flow control rx/tx
[   71.795873][   T20] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   73.786491] rc.local[1915]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 i                               nterval 6
[   76.553496] rc.local[1915]: DHCPOFFER of 192.168.2.112 from 192.168.2.1
[   76.561196] rc.local[1915]: DHCPREQUEST for 192.168.2.112 on eth0 to 255.255.                               255.255 port 67
[   76.590996] rc.local[1915]: DHCPACK of 192.168.2.112 from 192.168.2.1
[   77.002922] rc.local[1915]: bound to 192.168.2.112 -- renewal in 18447 second                               s.
[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Started Getty on tty1.
[  OK  ] Started Serial Getty on ttyS0.
[  OK  ] Reached target Login Prompts.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.
[   78.800030][ T2066] fbcon: Taking over console

Debian GNU/Linux 10 Neutron ttyS0

Neutron login: root
Password:
Last login: Thu Feb 14 02:15:21 PST 2019 on ttyS0
Linux Neutron 5.8.5-mvebu-370xp-tld-1 #1.0 SMP PREEMPT Mon Aug 31 00:00:32 PDT 2                               020 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Neutron
192.168.2.112
NETGEAR ReadyNAS 102
Linux version 5.8.5-mvebu-370xp-tld-1 (root@tldDebianVM) (arm-linux-gnueabihf-gc                               c (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04) 7.5.0, GNU ld (GNU Binutils for Ubuntu) 2                               .30) #1.0 SMP PREEMPT Mon Aug 31 00:00:32 PDT 2020
Debian 10.5
Thu Feb 14 02:13:04 PST 2019 up 1 minute
root@Neutron:~# lsblk
NAME      MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda         8:0    0 37.3G  0 disk
└─sda1      8:1    0 37.3G  0 part /
sdb         8:16   0  7.5G  0 disk
└─sdb1      8:17   0  7.5G  0 part
mtdblock0  31:0    0  1.5M  0 disk
mtdblock1  31:1    0  128K  0 disk
mtdblock2  31:2    0    6M  0 disk
mtdblock3  31:3    0    4M  0 disk
mtdblock4  31:4    0  116M  0 disk
root@Neutron:~# dmesg | grep -i sata
[    4.882466] ahci 0000:01:00.0: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 imp                               l SATA mode
[    4.911660] ata1: SATA max UDMA/133 abar m512@0xf8010000 port 0xf8010100 irq                                42
[    4.919456] ata2: SATA max UDMA/133 abar m512@0xf8010000 port 0xf8010180 irq                                42
[    4.927854] sata_mv d00a0000.sata: version 1.28
[    4.928070] sata_mv d00a0000.sata: slots 32 ports 1
[    4.936508] scsi host2: sata_mv
[    4.940844] ata3: SATA max UDMA/133 irq 27
[    5.255897] ata2: SATA link down (SStatus 0 SControl 300)
[    5.261584] ata1: SATA link down (SStatus 0 SControl 300)
[    5.444702] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl F300)
root@Neutron:~#

One interesting behavior i see; act led is off; normally this led was always on and even internal bays are empty 1st led sees activity on e-SATA port.
Another info; it seems this e-SATA port directly connected to armada cpu so maybe SSD detection works i cant test because i dont have a spare one best i can do is i will make a socket for mSATA drive and solder socket wires to pcb and use it with mSATA drive.
Regards.



Edited 1 time(s). Last edit at 09/30/2020 04:14AM by whitepawn.
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: