Toon Recovery

Forum about Toon hardware, both versions 1 and 2 of Toon

Moderators: marcelr, TerrorSource, Toonz, TheHogNL

Re: Toon Recovery

Postby TheHogNL » Fri Nov 08, 2019 7:47 pm

Yes that is ok as long as you own those two toons yourself.
Member of the Toon Software Collective
User avatar
TheHogNL
Forum Moderator
Forum Moderator
 
Posts: 1391
Joined: August 2017

Re: Toon Recovery

Postby NLKris » Sun Nov 10, 2019 5:19 pm

Haha yes, the Toon that doens't have the VPN files is my Toon to test thing on. It doent have a screen anymore. I can put the files from my main Toon on it if nessesery.
NLKris
Starting Member
Starting Member
 
Posts: 25
Joined: January 2019

Re: Toon Recovery

Postby Elektrol » Wed Nov 27, 2019 1:40 pm

Hi, I managed to get the script working. Everything seems to work just fine exept for the part where I need to get a serial connection after the recoveryboot. I can make a serial connection to Toon, but nothing happens after the recovery script has finished and Toon reboots. I included the output of the serial console of Toon. This includes the whole recovery process. I expected the console to show the "Welcome to the Toon recovery environment." after rebooting.

Anybody any idea what might go wrong?

Code: Select all
boot_nand_backup=run nandargs addmtd addtty addmisc addlcd; nand read ${loadaddr} kernel-backup; bootm ${loadaddr}
bootcmd=run boot_nand
splashimage=0x180000
ethact=FEC
sn=16-39-013-782
pn=6599-1500-4100
software_compatibility=0
manufacture_date=2016/10
ethaddr=00:0F:11:08:99:69
addmisc=setenv bootargs ${bootargs} mem=${mem} lpj=999424
lcd=TDA-WVGA0700F00048
gatewayip=10.0.0.160
netmask=255.255.255.0
ipaddr=10.0.0.18
dnsip=10.0.0.160

Environment size: 1183/131068 bytes
U-Boot> setenv serverip 10.0.0.40
U-Boot> setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:/srv/nfs/toon,nfsvers=3,nolock,tcp console=ttymxc0,115200 loglevel=8 mtdparts=mxc_nand:512K@0x00100000(u-boot-env)ro,1536K(splash-image),3M(kernel),3M(kernel-backup),119M(rootfs) ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:toon::off panic=0
U-Boot> nfs 0xa1000000 /srv/nfs/toon/boot/uImage-nfs;bootm
Using FEC device
File transfer via NFS from server 10.0.0.40; our IP address is 10.0.0.18
Filename '/srv/nfs/toon/boot/uImage-nfs'.
Load address: 0xa1000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##################################
done
Bytes transferred = 2503412 (2632f4 hex)
## Booting kernel from Legacy Image at a1000000 ...
   Image Name:   Linux-2.6.36-R07-h21
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2503348 Bytes = 2.4 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@laptop46.wfw.wtb.tue.nl) (gcc version 4.5.3 20110223 (prerelease) (GCC) ) #1 PREEMPT Wed Feb 24 19:02:12 CET 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 c04b2a14, node_mem_map c04da000
  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: root=/dev/nfs rw nfsroot=10.0.0.40:/srv/nfs/toon,nfsvers=3,nolock,tcp console=ttymxc0,115200 loglevel=8 mtdparts=mxc_nand:512K@0x00100000(u-boot-env)ro,1536K(splash-image),3M(kernel),3M(kernel-backup),119M(rootfs) ip=10.0.0.18:10.0.0.40:10.0.0.160:255.255.255.0:toon::off panic=0
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: 124984k/124984k available, 6088k 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 - 0xc0025000   ( 116 kB)
      .text : 0xc0025000 - 0xc044d000   (4256 kB)
      .data : 0xc046a000 - 0xc04b3020   ( 293 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_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
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"
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
ULPI ID does not match any known transceiver.
mxc-ehci mxc-ehci.0: unable to init transceiver, probably missing
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 1
mxc-ehci mxc-ehci.2: irq 55, io mem 0x10024400
mxc-ehci mxc-ehci.2: 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.2
hub 1-0:1.0: USB hub found
hub 1-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: 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.
usbcore: registered new interface driver r871x_usb_drv
nf_conntrack version 0.5.0 (1952 buckets, 7808 max)
IPv4 over IPv4 tunneling driver
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
lib80211_crypt: registered algorithm 'NULL'
Registering the dns_resolver key type
rtc-isl1208 1-006f: setting system clock to 2019-11-27 11:00:46 UTC (1574852446)
usb 1-1: new high speed USB device using mxc-ehci and address 2
usb 1-1: New USB device found, idVendor=148f, idProduct=5370
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: 802.11 n WLAN
usb 1-1: Manufacturer: Ralink
usb 1-1: SerialNumber: 1.0
eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:10, irq=-1)
ADDRCONF(NETDEV_UP): eth0: link is not ready
IP-Config: Complete:
     device=eth0, addr=10.0.0.18, mask=255.255.255.0, gw=10.0.0.160,
     host=toon, domain=, nis-domain=(none),
     bootserver=10.0.0.40, rootserver=10.0.0.40, rootpath=
