4.4.97-1-ARCH wrong NAND chip timing in the DTS? NSA310 NAS

[summers]

Probably worth digging round in /proc/device-tree and see whats set there. the nand settings are in the directory where we set the chip delay. Anyway see what the device tree has different between partition0 and partition1.

[arti74]

This is what is there:
$this->bbcode_second_pass_code('', '[root@alarm rtorrent]# ls -l /proc/device-tree/
total 0
-r--r--r-- 1 root root 4 May 9 12:08 '#address-cells'
-r--r--r-- 1 root root 4 May 9 12:08 '#size-cells'
drwxr-xr-x 2 root root 0 May 9 12:02 aliases
drwxr-xr-x 2 root root 0 May 9 12:02 chosen
-r--r--r-- 1 root root 55 May 9 12:08 compatible
drwxr-xr-x 3 root root 0 May 9 12:02 cpus
drwxr-xr-x 12 root root 0 May 9 12:02 gpio-leds
drwxr-xr-x 5 root root 0 May 9 12:02 gpio_keys
drwxr-xr-x 2 root root 0 May 9 12:02 gpio_poweroff
-r--r--r-- 1 root root 4 May 9 12:08 interrupt-parent
drwxr-xr-x 5 root root 0 May 9 12:02 mbus@f1000000
drwxr-xr-x 2 root root 0 May 9 12:02 memory
-r--r--r-- 1 root root 13 May 9 12:08 model
-r--r--r-- 1 root root 1 May 9 12:08 name
drwxr-xr-x 31 root root 0 May 9 12:02 ocp@f1000000
drwxr-xr-x 3 root root 0 May 9 12:02 regulators')
$this->bbcode_second_pass_code('', 'ls -l /proc/device-tree/mbus\@f1000000/nand\@12f/partition\@0/
total 0
-r--r--r-- 1 root root 6 May 9 12:06 label
-r--r--r-- 1 root root 10 May 9 12:06 name
-r--r--r-- 1 root root 0 May 9 12:06 read-only
-r--r--r-- 1 root root 8 May 9 12:06 reg')
$this->bbcode_second_pass_code('', '[root@alarm rtorrent]# ls -l /proc/device-tree/mbus\@f1000000/nand\@12f/partition\@100000/
total 0
-r--r--r-- 1 root root 10 May 9 12:05 label
-r--r--r-- 1 root root 10 May 9 12:05 name
-r--r--r-- 1 root root 8 May 9 12:05 reg')
What if manually remove this (empty) 'read-only' file?
EDIT:
$this->bbcode_second_pass_code('', '[root@alarm rtorrent]# mv /proc/device-tree/mbus\@f1000000/nand\@12f/partition\@0/read-only /home/rtorrent/
mv: cannot remove '/proc/device-tree/mbus@f1000000/nand@12f/partition@0/read-only': Operation not permitted
')
So not so easy, without first unmounting it (or changing permissions?) - it can't be done i think. Maybe when plugging this disk as an external drive to my computer I could do it. I'm not sure about result of this though.

Changing permission didn't help - after chmod u+x I have still 'Operation not permitted' error
$this->bbcode_second_pass_code('', '[root@alarm rtorrent]# ls -l /proc/device-tree/mbus\@f1000000/nand\@12f/partition\@0/read-only
-r-xr--r-- 1 root root 0 May 9 12:06 /proc/device-tree/mbus@f1000000/nand@12f/partition@0/read-only')

[summers]

alas no you can't change the device tree on a running system. /proc is a virtual system - so it won't exist when the hdd is elsewhere, its just the kernel reporting what its device tree is.

So something is pushing it read only. I'll check the dts when I get home, but it seems strange. I could try just giving you the chosen node, that you usually get with a device tree uboot. Anyway that would make you as close to a usual system as possible, and we know my nsa325 works ....

$this->bbcode_second_pass_quote('', '/')proc is a virtual system

[summers]

Just a though, did you put it in /dev/sda1 ? the old uboot can only boot from ext2, so it has to go in /dev/sda1 ...

[arti74]

Of course - I put it in my boot directory which is on /dev/sda1 - ext2
From fdisk:
$this->bbcode_second_pass_code('', 'Command (m for help): p
Disk /dev/sda: 698.7 GiB, 750156374016 bytes, 1465149168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xab197877

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 34815 32768 16M 83 Linux
/dev/sda2 34816 1465149167 1465114352 698.6G 83 Linux')

[summers]

Are ok - was just thinking you said before that mount didn't show it ...

As I was eating over lunch, looked into what could be going wrong. it doesn't make much sense. So I'll check what I sent was correct, then look into adding chosen ...

OK have checked. am 95% sure that I made the right change. I'll look at doing it in chosen, as that is all else I can think of.

Pity we havn't heard from anyone else with an nsa310 ...

[arti74]

Hey, maybe provide yet the md5sum for the new uImage...
$this->bbcode_second_pass_quote('', 'P')ity we havn't heard from anyone else with an nsa310

[summers]

OK I've just done another uImage same place as before. This what I set chosen, which is the only other think I have set. You can check it has worked by:
$this->bbcode_second_pass_code('', 'cat /proc/device-tree/chosen/bootargs
console=ttyS0,115200 mtdparts=orion_nand:0xC0000(uboot),0x40000(uboot_env),0x80000(old_uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2)')

[arti74]

After changing for the new uImage (md5sum 2f39f05a43bf3556a67749487893a0ef)
$this->bbcode_second_pass_code('', 'cat /proc/device-tree/chosen/bootargs
console=ttyS0,115200=mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/sda2 rw rootwait loglevel=8')
$this->bbcode_second_pass_code('', '[rtorrent@alarm ~]$ mtdinfo /dev/mtd0
mtd0
Name: uboot
Type: nand
Eraseblock size: 131072 bytes, 128.0 KiB
Amount of eraseblocks: 8 (1048576 bytes, 1024.0 KiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 512 bytes
OOB size: 64 bytes
Character device major/minor: 90:0
Bad blocks are allowed: true
Device is writable: false')

Maybe I should do this dts change on my own device? If it could change anything.. (then I would need more step by step directions...)