Rooting Toon (or boxx)

Everything about rooting Toons 1 and 2.

Moderators: marcelr, TheHogNL, Toonz

Post Reply
marcelr
Global Moderator
Global Moderator
Posts: 1153
Joined: Thu May 10, 2012 10:58 pm
Location: Ehv

Re: Rooting Toon

Post by marcelr »

/etc/inittab looks OK, and, according to your comments, you now have root access. Good. I adapted the rooting manual a little to address the issues you encountered.

To connect the z-wave energy adapter again, be sure to remove it properly within the software first. It may take quite a few tries before it actually works. Had this issue myself as well. The rooting process doesn't block any communication, the zwave handling is done by code that hasn't been touched by the rooting.
Ronald
Starting Member
Starting Member
Posts: 6
Joined: Sat Jul 01, 2017 8:22 pm

Re: Rooting Toon

Post by Ronald »

Hello,

I have a toon with a 16-XXX serial number, so I have to use root using JTAG.
I cannot get into telnet because the openocd-command ends with "Permission denied"

I use a ftdi-usb-connector for the serial monitor.
For JTAG I use a direct connection from a RaspberryPi 2b GPIO to the JTAG connector of the Toon.
I tripple checked the wires.

Can you help me with this?

Serial monitor:
U-Boot 2010.09-R10 (Dec 14 2015 - 19:28:18)

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
Configure for LCD: TDA-WVGA0700F00048
LCD: Initializing LCD frambuffer at a1400000
LCD: 800x480, pbb 4
LCD: Drawing the logo...
Display-bmp: 800 x 480 with 16777216 colors
Net: FEC
Warning: FEC MAC addresses don't match:
Address in SROM is 00:00:20:03:00:00
Address in environment is 00:0f:11:06:f7:48


Enter password - autoboot in 2 sec...

NAND read: device 0 offset 0x300000, size 0x300000
3145728 bytes read: OK
## Booting kernel from Legacy Image at a1000000 ...
Image Name: Linux-2.6.36-R10-h25
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2245600 Bytes = 2.1 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-R10-h25 (jbraam@dvl) (gcc version 4.5.3 20110223 (prerelease) (GCC) ) #1 PREEMPT Tue May 24 11:41:01 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
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 lcd=TDA-WVGA0700F00048
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: 125536k/125536k available, 5536k 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 - 0xc03ea000 (3864 kB)
.data : 0xc0404000 - 0xc042a5a0 ( 154 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: TDA-WVGA0700F00048
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 245
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: K9F1G08U0E detected, disabling sub-page writes
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
Scanning device for bad blocks
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: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: max. sequence number: 91363
UBI: attached mtd4 to ubi0
UBI: MTD device name: "rootfs"
UBI: MTD device size: 119 MiB
UBI: number of good PEBs: 952
UBI: number of bad PEBs: 0
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: 952
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 289/95
UBI: image sequence number: 1402297494
UBI: background thread "ubi_bgt0d" started, PID 319
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-h25 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-h25 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 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)
adt7410 0-0048: adt7410 temperature sensor registered.
adt7410 0-0049: adt7410 temperature sensor registered.
nf_conntrack version 0.5.0 (1961 buckets, 7844 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
Bridge firewalling registered
lib80211: common routines for IEEE802.11 drivers
rtc-isl1208 1-006f: setting system clock to 2017-07-01 18:11:47 UTC (1498932707)
UBIFS: recovery needed
usb 2-1: new high speed USB device using mxc-ehci and address 2
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size: 117833728 bytes (115072 KiB, 112 MiB, 928 LEBs)
UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 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: 112K
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
INIT: version 2.86 booting
(print_boot_msg)
Please wait: booting... (print_boot_msg)
* Kernel 2.6.36-R10-h25 (print_boot_msg)
* Firmware qb2/ene/3.7.9-1067-0 (print_boot_msg)
* Hostname eneco-001-269910 (print_boot_msg)
usbcore: registered new interface driver r871x_usb_drv
usbcore: registered new interface driver rt2870
Loading iptables settings: iptables.
(print_boot_msg)
Configuring network interfaces... (print_boot_msg)
Configuring network interfaces...
Running 'ifup -a' in the foreground (ifup-fg)
ifup: interface lo already configured
eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:10, irq=-1)
ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.18.3) started
Sending discover...
Sending discover...
Sending discover...
Lease failing, starting in bg: udhcpc -b -R -i eth0 -A 5 -p /var/run/udhcpc.eth0.pid -H eneco-001-269910
No lease, failing
udhcpc (v1.18.3) started
* Wired (eth0) 00:0f:11:06:f7:48 [No IP from DHCP Server] (print_boot_msg)
Sending discover...
* Wireless (wlan0) 00:00:00:00:00:00 [No IP from DHCP Server] (print_boot_msg)
Setting up IP spoofing protection: rp_filter.
INIT: Entering runlevel: 5
Starting syslogd/klogd: done
HCBv2 apps started via runlevels, performing 'addstartables && reload && init 5 or 5'.
HCBv2 adding: comm eventmgr kpi pwrusage scsync smartplug thermstat usermsg weather bxtproxy config log rrd upnp watchdog hue p1 zwave lighttpd.
HCBv2 startables unchanged, not writing /etc/inittab.
Sending discover...
imx-fb imx-fb.0: PreserveUBootFramebuffer(4): xres=800, yres=480 [do _update_lcdc]
Sending discover...
Lease failing, already running in bg: udhcpc -b -R -i eth0 -A 5 -p /var/run/udhcpc.eth0.pid -H eneco-001-269910
No lease, forking to background
eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:10, irq=-1)
ADDRCONF(NETDEV_UP): eth0: link is not ready

