Support for Easybox 904 LTE

[Plonk34]

For example I have disassembled my router several times, and now the FXS ports a very friable and only one works.

[takimata]

I never opened my device.

[pc2005]

@Plonk34

For example I have disassembled my router several times, and now the FXS ports a very friable and only one works.

That's why I always buy two devices, one can be destroyed during the hacking

@takimata

I never opened my device.

I don't have Easybox, but the internal uart and its logs could probably help.

[suppenkasper0815]

Hi @Plonk34,

unfortunately there is still no offical support to this device in Openwrt-wiki. Is it maybe possible that it is because of the wrong topic name? We discuss only Easybox 904 xdsl here an the topic says Easybox 904 LTE...

Could also someone please conclude the actual information and a how-to or something? Maybe @QAuge , @arnysch or @henning-schild could say somehing about what's going on atm or how to proceed into offical support of Openwrt and solve the issue with XRX200 closed source...

I stick with my Box still on an older image and don't know how to proceed to be honest. - It syncs also like often from @majuss described with 18/2 on a 100/40 VVDSL2 subscriber-line.

Thank you very much for all your efforts already at this point!

[Plonk34]

Hi @suppenkasper0815,
I am not the TO, but I think the name of the thread have historical reasons see post #1, there is a link to a thread with the equal name on the old forum.
"Easybox 904 LTE open source code to be provide soon"
I know it contain Important information for potentially developers for the LTE variant.

Could also someone please conclude the actual information and a how-to or something?

what did you exact mean ?
The conclusion of information are in: https://github.com/Quallenauge/Easybox-904-XDSL

I stick with my Box still on an older image and don't know how to proceed to be honest. - It syncs also like often from @majuss described with 18/2 on a 100/40 VVDSL2 subscriber-line.

It is an General problem of the modems in xrx200 and it is more helpfull to open an separat thread.
But i think you need a vectoring capable Modemfirmware
see this post #3 for explanation.
You must extract an Modemfirmware from an Stockfirmware image like Fritzbox 7490 and copy them to your Routersystem
Them you should add the lines "option firmware "path-to-fw"" in the /etc/config/network under dsl
see https://openwrt.org/docs/guide-user/network/wan/isp-configurations

[Plonk34]

About: ""Add bad block table implementation" BREAKS all other NAND devices that use BBT-pattern"

"Add bad block table implementation" should be talked upstream with the linux-mtd developers. Probably there could be done something usefull for other devices out of this "quick hack"

Of it looks like the best way but this should done by a person that are have contact to the Kernel-developer and do know what are BBT are.
Them i guess it need long time to implement and a result ( so i guess ) are an extra Kernel config parameter.

For this reason it is not better to add a new Kernel parameter like MTD_NAND_CUSTOMIZED_BBT_VGV952CJW33EIR and hatches this service to ./config/Config-kernel.in

Because there is an other problem: the Easybox-904xDSL need a special openwrt-config like:
CONFIG_BUSYBOX_CONFIG_DEVMEM=y
and
CONFIG_KERNEL_DEVMEM=y
Or is this not a Problem ?

But at the moment i can not test i have some strange read errors on mtd device and i have not idea if it a hardware error, a problem with this devicetype or an general linux problem.

[slh]

@Plonk34

For this reason it is not better to add a new Kernel parameter like MTD_NAND_CUSTOMIZED_BBT_VGV952CJW33EIR and hatches this service to ./config/Config-kernel.in

While that might make things a bit neater, it won't really help the problem at hand, as the same kernel image is shared among all devices of a (sub-)target. Meaning if you need to enable your hypothetical MTD_NAND_CUSTOMIZED_BBT_VGV952CJW33EIR, and you do, if you want to support the EB904xDSL, you break all other xrx200 devices with NAND at the same time - nothing won. What would be needed here is some way to influence the kind of BBT at runtime, either by adding some kind of quirk for the EB904xDSL or maybe DTS side configuration.

