Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing
Posted by bodhi
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing January 29, 2016 02:48PM |
Registered: 8 years ago Posts: 59 |
Hmmm pin 16??
But that's probably just the first HDD...
I see no evidence in u-boot of that board having two SATA buses! (not that I would, what with the lack of code comments...)
So to power up the HDD(s?), this is what happens:
Where hddPowerBit = 16 unless my logic is flawed somewhere, this is 64K ??
Am I on the right track here?
I thought pin 16 was the green LED for the 1st HDD...
MV_BOARD_GPP_INFO rd88f6192AInfoBoardGppInfo[] =
/* {{MV_BOARD_GPP_CLASS devClass, MV_U8 gppPinNum}} */
{
{BOARD_GPP_USB_VBUS_EN, 10},
{BOARD_GPP_USB_HOST_DEVICE, 11},
{BOARD_GPP_RESET, 14},
{BOARD_GPP_POWER_ON_LED, 15},
{BOARD_GPP_HDD_POWER, 16},
{BOARD_GPP_WPS_BUTTON, 24},
{BOARD_GPP_TS_BUTTON_C, 25},
{BOARD_GPP_USB_VBUS, 26},
{BOARD_GPP_USB_OC, 27},
{BOARD_GPP_TS_BUTTON_U, 30},
{BOARD_GPP_TS_BUTTON_R, 31},
{BOARD_GPP_TS_BUTTON_L, 32},
{BOARD_GPP_TS_BUTTON_D, 34},
{BOARD_GPP_FAN_POWER, 35}
};
But that's probably just the first HDD...
I see no evidence in u-boot of that board having two SATA buses! (not that I would, what with the lack of code comments...)
So to power up the HDD(s?), this is what happens:
/* HDD power on */
MV_REG_BIT_SET(GPP_DATA_OUT_REG(hddHigh),(1<<hddPowerBit));
MV_REG_BIT_RESET(GPP_DATA_OUT_EN_REG(hddHigh),(1<<hddPowerBit));
Where hddPowerBit = 16 unless my logic is flawed somewhere, this is 64K ??
Am I on the right track here?
I thought pin 16 was the green LED for the 1st HDD...
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing January 29, 2016 03:09PM |
Admin Registered: 13 years ago Posts: 18,570 |
It does not seem like the right one. 16 is indeed the LED according to the DTS.
Did you find hddPowerBit any where else? it could be an index to an array too..
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Did you find hddPowerBit any where else? it could be an index to an array too..
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing January 29, 2016 03:33PM |
Registered: 8 years ago Posts: 59 |
Couldn't see it anywhere else than Orion and Kirkwood board defs:
What's odd is that Orion boards have HDD0 and HDD1 defined all over the place, but it almost looks like Kirkwood shouldn't have two HDDs...
Powering up the 2nd HDD on stock u-boot with the memory poke egenrates a MV_SATA_CABLE_EVENT_CONNECT event.
tearing my hair out :)
~/src//trunk/sysapps/u-boot-3.6.0_STG326/board$ grep -R hddPowerBit * mv_feroceon/mv_orion/mv_main.c: MV_32 hddPowerBit = mvBoarGpioPinNumGet(BOARD_DEV_HDD0_POWER); mv_feroceon/mv_orion/mv_main.c: MV_REG_BIT_SET(GPP_DATA_OUT_REG(0),(1<<hddPowerBit)); mv_feroceon/mv_orion/mv_main.c: MV_REG_BIT_RESET(GPP_DATA_OUT_EN_REG(0),(1<<hddPowerBit)); mv_feroceon/mv_orion/mv_main.c: MV_REG_BIT_SET(GPP_DATA_OUT_REG(0),(1<<hddPowerBit)); mv_feroceon/mv_orion/mv_main.c: MV_REG_BIT_RESET(GPP_DATA_OUT_EN_REG(0),(1<<hddPowerBit)); mv_feroceon/mv_orion/mv_main.c: MV_32 hddPowerBit = mvBoarGpioPinNumGet(BOARD_DEV_HDD0_POWER); mv_feroceon/mv_orion/mv_main.c: MV_REG_BIT_SET(GPP_DATA_OUT_REG(0),(1<<hddPowerBit)); mv_feroceon/mv_orion/mv_main.c: MV_REG_BIT_RESET(GPP_DATA_OUT_EN_REG(0),(1<<hddPowerBit)); mv_feroceon/mv_kw/mv_main.c: MV_32 hddPowerBit; mv_feroceon/mv_kw/mv_main.c: hddPowerBit = mvBoarGpioPinNumGet(BOARD_GPP_HDD_POWER, 0); mv_feroceon/mv_kw/mv_main.c: if (hddPowerBit > 31) mv_feroceon/mv_kw/mv_main.c: hddPowerBit = hddPowerBit % 32; mv_feroceon/mv_kw/mv_main.c: MV_REG_BIT_SET(GPP_DATA_OUT_REG(hddHigh),(1<<hddPowerBit)); mv_feroceon/mv_kw/mv_main.c: MV_REG_BIT_RESET(GPP_DATA_OUT_EN_REG(hddHigh),(1<<hddPowerBit));
What's odd is that Orion boards have HDD0 and HDD1 defined all over the place, but it almost looks like Kirkwood shouldn't have two HDDs...
Powering up the 2nd HDD on stock u-boot with the memory poke egenrates a MV_SATA_CABLE_EVENT_CONNECT event.
tearing my hair out :)
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing January 29, 2016 04:41PM |
Admin Registered: 13 years ago Posts: 18,570 |
Micky,
We forgot something:
> So, to recap:
> - stock uboot needs "mw.l f1010104 c70e0ffd;ide
> reset" to see the second disk
> - 2015.10 doesn't see the disk, even with the same
> poke
We know the poke does not work in u-boot-2015.10-tld-1, but it could mean that the value need to change. Trace back your value "c70e0ffd". How did you come up with this number (by dumping the current content and then do a logical OR?).
I.e., you might want to dump the current content while in the new u-boot serial console and see if it is different.
Please post the serial console dump for f1010104.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 01/29/2016 04:43PM by bodhi.
We forgot something:
> So, to recap:
> - stock uboot needs "mw.l f1010104 c70e0ffd;ide
> reset" to see the second disk
> - 2015.10 doesn't see the disk, even with the same
> poke
We know the poke does not work in u-boot-2015.10-tld-1, but it could mean that the value need to change. Trace back your value "c70e0ffd". How did you come up with this number (by dumping the current content and then do a logical OR?).
I.e., you might want to dump the current content while in the new u-boot serial console and see if it is different.
Please post the serial console dump for f1010104.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 01/29/2016 04:43PM by bodhi.
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing January 30, 2016 04:18AM |
Registered: 8 years ago Posts: 59 |
oh it came straight from MadAdmin: http://www.madadmin.com/zyxel-nsa320s-es-debian-linux-4-resz/
I found it strange that the 2nd HDD required a poke to initialise, but since stock uboot doesn't seem to do it by itself... maybe the stock kernel takes care of that through some crazy workaround?
MadAdmin said he couldn't get hold of Zyxel's kernel sources, so this is quite puzzling.
It doesn't explain why the green led at pin 16 looks like it's being used to power up the 1st HDD either...
I found it strange that the 2nd HDD required a poke to initialise, but since stock uboot doesn't seem to do it by itself... maybe the stock kernel takes care of that through some crazy workaround?
MadAdmin said he couldn't get hold of Zyxel's kernel sources, so this is quite puzzling.
It doesn't explain why the green led at pin 16 looks like it's being used to power up the 1st HDD either...
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing January 30, 2016 04:44AM |
Registered: 8 years ago Posts: 59 |
Looking at MadAdmin's kernel patch here :
I note that:
it uses the sata0/sata1 and hdd1/hdd2 naming conventions so we need to look for sata1 or hdd2
He looks to GPIO33 for sata1 power:
and both USB and SATA1 have separate regulators defined:
In his world of stock u-boot and mainline Linux kernel + patch, both USB and sata1 require pokes to initialise correctly, so we may be onto something here.
But I have no clue what to do with that - what's that "&gpio1 1" to power SATA1/HDD2 business all about then? It's next to "&gpio1 2" which is the green led for HDD2
Everything else is on gpio0 rather than gpio1.
I note that:
it uses the sata0/sata1 and hdd1/hdd2 naming conventions so we need to look for sata1 or hdd2
He looks to GPIO33 for sata1 power:
pmx_pwr_sata1: pmx-pwr-sata1 {
+ marvell,pins = "mpp33";
+ marvell,function = "gpio";
+ };
and both USB and SATA1 have separate regulators defined:
regulators {
+ compatible = "simple-bus";
+ #address-cells = <1>;
+ #size-cells = <0>;
+ pinctrl-names = "default";
+ pinctrl-0 = <&pmx_usb_power &pmx_pwr_sata1>;
+
+ usb0_power: regulator@1 {
+ compatible = "regulator-fixed";
+ reg = <1>;
+ regulator-name = "USB Power";
+ regulator-min-microvolt = <5000000>;
+ regulator-max-microvolt = <5000000>;
+ regulator-always-on;
+ regulator-boot-on;
+ enable-active-high;
+ gpio = <&gpio0 21 GPIO_ACTIVE_HIGH>;
+ };
+
+ sata1_power: regulator@2 {
+ compatible = "regulator-fixed";
+ reg = <2>;
+ regulator-name = "SATA1 Power";
+ regulator-min-microvolt = <5000000>;
+ regulator-max-microvolt = <5000000>;
+ regulator-always-on;
+ regulator-boot-on;
+ enable-active-high;
+ gpio = <&gpio1 1 GPIO_ACTIVE_HIGH>;
+ };
+ };
In his world of stock u-boot and mainline Linux kernel + patch, both USB and sata1 require pokes to initialise correctly, so we may be onto something here.
But I have no clue what to do with that - what's that "&gpio1 1" to power SATA1/HDD2 business all about then? It's next to "&gpio1 2" which is the green led for HDD2
Everything else is on gpio0 rather than gpio1.
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing January 30, 2016 06:53AM |
Registered: 8 years ago Posts: 59 |
NSA3x0S> md f1010104 f1010104: cfde5fff 00000000 00000000 13224080 ._...........@". f1010114: 132e4fb0 00000000 00000000 00000000 .O.............. f1010124: 00000000 00000000 00000000 00000000 ................ f1010134: 00000000 00000000 00000000 00000002 ................ f1010144: fffffff9 00000000 00000000 00000000 ................ f1010154: 00000000 00000000 00000000 00000000 ................ f1010164: 00000000 00000000 00000000 00000000 ................ f1010174: 00000000 00000000 00000000 00000000 ................ f1010184: 00000000 00000000 00000000 00000000 ................ f1010194: 00000000 00000000 00000000 00000000 ................ f10101a4: 00000000 00000000 00000000 00000000 ................ f10101b4: 00000000 00000000 00000000 00000000 ................ f10101c4: 00000000 00000000 00000000 00000000 ................ f10101d4: 00000000 00000000 00000000 00000000 ................ f10101e4: 00000000 00000000 00000000 00000000 ................ f10101f4: 00000000 00000000 00000000 00000000 ................
&gpio1 1 is gpio pin 33, isn't it?
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing January 30, 2016 07:55AM |
Admin Registered: 13 years ago Posts: 18,570 |
Micky,
If you look at my kernel patch, it is the same as madadmin/chrlee. I incorporated chrlee's patch back in kernel 4.0.0-kirkwood-tld-1 (see the kernel and rootfs thread).
That's why I mentioned it here.
Yes, gpio1 1 is 33.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
If you look at my kernel patch, it is the same as madadmin/chrlee. I incorporated chrlee's patch back in kernel 4.0.0-kirkwood-tld-1 (see the kernel and rootfs thread).
Quote
Updated 16 April 2015:
Kernel 4.0.0-kirkwood-tld-1 package has been uploaded. The following features were added:
1. This FDT kernel now supports NSA320S, Asus M25, and Netgear Stora. They are still under test, so please post feeback if you try this kernel.
2. Added back the NSA3xx Hardware Monitoring module (missing in previous kernel version)
3. Add module lirc_rpi
4. Added various kernel configs that are new in 4.0 (e.g. device tree overlay), and also various requested configs from forum members.
....
Credits: Thanks to chrlee for the NSA320S patch, moonman at Arch site for noticing the missing NSA3xx Hwmon module, TEN for lirc_rpi suggestion, balbes150 for Asus-M25 DTS, and t00 for the Netgear Stora DTS.
That's why I mentioned it here.
Yes, gpio1 1 is 33.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing January 30, 2016 10:10AM |
Admin Registered: 13 years ago Posts: 18,570 |
Micky,
What it looks like in stock u-boot with the same peek command?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> NSA3x0S> md f1010104 > f1010104: cfde5fff 00000000 00000000 13224080
What it looks like in stock u-boot with the same peek command?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing January 30, 2016 12:25PM |
Registered: 8 years ago Posts: 59 |
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing January 30, 2016 03:43PM |
Admin Registered: 13 years ago Posts: 18,570 |
Micky,
I kind of expect that.
I'm almost certain that this is a voltage problem (issue of 12v vs 5V). Because the 2.5" HDD in the 2nd slot works fine with the new u-boot.
During power up, the 3.5" HDDs need 5V and 12V, while the 2.5" HDDs need only 5V.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 01/30/2016 03:45PM by bodhi.
I kind of expect that.
I'm almost certain that this is a voltage problem (issue of 12v vs 5V). Because the 2.5" HDD in the 2nd slot works fine with the new u-boot.
During power up, the 3.5" HDDs need 5V and 12V, while the 2.5" HDDs need only 5V.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 01/30/2016 03:45PM by bodhi.
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing January 30, 2016 03:49PM |
Registered: 8 years ago Posts: 59 |
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing January 30, 2016 04:45PM |
Admin Registered: 13 years ago Posts: 18,570 |
Micky Wicky Wrote:
-------------------------------------------------------
> I suspected as much... The next question is, how
> to tell the SoC to use the higher voltage? I know
> there was a similar issue with the usb, but that
> actually works fine out of the bus with the new
> uboot.
I think it is slightly different. USB needs 5V. The new u-boot makes sure that the GPIO for USB power is trigger, and that would be enough.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> I suspected as much... The next question is, how
> to tell the SoC to use the higher voltage? I know
> there was a similar issue with the usb, but that
> actually works fine out of the bus with the new
> uboot.
I think it is slightly different. USB needs 5V. The new u-boot makes sure that the GPIO for USB power is trigger, and that would be enough.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing February 22, 2016 12:47AM |
Registered: 8 years ago Posts: 7 |
bodhi Wrote:
-------------------------------------------------------
> Hi Steve,
>
> Join in the ongoing investigation in thisthread:
> http://forum.doozan.com/read.php?3,23331
>
> To confirm this is a 12V/5V issue, use a 2.5" HDD
> on the 2nd slot. And boot up u-boot with serial
> console. Interrupt serial console, and run
>
Ok, so here are my results (using net console):
HDD0: 3,5", HDD1: none
HDD0: none, HDD1: 3,5"
HDD0: 3,5", HDD1: 2,5"
HDD0: 2,5", HDD1: 3,5"
In all other cases 3,5" drive is not working in HDD1 bay, and 2,5" is working in every bay.
Interesting fact; you can freely use anything after ide res, it is treated as "reset" anyway:
And of course:
Edited 3 time(s). Last edit at 02/22/2016 02:04AM by Steve1987.
-------------------------------------------------------
> Hi Steve,
>
> Join in the ongoing investigation in thisthread:
> http://forum.doozan.com/read.php?3,23331
>
> To confirm this is a 12V/5V issue, use a 2.5" HDD
> on the 2nd slot. And boot up u-boot with serial
> console. Interrupt serial console, and run
>
> ide reset >> See if the 2.5" HDD is initialized OK.
Ok, so here are my results (using net console):
HDD0: 3,5", HDD1: none
NSA3x0S> ide reset
ide reset
Reset IDE: Bus 0: OK Bus 1: not available
Device 0: Model: TOSHIBA DT01ABA300 Firm: MZ6OABB0 Ser#: 35JLXGTGS
Type: Hard Disk
Supports 48-bit addressing
Capacity: 2861588.4 MB = 2794.5 GB (5860533168 x 512)
HDD0: none, HDD1: 3,5"
NSA3x0S> ide reset ide reset Reset IDE: Bus 0: not available Bus 1: ................not available (waited for 40 seconds, then pulled out the drive)
HDD0: 3,5", HDD1: 2,5"
NSA3x0S> ide reset
ide reset
Reset IDE: Bus 0: OK Bus 1: OK
Device 0: Model: TOSHIBA DT01ABA300 Firm: MZ6OABB0 Ser#: 35JLXGTGS
Type: Hard Disk
Supports 48-bit addressing
Capacity: 2861588.4 MB = 2794.5 GB (5860533168 x 512)
Device 1: Model: WDC WD5000LPVX-60V0TT0 Firm: 01.01A01 Ser#: WD-WX71A4429506
Type: Hard Disk
Supports 48-bit addressing
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
HDD0: 2,5", HDD1: 3,5"
NSA3x0S> ide resev
ide resev
Reset IDE: Bus 0: OK Bus 1: ................................................not available
Device 0: Model: WDC WD5000LPVX-60V0TT0 Firm: 01.01A01 Ser#: WD-WX71A4429506
Type: Hard Disk
Supports 48-bit addressing
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
In all other cases 3,5" drive is not working in HDD1 bay, and 2,5" is working in every bay.
Interesting fact; you can freely use anything after ide res, it is treated as "reset" anyway:
NSA3x0S> ide res_i_want_it_to_work_badly
ide res_i_want_it_to_work_badly
Reset IDE: Bus 0: OK Bus 1: not available
Device 0: Model: WDC WD5000LPVX-60V0TT0 Firm: 01.01A01 Ser#: WD-WX71A4429506
Type: Hard Disk
Supports 48-bit addressing
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
And of course:
U-Boot 2015.10-tld-1 (Nov 06 2015 - 16:16:11 -0800) ZyXEL NSA310S/320S 1/2-Bay Power Media Server gcc (Debian 4.9.2-10) 4.9.2 GNU ld (GNU Binutils for Debian) 2.25
Edited 3 time(s). Last edit at 02/22/2016 02:04AM by Steve1987.
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing February 22, 2016 04:13AM |
Admin Registered: 13 years ago Posts: 18,570 |
Micky Wicky,
Try adding GPIO 20 or 22 or both in addition to the GPIO 33 in the mask.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 02/22/2016 04:50AM by bodhi.
Try adding GPIO 20 or 22 or both in addition to the GPIO 33 in the mask.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 02/22/2016 04:50AM by bodhi.
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing February 22, 2016 05:02AM |
Registered: 8 years ago Posts: 59 |
So there's two things to consider here:
1. MadAdmin's kernel patch looks like this:
2. PIN 16
I'm game for trying anything at this point.
What do you suggest I look at / poke?
Just for kicks, I decided to switch it to ON at boot like two other gpio LEDs, nothing has exploded on me after a reboot... can't check whether the LED is ON as I'm not physically near the NAS at the moment.
1. MadAdmin's kernel patch looks like this:
+
+ sata1_power: regulator@2 {
+ compatible = "regulator-fixed";
+ reg = <2>;
+ regulator-name = "SATA1 Power";
+ regulator-min-microvolt = <5000000>;
+ regulator-max-microvolt = <5000000>;
+ regulator-always-on;
+ regulator-boot-on;
+ enable-active-high;
+ gpio = <&gpio1 1 GPIO_ACTIVE_HIGH>;
If we have a voltage issue and the regulator has min-microvolt and max-microvolt as 5000000 (5V) for both USB (where it is correct) and sata1... is it that we need to change that to 12000000 somewhere???
2. PIN 16
I'm game for trying anything at this point.
What do you suggest I look at / poke?
Just for kicks, I decided to switch it to ON at boot like two other gpio LEDs, nothing has exploded on me after a reboot... can't check whether the LED is ON as I'm not physically near the NAS at the moment.
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing February 22, 2016 12:01PM |
Registered: 8 years ago Posts: 7 |
Would it help if I could provide you with complete source code for Zyxel 4.70? I got it today, but I am having a hard time reading it.
It is open source, so I guess there is no exposure when giving it to others. Is uploading, I'll give you a link when it is done.
Ok here is the link:
https://drive.google.com/file/d/0B9LKKOOjI1e6VFE4dmFKOTI4UVE/view?usp=sharing
And here is what I am currently looking at:
/NSA320S_470AANV0C0/trunk/linux-2.6.31.8/arch/arm/plat-feroceon/mv_drivers_lsp/mv_sata/mvLinuxIalHt.c
According to documentation, to run it we should be able to:
ftp://ftp.aslab.com/pub/windows/mvSata_Windows_3_6_3/Docs/SW%20Driver%20User%20Manual%20for%20Marvell%20Serial%20ATA%20Host%20Adapters.pdf
but I am not really sure if this is a driver that should be loaded. Back to reading...
According to /NSA320S_470AANV0C0/trunk/linux-2.6.31.8/LspReadme.txt, this driver should be compiled for linux and visible under /proc/scsi and it is among other things used to prevent overloading of power supply when both drives would spin up.
Edited 2 time(s). Last edit at 02/22/2016 01:13PM by Steve1987.
It is open source, so I guess there is no exposure when giving it to others. Is uploading, I'll give you a link when it is done.
Ok here is the link:
https://drive.google.com/file/d/0B9LKKOOjI1e6VFE4dmFKOTI4UVE/view?usp=sharing
And here is what I am currently looking at:
/NSA320S_470AANV0C0/trunk/linux-2.6.31.8/arch/arm/plat-feroceon/mv_drivers_lsp/mv_sata/mvLinuxIalHt.c
else if (!strncmp (buffer, "sata_phy_powerup", strlen ("sata_phy_powerup")))
{
int sata_phy;
i = sscanf (buffer + strlen ("sata_phy_powerup"), "%d\n", &sata_phy);
if (i == 1)
{ /* Three matched inputs */
if (mvSataChannelPhyPowerOn (pMvSataAdapter, sata_phy) == MV_TRUE)
According to documentation, to run it we should be able to:
ftp://ftp.aslab.com/pub/windows/mvSata_Windows_3_6_3/Docs/SW%20Driver%20User%20Manual%20for%20Marvell%20Serial%20ATA%20Host%20Adapters.pdf
Quote
Documentation
• Shut down a SATA physical interface: Execute echo "sata_phy_shutdown x" > /proc/scsi/mvSata/0 to shut down a SATA PHY x.
• Power up a SATA physical interface: Execute echo "sata_phy_powerup x" > /proc/scsi/mvSata/0 to power up a SATA PHY x.
but I am not really sure if this is a driver that should be loaded. Back to reading...
According to /NSA320S_470AANV0C0/trunk/linux-2.6.31.8/LspReadme.txt, this driver should be compiled for linux and visible under /proc/scsi and it is among other things used to prevent overloading of power supply when both drives would spin up.
Edited 2 time(s). Last edit at 02/22/2016 01:13PM by Steve1987.
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing February 22, 2016 02:26PM |
Registered: 8 years ago Posts: 59 |
I've got the sources, but I was focusing on Marvell's fork of u-boot (stock u-boot) rather than the Linux kernel.
Simple reason is, the stock u-boot initialises the 2nd SATA port before loading the Linux kernel.
Ergo, the key must be in there, but as you can see in this thread, it's not as simple as it could be.
(happy to be corrected... as long as I get the ^&%^$&! thing working :))
Activating PIN 16 just lights up the HDD1 green LED as expected.
Simple reason is, the stock u-boot initialises the 2nd SATA port before loading the Linux kernel.
Ergo, the key must be in there, but as you can see in this thread, it's not as simple as it could be.
(happy to be corrected... as long as I get the ^&%^$&! thing working :))
Activating PIN 16 just lights up the HDD1 green LED as expected.
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing February 22, 2016 03:22PM |
Registered: 8 years ago Posts: 7 |
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing February 22, 2016 06:41PM |
Registered: 8 years ago Posts: 59 |
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing February 22, 2016 11:48PM |
Admin Registered: 13 years ago Posts: 18,570 |
Micky Wicky,
> Activating PIN 16 just lights up the HDD1 green
> LED as expected.
GPIO 20 or 22 ? They are safe to try.
I know we are not doing this methodically. There is something called the mpp configuration (a register controls an MPP group). But I'm short on time to be able to read the stock GPL code.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Activating PIN 16 just lights up the HDD1 green
> LED as expected.
GPIO 20 or 22 ? They are safe to try.
I know we are not doing this methodically. There is something called the mpp configuration (a register controls an MPP group). But I'm short on time to be able to read the stock GPL code.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing February 23, 2016 04:34AM |
Admin Registered: 13 years ago Posts: 18,570 |
All,
Try this version with kwboot:
See if "ide reset" behaves differently.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Try this version with kwboot:
./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2015.10-tld-2.nsa310s.mtd0.kwb -p
See if "ide reset" behaves differently.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing February 23, 2016 12:43PM |
Registered: 8 years ago Posts: 7 |
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing February 23, 2016 12:48PM |
Admin Registered: 13 years ago Posts: 18,570 |
Steve1987,
> I had to compile kwboot for my OS X from sources
> though.
> I got sources from your GitHub, what should I do
> apart from gcc kwboot.c -o kwboot, should I set
> any flags?
You don't need to compile it. davygravy has a 64-bit version in his thread about UART:
http://forum.doozan.com/read.php?3,7852,7852
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I had to compile kwboot for my OS X from sources
> though.
> I got sources from your GitHub, what should I do
> apart from gcc kwboot.c -o kwboot, should I set
> any flags?
You don't need to compile it. davygravy has a 64-bit version in his thread about UART:
http://forum.doozan.com/read.php?3,7852,7852
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing February 23, 2016 12:49PM |
Registered: 8 years ago Posts: 59 |
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing February 23, 2016 12:51PM |
Registered: 8 years ago Posts: 59 |
No immediate change, what is different about this build?
NSA3x0S> ide reset
Reset IDE: Bus 0: OK Bus 1: not available
Device 0: Model: WDC WD20EZRX-00D8PB0 Firm: 80.00A80 Ser#: WD-WCC4MHECYZUX
Type: Hard Disk
Supports 48-bit addressing
Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512)
NSA3x0S> ide info
IDE device 0: Model: WDC WD20EZRX-00D8PB0 Firm: 80.00A80 Ser#: WD-WCC4MHECYZUX
Type: Hard Disk
Supports 48-bit addressing
Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512)
NSA3x0S>
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing February 23, 2016 12:54PM |
Registered: 8 years ago Posts: 7 |
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing February 23, 2016 01:05PM |
Registered: 8 years ago Posts: 59 |
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing February 23, 2016 01:11PM |
Registered: 8 years ago Posts: 59 |
U-Boot 2015.10tld-2 (Feb 23 2016 - 02:17:09 -0800)
ZyXEL NSA310S/320S 1/2-Bay Power Media Server
SoC: Kirkwood 88F6702_A1
DRAM: 256 MiB (ECC not enabled)
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot: 0
NSA3x0S> mw.l f1010104 c70e0ffd; ide reset
Reset IDE: Bus 0: OK Bus 1: .......OK
Device 0: Model: WDC WD20EZRX-00D8PB0 Firm: 80.00A80 Ser#: WD-WCC4MHECYZUX
Type: Hard Disk
Supports 48-bit addressing
Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512)
Device 1: Model: WDC WD20EZRX-00D8PB0 Firm: 80.00A80 Ser#: WD-WCC4MCY6Y4AH
Type: Hard Disk
Supports 48-bit addressing
Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512)
NSA3x0S> ide info
IDE device 0: Model: WDC WD20EZRX-00D8PB0 Firm: 80.00A80 Ser#: WD-WCC4MHECYZUX
Type: Hard Disk
Supports 48-bit addressing
Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512)
IDE device 1: Model: WDC WD20EZRX-00D8PB0 Firm: 80.00A80 Ser#: WD-WCC4MCY6Y4AH
Type: Hard Disk
Supports 48-bit addressing
Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512)
NSA3x0S>
Nice... :)
Trying to boot from USB returns "EHCI timed out on TD - token=0x80008d80" repeatedly, I'll try a clean boot with that poke...
|
Re: Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing February 23, 2016 01:21PM |
Registered: 8 years ago Posts: 59 |
No luck with the USB error. But it seems bodhi has done it again and cracked the big problem!
I'm doing this:
The only difference with the previous (working with tld-1) boot macro is the addition of the poke.
As it is it can boot neither Linux nor NetBSD:
I'm doing this:
usb start; mw.l f1010104 c70e0ffd; ide reset; setenv bootargs rootdev=sd0a; setenv netbsd_en yes; fatload usb 0 0x800000 /netbsd.ub; bootm 0x800000
The only difference with the previous (working with tld-1) boot macro is the addition of the poke.
As it is it can boot neither Linux nor NetBSD:
NSA3x0S> boot
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices...
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found
Reset IDE: Bus 0: OK Bus 1: .......OK
Device 0: Model: WDC WD20EZRX-00D8PB0 Firm: 80.00A80 Ser#: WD-WCC4MHECYZUX
Type: Hard Disk
Supports 48-bit addressing
Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512)
Device 1: Model: WDC WD20EZRX-00D8PB0 Firm: 80.00A80 Ser#: WD-WCC4MCY6Y4AH
Type: Hard Disk
Supports 48-bit addressing
Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512)
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
** Can't read partition table on 0:0 **
** Invalid partition 1 **
Wrong Image Format for bootm command
Error occured, error code = 112
ERROR: can't get kernel image!