My rpi.cfg:
#
# Config for using Raspberry Pi's expansion header
#
# This is best used with a fast enough buffer but also
# is suitable for direct connection if the target voltage
# matches RPi's 3.3V and the cable is short enough.
#
# Do not forget the GND connection, pin 6 of the expansion header.
#

interface bcm2835gpio

bcm2835gpio_peripheral_base 0x3F000000

# Transition delay calculation: SPEED_COEFF/khz - SPEED_OFFSET
# These depend on system clock, calibrated for stock 700MHz
# bcm2835gpio_speed SPEED_COEFF SPEED_OFFSET
bcm2835gpio_speed_coeffs 146203 36

# Each of the JTAG lines need a gpio number set: tck tms tdi tdo
# Header pin numbers: 23 22 19 21
# bcm2835gpio_jtag_nums 11 25 10 9
bcm2835gpio_jtag_nums 23 22 19 21

# or if you have both connected,
reset_config trst_and_srst srst_push_pull

# Each of the SWD lines need a gpio number set: swclk swdio
# Header pin numbers: 22 18
# bcm2835gpio_swd_nums 25 24

# If you define trst or srst, use appropriate reset_config
# Header pin numbers: TRST - 26, SRST - 18

# bcm2835gpio_trst_num 7
bcm2835gpio_trst_num 24
# reset_config trst_only

bcm2835gpio_srst_num 18
# reset_config srst_only srst_push_pull

# or if you have both connected,
reset_config trst_and_srst srst_push_pull

Raspberry Pi:
pi@raspberrypi:~ $ openocd -f rpi.cfg -f ed20.cfg
Open On-Chip Debugger 0.10.0+dev-00166-g0e4fbfb (2017-07-01-14:41)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
BCM2835 GPIO config: tck = 23, tms = 22, tdi = 19, tdo = 21
trst_and_srst separate srst_gates_jtag trst_push_pull srst_push_pull connect_deassert_srst
BCM2835 GPIO config: trst = 24
BCM2835 GPIO config: srst = 18
trst_and_srst separate srst_gates_jtag trst_push_pull srst_push_pull connect_deassert_srst
trst_and_srst srst_pulls_trst srst_gates_jtag trst_push_pull srst_push_pull connect_deassert_srst
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
dcc downloads are enabled
ed20_init
Info : BCM2835 GPIO JTAG/SWD bitbang driver
Info : JTAG only mode enabled (specify swclk and swdio gpio to add SWD mode)
open: Permission denied

