VDSL w/ vectoring 9.1.4, ADSL 9.0.D, annex A and B

[hardfalcon]

The latest "Labor" firmware for the Fritzbox 7490 contains the following:

vr9-A-dsl.bin: VDSL over ISDN incl. vectoring support for VRX200, version: 9.1.4 | ADSL Annex A for VRX200, version: 9.0.D
vr9-B-dsl.bin: VDSL over ISDN incl. vectoring support for VRX200, version: 9.1.4 | ADSL Annex B for VRX200, version: 9.0.D

The annex A firmware is shipped as a bsdiff to the annex B firmware image.

I've tested the annex B firmware successfully on a TP-Link VR200v.

[just2mad]

Hi, I don't understand why the bspatched are needed.
Is this to be compatible with Annex A and Annex B in one file?
Or is this for performance? What exactly is the points of the patching?

Thanks!

[hardfalcon]

@just2mad: Think of bspatch as a "binary diff" between the annex A firmware blob an the annex B firmware blob for the DSL modem inside the router.
By using bspatch, only either the annex A or the annex B firmware blob needs to be included in full, and the "full" firmware blob for the other annex can simply be obtained at runtime/during boot by applying the bspatch to the "full" firmware blob for the "first" annex. It's just a simple and efficient way to save a lot of space in the router's firmware image whilst still allowing the device vendor to support both DSL annexes with one common firmware.

[Lankaster]

Annex B, vectoring work very well on BT Home Hub 5A (openwrt-trunk):

ATU-C Vendor ID:                          Broadcom 192.85
ATU-C System Vendor ID:                   Broadcom
Chipset:                                  Lantiq-VRX200
Firmware Version:                         5.9.1.4.0.7
API Version:                              4.17.18.6
XTSE Capabilities:                        0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2
Annex:                                    B
Line Mode:                                G.993.5 (VDSL2 with down- and upstream vectoring)
Profile:                                  17a
Line State:                               UP [0x801: showtime_tc_sync]
Forward Error Correction Seconds (FECS):  Near: 0 / Far: 43
Errored seconds (ES):                     Near: 0 / Far: 3
Severely Errored Seconds (SES):           Near: 0 / Far: 0
Loss of Signal Seconds (LOSS):            Near: 0 / Far: 0
Unavailable Seconds (UAS):                Near: 100 / Far: 100
Header Error Code Errors (HEC):           Near: 0 / Far: 0
Non Pre-emtive CRC errors (CRC_P):        Near: 0 / Far: 0
Pre-emtive CRC errors (CRCP_P):           Near: 0 / Far: 0
Power Management Mode:                    L0 - Synchronized
Latency [Interleave Delay]:               0.14 ms [Fast]   0.0 ms [Fast]
Data Rate:                                Down: 90.760 Mb/s / Up: 33.706 Mb/s
Line Attenuation (LATN):                  Down: 12.6 dB / Up: 11.1 dB
Signal Attenuation (SATN):                Down: 12.6 dB / Up: 10.9 dB
Noise Margin (SNR):                       Down: 8.0 dB / Up: 10.6 dB
Aggregate Transmit Power (ACTATP):        Down: -1.0 dB / Up: 12.4 dB
Max. Attainable Data Rate (ATTNDR):       Down: 103.579 Mb/s / Up: 36.770 Mb/s
Line Uptime Seconds:                      280
Line Uptime:                              4m 40s

[just2mad]

So vectoring is included in openwrt now? What are you data rates? Do you reach the 90 Mbit/s in download?

…

