New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ramips: add support for Kimax U-25AWF 2.5" SATA WIFI HDD Enclosure #1402

Closed
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
5 participants
@danielkucera
Contributor

danielkucera commented Oct 6, 2017

Kimax U-25AWF is is a 2,5" HDD Enclosure with Wi-Fi/Eth conection
and battery, based on MediaTek MT7620N. Patch rewritten from:
https://forum.openwrt.org/viewtopic.php?pid=305643

Specification:

  • MT7620N CPU
  • 64 MB of RAM
  • 16 MB of FLASH
  • 802.11bgn WiFi
  • 1x 10/100 Mbps Ethernet
  • USB 2.0 Host
  • UART for serial console

more on: https://wikidevi.com/wiki/Kimax_U25AWF

Flash instruction:

  1. Download lede-ramips-mt7620-u25awf-squashfs-sysupgrade.bin
  2. Open webinterface a upgrade
  3. After boot connect via ethernet to ip 192.168.1.1

Tested on:

  • Blueendless U-35WF which is the same hardware but without battery
    and with 3,5" drive enclosure

Signed-off-by: Daniel Kucera daniel.kucera@gmail.com

@mkresin

This comment has been minimized.

Show comment
Hide comment
@mkresin

mkresin Oct 6, 2017

Contributor

I only had a brief look at the PR, but it still has some of the issues I already outlined in #826.

  • the gpios parameter in the DTS still contains invalid values
  • the GPIO_ACTIVE_* macros are not used
  • the key code macros are still not used

And you managed to introduce a new issue by removing the ";;" in the vocore-* section if 01_leds.

Please either close this PR, fix the issues by your self or find someone who is willing to do so.

Contributor

mkresin commented Oct 6, 2017

I only had a brief look at the PR, but it still has some of the issues I already outlined in #826.

  • the gpios parameter in the DTS still contains invalid values
  • the GPIO_ACTIVE_* macros are not used
  • the key code macros are still not used

And you managed to introduce a new issue by removing the ";;" in the vocore-* section if 01_leds.

Please either close this PR, fix the issues by your self or find someone who is willing to do so.

@danielkucera

This comment has been minimized.

Show comment
Hide comment
@danielkucera

danielkucera Oct 6, 2017

Contributor

@mkresin I'm trying... now it compiles ok. What are "key code macros" plesae?

Contributor

danielkucera commented Oct 6, 2017

@mkresin I'm trying... now it compiles ok. What are "key code macros" plesae?

@mkresin

This comment has been minimized.

Show comment
Hide comment
@mkresin

mkresin Oct 6, 2017

Contributor

What are "key code macros" plesae?

dt-bindings/input/input.h

Please reference nodes defined in the mt7620n.dtsi instead of redefine them:

&gpio2 {
	status = "okay";
};

vs.

palmbus@10000000 {
	gpio2: gpio@660 {
		status = "okay";
	};
};

Please have a look at the other mt7620n based dts files (like ZBT-CPE102.dts) and stick to the way it is done there.

Please be prepared for more change requests. Might be that I find more if I have a closer look and do not get distracted by the obvious stuff all the time :-).

Contributor

mkresin commented Oct 6, 2017

What are "key code macros" plesae?

dt-bindings/input/input.h

Please reference nodes defined in the mt7620n.dtsi instead of redefine them:

&gpio2 {
	status = "okay";
};

vs.

palmbus@10000000 {
	gpio2: gpio@660 {
		status = "okay";
	};
};

Please have a look at the other mt7620n based dts files (like ZBT-CPE102.dts) and stick to the way it is done there.

Please be prepared for more change requests. Might be that I find more if I have a closer look and do not get distracted by the obvious stuff all the time :-).

@f00b4r0

You're on the right track but there are still a few issues that you need to address, see my comments below. Thanks.

