Modify

Opened 4 years ago

Last modified 3 years ago

#15057 assigned defect

Fix / Support for Both Versions of the BT ECI VG3503J.

Reported by: anonymous Owned by: blogic
Priority: normal Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: Cc:

Description

There are two versions of the BT Openreach modem VG3503J 1-A-DC & "VG3503J-A-DC [1.1 vr9 chip]

From BT's opensource
proj_cfg.h
#define PROJ_MODEL_NAME "VG3503J 1-A-DC"
#define PROJ_SIGNATURE "ECIBT_TP1A"

This VG3503J 1-A-DC is supported by openwrt and runs the ROM 1.0.5 and GPHY Firmware 0x8400. 2012 with vr9_phy22f_a1x.bin.

roj_ver.h

define DDR_TYPE 2 1 : DDR1, 2 : DDR2#if (DDR_TYPE == 1) DDR1
Bootloader Version

#define PROJ_BLOADER_VERSION_MAJOR_NUM 0#define 0#define

PROJ_BLOADER_VERSION_MINOR_NUM 1#define
PROJ_BLOADER_VERSION_SUB_MINOR_NUM 4#define
PROJ_BLOADER_VERSION_TEST_NUM 0#elif (DDR_TYPE == 2) DDR2
Bootloader Version

#define PROJ_BLOADER_VERSION_MAJOR_NUM 0#define

PROJ_BLOADER_VERSION_MINOR_NUM 2#define
PROJ_BLOADER_VERSION_SUB_MINOR_NUM 4#define
PROJ_BLOADER_VERSION_TEST_NUM 0#endif#define
PROJ_IMAGE_VERSION_MAJOR_NUM 1#define
PROJ_IMAGE_VERSION_MINOR_NUM 1#define
PROJ_IMAGE_VERSION_SUB_MINOR_NUM 6#define
PROJ_IMAGE_VERSION_TEST_NUM 0 Morgan add.
Number 0 means formal release and will not be shown up.


This Newer VG3503J-A-DC Vesion uses ROM 1.1.4 and GPHY Firmware 0x0405.2013 and with vr9_phy22f_a2x.bin. [1.2 vr9 chip]

The lan ports are dead when openwrt current ECI xrx200 target.

BT Opensource "define PROJ_MODEL_ if it helps.

define PROJ_MODEL_NAME "VG3503J-A-DC"
#define PROJ_SIGNATURE "ECIBT_TP1A"

#define PROJ_BLOADER_VERSION_MAJOR_NUM_STR "0"#define
PROJ_BLOADER_VERSION_MINOR_NUM_STR "01"#define
PROJ_BLOADER_VERSION_SUB_MINOR_NUM_STR "03"#define
PROJ_IMAGE_VERSION_MAJOR_NUM 0#define
PROJ_IMAGE_VERSION_MINOR_NUM 1#define
PROJ_IMAGE_VERSION_SUB_MINOR_NUM 6

http://www.openreach.co.uk/orpg/home/products/super-fastfibreaccess/super-fastfibreaccess/landrgnu.do


If this could be fixed it would be great !

Thanks

Attachments (0)

Change History (21)

comment:1 Changed 4 years ago by anonymous

I wonder if these modems are the B-FOCuS V-2FUb/I Rev.B and B-FOCuS V-2FUb/R Rev.B, please?

comment:2 Changed 4 years ago by anonymous

Both are the ECI r model ( the "I" different all together option)

The B-FOCuS V-2FUb/r Rev.B (2012) [ VG3503J 1-A-DC ]date range 2012 has the 1.1 vr9 with the ROM 1.0.5 and GPHY Firmware 0x8400. 2012

The B-FOCuS V-2FUb/r Rev.B (2013) [ VG3503J -A-DC ] current 2013 on wards has ROM 1.1.4 and GPHY Firmware 0x0405.2013.

The Source code is here if it helps?

http://www.openreach.co.uk/orpg/home/products/super-fastfibreaccess/super-fastfibreaccess/landrgnu.do

Tried the recent Uboot patches but no luck...

Hopefully the clever people on here can help.
Thanks

comment:3 Changed 4 years ago by anonymous