@Plonk34

Because there is an other problem: the Easybox-904xDSL need a special openwrt-config like:
CONFIG_BUSYBOX_CONFIG_DEVMEM=y
and
CONFIG_KERNEL_DEVMEM=y
Or is this not a Problem ?

Yes, those are a problem, but compared to BBT and switch support an optional one (display/ touchscreen don't 'need' to work for basic device support --> defer to stage 2).

[kovz]

@Plonk34

CONFIG_BUSYBOX_CONFIG_DEVMEM=y
and
CONFIG_KERNEL_DEVMEM=y
Or is this not a Problem ?

This is not a problem. DEVMEM is used only to set needed MAC delay settings for port, where Ralink WiFi SoC connected. We can extend device tree parameters for xrx200 ethernet port to set this delay in the register. It just where done as DEVMEM manipulations in original firmware from Arcadian, but, indeed, this is a MAC settings register.

[takimata]

ICYMI: A few hours ago, this commit went into master:

kernel: add kmod-fb-tft

This module adds support for small TFT LCD display modules.

Which includes the ILI9341 in our Easyboxen.

[logarex1]

@takimata

Edit: Less than 8 hours later I arrived home to find the Easybox sitting on the "Your Easybox couldn't be started" red screen of death. So something effectively killed the system again, and this time it wasn't the wifi driver.

I have such a problem with my device.

[Plonk34]

There a alot of things that fail and can be the reason for the different errors:

ECC errors in UBI RB2011UiAS-2HnD-IN (and solution)

Hi all, This week, I wanted to upgrade my RB2011UiAS-2HnD-IN to a new version of OpenWRT. I got boot loops whenever I installed a version that used UBI (and not the old yaffs2). So I built a serial cable and saw lots of ECC errors scrolling past the screen. Those errors could be reproduced by ubiformat / ubiattach / ubimkvol / ubidetach / ubiattach (last command would fail with said errors) It turned out that my unit has a K9F1G08U0E flash chip which does not support sub-page writes (http://li…

TD-W8970 v1 crash with no visible errors in logs

Hello. I am opening this thread for mainly 2 reasons: If I open another separate thread for every issue that I encounter, admins will probably ban me... and they will be right to do it.... so I created this thread with every single problem I have now. Again I'm sorry that I created so many threads in the past. I want to find out if it is my TD-W8970 v1 (1.2) is broken or if it is my configuration that makes it crash. I think, but I might be completely wrong, that no-one is checking the working…

Are I/O errors on mtdblock concerning?

Hi, Just got a brand new Linksys EA8500 and the first thing I did was to flash the latest stable OpenWRT! I'm still configuring it, but whenever it boots I can see some I/O error messages. [ 10.326413] print_req_error: I/O error, dev mtdblock0, sector 0 [ 10.332545] print_req_error: I/O error, dev mtdblock0, sector 8 [ 10.333077] print_req_error: I/O error, dev mtdblock0, sector 16 [ 10.337791] print_req_error: I/O error, dev mtdblock0, sector 24 [ 10.344175] print_req_error: I/O er…

So i do not explore for it because it sucks, anything is always wrong since months,
It was not possible to build an stabel fullworking image.
(I build USB-Storage and f2fs inside my kernel)

At the moment i try to build a solution for the special-NAND-bbt-patch-destroy-other-devices problem.
I use minimal images without f2fs and USB-storage support and they are working (but possible that my Flash are defect on a higher position)

[Plonk34]

@logarex1
If you use the extra Kernel.config from post
do not use this part:

# adding theese kernel config for starting the image from usbstick

@all
Starting from USB-Stick does not really working too because:
It starts fine from USB-Stick but the overlay-fs is on UBI0_1 (from the size it looks like mtd12).
And this make not really sense.
How can i change it and not using any overlay-fs or using it on /dev/sda1 (f2fs)

[Plonk34]

About: ""Add bad block table implementation" BREAKS all other NAND devices that use BBT-pattern"

So i have add the field: "customized-samsung-K9F4G08U0x;" under "nand@1 {" inside the VGV952CJW33-E-IR.dts
Inside the drivers/mtd/nand/nand_bbt.c i asked for it and make a decision with or without modified BBT.
Here are the resulting nand_bbt.c and here are the resulting kernel patch: 4052-NAND-add-easybox904-bbt-byDTS.patch.

First test was positiv now i build/test again. If it positiv too, can anybody add this device to openwrt ?

[logarex1]

@Plonk34

Az első teszt pozitív volt, most megint építettem / teszteltem. Ha ez is pozitív, akkor bárki hozzáadhatja ezt az eszközt openwrt-hez?

I'd try the snapshot. Can you give me a download link please?

[Plonk34]

@logarex1

I'd try the snapshot. Can you give me a download link please?

Yes: https://yadi.sk/d/s0-SwLXFnepVQA
But with the following restriction because it is an testbuild:

• it was build on raspberry pi for this reason hostarch=arm7l
• but it is an minimal build without copy all packages from snapshot
• SMP support (no telefon) only
• it contain all drivers without USB but they are inside packages and must be install separate (kmod-usb-dwc2)
• no lcd4linux and i have no idea how can i test the lcd

[logarex1]

@Plonk34

no lcd4linux and i have no idea how can i test the lcd

How to switch off backlight of LCD screen?

I would like to thank you for the download link. I really like it so far. Currently I'm trying.
I need USB. I probe install the (kmod-usb-dwc2), but error Description

This driver provides USB Device Controller support for the Synopsys DesignWare USB OTG Core

• The installed version of package kernel is not compatible, require 4.14.103-1-71c08020… while 4.14.103-1-5990414d… is installed.

[takimata]

@logarex1

How to switch off backlight of LCD screen?

I don't have an EB904 set up right now, but If I remember correctly, the LCD is turned off and on the same way as a system LED. Have a look at QAuge's LUA script.

[suppenkasper0815]

@logarex1:

Support for Easybox 904 LTE

How to switch off backlight of LCD screen? I would like to thank you for the download link. I really like it so far. Currently I'm trying. I need USB. I probe install the (kmod-usb-dwc2), but error Description This driver provides USB Device Controller support for the Synopsys DesignWare USB OTG Core The installed version of package kernel is not compatible, require 4.14.103-1-71c08020… while 4.14.103-1-5990414d… is installed.

Hey, would you please also tell what's working and what not atm?

1. Modem?
2. 5GHz
3. Mesh-Networks
4. Voice/ISDN
5. NF / Software Offloading

Why is it so important to change from JFFS? I haven't gotten the point and also not why the device is still not officially supported?

[slh]

1. yes
2. yes, but the wlan situation as a whole is fragile and might not work at all at the moment.
3. no
4. yes/ no
5. yes, but it won't get you past 60-65 MBit/s either.

[suppenkasper0815]

@slh: Thanks, I also put on my old EasyBox 802 with LEDE 17.04 build and analysed that the Ralink 2870 chipset there is also still fragile. You can use the chipset already as a WWAN and AP at the same time, but usually then the wifi breaks with heavy load completly and takes a minute to come up again.

The driver says it should be possible to use it in mesh-networks, but unfortunately a test with an WR801v2 with working mesh-options don't work proper with this Ralink (shit) devices....

Is there any idea if also NF offloading will be enabled in the near future for Ralink-chipsets? As I understand other discussions there is usually only Atheros chipset support... unfortunately.

So still continueing to find a good working device...

It's so annyoing with the Easyboxes. They all have a descent hardware (RAM, Flash, CPU), but always lacks of driver support. - Especially the Easybox 904 with a price < 10€ a lot of RAM and Flash, fast CPU should be a perfect development plattform for openwrt and should get supported offically!