Home Automation Domotica Forum Europe, Bwired Forum

Domotica - Home Automation Forum
https://www.domoticaforum.eu/

Toon firmware: issues (and solutions)

https://www.domoticaforum.eu/viewtopic.php?t=11449

Page 4 of 24

Re: Toon firmware: issues (and solutions)

Posted: Sun Aug 20, 2017 2:40 pm
by marcelr
Can you ping your toon when connected through wifi?

Re: Toon firmware: issues (and solutions)

Posted: Sun Aug 20, 2017 4:16 pm
by homesweethome
I can't reach it in any way, ping, html port 10080 port 7080, nothing.
Visible in my router but nowhere else on my network, it does get the latest info from buienradar.

they're all on the same subnet, iptables configured as discriped in 'rooting Toon' no problems at all when connected via utp cable

Re: Toon firmware: issues (and solutions)

Posted: Sun Aug 20, 2017 6:26 pm
by marcelr
When you login to your toon, what do the commands

dmesg

and

ifconfig

say?

Re: Toon firmware: issues (and solutions)

Posted: Sun Aug 20, 2017 10:50 pm
by homesweethome
i had to connect Toon by cable again, else i can't query it
having done that, here are the results ( had to reconnect wireless in the settings page because ifconfig was not showing any wlan info)

Code: Select all

:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0F:11:04:09:92
          inet addr:192.168.1.120  Bcast:0.0.0.0  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2717 errors:0 dropped:0 overruns:0 frame:0
          TX packets:701 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:265403 (259.1 KiB)  TX bytes:89746 (87.6 KiB)
          Base address:0xc000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:18959 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18959 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:8264243 (7.8 MiB)  TX bytes:8264243 (7.8 MiB)

wlan0     Link encap:Ethernet  HWaddr 40:E2:30:3F:6B:68
          inet addr:192.168.1.125  Bcast:0.0.0.0  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:206 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:820416 (801.1 KiB)  TX bytes:37210 (36.3 KiB)
ping results:

Code: Select all

so my Toon's wifi address is 192.168.1.125 and Toon's nic address is 192.1658.1.120
the host i was pinging from was 192.168.1.85 (via wifi)

Pinging 192.168.1.125 with 32 bytes of data:
Reply from 192.168.1.125: bytes=32 time=123ms TTL=64
Reply from 192.168.1.125: bytes=32 time=25ms TTL=64
Reply from 192.168.1.125: bytes=32 time=8ms TTL=64
Reply from 192.168.1.125: bytes=32 time=18ms TTL=64

Ping statistics for 192.168.1.125:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 8ms, Maximum = 123ms, Average = 43ms

ping toon

Pinging toon [192.168.1.125] with 32 bytes of data:
Reply from 192.168.1.125: bytes=32 time=12ms TTL=64
Reply from 192.168.1.125: bytes=32 time=4ms TTL=64
Reply from 192.168.1.125: bytes=32 time=1ms TTL=64
Reply from 192.168.1.125: bytes=32 time=4ms TTL=64

Ping statistics for 192.168.1.125:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 12ms, Average = 5ms

ping 192.168.1.120

Pinging 192.168.1.120 with 32 bytes of data:
Reply from 192.168.1.120: bytes=32 time=1ms TTL=64
Reply from 192.168.1.120: bytes=32 time=1ms TTL=64
Reply from 192.168.1.120: bytes=32 time=1ms TTL=64
Reply from 192.168.1.120: bytes=32 time=10ms TTL=64

Ping statistics for 192.168.1.120:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 10ms, Average = 3ms
	
and as soon as i take out the cable, .125 (wifi) isn't reachable (like .120 which is cable)
and dmesg:

Code: Select all

