Support for Easybox 904 LTE

For Developers
112

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

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)

113

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

@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)

114

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 ?

1 Like
115

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

116

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
1 Like
117

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. :slight_smile:
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.
118

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.

1 Like
119

@logarex1:

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?

120
  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.
1 Like
121

@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!

122

Do not compare rt2800pci with RaLink rt3883 iNIC.

123

LCD does not work on my build
@takimata why did you think that fb-tft includes ILI9341 ?
I see no message in dmesg and no /dev/fb device exist.
I can not see any ILI9341-kmod.
A kmod-fb-tft-ili9486 exist but it is an other device.

An other thing are:
When enablening FB-devices the following lines are missed in kernelconfig and it is not possible to make an build without stopping, or adding this lines:

cat << EOF >> ./target/linux/lantiq/xrx200/config-4.14
CONFIG_VGA_CONSOLE=y 
CONFIG_VGACON_SOFT_SCROLLBACK=n 
CONFIG_DUMMY_CONSOLE_COLUMNS=80
CONFIG_DUMMY_CONSOLE_ROWS=25
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
EOF

In past i use this quick and dirty makefile for build with the ILI9341 with SDK:


And i missed some more modules as exist now. (if do a look inside the makefile)

124

of course you can use the kernel packages that are include the my archiv-file in path packages only.
(the kernel can use only modules that where built with them (I have no idea why is it, but the answer where much interessting for me))
You have to install from hand: scp first then opkg install full-path-file-name
Or theoreticly modifi the /etc/opkg/customfeeds.conf add

src/gz any_name	file://usb-path/to-packages"

And copy the files to the place where should be (it does make only sense on USB)

1 Like
125

I've edited /etc/opkg/customfeeds.conf and opkg / distfeeds.conf. I used an Apache server.
Install luci, nut-server and nut-mon, nut-web-cgi, usbutils, uhttp working now. Wifi working 5GHz and 2.4GHz, WAN port eth0.2 DHCP, Snapshot is stable.
Otherwise, a new kernel was released today.
http://downloads.openwrt.org/snapshots/targets/lantiq/xrx200/kmods/4.14.103-1-71c08020f8cd26e89ed7454da32dce5e/

:smile: Thank you

126

I have the scripts where i have created the patch and builds here: https://github.com/Plonkbong/create-openwrt-easybox904x-patches
And i add the resulting patch to my fork of openwrt: https://github.com/Plonkbong/openwrt
@QAuge should i do a pull request ?

1 Like
127

Hi Plonk34!

First, thanks for your effort =)
Regarding a PR: IMO why not using the several commits for the PR? I always push them at the top of my trees. This will preserve authorship and history. Your detailed description (which I like) can be the description of the PR itself. Otherwise I think there will be questions why things are done in this way (e.g. package/network/config/ltq-vdsl-app/files/dsl_control)
Also I see "Signed-off-by: Your Name <you@example.com>" at the end of the commit message - which isn't completed yet - right?
When I look at the patch, I see that some other things are changed as well, which has nothing related to the EasyBox904xdsl:
e.g.

-tplink,vr200 tplink,vr200v)
+tplink,vr200v)

...and others.

@takimata: Regarding the LCD driver. Although the upstream ILI9341 driver. I think I wrote it before, but the display isn't connected to a SPI interface but to an EBU interface which is working a little bit different. So we can't use the upstream driver (sadly).

Random: The random device reboots are really annoying. And I haven't found something what can caused this. Any ideas or conrete commands how to test this (except writing tests on the NAND please :slight_smile: - I setup an rootfs at the usb sdcard and experience these reboots also)?

128

Oh, right, I remember now. That's a real bummer, yes.

Not only annoying, unfortunately. In my tests not only did it reboot randomly, it broke the box requiring a reflash. That renders the thing effectively unusuable for anything beyond experiments. :frowning:

129

Which is really interesting. This way the box has restarted before the "reset" functionality kicks in. And this is really early - it should also work in recovery.

Sometimes I saw that the fw_config (which holds information about the uboot configuration location) wasn't right. So I added a workaround for that.

echo "fw_config is generated now"
/bin/sh /etc/uci-defaults/30_uboot-envtools

When you restart your box, can you please perform a

root@LEDE:~# fw_printenv bootnum
bootnum=1

and verify if it behaves like on my site ?

130

thanks i have fixed.

The reason are: I am not an git expert and i want a split into 2 parts one for the basics and one for the uboot.
For me i like to have an simple patch where i can exact see the what is going on.
In past i try to find out the relevant commits, cherry-pick them merge to openwrt but it was to complex and do not really work.
So i agree with you but i can not do it.

1 Like
131

How to build image from this link https://github.com/Quallenauge/Easybox-904-XDSL?
I follow this Build Instructions:
git clone https://github.com/Quallenauge/Easybox-904-XDSL.git Easybox-904-XDSL cd Easybox-904-XDSL ./scripts/feeds update &amp;&amp; ./scripts/feeds install -a cp vr9_default.config .config make oldconfig make V=s

But I can't build image. I got error always:

make[2]: *** [package/feeds/packages/bash/compile] Error 2
make[2]: Leaving directory '/Openwrt/Easybox-904-XDSL-master-lede-plonk/Easybox-904-XDSL-master-lede'
package/Makefile:103: recipe for target '/Openwrt/Easybox-904-XDSL-master-lede-plonk/Easybox-904-XDSL-master-lede/staging_dir/target-mips_24kc_musl/stamp/.package_compile' failed
make[1]: *** [/Openwrt/Easybox-904-XDSL-master-lede-plonk/Easybox-904-XDSL-master-lede/staging_dir/target-mips_24kc_musl/stamp/.package_compile] Error 2
make[1]: Leaving directory '/Openwrt/Easybox-904-XDSL-master-lede-plonk/Easybox-904-XDSL-master-lede'
/Openwrt/Easybox-904-XDSL-master-lede-plonk/Easybox-904-XDSL-master-lede/include/toplevel.mk:216: recipe for target 'world' failed
make: *** [world] Error 2

How to solve this error?