Binwalk of a backup of the original firmware shows the GPHY firmware is stored in the flash.

Presumably it can be changed / reverted to the older ECI /r's GPHY firmware so OpenWrt could work with the newer ROM 1.1.4 and GPHY Firmware 0x0405 ?


/mnt/share/rw/eci_r-1.0.5$ binwalk original-firmware-8mb.bin

DECIMAL HEX DESCRIPTION


19132 0x4ABC uImage header, header size: 64 bytes, header CRC: 0x2C94DEF7, created: Fri May 25 06:44:51 2012, image size: 51504 bytes, Data Address: 0xA0400000, Entry Point: 0xA0400000, data CRC: 0xEE3E562A, OS: Linux, CPU: MIPS, image type: Firmware Image, compression type: lzma, image name: "u-boot image"
19164 0x4ADC U-Boot boot loader reference
19196 0x4AFC LZMA compressed data, properties: 0x5D, dictionary size: 8388608 bytes, uncompressed size: 140248 bytes
73728 0x12000 uImage header, header size: 64 bytes, header CRC: 0x1172B473, created: Wed Sep 7 06:37:02 2011, image size: 56332 bytes, Data Address: 0x0, Entry Point: 0x0, data CRC: 0x943FCF00, OS: Linux, CPU: MIPS, image type: Multi-File Image, compression type: lzma, image name: "GPHY Firmware"
73800 0x12048 LZMA compressed data, properties: 0x5D, dictionary size: 8388608 bytes, uncompressed size: 262400 bytes
135168 0x21000 uImage header, header size: 64 bytes, header CRC: 0x43809A6F, created: Thu Jun 14 09:07:15 2012, image size: 942624 bytes, Data Address: 0x80002000, Entry Point: 0x802C4000, data CRC: 0x47732E02, OS: Linux, CPU: MIPS, image type: OS Kernel Image, compression type: lzma, image name: "MIPS IFXCPE Linux-2.6.20.19"
135232 0x21040 LZMA compressed data, properties: 0x5D, dictionary size: 8388608 bytes, uncompressed size: 3051672 bytes
1179648 0x120000 Squashfs filesystem, big endian, lzma signature, version 3.0, size: 2072326 bytes, 769 inodes, blocksize: 65536 bytes, created: Thu Jun 14 09:07:17 2012
7602176 0x740000 JFFS2 filesystem, big endian
8126464 0x7C0000 gzip compressed data, from Unix, last modified: Sat Jan 1 00:01:22 2000, max compression
8192000 0x7D0000 gzip compressed data, from Unix, last modified: Sat Jan 1 00:01:22 2000, max compression
8257544 0x7E0008 gzip compressed data, from Unix, last modified: Sat Jan 1 00:00:21 2000, max compression
8324066 0x7F03E2 U-Boot boot loader reference


Thanks

comment:4 Changed 4 years ago by anonymous

Don't know if this is relevant or not ?

But the Astoria Networks ARV7519RW22 also has the same two variants of firmware.

http://wiki.openwrt.org/toh/arcadyan/arv7519

"Important note
Models manufactured before 2013 have VR version 1.1 and eth phy fw is vr9_phy11g_a1x.bin. For 2013 built models (VR 1.2) is vr9_phy11g_a2x.bin "

Thanks

comment:5 Changed 4 years ago by anonymous

Did you try to load the later firmware, vr9_phy11g_a2x.bin, on the 2013 model?

comment:6 Changed 4 years ago by anonymous

Tried a few things including that & the newer UBoot patches in patchwork. {No Luck as of yet}

comment:7 Changed 4 years ago by anonymous

I see 4 firmware blobs for this series of devices. Guess you have tried them all? Seems to me the later rev is being used in ZyXel P-2812HNU-F3

comment:8 Changed 4 years ago by anonymous

Looking for these firmwares in trunk DTS files, I see three in use:

./target/linux/lantiq/dts/VG3503J.dts uses vr9_phy22f_a1x.bin
./target/linux/lantiq/dts/TDW8970.dts uses vr9_phy11g_a2x.bin
./target/linux/lantiq/dts/FRITZ3370.dts uses vr9_phy11g_a1x.bin