~# dmesg
Linux version 2.6.36-R10-h27 (jbraam@dvl) (gcc version 4.5.3 20110223 (prerelease) (GCC) ) #1 PREEMPT Tue Oct 25 20:03:05 CEST 2016
CPU: ARM926EJ-S [41069264] revision 4 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Prodrive B.V ED2.0
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 32768
free_area_init_node: node 0, pgdat c03a119c, node_mem_map c03c5000
  Normal zone: 256 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 32512 pages, LIFO batch:7
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Kernel command line: ubi.mtd=4 root=ubi0:rootfs rw rootfstype=ubifs mtdparts=mxc_nand:512K@0x00100000(u-boot-env)ro,1536K(splash-image),3M(kernel),3M(kernel-backup),119M(rootfs) console=ttymxc0,115200 mem=128M lpj=999424
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 126092k/126092k available, 4980k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffa00000 - 0xffe00000   (   4 MB)
    vmalloc : 0xc8800000 - 0xf4000000   ( 696 MB)
    lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .init : 0xc0008000 - 0xc0022000   ( 104 kB)
      .text : 0xc0022000 - 0xc0367000   (3348 kB)
      .data : 0xc037e000 - 0xc03a17a0   ( 142 kB)
Hierarchical RCU implementation.
        RCU-based detection of stalled CPUs is disabled.
        Verbose stalled-CPUs detection is disabled.
