OpenWrt Forum Archive

Topic: [MT7621A]WiTi Board is coming. Do you want to hack it?

The content of this topic has been archived between 8 Feb 2018 and 3 May 2018. Unfortunately there are posts – most likely complete pages – missing.

Hi guys,

please, can I use DS TTL-232R cable to connect to the serial interface?

Thanks! smile

@mucha

No. You need a USB - TTL adapter.

nitroshift

Hi @nitroshift,

Thanks for the quick answer,

actually I wrote here wrong model number by mistake, I have
TTL-232R-3V3
http://wiki.icub.org/images/c/c1/FTDI_- … TL232R.pdf

and it looks like it should be a USB-TTL adapter? (I havent used it yet, so I am kinda "not 100% sure"..)

Please confirm again, thank you! smile

@mucha

It's OK.

nitroshift

@nitroshift ok perfect!! thanks

@nitroshift,

Hi again, please, can you help me some hints to compile Chaos Calmer ?

I have already built current CC branch and there are several firmware binaries in the bin/ramips dir. However, not witi tagged file.

when executing make menuconfig, the closest target selection is this:
-> target system: Raling RT288x/RT3xxx
-> subtarget: MT7621 boards

but there is no witi profile.

So my question - do I understand it correctly that all i need is to apply this changeset to the CC head?:
https://dev.openwrt.org/changeset/478451

Or is there anything else?. Maybe I'd do a pull request to the branch. Thanks a lot!

PS Is there any particular reason why it is not there yet? (some incompatibilities or..)
Hawk
Best regards

WiTi is not supported in Chaos Calmer, it is in trunk though. Unless there's some specific reason to use CC, I advise you use trunk, it's stable.

nitroshift

@mucha
Not intending to hijack the thread but you're likely much better off with LEDE at this point as OpenWRT trunk lacks a lot of commits for this platform that's in LEDE (trunk).

(Last edited by diizzy on 6 Dec 2016, 09:27)

@nitroshift ok -- thanks for the clarification

@diizzy ok thanks for the info. can you be more specific?

what commits for example? and is the lede trunk as stable as openwrt's trunk? and another one does lede use any proprietary software? like drivers or so..

thanks guys!

Hi guys, how are you? @nitroshift @sugar @obsy @dizzy @others?

I am trying to put LEDE 17.01-rc2 on the board. While setting up the sw raid array I have encountered the following

root@LEDE:/lib# mdadm --create /dev/md0 -l1 -n2 /dev/sda1 /dev/sdb1
mdadm: Note: this array has metadata at the start and
    may not be suitable as a boot device.  If you plan to
    store '/boot' on this device please ensure that
    your boot-loader understands md/v1.x metadata, or use
    --metadata=0.90
Continue creating array? yes
mdadm: unexpected failure opening /dev/md0
root@LEDE:/lib#

This was the case for the 17.01-rc1 as well. I have tried the firmware from

http://ftp.mqmaker.com/WiTi/Firmware/

.. there is broken opkg repo reference. I have also built the image from the git repo to build packages myself to get over the opkg repo problem.

https://github.com/mqmaker/witi-openwrt

Well I have built it but after flashing it had problems connecting, in the

ifconfig

there was an ip assigned to the

br-lan

interface, however even after setting static ip in the range I could not connect (nor dhcp worked before). And I was conencted via serial interface.
I also tried the CC images from demetris and also from

https://forum.mqmaker.com/t/chaos-calmer-15-05-1-openwrt-firmware/362

demetris's img had broken opkg refs, maurer limited. (not all the pckgs)

Now tell me is there a working solution for the NAS? Do you guys have any succes with it? I was following the

https://mqmaker.com/tutorials/making-your-own-nas-with-witi-board/

I see packages

procps

are not available.


Please help me I am crying like a baby big_smile I think I have tried everything.
Thank you! And no matter if the working solution is based on BB/CC/DD/LEDE/... I need working RAID array.

yes and some dbg info:

root@LEDE:/# ls -l /dev/sd*
brw-------    1 root     root        8,   0 Feb  8 12:54 /dev/sda
brw-------    1 root     root        8,   1 Feb  8 12:54 /dev/sda1
brw-------    1 root     root        8,  16 Feb  8 12:54 /dev/sdb
brw-------    1 root     root        8,  17 Feb  8 12:54 /dev/sdb1
root@LEDE:/# ls -l /dev/md*
brw-------    1 root     root        9,   0 Feb  8 12:57 /dev/md0
root@LEDE:/# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath]
unused devices: <none>
root@LEDE:/# modprobe md-mod
md-mod is already loaded
root@LEDE:/# modprobe dm-mod
dm-mod is already loaded
root@LEDE:/# mdadm --create /dev/md0 -l1 -n2 /dev/sda1 /dev/sdb1
mdadm: Note: this array has metadata at the start and
    may not be suitable as a boot device.  If you plan to
    store '/boot' on this device please ensure that
    your boot-loader understands md/v1.x metadata, or use
    --metadata=0.90
Continue creating array? y
mdadm: unexpected failure opening /dev/md0
root@LEDE:/# uname -a
Linux LEDE 4.4.47 #0 SMP Mon Feb 6 21:34:28 2017 mips GNU/Linux

(Last edited by mucha on 8 Feb 2017, 14:26)

The discussion might have continued from here.