Rooting Toon (or boxx)

Everything about rooting Toons 1 and 2.

Moderators: marcelr, TheHogNL, Toonz

wbmk
Starting Member
Starting Member
Posts: 24
Joined: Sun Nov 13, 2016 5:10 pm

Re: Rooting Toon (or boxx)

Post by wbmk »

Great, thanx! :D
wbmk
Starting Member
Starting Member
Posts: 24
Joined: Sun Nov 13, 2016 5:10 pm

Re: Rooting Toon (or boxx)

Post by wbmk »

Hmm.. still no luck.

Booted with password and modified setenv string. no effect. rebooted again without password. again no luck.

This is the output from the second try...

Code: Select all

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
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
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: 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:       179801
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: 524/188
UBI: image sequence number:  468129398
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 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 (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-12-20 20:22:57 UTC (1513801377)
UBIFS: recovery needed
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)
usb 2-1: new high speed USB device using mxc-ehci and address 2
VFS: Mounted root (ubifs filesystem) on device 0:13.
Freeing init memory: 104K
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-h27 (print_boot_msg)
* Firmware          qb2/ene/4.9.23-1183-1 (print_boot_msg)
* Hostname          eneco-001-243843 (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)
udhcpc: started, v1.27.2
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
Lease failing, starting in bg: udhcpc -b -R -i eth0 -A 5 -p /var/run/udhcpc.eth0.pid -H eneco-001-243843
udhcpc: option -h NAME is deprecated, use -x hostname:NAME
udhcpc: started, v1.27.2
udhcpc: no lease, failing
udhcpc: sending discover
Successfully initialized wpa_supplicant
rfkill: Cannot get wiphy informa(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
tion
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
udhcpc: started, v1.27.2
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
Lease failing, starting in bg: udhcpc -b -R -i wlan0 -A 5 -p /var/run/udhcpc.wlan0.pid -H eneco-001-243843
udhcpc: no lease, failing
udhcpc: option -h NAME is deprecated, use -x hostname:NAME
udhcpc: started, v1.27.2
* Wired (eth0)      00:0f:11:06:83:b0  [No IP from DHCP Server] (print_boot_msg)
udhcpc: sending discover
* Wireless (wlan0)  28:c2:dd:e5:37:02  [No IP from DHCP Server] (print_boot_msg)
Setting up IP spoofing protection: rp_filter.
Lease failing, already running in bg: udhcpc -b -R -i eth0 -A 5 -p /var/run/udhcpc.eth0.pid -H eneco-001-243843
udhcpc: no lease, forking to background
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 watchdog hue p1 zwave lighttpd.
HCBv2 startables unchanged, not writing /etc/inittab.
udhcpc: sending discover
udhcpc: sending discover
imx-fb imx-fb.0: PreserveUBootFramebuffer(4): xres=800, yres=480 [do _update_lcdc]
Lease failing, already running in bg: udhcpc -b -R -i wlan0 -A 5 -p /var/run/udhcpc.wlan0.pid -H eneco-001-243843
udhcpc: no lease, forking to background
eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:10, irq=-1)
eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:10, irq=-1)
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
eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:10, irq=-1)
(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
Any suggestions what to do next to get a prompt and root access?

TIA, Wbmk
hafeez
Starting Member
Starting Member
Posts: 10
Joined: Thu Dec 21, 2017 10:26 am

Re: Rooting Toon (or boxx)

Post by hafeez »

For those who did upgrade their rooted Toon to 4.9.23 and lost passwd & getty due to the new busybox I have attached busybox from version 3.2.18 from a root_fs backup I had made before upgrading.
I have tested this method successfully and did not notice any issues.

Download attached files and remove the tgz extension by renaming them (because extension 7z not allowed to be attached)
Extract files with 7z (7z x busybox_1.18.3.001.7z) and copy the extracted busybox to /bin/ replacing the existing /bin/busybox

Once replaced it will allow these 2 commands again: passwd & getty

Code: Select all

eneco-001-xxxxxx:~# passwd
Changing password for root
New password:

eneco-001-xxxxxx:/root# BusyBox v1.18.3 (2011-08-26 19:32:05 CEST) multi-call binary.

Usage: getty [OPTIONS] BAUD_RATE TTY [TERMTYPE]

Open a tty, prompt for a login name, then invoke /bin/login

Options:
	-h		Enable hardware (RTS/CTS) flow control
	-i		Don't display /etc/issue before running login
	-L		Local line, don't do carrier detect
	-m		Get baud rate from modem's CONNECT status message
	-w		Wait for a CR or LF before sending /etc/issue
	-n		Don't prompt the user for a login name
	-f ISSUE_FILE	Display ISSUE_FILE instead of /etc/issue
	-l LOGIN	Invoke LOGIN instead of /bin/login
	-t SEC		Terminate after SEC if no username is read
	-I INITSTR	Send INITSTR before anything else
	-H HOST		Log HOST into the utmp file as the hostname
Attachments
busybox_1.18.3.7z.002.tgz
busysbox with passwd & getty part 2/2
(113.43 KiB) Downloaded 478 times
busybox_1.18.3.7z.001.tgz
busysbox with passwd & getty part 1/2
(200 KiB) Downloaded 419 times
Rudolf
Member
Member
Posts: 136
Joined: Mon Dec 04, 2017 8:50 pm

Re: Rooting Toon (or boxx)

Post by Rudolf »

Thanks! It works great on my system.

I took a slightly different approach, that doesn't touch the original busybox (and might be slightly safer because of that)

I copied the busybox executable to root's homefolder:
/root/busybox

Made the file executable:

Code: Select all

chmod u+x /root/busybox
Created symlinks for the missing applets:

Code: Select all

ln -s /root/busybox /usr/sbin/getty
ln -s /root/busybox /usr/sbin/passwd
Now I can use getty and setup a password for the root-user (although I prefer pub-key-login).

Users that are not (yet) rooted might be better off uploading this binary via minicom and replace/duplicate busybox and continue like before.
If you are replacing the original file you must make sure the filetransfer has succeeded.
hafeez
Starting Member
Starting Member
Posts: 10
Joined: Thu Dec 21, 2017 10:26 am

Re: Rooting Toon (or boxx)

Post by hafeez »

Rudolf's method is indeed preferred but I tested my method by doing some checks from a new ssh session after I replaced the busybox
Anyway I have kept the old & new busybox as backup in /root/ on my rooted Toon
jozg
Member
Member
Posts: 56
Joined: Wed Nov 15, 2017 1:13 pm

Re: Rooting Toon (or boxx)

Post by jozg »

Hello Hafeez, Rudolf,

Good work for the 4.9.23 version.
Does this method also apply for a toon with version 4.9.23 wich is nog yet rooted?.
I have a (extra) original 4.9.23 version toon, but i still have to start rooting it.

Thanks, and nice christmas days.

Regards
JacDomotica
Starting Member
Starting Member
Posts: 7
Joined: Tue Nov 07, 2017 10:12 pm

Re: Rooting Toon (or boxx)

Post by JacDomotica »

Hello,

I bougth an toon and an jtag interface and i am trying to connect the interface via openocd to my toon.
But i get this error:

Code: Select all

PS C:\Projecten\OpenOCD-20170821\bin> ./openocd -f ./interface/jlink.cfg -f ./ed20.cfg
Open On-Chip Debugger 0.10.0 (2017-08-21) [https://github.com/sysprogs/openocd]
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
trst_and_srst srst_pulls_trst srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
dcc downloads are enabled
ed20_init
Info : No device selected, using first device.
Info : J-Link ARM V8 compiled Nov 28 2014 13:44:46
Info : Hardware version: 8.00
Info : VTarget = 0.000 V
Error: JTAG I/O operation failed: 0x5.
Error: jaylink_jtag_io() failed: JAYLINK_ERR_DEV.
Error: An adapter speed is not selected in the init script. Insert a call to adapter_khz or jtag_rclk to proceed.
P.S. toon is not connected in this example but if it is then i get the same error.

I am a beginner but is there some one who can help me?
Bassie
Starting Member
Starting Member
Posts: 16
Joined: Mon Nov 06, 2017 4:24 pm

Re: Rooting Toon (or boxx)

Post by Bassie »

I have successfully rooted a Toon before.
I first upgraded to 4.8 (latest at the time) and then rooted using the manuals on this site.

I now have another Toon from a friend which I would like to root.
I see there are some problems with rooting version 4.9.

What should I do this time?
-Root the older firmware and stay on that? (the Toon currently has a very old firmware)
-Or root first and then upgrade (and keeping root?)
-Or update to a prior version 3.8 (is that even possible) and then root?
marcelr
Global Moderator
Global Moderator
Posts: 1153
Joined: Thu May 10, 2012 10:58 pm
Location: Ehv

Re: Rooting Toon (or boxx)

Post by marcelr »

Root first and then update. Once rooted, it is not easily undone.
marcelr
Global Moderator
Global Moderator
Posts: 1153
Joined: Thu May 10, 2012 10:58 pm
Location: Ehv

Re: Rooting Toon (or boxx)

Post by marcelr »

JacDomotica wrote:Hello,

I bougth an toon and an jtag interface and i am trying to connect the interface via openocd to my toon.
But i get this error:

Code: Select all

PS C:\Projecten\OpenOCD-20170821\bin> ./openocd -f ./interface/jlink.cfg -f ./ed20.cfg
Open On-Chip Debugger 0.10.0 (2017-08-21) [https://github.com/sysprogs/openocd]
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
trst_and_srst srst_pulls_trst srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
dcc downloads are enabled
ed20_init
Info : No device selected, using first device.
Info : J-Link ARM V8 compiled Nov 28 2014 13:44:46
Info : Hardware version: 8.00
Info : VTarget = 0.000 V
Error: JTAG I/O operation failed: 0x5.
Error: jaylink_jtag_io() failed: JAYLINK_ERR_DEV.
Error: An adapter speed is not selected in the init script. Insert a call to adapter_khz or jtag_rclk to proceed.
P.S. toon is not connected in this example but if it is then i get the same error.

I am a beginner but is there some one who can help me?
Looks like you are missing a line like this in jlink.cfg:

Code: Select all

adapter_khz 1000
hafeez
Starting Member
Starting Member
Posts: 10
Joined: Thu Dec 21, 2017 10:26 am

Re: Rooting Toon (or boxx)

Post by hafeez »

jozg wrote:Hello Hafeez, Rudolf,

Good work for the 4.9.23 version.
Does this method also apply for a toon with version 4.9.23 wich is nog yet rooted?.
I have a (extra) original 4.9.23 version toon, but i still have to start rooting it.

Thanks, and nice christmas days.

Regards
I have no experience in rooting 4.9.23 so cannot advice.
I rooted my 2 Toons on 3.82.18 and then updated to 4.9.23 and then replaced busybox with an old version.
Rudolf
Member
Member
Posts: 136
Joined: Mon Dec 04, 2017 8:50 pm

Re: Rooting Toon (or boxx)

Post by Rudolf »

I updated to 4.9.23 and managed to root it just fine (with a little help)

Any order is possible, rooting before upgrading is the preferred method.

The upside of upgrading first is that you don't have to 'upgrade while maintaining root', but rooting itself requires more steps.

But 'upgrading while maintaining root' is something you'll probably need in the future anyways, so it's useful to know the steps.
gijsje
Starting Member
Starting Member
Posts: 25
Joined: Sun Dec 03, 2017 12:52 am

Re: Rooting Toon

Post by gijsje »

Hi Guys,

I am a bit new to this but i stumble to the problem below when trying to root my U-Boot 2010.09-R10 (Dec 14 2015 - 19:28:18) Toon with a Pi3
So i can not get the > soft_reset_halt to stop the cpu at all.
Any advise how to get this working?

thanks in advance
Gijsje
TerrorSource wrote:
Ronald wrote: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.
how did you manage to solve this?
Got the same issue.

> soft_reset_halt
requesting target halt and executing a soft reset
Failed to halt CPU after 1 sec
Halt timed out, wake up GDB.
fkruis
Starting Member
Starting Member
Posts: 20
Joined: Sun May 01, 2016 7:44 pm

Re: Rooting Toon (or boxx)

Post by fkruis »

[quote="wbmk"]Hmm.. still no luck.

Booted with password and modified setenv string. no effect. rebooted again without password. again no luck.


@wbmk try run bootcmd and not run boot_nand
marcelr
Global Moderator
Global Moderator
Posts: 1153
Joined: Thu May 10, 2012 10:58 pm
Location: Ehv

Re: Rooting Toon (or boxx)

Post by marcelr »

It's probably a wiring issue.
Because of this:

Code: Select all

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...
The "all zeroes" means that none of the JTAG signal lines of the processor carry any signal. With proper wiring and power supply, that's impossible.
So before anything else, check your wiring and power supply.
Post Reply

Return to “Toon Rooting”