Home Automation Domotica Forum Europe, Bwired Forum

Posted: **Thu Feb 18, 2016 12:27 pm**

Excellent

Next 'question', you can still update to firmware 3.0/3.2 without subscription (i read a vpn tunnel should exist?)?

Posted: **Thu Feb 18, 2016 2:35 pm**

hvxl wrote:I blocked all external traffic. I tried opening up buienrader.nl to get the weather information, but unfortunately it doesn't work that way. So there's nothing the Toon needs from the internet (it pings a local server as a connectivity check and also gets its time from there).

Thanks for your answer.

Today I blocked Toon from accessing my router based on the mac adress. Unfortunately it does not work for me. My toon is not rooted or anything. I only get the standard tiles you get without subscription.

Still it bugs the hell out of me, i can not access my own freaking data. Its ridiculous.

Posted: **Thu Feb 18, 2016 7:43 pm**

you can still update to firmware 3.0/3.2 without subscription (i read a vpn tunnel should exist?)

Never tried, but I don't think so. There probably won't be a set of upgrade packages sitting there waiting for you.

Still it bugs the hell out of me, i can not access my own freaking data. Its ridiculous.

File a complaint at Eneco's.

Or root your toon. (Although there's still some work to do, then).

grtz,

marcelr

Posted: **Thu Feb 18, 2016 8:28 pm**

Software updates are part of the subscription. You have to root it to update it manually.
Manually means root it, copying packages (I have them) and start the update script. That's all.

And no, without subscription you cannot (not without root that is) access your own data.
Toon op afstand is also part of the same subscription.
So without subscription, even the basic subscription, Toon is nothing but a very expensive useless Thermostat.
Root it and you're king.

Posted: **Sat Feb 20, 2016 10:22 pm**

To continue with my resuscitation activities:

The patient's not dead yet

.

Today I got my tftpboot setup working and I successfully booted one of the kernels I made with the source tarball of quby's.

Here's the result:

Code: Select all

U-Boot 2010.09-R6 (Mar 14 2012 - 11:15:10)                                      
                                                                                
CPU:   Freescale i.MX27 at 400.168 MHz                                          
                                                                                
Prodrive B.V. ED2.0                                                             
DRAM:  128 MiB                                                                  
NAND:  128 MiB                                                                  
LCD: Initializing LCD frambuffer at a1400000                                    
LCD: 800x480, pbb 4                                                             
LCD: Drawing the logo...                                                        
In:    serial                                                                   
Out:   serial                                                                   
Err:   serial                                                                   
Error: no valid bmp image at a1d214a8 (signature 0xbe 0xda)                     
Net:   FEC                                                                      
Warning: FEC MAC addresses don't match:                                         
Address in SROM is         1f:56:1d:17:ee:22                                    
Address in environment is  xx:xx:xx:xx:xx:xx                                   
                                                                                
                                                                                
Enter password - autoboot in 2 sec...                                           
                                                                                
NAND read: device 0 offset 0x300000, size 0x300000                              
 3145728 bytes read: OK                                                         
Wrong Image Format for bootm command                                            
ERROR: can't get kernel image!                                                  
U-Boot> dhcp                                                                    
BOOTP broadcast 1                                                               
*** Unhandled DHCP Option in OFFER/ACK: 28                                      
*** Unhandled DHCP Option in OFFER/ACK: 28                                      
DHCP client bound to address 10.1.0.201                                         
U-Boot> tftpboot 0xa1000000 uImage-toon3                                        
Using FEC device                                                                
TFTP from server 10.1.0.10; our IP address is 10.1.0.201                        
Filename 'uImage-toon3'.                                                        
Load address: 0xa1000000                                                        
Loading: #################################################################      
         #################################################################      
         ###############################                                        
done                                                                            
Bytes transferred = 2353828 (23eaa4 hex)                                        
U-Boot> bootm                                                                   
## Booting kernel from Legacy Image at a1000000 ...                             
   Image Name:   Linux-2.6.36-R07-h21                                           
   Image Type:   ARM Linux Kernel Image (uncompressed)                          
   Data Size:    2353764 Bytes = 2.2 MiB                                        
   Load Address: a0008000                                                       
   Entry Point:  a0008000                                                       
   Verifying Checksum ... OK                                                    
   Loading Kernel Image ... OK                                                  
OK                                                                              
                                                                                
Starting kernel ...                                                             
                                                                                
Uncompressing Linux... done, booting the kernel.                                
Linux version 2.6.36-R07-h21 (marcelr@laptop) (gcc version 4.56
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                               
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=mxM
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: 125288k/125288k available, 5784k 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 - 0xc0024000   ( 112 kB)                               
      .text : 0xc0024000 - 0xc0405000   (3972 kB)                               
      .data : 0xc0420000 - 0xc0467e60   ( 288 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... 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                                              
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                                       
cfg80211: Calling CRDA to update world regulatory domain                        
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 244                                                      
io scheduler noop registered (default)                                          
imx-fb imx-fb.0: PreserveUBootFramebuffer(1): xres=800, yres=480 [skip _update_]
imx-fb imx-fb.0: PreserveUBootFramebuffer(2): xres=800, yres=480 [skip _update_]
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_]
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-b)
Scanning device for bad blocks                                                  
Bad eraseblock 669 at 0x0000053a0000                                            
Bad eraseblock 926 at 0x0000073c0000                                            
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 warning: check_what_we_have: 946 PEBs are corrupted                         
corrupted PEBs are: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 1
UBI error: check_what_we_have: too many corrupted PEBs, refusing this device    
UBI error: ubi_init: cannot attach mtd4                                         
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 0x04cc/0x1505                                
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-R07-h21 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-R07-h21 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                                               
USB Serial support registered for cp210x                                        
usbcore: registered new interface driver cp210x                                 
cp210x: v0.09:Silicon Labs CP210x RS232 serial adaptor driver                   
USB Serial support registered for FTDI USB Serial Device                        
usbcore: registered new interface driver ftdi_sio                               
ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver                              
USB Serial support registered for pl2303                                        
usbcore: registered new interface driver pl2303                                 
pl2303: Prolific PL2303 USB to serial adaptor driver                            
input: TSC2007 Touchscreen as /devices/virtual/input/input0                     
rtc-isl1208 1-006f: chip found, driver version 0.3                              
rtc-isl1208 1-006f: rtc core: registered rtc-isl1208 as rtc0                    
i2c /dev entries driver                                                         
imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=0)     
adt7410 0-0048: adt7410 temperature sensor registered.                          
adt7410 0-0049: adt7410 temperature sensor registered.                          
usbcore: registered new interface driver r871x_usb_drv                          
nf_conntrack version 0.5.0 (1957 buckets, 7828 max)                             
ip_tables: (C) 2000-2006 Netfilter Core Team                                    
TCP cubic registered                                                            
NET: Registered protocol family 10                                              
ip6_tables: (C) 2000-2006 Netfilter Core Team                                   
NET: Registered protocol family 17                                              
lib80211: common routines for IEEE802.11 drivers                                
rtc-isl1208 1-006f: setting system clock to 2016-02-20 20:01:37 UTC (1455998497)
UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi0:rootfs", error -19         
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)                
Please append a correct "root=" boot option; here are the available partitions: 
1f00             512 mtdblock0 (driver?)                                        
1f01            1536 mtdblock1 (driver?)                                        
1f02            3072 mtdblock2 (driver?)                                        
1f03            3072 mtdblock3 (driver?)                                        
1f04          121856 mtdblock4 (driver?)                                        
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)  
[<c00293d0>] (unwind_backtrace+0x0/0xf0) from [<c0326da4>] (panic+0x60/0x190)   
[<c0326da4>] (panic+0x60/0x190) from [<c0008ea0>] (mount_block_root+0x15c/0x20c)
[<c0008ea0>] (mount_block_root+0x15c/0x20c) from [<c00090d0>] (prepare_namespac)
[<c00090d0>] (prepare_namespace+0x8c/0x178) from [<c0008b50>] (kernel_init+0x10)
[<c0008b50>] (kernel_init+0x10c/0x14c) from [<c00258ec>] (kernel_thread_exit+0x)