NR_IRQS:272
MXC IRQ initialized
MXC GPIO hardware
Console: colour dummy device 80x30
Calibrating delay loop (skipped) preset value.. 199.88 BogoMIPS (lpj=999424)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Configured for LCD: TM070RDH11
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource mxc_timer1
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
msgmni has been set to 246
io scheduler noop registered (default)
imx-fb imx-fb.0: PreserveUBootFramebuffer(1): xres=800, yres=480 [skip _update_lcdc]
imx-fb imx-fb.0: PreserveUBootFramebuffer(2): xres=800, yres=480 [skip _update_lcdc]
Console: switching to colour frame buffer device 100x30
imx-fb imx-fb.0: fb0: DISP0 BG fb device registered successfully.
imx-fb imx-fb.0: PreserveUBootFramebuffer(3): xres=800, yres=480 [skip _update_lcdc]
imx-fb imx-fb.0: fb1: DISP0 FG fb device registered successfully.
Serial: IMX driver
imx-uart.0: ttymxc0 at MMIO 0x1000a000 (irq = 20) is a IMX
console [ttymxc0] enabled
imx-uart.1: ttymxc1 at MMIO 0x1000b000 (irq = 19) is a IMX
imx-uart.2: ttymxc2 at MMIO 0x1000c000 (irq = 18) is a IMX
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 666 at 0x000005340000
Bad eraseblock 789 at 0x0000062a0000
RedBoot partition parsing not available
5 cmdlinepart partitions found on MTD device mxc_nand
Creating 5 MTD partitions on "mxc_nand":
0x000000100000-0x000000180000 : "u-boot-env"
0x000000180000-0x000000300000 : "splash-image"
0x000000300000-0x000000600000 : "kernel"
0x000000600000-0x000000900000 : "kernel-backup"
0x000000900000-0x000008000000 : "rootfs"
UBI: attaching mtd4 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: max. sequence number:       105642
UBI: attached mtd4 to ubi0
UBI: MTD device name:            "rootfs"
UBI: MTD device size:            119 MiB
UBI: number of good PEBs:        950
UBI: number of bad PEBs:         2
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 950
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 363/110
UBI: image sequence number:  832555421
UBI: background thread "ubi_bgt0d" started, PID 309
at25 spi0.0: 32 KByte at25640B eeprom, pagesize 64
spi_imx spi_imx.0: probed
FEC Ethernet Driver
fec_enet_mii_bus: probed
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
mxc-ehci mxc-ehci.0: initializing i.MX USB Controller
mxc-ehci mxc-ehci.0: portsc setup 1: 0x80000000
mxc-ehci mxc-ehci.0: Work around for USB enabled
ULPI transceiver vendor/product ID 0x0424/0x000d
mxc-ehci mxc-ehci.0: Freescale On-Chip EHCI Host Controller
mxc-ehci mxc-ehci.0: new USB bus registered, assigned bus number 1
mxc-ehci mxc-ehci.0: irq 56, io mem 0x10024000
mxc-ehci mxc-ehci.0: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: Freescale On-Chip EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.36-R10-h27 ehci_hcd
usb usb1: SerialNumber: mxc-ehci.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
mxc-ehci mxc-ehci.2: initializing i.MX USB Controller
mxc-ehci mxc-ehci.2: portsc setup 1: 0x80000000
mxc-ehci mxc-ehci.2: Work around for USB enabled
mxc-ehci mxc-ehci.2: Freescale On-Chip EHCI Host Controller
mxc-ehci mxc-ehci.2: new USB bus registered, assigned bus number 2
mxc-ehci mxc-ehci.2: irq 55, io mem 0x10024400
mxc-ehci mxc-ehci.2: USB 2.0 started, EHCI 1.00
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: Freescale On-Chip EHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.36-R10-h27 ehci_hcd
usb usb2: SerialNumber: mxc-ehci.2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
usbserial: USB Serial Driver core
input: TSC2007 Touchscreen as /devices/virtual/input/input0
rtc-isl1208 1-006f: chip found, driver version 0.3
rtc-isl1208: dev (254:0)
rtc-isl1208 1-006f: rtc core: registered rtc-isl1208 as rtc0
i2c /dev entries driver
tmp431 0-004c: Could not read configuration register (-5)
imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=0)
Registered led device: led0
Registered led device: led1
adt7410 0-0048: adt7410 temperature sensor registered.
adt7410 0-0049: adt7410 temperature sensor registered.
nf_conntrack version 0.5.0 (1970 buckets, 7880 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
Bridge firewalling registered
rtc-isl1208 1-006f: setting system clock to 2017-08-20 19:53:29 UTC (1503258809)
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   119476224 bytes (116676 KiB, 113 MiB, 926 LEBs)
UBIFS: journal size:       9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:13.
Freeing init memory: 104K
usb 2-1: new high speed USB device using mxc-ehci and address 2
usb 2-1: New USB device found, idVendor=148f, idProduct=5370
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1: Product: 802.11 n WLAN
usb 2-1: Manufacturer: Ralink
usb 2-1: SerialNumber: 1.0
usbcore: registered new interface driver r871x_usb_drv
usbcore: registered new interface driver rt2870
eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:10, irq=-1)
PHY: 1:10 - Link is Up - 100/Full
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
NVM is Efuse and its size =2d[2d0-2fc]
phy mode> Error! The chip does not support 5G band 15!
RTMPSetPhyMode: channel is out of range, use first channel=1
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
AntCfgInit: primary/secondary ant 0/1
0x1300 = 00064300
Rcv Wcid(1) AddBAReq
Start Seq = 00000000
imx-fb imx-fb.0: PreserveUBootFramebuffer(4): xres=800, yres=480 [do _update_lcdc]
backlight ed2.0-bl.0: ramp brightness from 083 to 000 delay 1 [sync]
backlight ed2.0-bl.0: ramp brightness from 083 to 000 delay 1 [done]
backlight ed2.0-bl.0: ramp brightness from 000 to 100 delay 15 [sync]
backlight ed2.0-bl.0: ramp brightness from 000 to 100 delay 15 [done]
ERROR!!! RTMPSetTimer failed, Halt in Progress!
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
NVM is Efuse and its size =2d[2d0-2fc]
phy mode> Error! The chip does not support 5G band 15!
RTMPSetPhyMode: channel is out of range, use first channel=1
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
AntCfgInit: primary/secondary ant 0/1
0x1300 = 00064300

Re: Toon firmware: issues (and solutions)

Posted: Sun Aug 20, 2017 11:17 pm
by marcelr
From the dmesg output, I think it's a router problem:

Code: Select all

phy mode> Error! The chip does not support 5G band 15!
RTMPSetPhyMode: channel is out of range, use first channel=1
The wifi chipset of toon supports 2.4GHz wifi only. It seems to be offered 5GHz access only, and that's a no-go for toon.
So, try and configure your router to use the 2.4 GHz band for wifi as well.

Re: Toon firmware: issues (and solutions)

