Home Automation Domotica Forum Europe, Bwired Forum

Hi,

I'm having problems with my pi4 and ToonRooter app (also the ToonRecovery app).

the script runs fine until the " waiting for toon to restart" step

pi@raspberrypi:~/ToonRooter $ sudo python . --jtag-available --jtag-hardware rpi4
INFO:__main__:Starting up...
INFO:__main__:Written private and public key pair to ./id_rsa and ./id_rsa.pub, respectively
INFO:rooter:Waiting for Toon to restart
INFO:rooter:Toon has U-Boot version 2010.09-R10
INFO:rooter:Loading new bootloader
INFO:rooter:Starting openocd
INFO:rooter:Waiting for 10 seconds
INFO:rooter:Halting CPU
INFO:rooter:Loading new image to RAM
INFO:rooter:Starting up new image
INFO:rooter:Waiting for Toon to restart
pi@raspberrypi:~/ToonRooter $ sudo python . --jtag-available --jtag-hardware rpi4
INFO:__main__:Starting up...
INFO:__main__:Written private and public key pair to ./id_rsa and ./id_rsa.pub, respectively
INFO:rooter:Waiting for Toon to restart
INFO:rooter:Toon has U-Boot version 2010.09-R10
INFO:rooter:Loading new bootloader
INFO:rooter:Starting openocd
INFO:rooter:Waiting for 10 seconds
INFO:rooter:Halting CPU
INFO:rooter:Loading new image to RAM
INFO:rooter:Starting up new image
INFO:rooter:Waiting for Toon to restart


After this step nothing happens, it seems like the Toon isn't receiving the instruction to restart form my pio.

I performed the GPIO test script and it seems like it isn't related to a hardware fault of my pi.
I also tried swapping the jtag cables to fresh ones, it also didn't work.
A fresh raspberry pi install also didn't do the trick.

So. im kinda lost what is causing this issue.
Any thoughts?

some extra info:

it rooted R8 toon fine, but it froze again at a different R10.

So it seems like there is either an issue with OpenOCD or with my JTAG.
Anyone else experience these issues?

Check this post https://www.domoticaforum.eu/viewtopic. ... 420#p97088

I believe Pi4 is too fast for some openocd checks.

just read some stuff on google on PI4 and OPENOCD

seems like something changed on the pi4 regarding pull up and pull down requests?

does that ring a bell for someone?

toonnoot wrote:just read some stuff on google on PI4 and OPENOCD

seems like something changed on the pi4 regarding pull up and pull down requests?

does that ring a bell for someone?

didn't you reed the post I pointed to? just change the speed in the rpi4.cfg as noted in that post
and if you want us to look a a page you found on google, please point us there instead of letting us google also

TheHogNL wrote:

toonnoot wrote:just read some stuff on google on PI4 and OPENOCD

seems like something changed on the pi4 regarding pull up and pull down requests?

does that ring a bell for someone?

didn't you reed the post I pointed to? just change the speed in the rpi4.cfg as noted in that post
and if you want us to look a a page you found on google, please point us there instead of letting us google also

I tried the suggestions there.
I increased it to 1000, decreased it to 200, to 100, didnt work.

It seems like the pi is disabling (some of) the pins 18-25.
https://www.vinnie.work/20201106-baremetal-rpi4-setup/

I tried this suggestion, which also didnt help:
“ The one big gotcha that caught me off guard when attempting to test everything was the fact that, at reset, the BCM2711 has a default pull down on all GPIO pins. Therefore, there is an additional bit of configuration you have to do for the RPi4 (that was not required for any previous RPi). You must disable the pull down resistors for GPIO22 - GPIO27 to allow the TDI/TDO data to flow freely.”

Gebruik anders gewoon de software rooter https://github.com/ToonSoftwareCollective/Root-A-Toon

ToonRooter werkt blijkbaar niet altijd goed op een Pi4

TheHogNL wrote:Gebruik anders gewoon de software rooter https://github.com/ToonSoftwareCollective/Root-A-Toon

ToonRooter werkt blijkbaar niet altijd goed op een Pi4

Ja dat heb ik inderdaad ook gedaan, maar dan kan ik bv de ToonRecovery tool niet gebruiken met mijn nieuwe Pi...

toonnoot wrote:

TheHogNL wrote:Gebruik anders gewoon de software rooter https://github.com/ToonSoftwareCollective/Root-A-Toon

ToonRooter werkt blijkbaar niet altijd goed op een Pi4

Ja dat heb ik inderdaad ook gedaan, maar dan kan ik bv de ToonRecovery tool niet gebruiken met mijn nieuwe Pi...

Toon 1 is toch technisch afgeschreven
Maar ik ga wel eens een keer op mijn Pi4 testen.

TheHogNL wrote:

toonnoot wrote:

TheHogNL wrote:Gebruik anders gewoon de software rooter https://github.com/ToonSoftwareCollective/Root-A-Toon

ToonRooter werkt blijkbaar niet altijd goed op een Pi4

Ja dat heb ik inderdaad ook gedaan, maar dan kan ik bv de ToonRecovery tool niet gebruiken met mijn nieuwe Pi...

Toon 1 is toch technisch afgeschreven
Maar ik ga wel eens een keer op mijn Pi4 testen.

En.. gelukt?

toonnoot wrote:

En.. gelukt?

Eens een keer,.. dat betekend bij mij ergens komende weken

It still doesnt seem to work, the toonrooter with a rpi4.

Anyone been able to fix this?
The rpi4 asset file doesnt seem to fix it for me

anyone?