Again, there is some development.
Device specific changes in master:

• Integrated sysupgrade feature: means future versions can be flashed via web frontend

• Vendor bootloader recovery stopper: If bootnum is >=3 then the uboot env variable "bootnum" is erased.

• Integrated touch device

• Integrated display device: There may be some issues regarding coloring. Patches welcome

• Added lcd4linux sample package, which uses serdisplib as framebuffer output and uses a config adapted from this one: http://forum.ipfire.org/viewtopic.php?f … =15#p76616 Thanks!!!

• Developed lcdcontroller, which starts and stops lcd4linux on touch events

Current device shot:

Thats what i wanna hear

I dont have the time atm to do something but if it works my useless box will have a job again.

Thanks!

Hey,
Does anyone have the original firmware version 2.06 to EasyBox 904 xDSL?
If so, I would ask about my shed.

And the second thing, if you have the password can operate to U-Boot when connecting serial console? If so, I would also appreciate the message.

Thanks
Aleksy

Hmm i use this one:
http://arny.tjps.eu/OpenWrt/EasyBox904x … passwd.zip
what are the differenz to that:
https://mega.nz/#!bA1gADqB!TtTdK3ePNdRj … Ee3U3cnTvo
?
And how can i build my own bootloader ?

I have some understanding problems:
u-boot.lq starts without boot-env is this correct ?
Where are the env and what are the content of env ?
On a normal OpenWRT the boot-env normaly on the next partition ?
But where are the partiton s defined ?

Hi there.
With the help of @chipmunk is was able to implement a working sysupgrade.

Following steps should be done for the first time (also on a vanilla box  with vendor firmware installed):

• Prepare a tftp server on 192.168.2.100
  Copy fullimage.img to the tftp server

• Turn off the EasyBox 904

• Hold the reset button and switch on the box.
  Wait 5 seconds. Then release the button.

• The recovery screen should be appear

• Put the network cable into the box

• The box should say, image downloaded, image is flashed.

• After a while, the box should say, switch off and on the box. Do that.

• The box should boot, and is reachable by http://192.168.1.1
  There you are greeted by the recovery flash screen.
  Note, that this is only a recovery system, the kernel contains the rootfs within the initramfs. All changes made are lost after an reboot! Use this only for flashing the real system (next step)

• Upload the following image: sysupgrade.bin.

• The box should reboot after the process. Kernel is written to kernel partition while the rootfs is installed on mtd12 as ubi formatted partition.

• Future updates can be upload by normal update process via sysupgrade.bin upload. No recovery needed.

On a technical side, the display is working in RBG mode, huh. I don't know how to change this yet - maybe someone has an idea.

PS: The recovery is also required when a previous version was used, since the sysupgrade functionality was added in the recent version.

Update 1: NOTE: Currently there are some issues regarding network. I changed the download link and resolve this issue later.
Update 2: Issues resolved (quick&dirty). Sysupgrade image was reuploaded.
Update 3: fullimage.img 1-0-1 with network fix. (updated link in description).

(Last edited by QAuge on 19 Mar 2017, 13:14)

Congratulation, very nice.

The network on the fullimage.img was not correct working:
On the yellow port --> nothing
I have switch from the yellow ports to the gray --> nothing
I switch back --> It works

forget my post before.
I see that the uboot are inside the https://github.com/Quallenauge/Easybox-904-XDSL.git
But when you are finish can everbody explain what is going on boot and where are the MTD partition defined.
This is a heave complex device.

Nice work, really. Only one thing:

root@LEDE:~# mount
ubi0:rootfs on / type ubifs (rw,noatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000)
debugfs on /sys/kernel/debug type debugfs (rw,noatime)
root@LEDE:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
ubi0:rootfs          114031785270 6259669672 107772115598   5% /
tmpfs                27219277232 215512884 27003764349   1% /tmp
tmpfs                250778629         0 250778629   0% /dev
root@LEDE:~# df -h
Filesystem                Size      Used Available Use% Mounted on
ubi0:rootfs             106.3T      5.8T    100.5T   5% /
tmpfs                    25.4T    205.8G     25.2T   1% /tmp
tmpfs                   239.5G         0    239.5G   0% /dev
root@LEDE:~# 

106.3T?

(Last edited by obsy on 19 Mar 2017, 10:23)

I have uploaded a new fullimage.img and linked it within the description. Thanks for reporting it.
I will have a look at uboot description when I have some time for documentation.
Just note, that I don't built the uboot from the current master-lede branch but only with the easybox-devel
branch. The master branch should also work, but I never tested it. Do this only if you are familiar with the recovery procedure by shortcut some pins. For changes on the modified uboot have a look at Uboot modification

Cool compression algorithm isn't it ?
Btw. I don't know why this comes up - any ideas?

(Last edited by QAuge on 19 Mar 2017, 13:33)

Hi Qauge
You did very good work.
From the first version to the present is a great progress.
However, it is still a long way to a fully functioning image.
The installation of your image worked whitout problems.
The basic functions (WAN TelekomVDSL100, Fon VOIP-ISDN, WLAN) do not run for me.
I don't realy know, howto setup the VDSL line and the Telefon.

For daily use I take the opened firmware of arny. The box has been running for weeks without problems at my Telekom VDSL100line.

Unfortunately, the rescue mode does not work properly. Each flash of an image ends in a bootloop. My solution, fast and dirty:
Extract the rootFS from the openedImage and nandwrite the squashRootFS in UARTmode on /dev/mtd1 manually.
I spent some hours to find the error. Unfortunately without success

Thanks

For my needs, it is nearly feature complete.
Maybe there isn't an image which covers all functionality the box provides (since dect and isdn and (*maybe*) wlan will not be there).
@Someone can explain the setup process with the VDSL setup?! I'm not using it.
For the telephony I have the following setup (as example):
FritzBox as main router and as SIP server. Easybox asterix as client.

Prepare lantiq telephony ports, each individual channel line:

/etc/asterisk/lantiq.conf

; Number of FXS ports (default: 2)
channels = 2
; Create contexts per channel (default: off)
per_channel_context = on

Define SIP connection details:

/etc/asterisk/sip.conf

[Fritzbox]
username=620
secret=123456789
type=friend
insecure=port,invite
host=192.168.9.2
fromdomain=fritz.box
fromuser=620
context=incoming

# Accept all incoming calls on telephon port2

[incoming]
exten => 620,1,Answer()
exten => 620,n,Dial(TAPI/2,150,r,t,)

# Accept all outgoing calls for the 
[lantiq2]
exten => _0[1-9].,1,Dial(SIP/${EXTEN}@Fritzbox)

Note: Only the analogue ports are supported!

Do you mean the rescue mode does not work on arny's image?
Maybe this image is running in the same problems, I got when I was trying to flash my squashfs to the mtd1 partition.
On the rescue process, this partition is formatted as jffs2. Then the image is written to it
(see U-Boot upgrade for details).
When I do a flash_erase and nandwrite a squashfs on command line, it works.

(Last edited by QAuge on 20 Mar 2017, 08:19)

hi there ,found some pcb pics

*diy.habichdochgesagt.com/index.php?/category/1*

(Last edited by limbuskakerlake on 20 Mar 2017, 13:55)

@QAuge How can i rebuild the images from post 280 ?
I try master-lede:

git clone https://github.com/Quallenauge/Easybox-904-XDSL.git
cd Easybox-904-XDSL
git checkout master-lede

cp vr9_default.config .config
./scripts/feeds update
./scripts/feeds install

make menuconfig
make

My sysupgrade-image is only ~11MB and produce a bootloop.
I can not find the rescue-image.
The reason is i need some kernel modules, the imagebuilder and the SDK.
Where is Asterisk inside the menu ?

The next question is: how can i get to the rescue mode ?
OK i solved my problem when i redownload the rescue image but i guess this not in the interest of the developer.

VDSL:
I think these modules will additional needed:
- ltq-vdsl-app
and the Firmware
- dsl-vrx200-firmware-xdsl-a
- dsl-vrx200-firmware-xdsl-a-patch
- dsl-vrx200-firmware-xdsl-b
- dsl-vrx200-firmware-xdsl-b-patch
I guess firmware-xdsl-a + firmware-xdsl-b-patch or firmware-xdsl-b + firmware-xdsl-a-patch should pass
But i am not 100% how the vdsl-xy-patch working.

Note: the vr9 xdsl-firmware inside openwrt can no Vectoring
the reason is it is not allowed for openwrt to restructable it.

If you need Vectoring, copy your vdsl-firmware from an other Router firmware like FritzBox 7360 or other vr9 devices.
A list of other firmware versions, including those with vectoring support, can be found here: https://xdarklight.github.io/lantiq-xdsl-firmware-info/

on an other cool Arcadyan device (O2-Box 6431) my VDSL run fine with this parameter:

...

config atm-bridge 'atm'
        option vpi '1'
        option vci '32'
        option encaps 'llc'
        option payload 'bridged'

config dsl 'dsl'
        option annex 'b'
        option tone 'av'
        option xfer_mode 'ptm'
        option line_mode 'vdsl'
        option firmware '/lib/firmware/lantiq-vrx200-b.bin'
...

but try first:
option tone 'auto'
option firmware 'path-to-your-firmware'
option annex 'your-annex'

WLAN:
I was hoping it will run with: kmod-rt2800-pci

ISDN:
Does it definitiv not working or have nobody try it ?
I have nothing find inside the Forum about ISDN, but for ISDN exist many modules (capi dahdi etc).
Have everybody getting the ISDN on the EasyBox 803a running, and if yes how ?

(Last edited by Plonk34 on 20 Mar 2017, 18:46)

Your Installimage is the only that works properly in the rescue mode.
The rescue mode with the official image AT904X-03.17,  AT904X-03.12, as well as arnys openedImage, and my selfmodyfied openedImage end in a bootloop with following errormessage:

[    2.294000] end_request: I/O error, dev mtdblock1, sector 0
[    2.298000] SQUASHFS error: squashfs_read_data failed to read block 0x0
[    2.305000] SQUASHFS error: unable to read squashfs_super_block
[    2.311000] VFS: Cannot open root device "mtdblock1" or unknown-block(31,1)
[    2.401000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,1)
[    2.409000] Rebooting in 1 seconds..
  

Following commands in UARTmode solve the problem:

tftpboot $(loadaddr) $(tftppath)$(rootfs)
nand erase $(f_rootfs_addr) $(f_rootfs_size)
nand write.e $(loadaddr) $(f_rootfs_addr) $(f_rootfs_size)

Maybe I'll look again later for the cause of the error.
I have no time for that at the moment

Really...I though there is a miracle how to get this thing running. I also ended up in this error
when I was trying to get the fullimage.img running. Maybe there is a bug in vendor uboot code and
the jffs2 format is wrong in this piece of code ?! Was this ever working for someone
(I mean a vendor image recovery) ?

Exactly what I did to get this running - no errors when mounting the rootfs.
The uboot vendor code formats this with jffs (see here) , this would result in the following command:

nand erase $(f_rootfs_addr) $(f_rootfs_size) clean

and this never worked for me.

Thanks for reporting.

Correct steps.
[Update] Not really: Try a

./scripts/feeds install -a

to install all available packages.

Bootloop: Please adjust the bootcmd in

target/linux/lantiq/dts/VGV952CJW33-E-IR.dts

Size of build: I try it later from a really, really, really clean master.
Use this one
to boot from nand. I'm currently using the USB mass storage for development reasons.

Rescue image is build in another branch "recovery".
The reason is i need some kernel modules, the imagebuilder and the SDK.

Location -> Network -> Telephony -> asterisk13

Why not. It's only for the rescue. But If you want, you can use the following branch: "recovery"
I got it not running to build the rescue image within the normal build process. See this place
So I created this branch for it with the correct settings.
Please compile with "-j1" there where issues on multithreading builds.
Then the fullimage.img contains no rootfs for example. Maybe it is a hack and not intended by the lede developers,
but it works for the recovery and thats ok for me. (It would not ok for mainstream builds).

Have a look at this post
But maybe there is driver from @kovz ^^ which integrates in the newer kernel.

I never tried it, but there is an stollmann.ko module where no source exists. So I thought
it doesn't work here. Hopefully I'm wrong.

And don't forget as a wrote earlier:
Patches welcome ;-)

(Last edited by QAuge on 21 Mar 2017, 11:39)

Currently driver can upload configuration and firmware. Unfortunately sources very buggy In few days I will push my changes to github. Will be nice, if somebody could capture original driver initial communication. With wireshark I can see only broabcast responses from rt3883, but I need packets from driver, ideally after driver reports this sting:

RACFG_CMD_BOOT_STARTUP
Get concurrent card MAC address:88:03:55:e2:84:7a88:03:55:e2:84:7c

@Plonk:
Try

./scripts/feeds install -a

to install all packages.

How to capture these packets? Enabling these statements?
Just a question, does the open firmware driver also work on the "old" 2.6.32 system? That way we have more options to trace some calls.

For those, who doesn't want to compile a new image here's my current one.

Image 2017-03-21

Highlights:

• dsl firmware included

• simple-adblock

• luci addons added

• graph generation

I was able to connect with this image to my vdsl provider.

(Last edited by QAuge on 21 Mar 2017, 21:40)

I am on same position!

Hi QAuge,

Congratulations for your hard work.
Your firmware is essentially for xDSL version.

Can you please tell me if that's good for LTE version ?

What's working and not working ?
I only need LTE and one RJ45 port (and apps like VPN of course) : is that ok ?

Hi all,
https://github.com/kovz/ralink_inic
in this repository I pushed all my work. It is dirty and WIP.

Thanks

I can't test the image on a LTE box, since I doesn't own one.
The box should be similar - hopefully the GPIOs and the Display is the same, maybe you can give it a try.

For LTE box you don't need RTL switch driver and DSL soft. But you need driver for LTE modem.

Hi kovz,

I didn't get your WIP code to upload the firmware :-(
There's something that I'm doing wrong :-(

But I traced some network traffic when loading the driver.

Please have a look there:
The following line is the console log, with tcpdump in background, listening on the master device (eth0)
Console.txt

The following line is the wireshark log, separately recorded:
Wireshark.log