Am 27.08.2018 um 22:02 schrieb Yaroslav ***@***.***>: Annex B, vectoring work very well on BT Home Hub 5A (openwrt-trunk): ATU-C Vendor ID: Broadcom 192.85 ATU-C System Vendor ID: Broadcom Chipset: Lantiq-VRX200 Firmware Version: 5.9.1.4.0.7 API Version: 4.17.18.6 XTSE Capabilities: 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2 Annex: B Line Mode: G.993.5 (VDSL2 with down- and upstream vectoring) Profile: 17a Line State: UP [0x801: showtime_tc_sync] Forward Error Correction Seconds (FECS): Near: 0 / Far: 43 Errored seconds (ES): Near: 0 / Far: 3 Severely Errored Seconds (SES): Near: 0 / Far: 0 Loss of Signal Seconds (LOSS): Near: 0 / Far: 0 Unavailable Seconds (UAS): Near: 100 / Far: 100 Header Error Code Errors (HEC): Near: 0 / Far: 0 Non Pre-emtive CRC errors (CRC_P): Near: 0 / Far: 0 Pre-emtive CRC errors (CRCP_P): Near: 0 / Far: 0 Power Management Mode: L0 - Synchronized Latency [Interleave Delay]: 0.14 ms [Fast] 0.0 ms [Fast] Data Rate: Down: 90.760 Mb/s / Up: 33.706 Mb/s Line Attenuation (LATN): Down: 12.6 dB / Up: 11.1 dB Signal Attenuation (SATN): Down: 12.6 dB / Up: 10.9 dB Noise Margin (SNR): Down: 8.0 dB / Up: 10.6 dB Aggregate Transmit Power (ACTATP): Down: -1.0 dB / Up: 12.4 dB Max. Attainable Data Rate (ATTNDR): Down: 103.579 Mb/s / Up: 36.770 Mb/s Line Uptime Seconds: 280 Line Uptime: 4m 40s — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread. -- This email was Malware checked by UTM 9. http://www.sophos.com

[Lankaster]

@just2mad no, this version isn't include into openwrt, but you can extract from labor firmware it self.
Yes, i reach about 85Mbit. My DSL line is really bad and i should set the ds_snr_offset '20' for stable connection. ( https://www.dslreports.com/speedtest/33585346 , https://openwrt.org/toh/bt/homehub_v5a?s[]=bt&s[]=hub&s[]=5#und1_germany_vdsl2_annex_b_example )
I think it's possible reach the 100 Mbit/s on good dsl line.

[just2mad]

@Lankaster as I read here https://forum.openwrt.org/t/how-can-we-make-the-lantiq-xrx200-devices-faster/9724 ,there are throughput problems with xrx200 and vr9 chipsets as there is now hw acceleration available.

[Lankaster]

@just2mad at first BT5 haven't VMMC, second: BT5 have a SMP (dualcore) I think it's enough for 100Mbit/s WAN. With SQM shaping i have about 55-70 Mbit/s, but 100% CPU load. Because of CPU load i don't use a shaping. Via WiFi ( AC ) i reach about 20MB/s between my Tablet and NAS (160Mbit/sec).
I am happy with my BT5 :--)

[Lankaster]

@xdarklight Can we add information about new DSL Firmware ?

bk@tt:~/Projects/lantiq-xdsl-firmware-info$ ./ltq-xdsl-fw-info.sh
ltq-xdsl-fw-info.sh: UNKNOWN application type () for UNKNOWN platform (), version: .. | UNKNOWN application type () for UNKNOWN platform (), version: ..
vr9-B-dsl.bin: VDSL over ISDN incl. vectoring support for VRX200, version: 9.1.4 | ADSL Annex B for VRX200, version: 9.0.D
release-vr9-A-dsl.bin: VDSL over ISDN incl. vectoring support for VRX200, version: 7.8.9 | ADSL Annex A for VRX200, version: 7.1.E
vr9-A-dsl.bin: VDSL over ISDN incl. vectoring support for VRX200, version: 9.1.4 | ADSL Annex A for VRX200, version: 9.0.D
release-vr9-B-dsl.bin: VDSL over ISDN incl. vectoring support for VRX200, version: 7.8.9 | ADSL Annex B for VRX200, version: 7.2.4

bk@tt:~/Projects/lantiq-xdsl-firmware-info$ sha1sum *bin
b4c811ce46f6606f93165d03cc125e8db1d88038  release-vr9-A-dsl.bin
539162673a99a05d8343da06bebe7e6c356f0a7d  release-vr9-B-dsl.bin
33bcae8d8b213f3e6213d4553c8e7330fc8512c9  vr9-A-dsl.bin
3c97762499817686c688b71724ab6a329daa81f8  vr9-B-dsl.bin