Posted: Mon Aug 21, 2017 12:50 pm
by homesweethome
That's strange, my router can't offer 5GHz, it's a Technicolor TG789bvn which only offers 2,4GHz, i will look for my old router (Asus WL520 with DD-WRT) which i will test as soon as i'm home

Re: Toon firmware: issues (and solutions)

Posted: Mon Aug 21, 2017 7:51 pm
by homesweethome
Installed an old router, connect Toon to old router, no access via SSH no ping an hour later i saw in my 'new' router Toon's connected again, i tried ssh and succes!
did a dmesg and saw still the error about 5G.

now my Toon is connected same as before but i'm able to ping an connect to Toon with ssh, i think this isn't gonna last but until then i count my blessings :)

Re: Toon firmware: issues (and solutions)

Posted: Mon Aug 21, 2017 7:59 pm
by marcelr
Maybe one or both of the wifi antennas came loose when you reasssembled your toon?

Re: Toon firmware: issues (and solutions)

Posted: Mon Aug 28, 2017 9:37 pm
by makkie2002
Hi all,

Does any of you noticed inconsistent "dimmed screen" behaviour.
On some occasions the screen goes completely off, although the current state is in "thuis" or "comfort".
Sometimes it is OK.
I am unable to exactly reproduce under which conditions this happens, ... need to try some more.
It would be great if this behaviour happens with other people too, so we debug together :mrgreen: .

I am on 4.4.21 fw.

Re: Toon firmware: issues (and solutions)

Posted: Mon Aug 28, 2017 9:43 pm
by marcelr
My production toon has similar issues (fw 3.2.18)

Doesn't really bother me, though.

Re: Toon firmware: issues (and solutions)

Posted: Mon Aug 28, 2017 11:24 pm
by makkie2002
Strange, do you think this can be an effect of rooting or is this also happening on "virgin" Toons?
If it is on virgin models too, is there a way we can put this upstream with the Quby developers as it affects > 100.000 installations.
Do you know of an "official" Toon forum were I can bring this up?

Re: Toon firmware: issues (and solutions)

Posted: Tue Aug 29, 2017 7:59 am
by marcelr
You could bring it up in the thread "Suggesties, ideeen, verbeterpunten" of the official toon forum:

https://forum.toon.nl

It's an open forum for toon related matters, operated by Eneco.

Re: Toon firmware: issues (and solutions)

Posted: Wed Sep 06, 2017 12:41 pm
by PowerAce
Hello all,

After reading a lot on this forum about the possibilities of Toon I also decided to buy a second hand Toon.
Thanks to the clear manuals I successfully rooted my Toon as well. My Toon has an old firmware version (2.10.15) which doesn't have the QT-gui. Of course I like to install a few of the recently developed apps to take more advantage of the possibilities of Toon. From this thread I understood that updating Toon firmware is only possible using a subscription which I don't have.

Now I found out that there is a bunch of ipk files waiting to be installed on my Toon. The command opkg list-upgradable gives me a long list of program(parts) that can be updated. One of them is called "base-qb2-ene - 2.10.15-892-0 - 3.6.3-1022-0".

Now my question: Am I right that all necessary files for updating my Toon to firmware version 3.6.3. are present on my Toon? And what command do I need to use for updating to 3.6.3.? In the software menu's I can't find a button for updating the firmware.

Re: Toon firmware: issues (and solutions)

Posted: Wed Sep 06, 2017 2:57 pm
by raiden1985
By using your great guides I managed to root my toon. Thanks! :D

While browsing the forums yesterday I saw a post regarding updating the tariffs Toon computes with to the ones I am getting from budgetenergie. But I am unable to find this post today?

Does anyone have experience in updating those tariffs ?

Re: Toon firmware: issues (and solutions)

Posted: Wed Sep 06, 2017 11:06 pm
by michel30
Hello,

For add your own price you need to edit this file: vi /qmf/qml/qb/base/Globals.qml

On the top of the file you will find the price.
All times are UTC+02:00
Page 4 of 24

Powered by phpBB® Forum Software © phpBB Limited