Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[zxdavb]

Hi jsamuel,

I've just bought one of these units on eBay  , and would like to be able to tinker with the builds.

I can see you've got a .config file on http://vanquishsolutions.co.uk/openwrt/VG3503J/config, but I'd like to white-box it a little.  That is, rather than use make menuconfig to create the .config file, I do something similar to the following BASH script:

Code: [Select]


### Create the .CONFIG file (this WILL survive a make clean)
    VER=trunk;  cd ~/openwrt/${VER}/

cat << 'EOF' > .config
    CONFIG_TARGET_lantiq=y
    CONFIG_TARGET_lantiq_xrx200=y
    CONFIG_TARGET_lantiq_xrx200_VG3503J=y

    ...

EOF

### Finally, populate the config file...
    make defconfig


Could you help an old man out?  This unit hasn't arrived yet, but I am already playing with a build!

[jsamuel]

Nice work iMX - not sure how I missed that typo.

zxdavb I'm not quite sure what you mean to do? My apologies. 

The .config there is one I made specifically for these images using menuconfig - I tried to keep it at a minimum, with the exception of the following packages: luci, muninlite & nano

[zxdavb]

By using a script rather than the user interface to create the config file, we have something that is much easier to deal with, change control being one such example.

For example, to add luci, nano & muninlite:

Code: [Select]

## Create the .config file...
VER=trunk;  cd ~/openwrt/${VER}/

cat << 'EOF' > .config
CONFIG_TARGET_lantiq=y
CONFIG_TARGET_lantiq_xrx200=y
CONFIG_TARGET_lantiq_xrx200_VG3503J=y

CONFIG_PACKAGE_luci=y
CONFIG_PACKAGE_nano=y
CONFIG_PACKAGE_muninlite=y
EOF

### Then, populate the config file...
make defconfig

### Finally...
make -j 5

After creating the .config file, you then do a make defconfig, and all the other crap you see in your .config file (which is currently 6 lines long) get automatically put in (and becomes 100's of lines).  Try it!  The end result is the same as doing it via make menuconfig.

For me, it would help to understand the actual difference between your build and other builds I use.

I am not familar with muninlite, but it is a standard package. To see what I mean, start make menuconfig and type the slash key, and type 'munin' and hit enter.  It should show you something like PACKAGE_muninlite which becomes CONFIG_PACKAGE_muninlite.

I notice you have modulised (i.e. <M> via the UI, or =m via my method) a whole bunch of packages. Why?  I suggest (to keep it simple) you only do it for the ones you need. Or you can use https://downloads.openwrt.org/snapshots/trunk/lantiq/xrx200/packages/?

[zxdavb]

I guess other packages I'd defo be looking at installing are: dnsmasq, ddns-scripts, and sqm-scripts.

Optional packages might include: OpenSSH.

And then it's just a matter of seeing what the hardware will manage.

[digitalis]

Hi guys

I have a v1.1, flashed the image, it went well but now the modem boots up with green/red flashing power light, then finally ends with power and DSL light permanently lit (the modem isn't connected to an active line!). I cannot ping/access 192.168.1.1 via LAN2. Serial access appears to work still.

Any advice appreciated.

[digitalis]

I thought I'd reflash the modem which I was able to do, but still no joy. The final output from serial is below

Code: [Select]

[   90.232000] DSL[00]: Reboot on training timeout (60)!!!
[  156.424000] DSL[00]: Reboot on training timeout (60)!!!
[  184.288000] /home/dev/firmware/openwrt/build_dir/target-mips_34kc+dsp_musl-1.1.10/linux-lantiq_xrx200/ltq-ptm-vr9/ifxmips_ptm_vdsl.c:281:ptm_hard_start_xmit: not in showtime
[  184.300000] /home/dev/firmware/openwrt/build_dir/target-mips_34kc+dsp_musl-1.1.10/linux-lantiq_xrx200/ltq-ptm-vr9/ifxmips_ptm_vdsl.c:281:ptm_hard_start_xmit: not in showtime
[  221.716000] DSL[00]: Reboot on training timeout (60)!!!

I've also attached a complete log file to this post

[rp00]

Hello all
my first post on this forum.

from the first post in this thread:

Don't put the image for the v2 on a v1 otherwise your ethernet ports won't work effectively leaving you with a bricked unit.

Maybe try flashing it with v2 firmware? it's safe as long as bootloader is fine.

[digitalis]

But if the LAN gets screwed how would I change to another firmware after that? I cba with a JTAG, and my chipset definitely says v1.1

[rp00]

http://forum.kitz.co.uk/index.php/topic,15918.msg296860.html#msg296860

ethernet port will still work in bootloader.

[digitalis]

Okay, so I flashed image V2 to my v1.1 and ethernet port now works! Thanks, and very odd eh?

DSL light is still permanently on even though it's not connected to an active line, is this normal?

[rp00]

yup
I've just checked on my spare modem. power and dsl on, lan1,lan2 off

[jsamuel]

Yes, the DSL light always on is "normal" operation (by normal, that's the way I left it) 
Some GPIO-led tweaking is needed to fix it, but it never did bother me that much to warrant a fix.

It's odd that the v2 image will work on the v1.1, are you sure it's not a v2.1 SoC?

[digitalis]

The little chip says v1.1, shame I didn't take a picture as I've put the modem back together now and it was a nightmare getting it apart!

I wonder how difficult it would be to get the DSL light working correctly? I plan on using this modem at work and a working LED would be good for diagnosis from others when I'm not there (my manager wouldn't be able to handle web based management ;-) )

[digitalis]

Oh also, am I right when I say I'll be able to replace our HG612 (connected to an Huwaei cab) with this unlocked ECI and I'll retain G.INP?

[jsamuel]

I never investigated it to be honest, since it's always usually connected, but it requires a change in the profile and a firmware recompile if I recall correctly. it's why I just left it 


Yes, G.INP will work.