ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
shailangsa has quit [Ping timeout: 265 seconds]
Shailangsa_ has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
archetyp` has joined #linux-rockchip
archetyp has quit [Ping timeout: 252 seconds]
lurchi_ has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 252 seconds]
armoon has joined #linux-rockchip
armoon has quit [Quit: Client closed]
armoon has joined #linux-rockchip
lopsided98 has quit [Ping timeout: 265 seconds]
lurchi_ is now known as lurchi__
cyrozap has quit [Ping timeout: 240 seconds]
cyrozap has joined #linux-rockchip
warpme_ has joined #linux-rockchip
Shailangsa_ has quit []
lopsided98 has joined #linux-rockchip
levd has joined #linux-rockchip
levd has quit [Client Quit]
armoon has quit [Quit: Client closed]
armoon has joined #linux-rockchip
shailangsa has joined #linux-rockchip
archetyp` has quit [Remote host closed the connection]
archetyp has joined #linux-rockchip
lurchi__ is now known as lurchi_
lurchi__ has joined #linux-rockchip
lurchi_ has quit [Ping timeout: 255 seconds]
avg_II has joined #linux-rockchip
<avg_II> I have an interesting problem with dw-wdt on Rock64 (rk3328 based)
<avg_II> I wonder if I am alone or if anyone else experienced it
<avg_II> the pre-timeout works well, I get the interrupt
<avg_II> but on the second timeout (or the first timeout without pre-timeout) the system hard hangs (somewhat ironically)
<avg_II> instead of getting reset
<avg_II> just in case, my rock64-s are from a very cheap offer that was on amazon some time ago
archetyp has quit [Quit: Leaving]
armoon has quit [Quit: Client closed]
armoon has joined #linux-rockchip
archetyp has joined #linux-rockchip
armoon has quit [Quit: Client closed]
archetyp has quit [Quit: Leaving]
<mmind00> avg_II: another possibility might be the system resetting but not coming back up again (like hanging in bootrom or so) ... but so far I haven't heared anything like your problem
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
<avg_II> mmind00: I have serial console attached and there is nothing on it when the hang happens
<avg_II> also the heartbeat led stop blinking and the machine stops pinging
<mmind00> avg_II: doesn't matter for the case above ... the bootrom (tiny rom inside the soc) wouldn't emit anything
<avg_II> ah, I see
<avg_II> I tried playing with the watchdog's reset pulse length, but that did not help
lurchi__ has quit [Ping timeout: 255 seconds]
stikonas has quit [Quit: Konversation terminated!]
stikonas has joined #linux-rockchip
<robmur01> I wonder if it's a variant of the "Tinkerboard problem", wherein the reset happens while the SD card/eMMC is in a state that the bootrom can't fetch the bootloader from
<robmur01> if you have the right USB cable it might be worth seeing if it's actually rebooted into maskrom mode rather than just wedged
lurchi__ has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
armoon has joined #linux-rockchip
lurchi__ has quit [Quit: Konversation terminated!]
lurchi__ has joined #linux-rockchip
stikonas has quit [Ping timeout: 268 seconds]
stikonas has joined #linux-rockchip
lurchi_ has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 246 seconds]
lurchi__ has joined #linux-rockchip
lurchi_ has quit [Ping timeout: 252 seconds]
lurchi__ has quit [Ping timeout: 240 seconds]
lurchi__ has joined #linux-rockchip
<avg_II> let me research that, thank you
<avg_II> after some tinkering I found a "magic" change that makes the reset work, but not sure why it could be required
<avg_II> the change is flipping bit of CRU_GLB_CNT_TH to 1
<avg_II> bit 15
lurchi__ has quit [Ping timeout: 240 seconds]
lurchi_ has joined #linux-rockchip
lurchi_ is now known as lurchi__
<avg_II> "watch_dog trigger global soft reset select"
<avg_II> as far as I could understand it makes the watchdog use global soft reset number 1 instead of number 2
<avg_II> and the first one seems like it does a fuller reset
<avg_II> but, anyway, no idea why that hack could be required
lurchi__ is now known as lurchi_
<avg_II> I could not find any use of CRU_GLB_CNT_TH in any code base (linux, u-boot)
lurchi_ has quit [Remote host closed the connection]
lurchi_ has joined #linux-rockchip
lurchi_ is now known as lurchi__
armoon has quit [Quit: Client closed]
vagrantc has joined #linux-rockchip
vagrantc has quit [Client Quit]
macc24 has quit [Read error: Connection reset by peer]
macc24 has joined #linux-rockchip
vagrantc has joined #linux-rockchip
vagrantc has quit [Ping timeout: 252 seconds]
macc24 has quit [Quit: WeeChat 3.2]
macc24 has joined #linux-rockchip
vagrantc has joined #linux-rockchip
archetyp has joined #linux-rockchip
vagrantc has quit [Ping timeout: 268 seconds]
vagrantc has joined #linux-rockchip
lurchi__ is now known as lurchi_
archetyp has quit [Quit: Leaving]
archetyp has joined #linux-rockchip
vagrantc has quit [Ping timeout: 255 seconds]
vagrantc has joined #linux-rockchip
vagrantc has quit [Ping timeout: 255 seconds]
vagrantc has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
lurchi_ is now known as lurchi__