There are four firmware bin files at Daniel Schwierzeck's github repository, https://github.com/danielschwierzeck/firmware-lantiq/tree/master/lantiq

vr9_phy11g_a1x.bin
vr9_phy11g_a2x.bin
vr9_phy22f_a1x.bin
vr9_phy22f_a2x.bin

I wonder if the last of these might work?

comment:9 Changed 4 years ago by anonymous

2013 --->

PSB 80910 EL
v1.2
xway vrx268
7G30301B02
H1318

On the secondary [single] ethernet PHY chip

PSB 80190V
V1.1
XWAY VRX200
UMST4J3L01

Might help your quest.

comment:10 Changed 4 years ago by anonymous

i found this today and wondered if it works with an eci b-focus v-2fub/r rev.b vdsl modem

https://github.com/danielschwierzeck/openwrt-lantiq

comment:11 follow-up: Changed 4 years ago by vrx200

Thanks for the help with this unit.

Can confirm the new dts files works as both lan ports are operational.!

Thank you!

Last edited 4 years ago by vrx200 (previous) (diff)

comment:12 Changed 4 years ago by florian

  • Owner changed from developers to blogic
  • Status changed from new to assigned

Is there anything that is needed from OpenWrt at this point?

comment:13 Changed 4 years ago by vrx200

Its no problem manually changing the dts files to suit.

Some Phy's are causing a very long boot process and some put through issues, so a little more beta testing is required for now, just to see which works best for each unit variant.

Thanks for the continued support!

Last edited 4 years ago by vrx200 (previous) (diff)

comment:14 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

comment:15 in reply to: ↑ 11 Changed 3 years ago by anonymous

Replying to vrx200:

Thanks for the help with this unit.

Can confirm the new dts files works as both lan ports are operational.!

Thank you!

I have just built an images for this device, but the Ethernet ports are still dead? I'm about to try rebuilding with a copy of vdsl.bin, but I now assume I still need to make more changes to get the Ethernet working. Is it possible someone could post more precise rebuild instructions ?

Vdsl file info /ticket/15666.html
For the BT Openreach VG3503J, you should download ECI_Arcadyan_VDSL_modem.zip from ​http://www.openreach.co.uk/orpg/home/products/super-fastfibreaccess/super-fastfibreaccess/landrgnu.do. In that archive, you find the DSL firmware binaries in dsl_vr9_firmware_xdsl-05.04.07.09.01.06_05.04.04.04.01.01.tar.gz located in the dl subfolder. Extract xcpe_hw.bin and save it on the modem as /lib/firmware/vdsl.bin. After that you should be able to get the status with /etc/init.d/dsl_control status.
I have created ./files/lib/firmware structure and included the extracted file named vdsl.bin

comment:16 Changed 3 years ago by anonymous

bit more info added,

VR9 # reset
ROM VER: 1.0.5
CFG 01
DDR autotuning Rev 0.3c
DDR size from 0xa0000000 - 0xa3ffffff
DDR check ok... start booting...

VG3503J 1-A-DC BootLoader v2.00.01 (May 25 2012 - 13:44:42)

CLOCK CPU 333M RAM 166M
DRAM: 32 MiB
Flash: 8 MiB
In: serial
Out: serial
Err: serial
Net: Internal phy(GE) firmware version: 0x8400
vr9 Switch
Using vr9 Switch device
ping failed; host 1.1.1.1 is not alive
## Starting application at 0x80002000 ...

[ 1.312000] phy-xrx200 gphy-xrx200.7: requesting lantiq/vr9_phy22f_a2x.bin

CHAOS CALMER (Bleeding Edge, r43757)

mkdir -vp ./files/lib/firmware/lantiq
cp ./xcpe_hw.bin ./files/lib/firmware/vdsl.bin
cp ./vr9_phy22f_a2x.bin ./files/firmware/lantiq/vr9_phy22f_a2x.bin

make

comment:17 Changed 3 years ago by anonymous

Ok so I've rebuilt the image and now have both files in the image and on the device but still not Ethernet ports working ? Anyone have a clue?

comment:18 Changed 3 years ago by anonymous

found the issue, was using V2 image on V1 device.