Looking up port of RPC 100003/3 on 10.0.0.40
PHY: 1:10 - Link is Up - 100/Full
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Looking up port of RPC 100005/3 on 10.0.0.40
VFS: Mounted root (nfs filesystem) on device 0:13.
Freeing init memory: 116K
eth0: no IPv6 routers present

Elektrol
Starting Member
Starting Member
 
Posts: 3
Joined: November 2019

Re: Toon Recovery

Postby TheHogNL » Wed Nov 27, 2019 4:01 pm

From that point inittab should start /etc/rc.recovery and first message would be "It is booted".
Is the downloaded zip file for the recovery environment maybe corrupt? Can you check /srv/nfs/toon/etc/inittab and /srv/nfs/toon/etc/rc.recovery ?
Member of the Toon Software Collective
User avatar
TheHogNL
Forum Moderator
Forum Moderator
 
Posts: 1391
Joined: August 2017

Re: Toon Recovery

Postby Elektrol » Wed Nov 27, 2019 4:36 pm

This Toon was somehow broken. I rooted it with the automated script as I did with 2 others. After that it worked. Then I performed "sh /root/update-rooted.sh -f" to patch. After that it did not boot anymore. Only the 'new' splash logo appeared.

I downloaded the ZIP twice already, so I expect that to be OK.

rc.recovery
Code: Select all
echo "It is booted"
mount /proc
mount -t sysfs none /sys
/menu.sh


inittab
Code: Select all
# /etc/inittab: init(8) configuration.
# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $

# The default runlevel.
id:S:initdefault:

# Boot-time system configuration/initialization script.
# This is run first except when booting in emergency (-b) mode.
si::sysinit:/etc/rc.recovery

# What to do in single-user mode.
~~:S:wait:/bin/sh

# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.

l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
# Normally not reached, but fallthrough in case of emergency.
z6:6:respawn:/sbin/sulogin
S:2345:respawn:/sbin/getty 115200 ttymxc0

#flas:5:respawn:/usr/bin/startflash >/dev/null 2>&1
Elektrol
Starting Member
Starting Member
 
Posts: 3
Joined: November 2019

Re: Toon Recovery

Postby TheHogNL » Wed Nov 27, 2019 5:05 pm

Just sent you an email with my whatsapps details. Would like to take a look with teamviewer or something.
Member of the Toon Software Collective
User avatar
TheHogNL
Forum Moderator
Forum Moderator
 
Posts: 1391
Joined: August 2017

Re: Toon Recovery

Postby TheHogNL » Wed Nov 27, 2019 6:42 pm

Your boot is missing at the very end the start of INIT (INIT: version 2.86 booting). That is the last step of the kernel to start the linux system itself.
Can you check if these files exist on your /srv/nfs/toon nfsroot (should be if you unpacked the zip, but then again better check them).
/ # ls -las /linuxrc
0 lrwxrwxrwx 1 root root 12 Jul 5 2015 /linuxrc -> /bin/busybox
/ # ls -las /sbin/init
0 lrwxrwxrwx 1 root root 13 Jun 10 13:19 /sbin/init -> init.sysvinit
/ # ls -las /sbin/init.sysvinit
28 -rwxr-xr-x 1 root root 27567 Jul 5 2015 /sbin/init.sysvinit
Member of the Toon Software Collective
User avatar
TheHogNL
Forum Moderator
Forum Moderator
 
Posts: 1391
Joined: August 2017

Re: Toon Recovery