pi@raspberrypi:~ $ telnet localhost 4444
Trying ::1...
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
marcelr
Global Moderator
Global Moderator
Posts: 1153
Joined: Thu May 10, 2012 10:58 pm
Location: Ehv

Re: Rooting Toon

Post by marcelr »

Try and run openocd as root. (or use sudo). I think the OS won't let you open the JTAG interface.
Ronald
Starting Member
Starting Member
Posts: 6
Joined: Sat Jul 01, 2017 8:22 pm

Re: Rooting Toon

Post by Ronald »

Should have tried that...
How could I forget.
Will retry tomorrow. Thank you for the fast reply!
Ronald
Starting Member
Starting Member
Posts: 6
Joined: Sat Jul 01, 2017 8:22 pm

Re: Rooting Toon

Post by Ronald »

With sudo i managed to set up the telnet-connection.
The soft_reset_halt and reset halt are not capable of stopping the processor.
Could you help me again?

pi@raspberrypi:~ $ sudo openocd -f rpi.cfg -f ed20.cfg
Open On-Chip Debugger 0.10.0+dev-00166-g0e4fbfb (2017-07-01-14:41)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
adapter speed: 3000 kHz
BCM2835 GPIO config: tck = 23, tms = 22, tdi = 19, tdo = 21
BCM2835 GPIO config: trst = 24
BCM2835 GPIO config: srst = 18
trst_and_srst separate srst_gates_jtag trst_push_pull srst_push_pull connect_deassert_srst
trst_and_srst srst_pulls_trst srst_gates_jtag trst_push_pull srst_push_pull connect_deassert_srst
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
dcc downloads are enabled
ed20_init
Info : BCM2835 GPIO JTAG/SWD bitbang driver
Info : JTAG only mode enabled (specify swclk and swdio gpio to add SWD mode)
Info : clock speed 3073 kHz
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: imx27.etb: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : Embedded ICE version 0
Error: unknown EmbeddedICE version (comms ctrl: 0x00000000)
Info : imx27.cpu: hardware has 2 breakpoint/watchpoint units
Info : ETM v1.0
Info : accepting 'telnet' connection on tcp/4444
requesting target halt and executing a soft reset
Error: Failed to halt CPU after 1 sec
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: imx27.etb: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Warn : srst pulls trst - can not reset into halted mode. Issuing halt after reset.
Error: timed out while waiting for target halted
TARGET: imx27.cpu - Not halted
in procedure 'reset'
in procedure 'ocd_bouncer'


Error: Target not halted
Info : no working area available, falling back to memory writes
Warn : target not halted

Warn : target not halted

Info : Halt timed out, wake up GDB.

pi@raspberrypi:~ $ sudo telnet localhost 4444
Trying ::1...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Open On-Chip Debugger
> soft_reset_halt
requesting target halt and executing a soft reset
Failed to halt CPU after 1 sec
> reset halt
JTAG scan chain interrogation failed: all zeroes
Check JTAG interface, timings, target power, etc.
Trying to use configured scan chain anyway...
imx27.etb: IR capture error; saw 0x00 not 0x01
Bypassing JTAG setup events due to errors
srst pulls trst - can not reset into halted mode. Issuing halt after reset.
timed out while waiting for target halted
TARGET: imx27.cpu - Not halted
in procedure 'reset'
in procedure 'ocd_bouncer'


> load_image u-boot.bin 0xa1f00000
Target not halted
no working area available, falling back to memory writes
target not halted

> resume 0xa1f00000
target not halted

Halt timed out, wake up GDB.
marcelr
Global Moderator
Global Moderator
Posts: 1153
Joined: Thu May 10, 2012 10:58 pm
Location: Ehv

Re: Rooting Toon

Post by marcelr »

I have no experience with the raspberry as JTAG interface, but some other forum members do.

So guys; your help is needed here.
Ronald
Starting Member
Starting Member
Posts: 6
Joined: Sat Jul 01, 2017 8:22 pm

Re: Rooting Toon

Post by Ronald »

When I google "Error: JTAG scan chain interrogation failed: all zeroes" I find a lot of wiring problems.
I checked that multiple times, so I made a Fritzing on my wiring.
The little black block in the middle is de JTAG-interface on the Toon/Quby.
I use a Raspberry Pi 2 model B v 1.1, running Raspbian Jessie and OpenOCD 0.10.0 and used fresh dupont cables of max. 10 cm.
Quby-JTAG.png
b1r0n3r
Starting Member
Starting Member
Posts: 8
Joined: Tue Jul 04, 2017 8:17 pm

Re: Rooting Toon

Post by b1r0n3r »

marcelr wrote:@Templar: sounds like fun, although I can't make it, I'm afraid. Other stuff to do.
...

@hayman: Once it's rooted, it's rooted. New updates will shutdown ssh access, but IIRC, cygnusx posted a remedy for that. You will need to apply that remedy BEFORE you install updates, if you want to continue having access to your toon. Updates are pushed to your toon by Eneco, if you have a subscription. If not, there's not a lot to update[/b].


just to be 100% clear - once the subscription with Eneco has ended, you will not be able to update the TOON anymore the regular (pushed by Eneco) way?

I am on 3.6.3 currently with my rooted Toon; Is there another way to update TOON myself?
- Where would I get the latest firmware and instructions?
- would I benefit from updating? (if it isn't broke; don't fix it?!)
marcelr
Global Moderator
Global Moderator
Posts: 1153
Joined: Thu May 10, 2012 10:58 pm
Location: Ehv

Re: Rooting Toon

Post by marcelr »

b1r0n3r wrote: just to be 100% clear - once the subscription with Eneco has ended, you will not be able to update the TOON anymore the regular (pushed by Eneco) way?
Nope.
b1r0n3r wrote: I am on 3.6.3 currently with my rooted Toon; Is there another way to update TOON myself?
You will need to find the update packages. Tough call.
b1r0n3r wrote: - Where would I get the latest firmware and instructions?
From Eneco/Quby. AFAIK they are the sole supplier of updates for toon.
b1r0n3r wrote: - would I benefit from updating? (if it isn't broke; don't fix it?!)
The latest fw upgrade (4.3.20 to date) appears to be a little bit faster and less memory-hungry. Could be a benefit.
Ierlandfan
Member
Member
Posts: 151
Joined: Thu Oct 03, 2013 7:53 pm

Re: Rooting Toon

Post by Ierlandfan »

New 4.4.x update feels/is faster and they changed the screen design, there are no more references to Eneco. New start-up screens simply says "Toon" . because they sell it in other countries as well.)

The icon in the left upper corner also states "Toon" now instead of Eneco. The path /HCBv2/ is now a symlink to qmf...directories are the same.
They are preparing for a transistion to "data" instead of /HCBv2/ and qmf directory" (according to opkg) ,
I am not sure if imageViewer was already in the list of apps (not enabled by default) Fun that it is possible to upload pictures (SCP...eg...WINSCP will do if you like windows style explorer)) and use Toon (There's a auto-play function) to show them. If enabled (Global,qml) you can find it in the menu. VNCviewer says something about a VenNCrypt not found but I saw a openssl config error when (manually) updating so that probably explains. Also Vfat and msdos packages are added, probably for the same reason. (Or for later use by using a USB-Stick for log/Image upload)
I also saw that there' are MQTT packages available and an mp3 player, sox, probably development for a Toon "3" Or they're gonna use the tiny speaker for something.

The global configuration resides now in /qmf/etc/qmf_project.xml, other files are still in /qmf/data.
They whitelisted hdrv_hue in the web interface so that seems new. (Links to myfox/Somfy) Also the "StartBackendless" is I think an interesting qml file

I am not sure how they update the OT table internally, the table is now completely gone when debugging so I will look into that.
klaphekje
Starting Member
Starting Member
Posts: 36
Joined: Sat Oct 08, 2016 10:05 pm

Re: Rooting Toon

Post by klaphekje »

Ronald wrote:When I google "Error: JTAG scan chain interrogation failed: all zeroes" I find a lot of wiring problems.
I checked that multiple times, so I made a Fritzing on my wiring.
The little black block in the middle is de JTAG-interface on the Toon/Quby.
I use a Raspberry Pi 2 model B v 1.1, running Raspbian Jessie and OpenOCD 0.10.0 and used fresh dupont cables of max. 10 cm.
I also used a RPI for this, do you still have this issue? I dont remember the exact steps and output anymore but i can reconnect the pi to toon to figure them out if needed.'
Let me know!
Ronald
Starting Member
Starting Member
Posts: 6
Joined: Sat Jul 01, 2017 8:22 pm

Re: Rooting Toon

Post by Ronald »

klaphekje wrote:
Ronald wrote:When I google "Error: JTAG scan chain interrogation failed: all zeroes" I find a lot of wiring problems.
I checked that multiple times, so I made a Fritzing on my wiring.
The little black block in the middle is de JTAG-interface on the Toon/Quby.
I use a Raspberry Pi 2 model B v 1.1, running Raspbian Jessie and OpenOCD 0.10.0 and used fresh dupont cables of max. 10 cm.
I also used a RPI for this, do you still have this issue? I dont remember the exact steps and output anymore but i can reconnect the pi to toon to figure them out if needed.'
Let me know!
I haven't worked on this during the week, so the issue still exists.
Can you let me know how you did this?
Could it be a problem that I used OpenOCD 0.10.0 in stead of 0.9.0?
marcelr
Global Moderator
Global Moderator
Posts: 1153
Joined: Thu May 10, 2012 10:58 pm
Location: Ehv

Re: Rooting Toon

Post by marcelr »

If it's a matter of the software version, I think that's easliy tested. AFAIK, the config files for openocd 0.10.0 and 0.9.0 are interchangeable.
mennie
Starting Member
Starting Member
Posts: 3
Joined: Mon Jul 17, 2017 9:20 pm

Re: Rooting Toon

Post by mennie »

TerrorSource wrote:Hi Guys,

Rooted my Toon today with some help of marcelr but i'm missing some options as far i as i know of.
I want to connect 1 of my Fibaro plugs to the Toon to test things out but i cant find the "Plugs" option.
Or is it because it's not connected to my P1 or boiler? Using it as stand-alone to test things out before i'm going to use it permanently.

Image

This is the subscription menu:
Image

EDIT: After running "killall -9 qt-gui" a few times a few apps showed up. Going to configure all in globals.qml and running the command again.
Hi TerrorSource, would you mind sharing how you got the "Plugs" tile?
For me I only have the options to add power, gas or weather tiles.
mennie
Starting Member
Starting Member
Posts: 3
Joined: Mon Jul 17, 2017 9:20 pm

Re: Rooting Toon

Post by mennie »

I just updated my Toon from 2.10.15 by adding these files:
base-feed.conf:src/gz base http://feed.hae.int/feeds/qb2/ene/4.4.21
oebase-feed.conf:src/gz oebase http://feed.hae.int/feeds/qb2/oe/2.6.36-base-r10-qmf0
oekern-feed.conf:src/gz oekern http://feed.hae.int/feeds/qb2/oe/2.6.36-R10-h27-no6

And running:
opkg update
opkg list-upgradable
opkg upgrade

It seems to have worked.
Post Reply

Return to “Toon Rooting”