VG3503J-1-A-DC uses ROM 1.0.5 and GPHY Firmware 0x8400. 2012 [1.1 vr9 chip] vr9_phy22f_a1x.bin [TARGETPROFILE= VG3503J ]

VG3503J-A-DC uses ROM 1.1.4 and GPHY Firmware 0x0405. 2013 [1.2 vr9 chip] vr9_phy22f_a2x.bin [TARGETPROFILE= VG3503J_V2 ]

comment:19 follow-up: Changed 3 years ago by anonymous

working build with included vdsl.bin and vr9_phy22f_a1x.bin , however it needs a bit more work.

the device originally reports as

ROM VER: 1.0.5
CFG 01
DDR autotuning Rev 0.3c
DDR size from 0xa0000000 - 0xa3ffffff
DDR check ok... start booting...

VG3503J 1-A-DC BootLoader v2.00.01 (May 25 2012 - 13:44:42)

CLOCK CPU 333M RAM 166M
DRAM: 32 MiB
Flash: 8 MiB
In: serial
Out: serial
Err: serial
Net: Internal phy(GE) firmware version: 0x8400
vr9 Switch

Board Name : BFocusV2FubR
Bloader Version : v2.00.01

BuildDate : 2012/06/14 16:07:18

PPE datapath driver info:

Version ID: 128.3.3.1.0.0.1
Family : N/A
DR Type : Normal Data Path | Indirect-Fast Path
Interface : MII0 | MII1
Mode : Routing
Release : 0.0.1

PPE 0 firmware info:

Version ID: 7.1.5.1.0.33
Family : VR9
FW Type : Standard
Interface : MII0/1 + PTM
Mode : reserved - 1
Release : 0.33

PPE 1 firmware info:

Version ID: 7.2.1.6.1.12
Family : VR9
FW Type : Acceleration
Interface : MII0 + MII1
Mode : Bridging + IPv4 Routing
Release : 1.12

PPA API --- init successfully

using image openwrt-lantiq-xrx200-VG3503J-squashfs.image with the vdsl.bin and vr9_phy22f_a1x.bin included in the build r43757. i have access to a lot of logs from the device as provided, but will refrain from posting unless requested.

Issues :

LAN PORT 1 missing erratic front LED and only amber on rear
LAN PORT 2 missing front LED and only amber on rear

comment:20 in reply to: ↑ 19 Changed 3 years ago by anonymous

Forgot to Add OpenWrt errors