Postby TheHogNL » Wed Nov 27, 2019 8:00 pm

And also, as a test, could you rename /sbin/init to /sbin/init2 (or something else)? And then boot?
You should be prompted with an /bin/sh prompt instead of init then.

If that works, then start, after you get the /bin/sh prompt the init manually with /sbin/init2 -i
Member of the Toon Software Collective
User avatar
TheHogNL
Forum Moderator
Forum Moderator
 
Posts: 1391
Joined: August 2017

Re: Toon Recovery

Postby Elektrol » Sun Dec 08, 2019 10:41 am

It took a while due to a busy decembermonth, but it turned out I had problems with my NFS server. I installed an NFS server on my Pi instead of a using an external one and thing went really great after that.

Thanks for the support!
Elektrol
Starting Member
Starting Member
 
Posts: 3
Joined: November 2019

Bicked my Toon using ToonRecovery?

Postby Mazzo » Fri Jan 24, 2020 6:05 pm

Hello, im new here and own a Toon since yesterday.

I rooted the Toon with ToonRooter and after that used Update-Rooted, it was allready on firmware 5.1.18 so it only updated Toonstore and fixed some files etc.. and all was working perfectly till i downloaded Domoticz from the ToonStore and got stuck in activation wizard after restart, tried Update-Rooted and gave me errors on scsync file, checked the file and it was empty and different folder then Update-Rooted wanted him.
Didnt know how to fix it so made the choose of first reroot again but still gave me the same errors afterr Update-Rooted on scsync so i decided to use ToonRecovery.
Everything went fine and saved VPN then formated and restored to 5.0.6 after that i run Update-Rooted again and gave no errors but after i reboot i got stuck in a bootscreen with a powerbutton symbol.
i dont have SSH access anymore and if i use ToonRooter or ToonRecvery again it wont find Toon on Serial so i tried with Jtag connection because i thought maybe the bootloader is updated but still nothing happening.

Please tell me what went wrong and why i cannot acces my Toon anymore.

Greetings.
Mazzo
Starting Member
Starting Member
 
Posts: 3
Joined: January 2020

Re: Toon Recovery

Postby TheHogNL » Fri Jan 24, 2020 10:01 pm

First of all.. how do you 'reboot' the toon after an update? Never just 'kill the power' because causes empty files.

And then, if toonrecovery worked earlier it should work again. Serial should be found always (unless you broke the uboot but I don't think that is the case).
Member of the Toon Software Collective
User avatar
TheHogNL
Forum Moderator
Forum Moderator
 
Posts: 1391
Joined: August 2017

Re: Toon Recovery

Postby Mazzo » Sat Jan 25, 2020 3:52 pm

Thanks for your reply and your development on the Toon.

I indeed reboot taking out the adapter, didn’t know it makes a difference.

I tried a few times with Screen terminal on serial but no response after that with Jtag also no response.
Then tried ToonRooter and again ToonRecovery on serial and Jtag but when it says boot Toon nothing happens.

ToonRecovery didn’t update the boot loader right? So serial connection should still works then i think.
Makes me think the wiring maybe not correct even after checking many times, will try again later since you say that there is a small change of a corrupt boot loader.

Keep you updated.
Mazzo
Starting Member
Starting Member
 
Posts: 3
Joined: January 2020

Re: Toon Recovery

Postby Mazzo » Sat Jan 25, 2020 5:55 pm

Well good News, i tried again and dont know what i did wrong yesterday, maybe wiring wrong or restarting NFS which i didnt do yesterday.
i took a few times U-Boot start loading but now restored to 5.0.6 and boots into Toon Menu again.

Still want to update to 5.1.18 and install Domoticz but im a bit scared now.
Does it make any difference which version of Domoticz? Is the one in ToonStore the latest or better install with SSH?

Thanks again for your support
Mazzo
Starting Member
Starting Member
 
Posts: 3
Joined: January 2020

Re: Toon Recovery

Postby TheHogNL » Sat Jan 25, 2020 6:41 pm

It should not make any difference. I'm not a user of that app but it should not break your Toon. I guess it broke because you unplugged the power cable while it was doing somethign on the filesystem.
Member of the Toon Software Collective
User avatar
TheHogNL
Forum Moderator
Forum Moderator
 
Posts: 1391
Joined: August 2017

Previous

Return to Toon Hardware

Who is online

Users browsing this forum: No registered users and 1 guest