The kernel loads, can read the NAND chip, and then decides that the root filesystem on it is really fucked up beyond any recognition, resulting in a kernel panic.

But that's OK. Not a thing that can't be fixed.

The good News is that kernels built from the source tree actually boot the way they should. This opens new ways for adapting toon to other needs. We can basically add anything we like, from printers to webcams, remotely mounted filesystems, data acquisition hardware, whatever, take you pick.

grtz,

marcelr

Posted: **Wed Feb 24, 2016 11:59 pm**

The patient's still in ICU, but stable

, he's gonna make it.

Last week, one of the forum members sent me a set of mtd dumps, and these turned out to be quite useless. Wasn't his fault, the rootfs, as flashed onto toon, is hard to mount without the right hardware (i.e. nand flash memory). So I sent him a script to dump the rootfs over ssh. That rendered a useful tarball, holding a complete root filesystem with a recent copy of toon's firmware.

The tarball holding the rootfs of his toon, together with a modified linux kernel, could be used to revive my toon (or any other, for that matter). It took some effort, the description of the inner workings of u-boot, nfsd and the combination, on modern linuxes, as found on the internet is less than optimal, let's put it that way ..
The kernel loads via tftp, the rootfs via nfs, from a dedicated set of servers (NFS, DHCP, TFTP) in combination with an old router limited to issuing 1 IP address only.
In case anyone's interested in the details, not sure if I will find the time to post them all, it's quite a long story ...