BusyBox v1.22.1 (2015-01-15 16:55:27 GMT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

_

| |.-----.-----.-----.| | | |.----.| |_

| - |_
_ | -| | | _ _|
|_||| ||

|| W I R E L E S S F R E E D O M

-----------------------------------------------------
CHAOS CALMER (Bleeding Edge, r43757)
-----------------------------------------------------

  • 1 1/2 oz Gin Shake with a glassful
  • 1/4 oz Triple Sec of broken ice and pour
  • 3/4 oz Lime Juice unstrained into a goblet.
  • 1 1/2 oz Orange Juice
  • 1 tsp. Grenadine Syrup

-----------------------------------------------------

root@OpenWrt:/# dmesg | grep -iE '(error|warn|fail|firmware|mac)'
[ 0.000000] MIPS: machine is VG3503J - BT OpenReach VDSL Modem
[ 1.172000] pcie_rc_initialize link up failed!!!!!
[ 1.320000] phy-xrx200 gphy-xrx200.7: booting GPHY0 firmware at 18C0000
[ 1.328000] phy-xrx200 gphy-xrx200.7: booting GPHY1 firmware at 18C0000
[ 1.740000] net-xrx200: invalid MAC, using random
[ 1.908000] UBIFS error (pid 1): ubifs_mount: cannot open "ubi0:rootfs", error -19
[ 21.156000] PTM 1.0.27 PTM (E1) firmware version 0.30
root@OpenWrt:/# dmesg | grep -iE '(phy|pci)'
[ 0.000000] Determined physical RAM map:
[ 0.092000] arch/mips/pci/ifxmips_pcie_vr9.h:pcie_device_rst_assert[185]
[ 0.204000] arch/mips/pci/ifxmips_pcie_vr9.h:pcie_device_rst_deassert[193]
[ 0.304000] ifx_pcie_wait_phy_link_up timeout
[ 0.308000] arch/mips/pci/ifxmips_pcie_vr9.h:pcie_device_rst_assert[185]
[ 0.420000] arch/mips/pci/ifxmips_pcie_vr9.h:pcie_device_rst_deassert[193]
[ 0.520000] ifx_pcie_wait_phy_link_up timeout
[ 0.524000] arch/mips/pci/ifxmips_pcie_vr9.h:pcie_device_rst_assert[185]
[ 0.636000] arch/mips/pci/ifxmips_pcie_vr9.h:pcie_device_rst_deassert[193]
[ 0.736000] ifx_pcie_wait_phy_link_up timeout
[ 0.740000] arch/mips/pci/ifxmips_pcie_vr9.h:pcie_device_rst_assert[185]
[ 0.852000] arch/mips/pci/ifxmips_pcie_vr9.h:pcie_device_rst_deassert[193]
[ 0.952000] ifx_pcie_wait_phy_link_up timeout
[ 0.956000] arch/mips/pci/ifxmips_pcie_vr9.h:pcie_device_rst_assert[185]
[ 1.068000] arch/mips/pci/ifxmips_pcie_vr9.h:pcie_device_rst_deassert[193]
[ 1.168000] ifx_pcie_wait_phy_link_up timeout
[ 1.172000] pcie_rc_initialize link up failed!!!!!
[ 1.272000] PCI: CLS 0 bytes, default 32
[ 1.312000] phy-xrx200 gphy-xrx200.7: requesting lantiq/vr9_phy22f_a1x.bin
[ 1.320000] phy-xrx200 gphy-xrx200.7: booting GPHY0 firmware at 18C0000
[ 1.328000] phy-xrx200 gphy-xrx200.7: booting GPHY1 firmware at 18C0000
[ 1.736000] libphy: lantiq,xrx200-mdio: probed
[ 1.808000] eth0: attached PHY [Lantiq XWAY XRX PHY22F v1.4] (phy_addr=0:11, irq=-1)
[ 1.876000] eth0: attached PHY [Lantiq XWAY XRX PHY22F v1.4] (phy_addr=0:13, irq=-1)

Replying to anonymous:

working build with included vdsl.bin and vr9_phy22f_a1x.bin , however it needs a bit more work.

the device originally reports as

ROM VER: 1.0.5
CFG 01
DDR autotuning Rev 0.3c
DDR size from 0xa0000000 - 0xa3ffffff
DDR check ok... start booting...

VG3503J 1-A-DC BootLoader v2.00.01 (May 25 2012 - 13:44:42)

CLOCK CPU 333M RAM 166M
DRAM: 32 MiB
Flash: 8 MiB
In: serial
Out: serial
Err: serial
Net: Internal phy(GE) firmware version: 0x8400
vr9 Switch

Board Name : BFocusV2FubR
Bloader Version : v2.00.01

BuildDate : 2012/06/14 16:07:18

PPE datapath driver info:

Version ID: 128.3.3.1.0.0.1
Family : N/A
DR Type : Normal Data Path | Indirect-Fast Path
Interface : MII0 | MII1
Mode : Routing
Release : 0.0.1

PPE 0 firmware info:

Version ID: 7.1.5.1.0.33
Family : VR9
FW Type : Standard
Interface : MII0/1 + PTM
Mode : reserved - 1
Release : 0.33

PPE 1 firmware info:

Version ID: 7.2.1.6.1.12
Family : VR9
FW Type : Acceleration
Interface : MII0 + MII1
Mode : Bridging + IPv4 Routing
Release : 1.12

PPA API --- init successfully

using image openwrt-lantiq-xrx200-VG3503J-squashfs.image with the vdsl.bin and vr9_phy22f_a1x.bin included in the build r43757. i have access to a lot of logs from the device as provided, but will refrain from posting unless requested.

Issues :

LAN PORT 1 missing erratic front LED and only amber on rear
LAN PORT 2 missing front LED and only amber on rear

comment:21 Changed 3 years ago by anonymous

So does this mean OpenWRT can be installed (and work) on the ECI modem?

Add Comment

Modify Ticket

Action
as assigned .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.