Show outdated Hide outdated target/linux/ramips/dts/U25AWF.dts Outdated
Show outdated Hide outdated target/linux/ramips/dts/U25AWF.dts Outdated
Show outdated Hide outdated target/linux/ramips/dts/U25AWF.dts Outdated
Show outdated Hide outdated target/linux/ramips/dts/U25AWF.dts Outdated
};
&wmac {
ralink,mtd-eeprom = <&factory 0>;

This comment has been minimized.

@f00b4r0

f00b4r0 Oct 6, 2017

Contributor

Have you confirmed that the device gets the correct MAC address for the wireless interface?

@f00b4r0

f00b4r0 Oct 6, 2017

Contributor

Have you confirmed that the device gets the correct MAC address for the wireless interface?

Show outdated Hide outdated target/linux/ramips/image/mt7620.mk Outdated
Show outdated Hide outdated target/linux/ramips/image/mt7620.mk Outdated
Show outdated Hide outdated target/linux/ramips/dts/U25AWF.dts Outdated
Show outdated Hide outdated target/linux/ramips/dts/U25AWF.dts Outdated
ramips: add support for Kimax U-25AWF 2.5" SATA WIFI HDD Enclosure
Kimax U-25AWF is is a 2,5" HDD Enclosure with Wi-Fi/Eth conection
and battery, based on MediaTek MT7620N. Patch rewritten from:
https://forum.openwrt.org/viewtopic.php?pid=305643

Specification:

- MT7620N CPU
- 64 MB of RAM
- 16 MB of FLASH
- 802.11bgn WiFi
- 1x 10/100 Mbps Ethernet
- USB 2.0 Host
- UART for serial console

more on: https://wikidevi.com/wiki/Kimax_U25AWF

Flash instruction:
1. Download lede-ramips-mt7620-u25awf-squashfs-sysupgrade.bin
2. Open webinterface a upgrade
3. After boot connect via ethernet to ip 192.168.1.1

Tested on:

- Blueendless U-35WF which is the same hardware but without battery
and with 3,5" drive enclosure

Signed-off-by: Daniel Kucera <daniel.kucera@gmail.com>
@f00b4r0

Looks better, thank you. Please confirm that the wireless MAC advertised in LEDE is correct (matches the value written on the enclosure).

@Mynzer

This comment has been minimized.

Show comment
Hide comment
@Mynzer

Mynzer Oct 7, 2017

@f00b4r0 Hi, I can confirm that the device boot with the changes you ask to @danielkucera and I can confirm, that the mac address in lede is the same mac address reported in my boot loader (I have breed boot loader in my device), the enclosure doesn't have any mac address written on it, I add a boot log from my device with @f00b4r0 changes. I'll add a new boot log when @danielkucera do the new changes requested by @mkresin
dmesg.txt

Mynzer commented Oct 7, 2017

@f00b4r0 Hi, I can confirm that the device boot with the changes you ask to @danielkucera and I can confirm, that the mac address in lede is the same mac address reported in my boot loader (I have breed boot loader in my device), the enclosure doesn't have any mac address written on it, I add a boot log from my device with @f00b4r0 changes. I'll add a new boot log when @danielkucera do the new changes requested by @mkresin
dmesg.txt

@danielkucera

This comment has been minimized.

Show comment
Hide comment
@danielkucera

danielkucera Oct 7, 2017

Contributor

@Mynzer please run git log in source directory and paste here the hash of latest commit to make sure you are on the latest version.

Contributor

danielkucera commented Oct 7, 2017

@Mynzer please run git log in source directory and paste here the hash of latest commit to make sure you are on the latest version.

@Mynzer

This comment has been minimized.

Show comment
Hide comment
@Mynzer

Mynzer Oct 7, 2017

Here is the hash output from git log

5b975153fe6502db7a4cabe7d3e6b264d55c2c27

Just tell me if you need to pull again the new changes

Mynzer commented Oct 7, 2017

Here is the hash output from git log

5b975153fe6502db7a4cabe7d3e6b264d55c2c27

Just tell me if you need to pull again the new changes

@danielkucera

This comment has been minimized.

Show comment
Hide comment
@danielkucera

danielkucera Oct 7, 2017

Contributor

@Mynzer please do git pull and make sure you are on 59fd9d11e49545fce393ea6cb28976d4d3dec3e6, then make and test again please.

Contributor

danielkucera commented Oct 7, 2017

@Mynzer please do git pull and make sure you are on 59fd9d11e49545fce393ea6cb28976d4d3dec3e6, then make and test again please.

@Mynzer

This comment has been minimized.

Show comment
Hide comment
@Mynzer

Mynzer Oct 7, 2017

Ok, now git log show me that I'm in commit 59fd9d11e49545fce393ea6cb28976d4d3dec3e6
here is the new boot log

dmesg.txt

Mynzer commented Oct 7, 2017

Ok, now git log show me that I'm in commit 59fd9d11e49545fce393ea6cb28976d4d3dec3e6
here is the new boot log

dmesg.txt

@danielkucera

This comment has been minimized.

Show comment
Hide comment
@danielkucera

danielkucera Oct 7, 2017

Contributor

@Mynzer can you please confirm that all drivers are working correctly (LEDs, reset button, USB, ethernet, wifi)?

Contributor

danielkucera commented Oct 7, 2017

@Mynzer can you please confirm that all drivers are working correctly (LEDs, reset button, USB, ethernet, wifi)?

@Mynzer

This comment has been minimized.

Show comment
Hide comment
@Mynzer

Mynzer Oct 7, 2017

Almost all work fine, Wifi and Ethernet leds work fine, for usb and internal enclosure hard drive, I have installed samba and create a share in LEDE, one form the internal hard drive of the enclosure and one for the usb memory on the usb port, and works good getting access and writing for both shares from my laptop, the only thing that do not work well is the reset button, it simply not reset to factory defaults.

I don't know if it helps, but for breed boot loader I'm using breed-mt7620-reset13.bin

Mynzer commented Oct 7, 2017

Almost all work fine, Wifi and Ethernet leds work fine, for usb and internal enclosure hard drive, I have installed samba and create a share in LEDE, one form the internal hard drive of the enclosure and one for the usb memory on the usb port, and works good getting access and writing for both shares from my laptop, the only thing that do not work well is the reset button, it simply not reset to factory defaults.

I don't know if it helps, but for breed boot loader I'm using breed-mt7620-reset13.bin

@mkresin

mkresin approved these changes Oct 8, 2017

@mkresin

This comment has been minimized.

Show comment
Hide comment
@mkresin

mkresin Oct 8, 2017

Contributor

the only thing that do not work well is the reset button, it simply not reset to factory defaults.

You need to keep the reset button pressed for > 5sec to start a factory reset. If you press the button for < 5 sec a reboot is done.

If the button can not distinguish between long and short press, the polarity (HIGH vs. LOW) is usually wrong.

The easiest way to test if the button works at all, is to (short) press the button during boot at the time the LED blinks really fast. The device should switch to failsafe. The diag LED (here wlan) should blink insane fast and ssh connections to 192.168.1.1 are accepted.

Contributor

mkresin commented Oct 8, 2017

the only thing that do not work well is the reset button, it simply not reset to factory defaults.

You need to keep the reset button pressed for > 5sec to start a factory reset. If you press the button for < 5 sec a reboot is done.

If the button can not distinguish between long and short press, the polarity (HIGH vs. LOW) is usually wrong.

The easiest way to test if the button works at all, is to (short) press the button during boot at the time the LED blinks really fast. The device should switch to failsafe. The diag LED (here wlan) should blink insane fast and ssh connections to 192.168.1.1 are accepted.

@danielkucera

This comment has been minimized.

Show comment
Hide comment
@danielkucera

danielkucera Oct 8, 2017

Contributor

@Mynzer if you can enter breed command mode, please test the button using btntst command
btntst

Contributor

danielkucera commented Oct 8, 2017

@Mynzer if you can enter breed command mode, please test the button using btntst command
btntst

@Mynzer

This comment has been minimized.

Show comment
Hide comment
@Mynzer

Mynzer Oct 8, 2017

Hi again, @mkresin I've tried the steps that you recommend for testing the reset button, but unfortunately I could not put in failsafe the device (pressing the reset button on boot time), once that the device fully boot in LEDE, I've tried pressing the reset button of 3 seconds to make it reboot, and I've tried pressing for 6 seconds for factory reset but for now, both steps not work in the UA25AWF device.
@mkresin Using all this steps, effectively put my other device (a Xiaomi Mi Wifi Router) on fail safe (press reset on boot), reboots it (press reset for 3 seconds), an return to factory defaults (press reset for 6 seconds)

@danielkucera Here is the output from btntst from breed
breed-btntst
When i press reset button, change to 0, when i release it, change to 1

`

Mynzer commented Oct 8, 2017

Hi again, @mkresin I've tried the steps that you recommend for testing the reset button, but unfortunately I could not put in failsafe the device (pressing the reset button on boot time), once that the device fully boot in LEDE, I've tried pressing the reset button of 3 seconds to make it reboot, and I've tried pressing for 6 seconds for factory reset but for now, both steps not work in the UA25AWF device.
@mkresin Using all this steps, effectively put my other device (a Xiaomi Mi Wifi Router) on fail safe (press reset on boot), reboots it (press reset for 3 seconds), an return to factory defaults (press reset for 6 seconds)

@danielkucera Here is the output from btntst from breed
breed-btntst
When i press reset button, change to 0, when i release it, change to 1

`

@mkresin

This comment has been minimized.

Show comment
Hide comment
@mkresin

mkresin Oct 9, 2017

Contributor

Seem to me the reset button gpio is wrong in the DTS.

@Mynzer would you please build an image from my staging tree and test again!

Contributor

mkresin commented Oct 9, 2017

Seem to me the reset button gpio is wrong in the DTS.

@Mynzer would you please build an image from my staging tree and test again!

@mkresin

This comment has been minimized.

Show comment
Hide comment
@mkresin

mkresin Oct 9, 2017

Contributor

I have more one more question. Does the Kimax U-25AWF have more than one network port? There is currently a lan + wan port config applied by default. If the board has only a single lan port, we can make it way simpler.

Maybe better to check this first, before another round of testing is required.

Contributor

mkresin commented Oct 9, 2017

I have more one more question. Does the Kimax U-25AWF have more than one network port? There is currently a lan + wan port config applied by default. If the board has only a single lan port, we can make it way simpler.

Maybe better to check this first, before another round of testing is required.

@Mynzer

This comment has been minimized.

Show comment
Hide comment
@Mynzer

Mynzer Oct 9, 2017

@mkresin That's right, the Kimax U-25AWF only has a single lan port.

Mynzer commented Oct 9, 2017

@mkresin That's right, the Kimax U-25AWF only has a single lan port.

@danielkucera

This comment has been minimized.

Show comment
Hide comment
@danielkucera

danielkucera Oct 9, 2017

Contributor

@Mynzer for testing mkresins code you can do following in our working folder:

git checkout master
git remote add mkresin https://git.lede-project.org/lede/mkresin/staging.git
git pull mkresin master
make

you don't need to recompile the whole project again.

Contributor

danielkucera commented Oct 9, 2017

@Mynzer for testing mkresins code you can do following in our working folder:

git checkout master
git remote add mkresin https://git.lede-project.org/lede/mkresin/staging.git
git pull mkresin master
make

you don't need to recompile the whole project again.

@mkresin

This comment has been minimized.

Show comment
Hide comment
@mkresin

mkresin Oct 9, 2017

Contributor

@Mynzer please pull my staging tree now.

@danielkucera fine with with my changes?

Contributor

mkresin commented Oct 9, 2017

@Mynzer please pull my staging tree now.

@danielkucera fine with with my changes?

@danielkucera

This comment has been minimized.

Show comment
Hide comment
@danielkucera

danielkucera Oct 9, 2017

Contributor

@mkresin yes, without objections.

Contributor

danielkucera commented Oct 9, 2017

@mkresin yes, without objections.

@Mynzer

This comment has been minimized.

Show comment
Hide comment
@Mynzer

Mynzer Oct 9, 2017

@danielkucera thanks for the clear instructions, that save a lot of time, and I successfully pull from mkresin staging tree

@mkresin from commit 72b98f2749560eac49d20576f95bdf6ad12d5c78 now the device could enter in fail safe pressing the reset button on boot, and once the device fully boot in LEDE, now it can reset to factory defaults when pressing the reset button for more than 5 seconds

v_20171009_102517_gif

Here is the boot log from this commit

dmesg.txt

Mynzer commented Oct 9, 2017

@danielkucera thanks for the clear instructions, that save a lot of time, and I successfully pull from mkresin staging tree

@mkresin from commit 72b98f2749560eac49d20576f95bdf6ad12d5c78 now the device could enter in fail safe pressing the reset button on boot, and once the device fully boot in LEDE, now it can reset to factory defaults when pressing the reset button for more than 5 seconds

v_20171009_102517_gif

Here is the boot log from this commit

dmesg.txt

@f00b4r0

This comment has been minimized.

Show comment
Hide comment
@f00b4r0

f00b4r0 Oct 9, 2017

Contributor

Took a quick look at the original firmware bootlog here and I notice this:

[    0.860000] 0x000000050000-0x000000ff0000 : "firmware"
[    1.470000] 0x000000ff0000-0x000001000000 : "hui-ai"

I don't know if that's relevant but I am concerned that by making the firmware partition in LEDE extend over that hui-ai one in the original firmware, you might be making it impossible to revert to stock firmware.

It also appears from that post and from your dmesg that there are several variants of that device and that the Blueendless and Kimax versions aren't exactly the same: @danielkucera mentions MT7620N, in line with the bootlog linked above which has DDR1 RAM, while @Mynzer dmesg output shows an MT7620A with DDR2 RAM. The commit message might want to reflect that.

I wonder if that could also explain the discrepancy with the reset button. It might be a good idea if @danielkucera could confirm the last change works for him and provide dmesg output.

Contributor

f00b4r0 commented Oct 9, 2017

Took a quick look at the original firmware bootlog here and I notice this:

[    0.860000] 0x000000050000-0x000000ff0000 : "firmware"
[    1.470000] 0x000000ff0000-0x000001000000 : "hui-ai"

I don't know if that's relevant but I am concerned that by making the firmware partition in LEDE extend over that hui-ai one in the original firmware, you might be making it impossible to revert to stock firmware.

It also appears from that post and from your dmesg that there are several variants of that device and that the Blueendless and Kimax versions aren't exactly the same: @danielkucera mentions MT7620N, in line with the bootlog linked above which has DDR1 RAM, while @Mynzer dmesg output shows an MT7620A with DDR2 RAM. The commit message might want to reflect that.

I wonder if that could also explain the discrepancy with the reset button. It might be a good idea if @danielkucera could confirm the last change works for him and provide dmesg output.

@danielkucera

This comment has been minimized.

Show comment
Hide comment
@danielkucera

danielkucera Oct 9, 2017

Contributor

@f00b4r0 my device is U-35WF but the original patch worked for me except the reset button - it didn't work as far as I remember.

Contributor

danielkucera commented Oct 9, 2017

@f00b4r0 my device is U-35WF but the original patch worked for me except the reset button - it didn't work as far as I remember.

@f00b4r0

This comment has been minimized.

Show comment
Hide comment
@f00b4r0

f00b4r0 Oct 9, 2017

Contributor

@danielkucera that btntst excerpt you posted, is it from your device? Because if it is, it shows GPIO 12. @Mynzer shows GPIO 13.
Hence me wondering if you are trying to reconcile two different versions of that hardware. It's possible they're clones implemented differently, given their "origins".

Contributor

f00b4r0 commented Oct 9, 2017

@danielkucera that btntst excerpt you posted, is it from your device? Because if it is, it shows GPIO 12. @Mynzer shows GPIO 13.
Hence me wondering if you are trying to reconcile two different versions of that hardware. It's possible they're clones implemented differently, given their "origins".

@danielkucera

This comment has been minimized.

Show comment
Hide comment
@danielkucera

danielkucera Oct 9, 2017

Contributor

@f00b4r0 no, it's not from mine. I found the picture on internet.

Contributor

danielkucera commented Oct 9, 2017

@f00b4r0 no, it's not from mine. I found the picture on internet.

@Mynzer

This comment has been minimized.

Show comment
Hide comment
@Mynzer

Mynzer Oct 9, 2017

@f00b4r0 Let me check if i could found the stock firmware from this device and check if i could go back to stock. My device It's marked on front Kimax, in the back Blueenndless and bottom BS-25AWF

v_20171009_135309_segment_0_gif

v_20171009_140625_gif

Maybe the difference is the revision of the board, in my device it's printed on board
U25AWF-7620A-1153-V2.0

Mynzer commented Oct 9, 2017

@f00b4r0 Let me check if i could found the stock firmware from this device and check if i could go back to stock. My device It's marked on front Kimax, in the back Blueenndless and bottom BS-25AWF

v_20171009_135309_segment_0_gif

v_20171009_140625_gif

Maybe the difference is the revision of the board, in my device it's printed on board
U25AWF-7620A-1153-V2.0

@Mynzer

This comment has been minimized.

Show comment
Hide comment
@Mynzer

Mynzer Oct 10, 2017

@f00b4r0 I could go back to stock using firmware from here using the luci web interface using Kimax-H1 firmware
https://www.dropbox.com/sh/lmiogomcxqnaghv/AABORq743r3X7hEV70978Suua?dl=0
All seems to work well on stock firmware, and I could go back to LEDE from stock using the image generated by @mkresin build environment.

Mynzer commented Oct 10, 2017

@f00b4r0 I could go back to stock using firmware from here using the luci web interface using Kimax-H1 firmware
https://www.dropbox.com/sh/lmiogomcxqnaghv/AABORq743r3X7hEV70978Suua?dl=0
All seems to work well on stock firmware, and I could go back to LEDE from stock using the image generated by @mkresin build environment.

@Mynzer

This comment has been minimized.

Show comment
Hide comment
@Mynzer

Mynzer Oct 10, 2017

When i see that there was 2 stock firmwares version in the dropbox link, I decide to take time to test both firmwares in my device

The HSY-02 firmware boot on my device and all woks fine except the reset button that not work, the same thing that was happening before @mkresin do the change in the dts file in the reset button. When i see the U25AWF stock firmware boot log firmware from openwrt forum I see all the things that @f00b4r0 mention before, that the original Kimax version have MT7620N and DDR1 but also notice this
[ 0.000000] MIPS: machine is HSY HSY-02

The H1 firmware is the original firmware that came in my device, with this firmware all work fine, including the reset button, there are other U25AWF users in the openwrt forum here, here and this Russian guy that have the U25AWF H1 version with MT7620A and DDR2 memory.

The HSY-02 or H1 version it's displayed in the stock configuration web page of the device, and it seems that in the stock boot log too.

So my conclusion is, that there are 2 versions of the Kimax U25AWF

  • Version 1 have MT7620N, DDR1 RAM, on board it's printed HSEN-KI-300M-HDD-V3.0 and uses stock Kimax HSY-02 firmware
    The original patch was written for this device, i think so, because in openwrt forum, the creator of this patch say that all work including the reset button

  • Version 2 have MT7620A, DDR2 RAM, on board it's printed U25AWF-7620A-1153-V2.0 and uses stock Kimax H1 firmware
    So far, the original patch on this device works except for the reset button, but with the changes that @danielkucera and @mkresin kindly do, this device could have support.

With this information, I don't know if could be possible add support for the 2 versions of this device, maybe my ignorance is big, but it seems that the only difference, in the software side, it's the different gpio for the reset button.

Mynzer commented Oct 10, 2017

When i see that there was 2 stock firmwares version in the dropbox link, I decide to take time to test both firmwares in my device

The HSY-02 firmware boot on my device and all woks fine except the reset button that not work, the same thing that was happening before @mkresin do the change in the dts file in the reset button. When i see the U25AWF stock firmware boot log firmware from openwrt forum I see all the things that @f00b4r0 mention before, that the original Kimax version have MT7620N and DDR1 but also notice this
[ 0.000000] MIPS: machine is HSY HSY-02

The H1 firmware is the original firmware that came in my device, with this firmware all work fine, including the reset button, there are other U25AWF users in the openwrt forum here, here and this Russian guy that have the U25AWF H1 version with MT7620A and DDR2 memory.

The HSY-02 or H1 version it's displayed in the stock configuration web page of the device, and it seems that in the stock boot log too.

So my conclusion is, that there are 2 versions of the Kimax U25AWF

  • Version 1 have MT7620N, DDR1 RAM, on board it's printed HSEN-KI-300M-HDD-V3.0 and uses stock Kimax HSY-02 firmware
    The original patch was written for this device, i think so, because in openwrt forum, the creator of this patch say that all work including the reset button

  • Version 2 have MT7620A, DDR2 RAM, on board it's printed U25AWF-7620A-1153-V2.0 and uses stock Kimax H1 firmware
    So far, the original patch on this device works except for the reset button, but with the changes that @danielkucera and @mkresin kindly do, this device could have support.

With this information, I don't know if could be possible add support for the 2 versions of this device, maybe my ignorance is big, but it seems that the only difference, in the software side, it's the different gpio for the reset button.

@mkresin

This comment has been minimized.

Show comment
Hide comment
@mkresin

mkresin Oct 11, 2017

Contributor

Oh my godness, it's getting complicated.

To summarize, there are two different revisions of the Kimax U25AWF

  • MT7620N with DDR1 RAM

    • board is labelled HSEN-KI-300M-HDD-V3.0
    • stock firmware is named HSY-02
  • MT7620A with DDR2 RAM

    • board is labelled U25AWF-7620A-1153-V2.0
    • stock firmware is named H1

Both of you are having the U25AWF-7620A-1153-V2.0 (MT7620A) board? If yes, we need to touch the DTS file again, since it includes the mt7620n.dtsi and has a compatible string for the mt7620n-soc.

Is it confirmed that both revisions are named U25AWF? Is there any way do distinguish the devices from the outside (suffix H1/HSY-02, revision number or similar on the case)? How does one know which stock firmware needs to be installed?

I would like to refrain from adding support for a revision which can not be tested at the moment. But I would like to name the board/image in a way that it is possible to understand it is meant for the MT7620A revision.

@f00b4r0 thanks for bringing up the issue

@Mynzer thanks for doing the research

Contributor

mkresin commented Oct 11, 2017

Oh my godness, it's getting complicated.

To summarize, there are two different revisions of the Kimax U25AWF

  • MT7620N with DDR1 RAM

    • board is labelled HSEN-KI-300M-HDD-V3.0
    • stock firmware is named HSY-02
  • MT7620A with DDR2 RAM

    • board is labelled U25AWF-7620A-1153-V2.0
    • stock firmware is named H1

Both of you are having the U25AWF-7620A-1153-V2.0 (MT7620A) board? If yes, we need to touch the DTS file again, since it includes the mt7620n.dtsi and has a compatible string for the mt7620n-soc.

Is it confirmed that both revisions are named U25AWF? Is there any way do distinguish the devices from the outside (suffix H1/HSY-02, revision number or similar on the case)? How does one know which stock firmware needs to be installed?

I would like to refrain from adding support for a revision which can not be tested at the moment. But I would like to name the board/image in a way that it is possible to understand it is meant for the MT7620A revision.

@f00b4r0 thanks for bringing up the issue

@Mynzer thanks for doing the research

@mkresin mkresin self-assigned this Oct 11, 2017

@Mynzer

This comment has been minimized.

Show comment
Hide comment
@Mynzer

Mynzer Oct 12, 2017

@mkresin Yes, my device it's U25AWF-7620A-1153-V2.0 MT7620A board, this user claims that have the same board, and this user says that have an U25AWF with MT7260A chipset.

Both versions are named U25AWF, there is another version, the U25WF, but the case it's different and it use RT5350F chipset.

It's not clear how to know which U25AWF version is each one from the outside, the external case is similar for both versions, and the info printed in the case i don't think that be reliable, because it change between sub manufacturers as mention in the openwt forum.

The way that I think that could be more reliable to identify the device version could be checking the stock firmware web page configuration.

This is the stock Kimax U25AWF MT7620N configuration page
hsy-02

This is the stock Kimax U25AWF MT7620A configuration page
h1

And then unmount to check the revision board
Kimax U25AWF MT7620N board with DDR1 RAM
MT7620N

Kimax U25AWF MT7620A board with DDR2 RAM
MT7620A

i don't think that unmount the board could be a big problem, because you need to disassembly the case to insert a sata hard drive, once you follow the same steps that you use to put the sata drive, you only need to remove two additional screws to pull out the board.

Maybe the firmware image could be named u25awf-hsy02 for the MT7260N version (when it gets support in the future) and u25awf-h1 for the MT7620A version.

Mynzer commented Oct 12, 2017

@mkresin Yes, my device it's U25AWF-7620A-1153-V2.0 MT7620A board, this user claims that have the same board, and this user says that have an U25AWF with MT7260A chipset.

Both versions are named U25AWF, there is another version, the U25WF, but the case it's different and it use RT5350F chipset.

It's not clear how to know which U25AWF version is each one from the outside, the external case is similar for both versions, and the info printed in the case i don't think that be reliable, because it change between sub manufacturers as mention in the openwt forum.

The way that I think that could be more reliable to identify the device version could be checking the stock firmware web page configuration.

This is the stock Kimax U25AWF MT7620N configuration page
hsy-02

This is the stock Kimax U25AWF MT7620A configuration page
h1

And then unmount to check the revision board
Kimax U25AWF MT7620N board with DDR1 RAM
MT7620N

Kimax U25AWF MT7620A board with DDR2 RAM
MT7620A

i don't think that unmount the board could be a big problem, because you need to disassembly the case to insert a sata hard drive, once you follow the same steps that you use to put the sata drive, you only need to remove two additional screws to pull out the board.

Maybe the firmware image could be named u25awf-hsy02 for the MT7260N version (when it gets support in the future) and u25awf-h1 for the MT7620A version.

@mkresin

This comment has been minimized.

Show comment
Hide comment
@mkresin

mkresin Oct 13, 2017

Contributor

@Mynzer I've reworked the commit in my staging tree. The board is now named Kimax U25AWF-H1 and uses the mt7620a stuff.

Would you please do your testing once more (and hopefully for the last time).

Contributor

mkresin commented Oct 13, 2017

@Mynzer I've reworked the commit in my staging tree. The board is now named Kimax U25AWF-H1 and uses the mt7620a stuff.

Would you please do your testing once more (and hopefully for the last time).

@Mynzer

This comment has been minimized.

Show comment
Hide comment
@Mynzer

Mynzer Oct 13, 2017

@mkresin I don't have problems testing all the necessary times that could be needed.
I pulled the new changes from your staging tree, but now it seems that the new Kimax U25AWF-H1 target don't appear in the make menuconfig menu.

Maybe i'm wrong, I'm still learning, but it could be that in the mt7620.mk file in the target/linux/ramips/image folder
TARGET_DEVICES += u25awf
should be?
TARGET_DEVICES += u25awf-h1

Mynzer commented Oct 13, 2017

@mkresin I don't have problems testing all the necessary times that could be needed.
I pulled the new changes from your staging tree, but now it seems that the new Kimax U25AWF-H1 target don't appear in the make menuconfig menu.

Maybe i'm wrong, I'm still learning, but it could be that in the mt7620.mk file in the target/linux/ramips/image folder
TARGET_DEVICES += u25awf
should be?
TARGET_DEVICES += u25awf-h1

@mkresin

This comment has been minimized.

Show comment
Hide comment
@mkresin

mkresin Oct 13, 2017

Contributor

@Mynzer

On spot! That was the change I missed. Seem to me now you're reviewing my changes ;-).

It is fixed in my staging tree. You might need to remove the tmp directory within the LEDE directory to see the changed board name.

Contributor

mkresin commented Oct 13, 2017

@Mynzer

On spot! That was the change I missed. Seem to me now you're reviewing my changes ;-).

It is fixed in my staging tree. You might need to remove the tmp directory within the LEDE directory to see the changed board name.

@Mynzer

This comment has been minimized.

Show comment
Hide comment
@Mynzer

Mynzer Oct 13, 2017

@mkresin Now I can see the change in the board name, here is the boot log from your staging tree, commit 8c4c2cb407a0f8a39986badb39806b325cf17c7d

dmesg.txt

All is working fine on the device (leds, internal hard drive, wifi, usb port, Ethernet, reset button).
Tell me if i can assist you with some other specific tests on the device and post results.

Mynzer commented Oct 13, 2017

@mkresin Now I can see the change in the board name, here is the boot log from your staging tree, commit 8c4c2cb407a0f8a39986badb39806b325cf17c7d

dmesg.txt

All is working fine on the device (leds, internal hard drive, wifi, usb port, Ethernet, reset button).
Tell me if i can assist you with some other specific tests on the device and post results.

@mkresin

This comment has been minimized.

Show comment
Hide comment
@mkresin

mkresin Oct 14, 2017

Contributor

Tell me if i can assist you with some other specific tests on the device and post results.

Nothing left to do. I've merged the commit. Thanks to all!

Contributor

mkresin commented Oct 14, 2017

Tell me if i can assist you with some other specific tests on the device and post results.

Nothing left to do. I've merged the commit. Thanks to all!

@mkresin mkresin closed this Oct 14, 2017

@cristipatty

This comment has been minimized.

Show comment
Hide comment
@cristipatty

cristipatty Jan 10, 2018

Hello guys @danielkucera @mkresin @Mynzer ,
I have this device: https://www.aliexpress.com/item/Wireless-Hdd-Docking-station-for-2-5-3-5-SATA-hard-disk-USB3-0-wWifi-HDD/32623783372.html .
Device model is BS-HD03WF, board's chipset is MT7620N.
On default firmware web interface it says "Router model HSY-02".

As you can see it has a different form-factor but considering the HW is the same I',m tempted to try this FW. The only thing different is that it has 2 x RJ45 - WAN and LAN instead of just one. Otherwise USB3.0 is there, USB2.0 (with card-reader) is there, maybe leds might be different but they aren't that important for now.

Do you think I could flash this FW from stock web-update section?
I'm interested in LAN and Wifi to work and be able to access mounted storages (HDD sata or USB with card-reader).
Do you think the firmware will work and device won't break?

Thanks.

cristipatty commented Jan 10, 2018

Hello guys @danielkucera @mkresin @Mynzer ,
I have this device: https://www.aliexpress.com/item/Wireless-Hdd-Docking-station-for-2-5-3-5-SATA-hard-disk-USB3-0-wWifi-HDD/32623783372.html .
Device model is BS-HD03WF, board's chipset is MT7620N.
On default firmware web interface it says "Router model HSY-02".

As you can see it has a different form-factor but considering the HW is the same I',m tempted to try this FW. The only thing different is that it has 2 x RJ45 - WAN and LAN instead of just one. Otherwise USB3.0 is there, USB2.0 (with card-reader) is there, maybe leds might be different but they aren't that important for now.

Do you think I could flash this FW from stock web-update section?
I'm interested in LAN and Wifi to work and be able to access mounted storages (HDD sata or USB with card-reader).
Do you think the firmware will work and device won't break?

Thanks.

@Mynzer

This comment has been minimized.

Show comment
Hide comment
@Mynzer

Mynzer Feb 13, 2018

Hi @cristipatty
Sorry for the long delay. Kimax/Blueendless company seem to use the same "Router model HSY-02" firmware for various devices as stated in the manual for our devices.

Mr. @danielkucera seem to be using this firmware on his U-35WF. The stock HSY-02 firmware don't make any verification in the firmware upgrade process, so you can flash it and maybe it could work with your BS-HD03WF device.

The bad news is that I could not find any information, any internal pics or any information how your Router/HDDcase could be recovered, so in case of brick of your device, you are alone..

Now, in the best of the cases that the hardware is the same, and the device boot with OpenWRT/LEDE firmware, you will end with a device with not correct switch configuration (maybe 1 or none of the Ethernet ports will work). In case that you want full support for your device, you will need to provide information from your device and open a new PR, (maybe @danielkucera could help you opening the new PR if you kindly ask him for help and only if you are willing to take the risk and provide the info that the developers need).

If you are interested in continue anyway,, I think that the best place to continue the discussion is in the forums, I don't think that the developers like to bring back closed PR, and maybe find there more people interested in bring support for your device.

Greetings.

Mynzer commented Feb 13, 2018

Hi @cristipatty
Sorry for the long delay. Kimax/Blueendless company seem to use the same "Router model HSY-02" firmware for various devices as stated in the manual for our devices.

Mr. @danielkucera seem to be using this firmware on his U-35WF. The stock HSY-02 firmware don't make any verification in the firmware upgrade process, so you can flash it and maybe it could work with your BS-HD03WF device.

The bad news is that I could not find any information, any internal pics or any information how your Router/HDDcase could be recovered, so in case of brick of your device, you are alone..

Now, in the best of the cases that the hardware is the same, and the device boot with OpenWRT/LEDE firmware, you will end with a device with not correct switch configuration (maybe 1 or none of the Ethernet ports will work). In case that you want full support for your device, you will need to provide information from your device and open a new PR, (maybe @danielkucera could help you opening the new PR if you kindly ask him for help and only if you are willing to take the risk and provide the info that the developers need).

If you are interested in continue anyway,, I think that the best place to continue the discussion is in the forums, I don't think that the developers like to bring back closed PR, and maybe find there more people interested in bring support for your device.

Greetings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment