Topic: Easybox 904 LTE open source code to be provide soon

The content of this topic has been archived between 1 Apr 2018 and 5 May 2018. Unfortunately there are posts – most likely complete pages – missing.

Page 11 of 19

Post #251

Plonk34

22 Jan 2017, 01:14

Thanks,
but i think my biggest problem is i can not found the original 3.07 xDSL image.

i try it with 3.05 and 3.17 without success

3.05:

dd bs=1 if=fullimage-3.05.img count=19255360 of=RootFS.bin
dd bs=1 if=fullimage-3.05.img count=1441792 skip=19261504 of=Kernel.bin
cat RootFS.bin > fullimage.img
cat Kernel.bin >> fullimage.img

http://pastebin.com/NB380J0q

3.17

dd bs=1 if=fullimage_AT904X-03.17.01.16.bin of=RootFS.bin count=22192192
dd bs=1 if=fullimage_AT904X-03.17.01.16.bin of=Kernel.bin skip=22198336 count=1572864
cat RootFS.bin > fullimage.img
cat Kernel.bin >> fullimage.img

http://pastebin.com/BMEp4hFY

Post #252

QAuge

27 Jan 2017, 22:55

Hi plonk34!

Thanks for your detailed information. The logs are really helpful to understand the problem.
I think something is missing in the uboot environment. Are you able to use the unlocked bootloader by using the recovery method, mentioned here: wiki.openwrt.org/inbox/arcadyanastoria/arcadyan_astoria_easybox_904xdsl_r01#debricking ? So you can show us the values where I can compare to my device. Next step where maybe to boot up with an kernel over tftp and later maybe flash an image over

BTW: I'm able to run upstream lede version on it. After some sleepless nights I catched the fruits from @arnysch and the other cool developers, mixed them together and tried so much combinations... at least one configuration worked to get the network running. Some findings:
RTL3867RB:
- Switch is enabled via MDIO based RTL3867RB which is currently a pull request, see: github.com/lede-project/source/pull/537
- No tagged port allowed.
- Switch is also enabled by modified sequence in uboot.

Lantiq Switch
- Switch can't using the SWITCH_ROUTING feature - it is blocking arp broadcasts etc.
- Switch ports has to be assigned to a vlan / pvid. No tagged port allowed.

Boot Log here:
pastebin.com/t9Vs4WTK

Post #253

Plonk34

31 Jan 2017, 15:44

Are you able to use the unlocked bootloader by using the recovery method

Och nööö, this is not the anwser that i have wish to hear.
Can you exact tell me what i have todo. should i remove the R148 or break the line to it, but how ?
I have to unbox first, for this reason at the moment i can not equal the platine with the image and i have no idea what the image try me to tell.

Is it possible to bring the uboot-env back via image update ?
This will be my preferred method.

Is it possible to start uboot twice instead of the Kernel ?
(first the original uboot and them the own uboot)

Post #254

QAuge

6 Feb 2017, 20:18

Good times for the Easybox 904xDSL

I'm able to get network and telephony running, thanks to the patches which flies around.
If someone is interested, try this one:

!! No warranty ! Use it on your own risk !!

---------------
COMPILE
---------------

git clone https://github.com /Quallenauge/Easybox-904-XDSL.git
cd Easybox-904-XDSL
git checkout tags/Easybox-904-XDSL-1-0-0
cp vr9_default.config .config
./scripts/feeds update
./scripts/feeds install
make

Then in bin/lantiq/ are two important files:
bin/targets/lantiq/xrx200-uClibc/lede-lantiq-xrx200-device-vgv952cjw33-rootfs.tar.gz (rootfs, tar gz)
build_dir/target-mips_24kc_uClibc-1.0.22/linux-lantiq_xrx200/VGV952CJW33-kernel.bin (kernel)

---------------
INSTALL
---------------
(Taken and adapted from: This thread page #5
To install OpenWRT on an EasyBox do the following:
1. Download the opened vendor Firmware-Image: http://arny.tjps.eu/OpenWrt/EasyBox904x … opened.img

2. And install it via the rescue mode (see http://arny.tjps.eu/OpenWrt/EasyBox904x … eadme.txt)

3. Then boot the box with an connected usb stick that includes the special text file (see v0.1-readme.txt) and wait 5 minutes

4. Set an password via the web interface (192.168.2.1)

5. Then power off the box, remove then the usb stick

6. Power on the box again

7. Now connect via ssh and the setted password:

ssh root@192.168.2.1

8. connect another usb stick with the rootfs and kernel files and go to these data dir:

cd /tmp/usb/a1

9. Write kernel to nand

flash_eraseall /dev/mtd2
nandwrite -p /dev/mtd2 linux-lantiq_xrx200/VGV952CJW33-kernel.bin

10. write rootfs to to a sdcard on a (linux pc)
Create 3 Partitions (e.g. with cfdisk)

# assume the usb memory is recognized as sda
mkfs.f2fs /dev/sda3
mkdir /tmp/disk
mount /dev/sda3 /tmp/disk
cd /tmp/disk
tar xfz bin/targets/lantiq/xrx200-uClibc/lede-lantiq-xrx200-device-vgv952cjw33-rootfs.tar.gz

11. Insert usb storage into the EasyBox

12. boot the device again

reboot

-------------------------------------
OPTIONAL: Bootloader without password, network support and no uboot-env setting on every boot.
-------------------------------------
To write a bootloader that is accessible without a password do this:
1. Download and extract
uboot.tar.xz

2. copy u-boot.lq to "another" usb stick (without the special text file for enabling SSH)

3. CHECK if you could access the u-boot.lq file (stick is mounted, file is listed)
because after erasing a bootloder a new one must be written
(otherwise the router is BRICKED and a special rescue mode is needed)

3. erase nand area, write modified u-boot without passwort to it:

flash_eraseall /dev/mtd0
nandwrite -p /dev/mtd0 u-boot.lq
reboot

4. u-boot could accessed via serial line with empty password

!!!! PS: Big thanks for all people which done a fundamental research to allow this release !!!!

Post #255

QAuge

6 Feb 2017, 20:25

HI Plonk34!

Och nööö, this is not the anwser that i have wish to hear.
Can you exact tell me what i have todo. should i remove the R148 or break the line to it, but how ?
I have to unbox first, for this reason at the moment i can not equal the platine with the image and i have no idea what the image try me to tell.

No, it seems to only needed to shortcut the two pins (überbrücken/kurzschließen) for the time of power on - no removing/destroying. This would be my only guess

Is it possible to bring the uboot-env back via image update ?
This will be my preferred method.

I never built an own image, which corrects a uboot env. Maybe someone else can do it?

Is it possible to start uboot twice instead of the Kernel ?
(first the original uboot and them the own uboot)

I don't think so.

Post #256

trg8984

18 Feb 2017, 08:54

Hello,
@QAuge
I found the files. But unfortunately I do not get so clear with your instructions.
I can connect via ssh to the box and also install the kernel image. But where is the file root.squashfs?
In section 10, you write 3 partitions. Why 3? Is it not enough if you create a partition and unpack the file?
Thanks in advance.

Post #257

QAuge

18 Feb 2017, 17:17

trg8984 wrote:

Hello,
@QAuge
I found the files. But unfortunately I do not get so clear with your instructions.
I can connect via ssh to the box and also install the kernel image. But where is the file root.squashfs?

I used f2fs as filesystem. There is a tar.gz file within the bin folder, which contains the root filesystem. I extracted it to the usb stick partition. I don't use the squashfs.

trg8984 wrote:

In section 10, you write 3 partitions. Why 3? Is it not enough if you create a partition and unpack the file?
Thanks in advance.

Have a look at the file
VGV952CJW33.dts file. At the boot cmd you can define your root as you wish. In case no partition is involved just define

root=/dev/sda

. (To use the new parameter, recompile and install the kernel and prepare the usb stick like this

mkfs.f2fs /dev/sda
mkdir /tmp/disk
mount /dev/sda /tmp/disk
cd /tmp/disk
tar xfz <path to tar gz>
sync
umount /tmp/disk

NOTE: make sure /dev/sda should your usb stick - not your harddisk ). After that your USB Stick contains the rootfs which is mounted by the kernel.
In the release tag, I used the /dev/sda3 partition and so I described it).

Hint, use tftp to test the kernel. Prepare a ttfp server at 192.168.2.100 and copy the kernel as "uImage" to the tftp server. Boot into u-boot and type:

tftp
bootm

Then the kernel (should) start up.

Post #258

QAuge

28 Feb 2017, 23:24

Hi there.

I got the display up and running...

( http://picpaste.de/pics/EB904.1488320671.JPG )
Currently no fancy graphics, lcd4linux base install.

I wrote a (my first) driver to support the touchpad as input device. The touchpad is capable for multitouch, bit I doubt. there is a use case at this device - so this is currently not supported. The result is the following:

No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:      eb904_keypad
Select the device event number [0-0]: 0-0
Input driver version is 1.0.1
Input device ID: bus 0x18 vendor 0x1 product 0x1 version 0x1
Input device name: "eb904_keypad"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 28 (KEY_ENTER)
    Event code 103 (KEY_UP)
    Event code 105 (KEY_LEFT)
    Event code 106 (KEY_RIGHT)
    Event code 108 (KEY_DOWN)
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
Event: time 1487804635.364856, type 4 (EV_MSC), code 4 (MSC_SCAN), value 05
Event: time 1487804635.364856, type 1 (EV_KEY), code 28 (KEY_ENTER), value 1
Event: time 1487804635.364856, -------------- SYN_REPORT ------------
Event: time 1487804635.400817, type 4 (EV_MSC), code 4 (MSC_SCAN), value 04
Event: time 1487804635.400817, type 1 (EV_KEY), code 105 (KEY_LEFT), value 1
Event: time 1487804635.400817, -------------- SYN_REPORT ------------
Event: time 1487804635.554515, type 4 (EV_MSC), code 4 (MSC_SCAN), value 04
Event: time 1487804635.554515, type 1 (EV_KEY), code 105 (KEY_LEFT), value 0
Event: time 1487804635.554515, -------------- SYN_REPORT ------------
Event: time 1487804635.592111, type 4 (EV_MSC), code 4 (MSC_SCAN), value 05
Event: time 1487804635.592111, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0
Event: time 1487804635.592111, -------------- SYN_REPORT ------------

(Last edited by QAuge on 1 Mar 2017, 22:30)

Post #259

violentstorm

4 Mar 2017, 12:03

Hey there,
I've obtained a 904 xdsl box for cheap.
Now I'm trying to get my T-Home VDSL working with this Router.
I've managed to get access via ssh with the 3.17 image.
Now I've followed the steps from post 176.
But Somehow the box don't save the vlan_ID@wan050.
Its always reset vlan 132.

On the GUI I see, that the VDSL is connected and the speed is correct detected, but because of the wrong vlan I can't use it.

Could anyone help me please?

Post #260

xl2cc

10 Mar 2017, 15:55

My 904xDSL is still in bootloop...

i tryed almost everything without opening the box for UART.
Flashed several images - everytime the same result - bootloop
i made my own image under Kali , same size as original - bootloop....

normally it is not my "way" but is there a guy i can send the box? I don´t have the time to do another 20 hour session for trying to unbrick it without solution.

some pages before i read "flashing takes 2 minutes" - mine is ready in 10 seconds - is there a problem?

2 times it happend that the box wrote "downloaded the image - flashing" but there was NO tftp up for downloading?! how can that possible?

any solutions? OR
german adress would be fine or the trash is his new home.

Post #261

QAuge

11 Mar 2017, 20:41

xl2cc wrote:

My 904xDSL is still in bootloop...

Hi!
Maybe you want to try an highly experimental fullimage.img which boots a customized rootfs from a usb stick?
@Plonk: Maybe you want this also try for your box?

Nevertheless, I think there's no way back to the vendor firmware.

Post #262

Plonk34

12 Mar 2017, 01:40

Yes i want !
I have not yet come to test the UART mode because In my infinite wisdom i have close the case and i must reopen first if i want to use UART.

Post #263

QAuge

12 Mar 2017, 14:35

Ok, I tried this on my second box, which has version 3.16 flashed.

Download the following files:
lede-lantiq-xrx200-device-vgv952cjw33-rootfs.tar.gz
lede-lantiq-xrx200-VGV952CJW33-ubifs-fullimage-ubinized.bin

Perform the following steps:

Switch off the box. Remove the network cable.
scp ~/lede-lantiq-xrx200-VGV952CJW33-ubifs-fullimage-ubinized.bin tftpuser@tftpserver:/tftpboot/fullimage.img
Insert USB Stick:
sudo cfdisk /dev/sdX (whery sdX is the usb drive).
Create a partition on it.
Format it to fs2fs:
mkfs.f2fs /dev/sdX1
Mount it:
mkdir /tmp/disk
sudo mount /dev/sdX1 /tmp/disk
cd /tmp/disk
Make sure you are on the right directory:
ls -la
It has to be empty. If not, check your commands again.
tar xfz ~/lede-lantiq-xrx200-device-vgv952cjw33-rootfs.tar.gz
sudo chown -r root:root .
Sync and umount:
sync && sudo umount /tmp/disk
Now you put the stick into the box
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, the usb stick should show some action (if it has an led)
After some minutes, the box should be appear with default ip 192.168.1.1
I recommend to flash the uboot since every boot the uboot env is rewritten to flash.
After three reboots the recovery mode will jump in then.

(Last edited by QAuge on 12 Mar 2017, 14:41)

Post #264

xl2cc

12 Mar 2017, 19:36

Thanks @QAuge

the box is booting "from" USB Stick now into your "image".

When i remove the USB Stick and switch off/on the box is again in bootloop - so i think i am booting atm from USB - right?

then i tryed to flash via the webinterface a image (mine - original) - did not work
everytime the same error: "The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform. "

so i am stuck here. will not do the wrong thing, again....

can you explain the next steps , simple as before, what to do next?

That would be fantastic and if we meet i'll pay the beer, for sure!

Post #265

QAuge

12 Mar 2017, 20:29

Yes, the rootfs is taken from the stick and not from the flash. There are issues to write that via the fullimage.img recovery function.

And now: I'm out. I have some ideas how to flash back the image, but without serial line access, this can be difficult.
It's not clear for me, why the recovery doesn't work via vendor fullimage.img. @Plonk34 has provided some logs from the update process - which doesn't show an error. But the image isn't loading.

So, how to proceed?!
Is there a special need for the vendor image?

Post #266

xl2cc

12 Mar 2017, 20:46

No, no need for the vendor image. I have to flash a different cause i wanna use the box with Telekom DSL. That was the reason i tryed to flash my selfmade image.

do you have a different image for me to test? A "opened" would be fine, working with Telekom

Post #267

QAuge

12 Mar 2017, 21:08

It should be possible to utilize the embedded modem. If I remember, the base packages are included in the image to get a sync. But there are no ppp related packages compiled in.
I never tried that. SInce this is a standard chip, it should sync.

BTW: WLAN doesn't work - there are no sources for this device :-(

Post #268

xl2cc

12 Mar 2017, 21:23

no way to get the WLAN function working with non-vendor image?

I do have a Netgear Access point but a second device on the sideboard is not what i want.

As longer as it takes, i more think about a diffenrent router, for the coming Vectoring DSL my yet active router can´t handle. That was the reason why i bought the cheap 904.

Any idea for a cheap device which can handle vectoring DSL + WLAN? if it is not too off-topic or via PN

Post #269

QAuge

12 Mar 2017, 21:25

> no way to get the WLAN function working with non-vendor image?
no way.
... or via attached usb stick (The box has 2 of them). But this means no out of the box experience.

(Last edited by QAuge on 12 Mar 2017, 22:00)

Post #270

kovz

13 Mar 2017, 15:07

no way to get the WLAN function working with non-vendor image?

There is old sources for wlan driver. I have done some investigation of them, so now I am understand how it works and trying to port them to new kernel. But this is my firs experience with kernel module. And it quite hard

Post #271

chipmunk

14 Mar 2017, 12:21

Hi,

first of all thank you QAuge for your excellent work on this device (904xDSL)! I found a way to boot from nand. You will need serial access to modify bootargs and a custom kernel with CONFIG_MIPS_CMDLINE_FROM_BOOTLOADER=y (target/linux/lantiq/config-4.9)
I use the device in this config since seven days without problems as my home router on a 16/1 Mbit DSL link (easybell) with sqm. I dont need the FSX ports/asterisk. Thats why i enabled SMP again to have a dual core router. :-)

1. Do the steps 1.-12. mentioned in post 254. Then you should have a device, which boots nicely from sda3.

2. On your PC (not on the easybox904!) prepare an ubifs.img.
2.1. decompress in a new directory (e.g. /tmp/rootfs) the lede-lantiq-xrx200-device-vgv952cjw33-rootfs.tar.gz (sudo tar -xzf lede-lantiq-xrx200-device-vgv952cjw33-rootfs.tar.gz)
2.2. change directory to /tmp
2.3. sudo mkfs.ubifs -q -r rootfs/ -v -m 2048 -e 126976 -c 2047 -F -o ubifs.img

3. log via ssh into the easybox904xDSL to prepare ubi and ubifs on /dev/mtd12 (it is a big partition, like 300 MB, label "misc", i suppose the vendor used it for the answering machine)
3.1. ubiformat /dev/mtd12 -s 2048 ---> say yes to the errors
3.2. ubiattach -m 12 -O 2048
3.3. ubimkvol /dev/ubi0 -N rootfs -m
3.4. transfer the ubifs.img from step 2 to the device and do ubiupdatevol /dev/ubi0_0 ubifs.img

4. change the bootargs in u-boot to
setenv bootargs ubi.mtd=12,2048 root=ubi0:rootfs rootfstype=ubifs console=ttyLTQ0,115200

5. Enjoy "out of the box experience" :-)

Bootlog with succesful boot from nand:

[    0.000000] Linux version 4.9.8 (tim@neuron) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3503-023da1a) ) #0 SMP Wed Mar 1 21:56:15 2017
[    0.000000] SoC: xRX200 rev 1.2
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 00019556 (MIPS 34Kc)
[    0.000000] MIPS: machine is VGV952CJW33-E-IR - EasyBox 904 xDSL
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 08000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Detected 1 available secondary CPU(s)
[    0.000000] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] On node 0 totalpages: 32768
[    0.000000] free_area_init_node: node 0, pgdat 80681120, node_mem_map 8100a0e0
[    0.000000]   Normal zone: 256 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 32768 pages, LIFO batch:7
[    0.000000] percpu: Embedded 13 pages/cpu @8110d000 s21584 r8192 d23472 u53248
[    0.000000] pcpu-alloc: s21584 r8192 d23472 u53248 alloc=13*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: ubi.mtd=12,2048 root=ubi0:rootfs rootfstype=ubifs console=ttyLTQ0,115200 
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Writing ErrCtl register=00000000
[    0.000000] Readback ErrCtl register=00000000
[    0.000000] Memory: 121564K/131072K available (5075K kernel code, 200K rwdata, 1380K rodata, 1264K init, 248K bss, 9508K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:256
[    0.000000] Setting up vectored interrupts
[    0.000000] Setting up IPI vectored interrupts
[    0.000000] arch/mips/lantiq/xway/sysctrl.c:ltq_soc_init:517 LTQ_EBU_BUSCON2: 0x0001d3dd
[    0.000000] arch/mips/lantiq/xway/sysctrl.c:ltq_soc_init:520 LTQ_EBU_BUSCON2: 0x0001d3dd
[    0.000000] CPU Clock: 500MHz
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041786 ns
[    0.000011] sched_clock: 32 bits at 250MHz, resolution 4ns, wraps every 8589934590ns
[    0.008037] Console: colour dummy device 80x25
[    0.012363] Calibrating delay loop... 332.54 BogoMIPS (lpj=665088)
[    0.046867] pid_max: default: 32768 minimum: 301
[    0.051741] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.058281] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.069843] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[    0.069861] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[    0.070088] CPU1 revision is: 00019556 (MIPS 34Kc)
[    0.129191] Synchronize counters for CPU 1: 
[    0.129193] done.
[    0.135470] Brought up 2 CPUs
[    0.143870] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.153599] pinctrl core: initialized pinctrl subsystem
[    0.159694] NET: Registered protocol family 16
[    0.173887] pinctrl-xway 1e100b10.pinmux: Init done
[    0.179932] dma-xway 1e104100.dma: Init done - hw rev: 7, ports: 7, channels: 28
[    0.294573] dcdc-xrx200 1f106a00.dcdc: Core Voltage : 1016 mV
[    0.305711] FPU Affinity set after 2008 emulations
[    0.533639] ifx_pcie_wait_phy_link_up timeout
[    0.545914] random: fast init done
[    0.753650] ifx_pcie_wait_phy_link_up timeout
[    0.970420] ifx_pcie_wait_phy_link_up timeout
[    1.187191] ifx_pcie_wait_phy_link_up timeout
[    1.403974] ifx_pcie_wait_phy_link_up timeout
[    1.408192] pcie_rc_initialize link up failed!!!!!
[    1.445061] gpio-stp-xway 1e100bb0.stp: Init done
[    1.450834] SCSI subsystem initialized
[    1.455512] usbcore: registered new interface driver usbfs
[    1.461093] usbcore: registered new interface driver hub
[    1.466474] usbcore: registered new device driver usb
[    1.474685] clocksource: Switched to clocksource MIPS
[    1.498908] NET: Registered protocol family 2
[    1.504733] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    1.511637] TCP bind hash table entries: 1024 (order: 1, 8192 bytes)
[    1.518036] TCP: Hash tables configured (established 1024 bind 1024)
[    1.524545] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    1.530365] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    1.537009] NET: Registered protocol family 1
[    1.541297] PCI: CLS 0 bytes, default 32
[    1.542317] gptu: totally 6 16-bit timers/counters
[    1.547394] gptu: misc_register on minor 63
[    1.551548] gptu: succeeded to request irq 126
[    1.556066] gptu: succeeded to request irq 127
[    1.560553] gptu: succeeded to request irq 128
[    1.565089] gptu: succeeded to request irq 129
[    1.569579] gptu: succeeded to request irq 130
[    1.574104] gptu: succeeded to request irq 131
[    1.581667] lantiq,vmmc 1f103000.vmmc: requested GPIO 499
[    1.586964] lantiq,vmmc 1f103000.vmmc: reserved 1MB at 0x07400000
[    1.593582] phy-xrx200 gphy-xrx200: requesting lantiq/vr9_phy11g_a2x.bin
[    1.600821] phy-xrx200 gphy-xrx200: booting GPHY0 firmware at 7F40000
[    1.607178] phy-xrx200 gphy-xrx200: booting GPHY1 firmware at 7F40000
[    1.714740] No VPEs reserved for AP/SP, not initialize VPE loader
[    1.714740] Pass maxvpes=<n> argument as kernel argument
[    1.726119] No TCs reserved for AP/SP, not initializing RTLX.
[    1.726119] Pass maxtcs=<n> argument as kernel argument
[    1.738970] futex hash table entries: 512 (order: 2, 16384 bytes)
[    1.745086] Crashlog allocated RAM at address 0x3f00000
[    1.751011] workingset: timestamp_bits=30 max_order=15 bucket_order=0
[    1.778412] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    1.784136] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    1.800872] io scheduler noop registered
[    1.804703] io scheduler deadline registered (default)
[    1.811200] 1e100c00.serial: ttyLTQ0 at MMIO 0x1e100c00 (irq = 112, base_baud = 0) is a lantiq,asc
[    1.820111] console [ttyLTQ0] enabled
[    1.827442] bootconsole [early0] disabled
[    1.838254] gen_nand 14000000.nand-parts: platform_nand_data is missing
[    1.843502] gen_nand: probe of 14000000.nand-parts failed with error -22
[    1.850766] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xdc
[    1.856486] nand: Samsung NAND 512MiB 3,3V 8-bit
[    1.861101] nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    1.868803] Scanning device for bad blocks
[    2.137494] Bad eraseblock 2618 at 0x000014740000
[    2.289553] 16 ofpart partitions found on MTD device 14000000.nand-parts
[    2.294844] Creating 16 MTD partitions on "14000000.nand-parts":
[    2.300879] 0x000000000000-0x000000040000 : "uboot"
[    2.308060] 0x000000040000-0x000003c40000 : "rootfs1"
[    2.314641] 0x000003c40000-0x000004140000 : "kernel1"
[    2.320574] 0x000004140000-0x000004240000 : "tmp1"
2.326360] 0x000004240000-0x000004440000 : "tmp2"
[    2.332022] 0x000004440000-0x000004540000 : "sysconfig"
[    2.338306] 0x000004540000-0x000004640000 : "ubootconfig"
[    2.344537] 0x000004640000-0x000004700000 : "fwdiag"
[    2.350862] 0x000004700000-0x000004a00000 : "lcdimage"
[    2.356798] 0x000004a00000-0x000004b00000 : "mfgconfig"
[    2.362918] 0x000004b00000-0x000004c00000 : "sipdata"
[    2.368714] 0x000004c00000-0x000008c00000 : "voice"
[    2.375191] 0x000008c00000-0x00001be00000 : "misc"
[    2.384340] 0x00001be00000-0x00001fa00000 : "rootfs2"
[    2.391064] 0x00001fa00000-0x00001ff00000 : "kernel2"
[    2.396904] 0x00001ff00000-0x000020000000 : "mystery"
[    2.407394] libphy: Fixed MDIO Bus: probed
[    2.489856] libphy: lantiq,xrx200-mdio: probed
[    2.566637] Intel XWAY PHY11G (xRX integrated) 0:11: attached PHY driver [Intel XWAY PHY11G (xRX integrated)] (mii_bus:phy_addr=0:11, irq=-1)
[    2.650642] Intel XWAY PHY11G (xRX integrated) 0:13: attached PHY driver [Intel XWAY PHY11G (xRX integrated)] (mii_bus:phy_addr=0:13, irq=-1)
[    2.664262] dwc2 1e101000.ifxhcd: requested GPIO 495
[    2.768487] dwc2 1e101000.ifxhcd: DWC OTG Controller
[    2.772143] dwc2 1e101000.ifxhcd: new USB bus registered, assigned bus number 1
[    2.779417] dwc2 1e101000.ifxhcd: irq 62, io mem 0x00000000
[    2.784964] dwc2 1e101000.ifxhcd: Hardware does not support descriptor DMA mode -
[    2.792375] dwc2 1e101000.ifxhcd: falling back to buffer DMA mode.
[    2.800308] hub 1-0:1.0: USB hub found
[    2.802836] hub 1-0:1.0: 1 port detected
[    2.908258] dwc2 1e106000.ifxhcd: DWC OTG Controller
[    2.911886] dwc2 1e106000.ifxhcd: new USB bus registered, assigned bus number 2
[    2.919173] dwc2 1e106000.ifxhcd: irq 91, io mem 0x00000000
[    2.924698] dwc2 1e106000.ifxhcd: Hardware does not support descriptor DMA mode -
[    2.932145] dwc2 1e106000.ifxhcd: falling back to buffer DMA mode.
[    2.940051] hub 2-0:1.0: USB hub found
[    2.942564] hub 2-0:1.0: 1 port detected
[    2.947711] usbcore: registered new interface driver usb-storage
[    3.053965] ltq-cputemp cputemp@0: Current CPU die temperature: 52.5 °C
[    3.059696] wdt 1f8803f0.watchdog: Init done
[    3.067556] NET: Registered protocol family 10
[    3.073025] NET: Registered protocol family 17
[    3.076225] 8021q: 802.1Q VLAN Support v1.8
[    3.083964] rtl8367b rtl8367b: using bus lantiq,xrx200-mdio
[    3.088433] rtl8367b rtl8367b: RTL8367RB chip found
[    4.423594] ubi0: attaching mtd12
[    4.846589] ubi0: scanning is finished
[    4.866113] ubi0: attached mtd12 (name "misc", size 306 MiB)
[    4.870376] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    4.877249] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
[    4.883952] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[    4.890914] ubi0: good PEBs: 2447, bad PEBs: 1, corrupted PEBs: 0
[    4.896984] ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
[    4.904251] ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1396515132
[    4.913365] ubi0: available PEBs: 0, total reserved PEBs: 2447, PEBs reserved for bad PEB handling: 79
[    4.922738] ubi0: background thread "ubi_bgt0d" started, PID 544
[    4.978080] UBIFS (ubi0:0): recovery needed
[    5.042967] UBIFS (ubi0:0): recovery deferred
[    5.046079] UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "rootfs", R/O mode
[    5.054188] UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    5.064104] UBIFS (ubi0:0): FS size: 258523136 bytes (246 MiB, 2036 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    5.074813] UBIFS (ubi0:0): reserved for root: 0 bytes (0 KiB)
[    5.080630] UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID C50B1FC8-721D-4E09-A6C2-26BCA56B1F62, small LPT model
[    5.092879] VFS: Mounted root (ubifs filesystem) readonly on device 0:10.
[    5.102630] Freeing unused kernel memory: 1264K (80684000 - 807c0000)
[    5.107673] This architecture does not have kernel memory protection.
[    5.214279] init: Console is alive
[    5.216559] init: - watchdog -
[    5.476119] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    5.512001] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    5.521419] init: - preinit -
[    7.995755] mount_root: mounting /dev/root
[    7.999406] UBIFS (ubi0:0): completing deferred recovery
[    8.047930] UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 604
[    8.051525] UBIFS (ubi0:0): deferred recovery completed
[    8.062618] urandom-seed: Seeding with /etc/urandom.seed
[    8.117784] procd: - early -
[    8.120410] procd: - watchdog -
[    8.814541] procd: - ubus -
[    8.873363] procd: - init -
[    9.307024] kmodloader: loading kernel modules from /etc/modules.d/*
[    9.337477] fbtft_of_value: buswidth = 8
[    9.340051] fbtft_of_value: debug = 1
[    9.343649] fbtft_of_value: rotate = 270
[    9.347591] fbtft_of_value: fps = 30
[    9.351662] fb_ili9341_eb904 0.easybox904-display: fbtft_request_one_gpio: 'reset-gpios' = GPIO468
[    9.360202] fb_ili9341_eb904 0.easybox904-display: fbtft_request_one_gpio: 'led-gpios' = GPIO490
[    9.490325] ili9341_Probe: Probed ID4: 9341
[    9.656979] graphics fb0: fb_ili9341_eb904 frame buffer, 320x240, 150 KiB video memory, 16 KiB DMA buffer memory, fps=31
[    9.672138] IFXOS, Version 1.5.19 (c) Copyright 2009, Lantiq Deutschland GmbH
[    9.707068] Lantiq TAPI device driver, version 3.13.0.2, (c) 2001-2010 Lantiq Deutschland GmbH
[    9.726067] NET: Registered protocol family 8
[    9.729001] NET: Registered protocol family 20
[    9.787547] RPC: Registered named UNIX socket transport module.
[    9.792155] RPC: Registered udp transport module.
[    9.796841] RPC: Registered tcp transport module.
[    9.801470] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    9.827895] tun: Universal TUN/TAP device driver, 1.6
[    9.831626] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    9.951517] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    9.966116] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   10.054941] Lantiq (VRX) DSL CPE MEI driver, version 1.5.17.6, (c) 2007-2015 Lantiq Beteiligungs-GmbH & Co. KG
[   10.075149] i2c /dev entries driver
[   10.115094] 
[   10.115094] 
[   10.115094] Lantiq CPE API Driver version: DSL CPE API V4.17.18.6
[   10.122793] 
[   10.122793] Predefined debug level: 3
[   10.134204] i2c-gpio 0.i2c: using pins 481 (SDA) and 476 (SCL)
[   12.731549] input: eb904_keypad as /devices/platform/0.i2c/i2c-0/0-0014/input/input0
[   12.762561] hidraw: raw HID events driver (C) Jiri Kosina
[   12.783903] u32 classifier
[   12.785178]     input device check on
[   12.788857]     Actions configured
[   12.794835] Mirror/redirect action on
[   12.819020] nf_conntrack version 0.5.0 (2048 buckets, 8192 max)
[   12.849055] Console: switching to colour frame buffer device 40x30
[   12.918541] Lantiq MIPS34KEc MPS driver, version 2.2.2.5, (c) 2006-2010 Lantiq Deutschland GmbH
[   12.925886] request_timer(2, 0x000001AE, 1)...
[   12.930114] successful!
[   12.933078] Lantiq VMMC device driver, version 1.9.0.3, (c) 2006-2010 Lantiq Deutschland GmbH
[   12.947387] ip_tables: (C) 2000-2006 Netfilter Core Team
[   12.961520] Infineon Technologies DEU driver version 2.0.0 
[   12.967661] IFX DEU DES initialized (multiblock).
[   12.972321] IFX DEU AES initialized (multiblock).
[   12.976230] IFX DEU ARC4 initialized (multiblock).
[   12.980737] IFX DEU SHA1 initialized.
[   12.984496] IFX DEU MD5 initialized.

root@LEDE:~# df -h
Filesystem                Size      Used Available Use% Mounted on
ubi0:rootfs             227.4M     34.0M    193.4M  15% /
tmpfs                    60.0M      1.5M     58.4M   3% /tmp
tmpfs                   512.0K         0    512.0K   0% /dev
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)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
root@LEDE:~#

(Last edited by chipmunk on 14 Mar 2017, 12:23)

Post #272

Plonk34

15 Mar 2017, 21:00

Great Thanks QAuge it was working !
I have start in OpenWRT from the USB-Stick and replace the uboot by the password-free-uboot (from post 120).
And them i have installed my openwrt-lantiq-xrx200-VGV952CJW33-uImage to /dev/mtd2 and
openwrt-lantiq-xrx200-VGV952CJW33-squashfs-ubinized.bin to /dev/mtd12 (see Posts: 120).
But does not work because i get a bootloop: http://pastebin.com/raw/EcJZJxnX

I have reinstall your image and it work again.

Now i have a free booloader and will see how i can get a working openwrt on the device.
Thanks for your troubles !

Post #273

QAuge

16 Mar 2017, 09:18

Hi chipmunk!

Thanks for your steps. I currently prepare the sysupgrade functionality and ran into some issues regarding the
VID header offset size (parameter -s / -o of ubiformat and ubiattach). Where did you take this values.
If I perform a ubiformat / ubiattach it tooks standard values (512) with ecc errors as result. In opposite to that,
If I use your values, the format / attach /detach / re-attach cycle is just fine.
Can you please explain this - and is it possible to set the 2048 as default values?!
If this is not the case I have to update the nand.sh script and introduce another value ( CU_UBI_VID_HEADER_OFFSET ).

Also why "-c 2047" on mkfs.ubifs?

Post #274

QAuge

16 Mar 2017, 12:08

kovz wrote:

no way to get the WLAN function working with non-vendor image?
There is old sources for wlan driver. I have done some investigation of them, so now I am understand how it works and trying to port them to new kernel. But this is my firs experience with kernel module. And it quite hard

Indeed, that are the sources. I'm not aware of it. Hopefully there where no device specific changes by the vendor.
Regarding to the age of the sources - linux development is so fast, and interfaces (within the kernel) where changed very often - so I hope the wlan part isn't affected very much, to make the porting easier.
If you need some help let me know. It would be nice to have another feature reactivated by an alternative firmware.
Thumbs up ! :-)

Post #275

QAuge

16 Mar 2017, 12:08

Plonk34 wrote:

Great Thanks QAuge it was working !
I have start in OpenWRT from the USB-Stick and replace the uboot by the password-free-uboot (from post 120).
And them i have installed my openwrt-lantiq-xrx200-VGV952CJW33-uImage to /dev/mtd2 and
openwrt-lantiq-xrx200-VGV952CJW33-squashfs-ubinized.bin to /dev/mtd12 (see Posts: 120).
But does not work because i get a bootloop: http://pastebin.com/raw/EcJZJxnX
I have reinstall your image and it work again.
Now i have a free booloader and will see how i can get a working openwrt on the device.
Thanks for your troubles !

Nice to hear it is working
Regarding the U-Boot: I recommend to use my modified boot loader to not fall into the recovery issue.

(Last edited by QAuge on 16 Mar 2017, 12:09)

Page 11 of 19