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

Problems with packages? Post here, using [tags] of the package name.

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

Postby arti74 » Sat May 12, 2018 7:01 pm

Yeah it was a pain for me for several days, I feel relieved now ;) Thanks again for this great help. I think that my box is somewhat special...

The commands shows something:
$this->bbcode_second_pass_code('', 'sudo i2cdetect -l
i2c-0 i2c mv64xxx_i2c adapter I2C adapter
[rtorrent@alarm ~]$ sudo i2cdetect -l
i2c-0 i2c mv64xxx_i2c adapter I2C adapter')
arti74
 
Posts: 75
Joined: Tue Apr 17, 2018 10:33 am

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

Postby summers » Sun May 13, 2018 11:04 am

Well as expected you have an i2c bus. $this->bbcode_second_pass_code('', 'i2cdetect 0') will show what address are responded to. $this->bbcode_second_pass_code('', 'i2cdump 0 address') will show you the data on that address.

Now what you have on you i2c bus, who can say, nas central doesn't really say, and that I find the best resource. But you could try monitoring the various numbers, and see what changes say when the case is closed, or the fan unplugged. But working out whats on the i2c bus will be a bit of work ...

eg, 10 minutes or so on my box gave the address for temp and fan speed, and $this->bbcode_second_pass_code('', 'i2cdump 0x0 0x50') gives the eth mac address ...

For example on my nsa325 now the case is closed, it says 36degC and fan at 625rpm.

Finished my rebuild this morning, and hour or so closing up the case, then rebuilding the beagle farm, and updating the little boxes.
summers
 
Posts: 984
Joined: Sat Sep 06, 2014 12:56 pm

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

Postby arti74 » Sun May 13, 2018 12:31 pm

Hello again :)
This is result of the i2detect command:
$this->bbcode_second_pass_code('', '[rtorrent@alarm ~]$ sudo i2cdetect 0
[sudo] password for rtorrent:
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0.
I will probe address range 0x03-0x77.
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- 2e --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- 64 -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --')
$this->bbcode_second_pass_code('', '[rtorrent@alarm ~]$ sudo i2cdump 0 0x2e
[sudo] password for rtorrent:
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0, address 0x2e, mode byte
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
20: 00 00 00 00 00 80 80 80 00 00 00 00 00 00 00 00 .....???........
30: ff ff ff 00 00 00 00 00 ff ff ff 00 00 76 41 69 .............vAi
40: 04 00 00 00 00 ff 00 ff 00 ff 00 ff 00 ff 81 7f ?.............??
50: 81 7f 81 7f ff ff ff ff ff ff ff ff 62 62 62 c4 ????........bbb?
60: c4 c4 00 00 80 80 80 5a 5a 5a 64 64 64 44 40 00 ??..???ZZZdddD@.
70: 00 00 00 00 00 00 00 00 00 00 00 55 01 00 00 00 ...........U?...
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................')
$this->bbcode_second_pass_quote('', 'y')ou could try monitoring the various numbers

Which numbers for example? Eg. adresses like 0x4 0x3...? I'm not sure which values are correct.
And my box is closed already - since the kernel/uboot work is done.
arti74
 
Posts: 75
Joined: Tue Apr 17, 2018 10:33 am

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

Postby summers » Sun May 13, 2018 2:35 pm

Well its about numerology on numbers, e.g. the 0x00 and 0xff probably don't mean much, so probably not used. Similarly the repeating numbers, also don't contain much information eg. 80 80 80 5a 5a 5a 64 64 64. But why they have numbers is strange.

So the numbers that seem to have some content: 76 41 69 04, but as to what they mean, hard to say. Don't look like a mac address. Do the numbers change over time?

Did address 0x64 have anything in it?
summers
 
Posts: 984
Joined: Sat Sep 06, 2014 12:56 pm

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

Postby arti74 » Sun May 13, 2018 2:52 pm

$this->bbcode_second_pass_quote('', 'D')o the numbers change over time?

As far I see the numbers diplayed previously remains constant.
$this->bbcode_second_pass_quote('', 'D')id address 0x64 have anything in it?

The 0x64 address shows all the "X"-es - so probably empty.
arti74
 
Posts: 75
Joined: Tue Apr 17, 2018 10:33 am
Top

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

Postby arti74 » Mon May 21, 2018 7:51 pm

Problem with sensors solved!
Please check here:
https://archlinuxarm.org/forum/viewtopic.php?f=53&t=12715
arti74
 
Posts: 75
Joined: Tue Apr 17, 2018 10:33 am

Previous

Return to Packages

Who is online

Users browsing this forum: No registered users and 13 guests