Now I will need to find a way to turn this rootfs into a flashable file for my toon, that's the easy part, before that I would like to return the rootfs to a more or less virgin state, i.e., get rid of all the data, settings, serial number-specific entries etc.

grtz,

marcelr

Posted: **Fri Feb 26, 2016 6:35 pm**

i'n new hier thanks all for the nice work,
i'm planing to buy Toon is there how to root and this kind of thing ,
is it possible to use there app on the go ....?

i'm planing to enjoy Eneco but without monthly toon subscribe...

thanks all

Posted: **Sat Feb 27, 2016 5:32 pm**

is there how to root and this kind of thing

Read this thread.

Completely, that is. Start at page 1, and work yourself all the way through.

grtz,

marcelr

Posted: **Sat Feb 27, 2016 11:03 pm**

thanks

Posted: **Sun Feb 28, 2016 12:36 pm**

You're welcome,

A quick summary is posted here:
http://www.domoticaforum.eu/viewtopic.p ... =75#p77439
Getting your data on screen without subscription is possible, not sure about the app.

Good luck,

marcelr

Posted: **Sun Feb 28, 2016 4:45 pm**

Now I will need to find a way to turn this rootfs into a flashable file for my toon, that's the easy part,

Me and my big mouth ...

Stripping the rootfs down to an anonymous, virgin, root filesystem turned out to be the easy part. That's done. Toon installs like it should, had to patch
/HCBv2/config/config_happ_scsync.xml manually, but that all works, now I have the whole lot of tiles as presented to "customers only". Just traffic and weather aren't working, known issue.

Flashing the rootfs onto toon is easy. Booting toon from it, that's a totally different kettle of fish.
Will keep trying, playing with bootloader, kernel flags, UBI layout, that sort of stuff. If anyone's an expert on UBIfs and flashing boot partitions on NAND flash, please come forward.

In the meantime another question:

I have solar panels on my roof, and just for fun switched on the solar option in toon. Now it complains about some connection to a kWh meter (see attached image, top right on toon's screen, although hard to see). Does anyone have toon solar? What's extra in the hardware/software with respect to the "normal" version?

grtz,

marcelr

Posted: **Mon Feb 29, 2016 10:04 am**

marcelr wrote:
I have solar panels on my roof, and just for fun switched on the solar option in toon. Now it complains about some connection to a kWh meter (see attached image, top right on toon's screen, although hard to see). Does anyone have toon solar? What's extra in the hardware/software with respect to the "normal" version?

As far as I know there isn't any special hardware but the information is coming from the smart meter port P1, your meter supposes to slow down or even turn backwards if you produce energy.

Posted: **Mon Feb 29, 2016 11:23 am**

As far as I know there isn't any special hardware but the information is coming from the smart meter port P1, your meter supposes to slow down or even turn backwards if you produce energy.

I don't think so. I have a meter with P1 port, apparently another kWh meter should be installed. This makes sense because there's no way for the kWh meter that's installed for metering your energy consumption, to tell the difference between gross power generation and direction consumption of your home-produced energy. This energy never passes the meter.

According to this page:
http://www.klimaatgids.nl/nieuws/toon-l ... nelen-zien
(in Dutch, I'm afraid), extra software and an extra kWh meter are required. The question is: which software, which hardware, and even more interesting: how is it connected?

grtz,

marcelr

Posted: **Mon Feb 29, 2016 5:33 pm**

hayman wrote:i'n new hier thanks all for the nice work,
i'm planing to buy Toon is there how to root and this kind of thing ,
is it possible to use there app on the go ....?

i'm planing to enjoy Eneco but without monthly toon subscribe...

thanks all

No, app won't work without subscription.

Ierlandfan pretty much sums it up:

Ierlandfan wrote: ... without subscription, even the basic subscription, Toon is nothing but a very expensive useless Thermostat.

Regarding expensive. I suggest you buy a used one. Not worth 200 euro + for a new one, plus installation is a piece of cake, if you can handle a screwdriver, you can do it. Avoid marktplaats.nl people ask way too much. From time to time usedproducts have them for sale at reasonable price including 1 month warrenty. I got mine for 95 Euro shipped.

Posted: **Mon Feb 29, 2016 9:07 pm**

Last weekend I built a newer version of dropbear. This one should resolve issues with no longer secure encryption algorithms in version 0.51, which was posted earlier.
Unzip, copy to toon and install: opkg install <name of package>.

enjoy.

EDIT: dropbear has been moved to the downloads section in the new subforum:
http://www.domoticaforum.eu/viewtopic.php?f=87&t=11236

Did some new search on the solar thing. Apparently, the meter adapter wants S0 pulses plugged into it, next to the P1 data coming from the meter. Most likely it will need a firmware upgrade for that. The good News is that my power inverter already generates those pulses, so an extra (3 phase, in my case) kWh meter shouldn't be necessary.

Anyway, will have to get my machine cranked up properly again, first ...

... without subscription, even the basic subscription, Toon is nothing but a very expensive useless Thermostat.

I wouldn't call it useless. It's a thermostat, and with a small hack it gives you a lot of information about your energy status, for free. It's not a lot more expensive than a native thermostat for any boiler, with the same level of control flexibility.

marcelr

Home Automation Domotica Forum Europe, Bwired Forum

Toon as a domotica controller?

Re: Toon as a domotica controller?

Re: Toon as a domotica controller?

Re: Toon as a domotica controller?

Re: Toon as a domotica controller?

Re: Toon as a domotica controller?

Re: Toon as a domotica controller?

Re: Toon as a domotica controller?

Re: Toon as a domotica controller?

Re: Toon as a domotica controller?

Re: Toon as a domotica controller?

Re: Toon as a domotica controller?

Re: Toon as a domotica controller?

Re: Toon as a domotica controller?

Re: Toon as a domotica controller?

Re: Toon as a domotica controller?