bk@tt:~/Projects/lantiq-xdsl-firmware-info$ ls -la | grep bin
-rw-r--r--  1 bk bk 913736 Aug 27 21:42 release-vr9-A-dsl.bin
-rw-r--r--  1 bk bk 896592 Aug 27 21:42 release-vr9-B-dsl.bin
-rw-r--r--  1 bk bk 926364 Aug 27 21:42 vr9-A-dsl.bin
-r-xr-xr-x  1 bk bk 908164 Aug 17 16:04 vr9-B-dsl.bin

[alanswanson]

Just to add this is working with ADSL annex A on a TP-Link 8970 in the UK (pending VDSL2 vectoring sometime in the future).

However compared to redistributable 8.0.B, the data rate is the same but the line and signal attenuation are wrong dropping from 26-27dB to 10-12dB for a 13Mb/s connection. Firmware API version remains the same so looks a firmware bug.

[BigNerd95]

What is the difference between Release and Pre-release?

[stonerl]

The firmware can also be found in this stable release for the 7490.

vr9-B-dsl.bin: VDSL over ISDN incl. vectoring support for VRX200, version: 9.1.4 | ADSL Annex B for VRX200, version: 9.0.D

[Borromini]

Verbose script output:

filename: vr9-A-dsl.bin
version: 5.9.1.4.0.7-5.9.0.D.0.1
sha1sum: 33bcae8d8b213f3e6213d4553c8e7330fc8512c9
filesize: 926364
Firmware1:
	PLATFORM: 5
	PLATFORM_STR: VRX200
	APPLICATION_TYPE: 7
	APPLICATION_TYPE_STR: VDSL over ISDN incl. vectoring support
	VERSION_STR: 9.1.4
	RELEASE_STATUS: 0
	RELEASE_STATUS_STR: Release
Firmware2:
	PLATFORM: 5
	PLATFORM_STR: VRX200
	APPLICATION_TYPE: 1
	APPLICATION_TYPE_STR: ADSL Annex A
	VERSION_STR: 9.0.D
	RELEASE_STATUS: 0
	RELEASE_STATUS_STR: Release

filename: vr9-B-dsl.bin
version: 5.9.1.4.0.7-5.9.0.D.0.2
sha1sum: 3c97762499817686c688b71724ab6a329daa81f8
filesize: 908164
Firmware1:
	PLATFORM: 5
	PLATFORM_STR: VRX200
	APPLICATION_TYPE: 7
	APPLICATION_TYPE_STR: VDSL over ISDN incl. vectoring support
	VERSION_STR: 9.1.4
	RELEASE_STATUS: 0
	RELEASE_STATUS_STR: Release
Firmware2:
	PLATFORM: 5
	PLATFORM_STR: VRX200
	APPLICATION_TYPE: 2
	APPLICATION_TYPE_STR: ADSL Annex B
	VERSION_STR: 9.0.D
	RELEASE_STATUS: 0
	RELEASE_STATUS_STR: Release

[nouman8]

A new release is out http://download.avm.de/fritzbox/fritzbox-7490/deutschland/fritz.os/
can someone check if there's any new version.

[pstlr78]

A new release is out http://download.avm.de/fritzbox/fritzbox-7490/deutschland/fritz.os/
can someone check if there's any new version.

I just checked image 07.11:

release-vr9-A-dsl.bin and release-vr9-B-dsl.bin are identical to the ones above. Even the checksum is the same. The "release" version is 5.7.8.9.1.7.

vr9-A-dsl.bin and vr9-B-dsl.bin do have the same firmware version as above (5.9.1.4.0.7), but the checksum is not the same as before. I do not know how I could check the ADSL firmware version (the second part : i.e. 9.0.D) as I am running VDSL.

I assume that even if there is some difference this should be minor.

[nouman8]

Thanks for quick reply...can you plz do the same for the following firmware which also apparently is for vr9 chip.
http://download.avm.de/fritzbox/fritzbox-7362-sl/deutschland/fritz.os/