ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion
hanetzer has quit [Ping timeout: 268 seconds]
Danct12 has quit [Read error: Connection reset by peer]
hanetzer has joined #linux-rockchip
stikonas has quit [Ping timeout: 268 seconds]
vagrantc has quit [Quit: leaving]
lurchi__ has joined #linux-rockchip
lurchi_ has quit [Ping timeout: 268 seconds]
Danct12 has joined #linux-rockchip
uis has quit [Quit: ZNC 1.7.5 - https://znc.in]
uis has joined #linux-rockchip
kevery has quit [Remote host closed the connection]
kevery has joined #linux-rockchip
stikonas has joined #linux-rockchip
uis has quit [Quit: ZNC 1.7.5 - https://znc.in]
uis has joined #linux-rockchip
uis has quit [Quit: ZNC 1.7.5 - https://znc.in]
uis has joined #linux-rockchip
stikonas has quit [Ping timeout: 268 seconds]
tlwoerner has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
vagrantc has joined #linux-rockchip
<hanetzer> anyone here got a rk3288/rk3399 device with u-boot on hand who can do some poking for me?
<mps> hanetzer: if it counts I'm preparing to test mainline u-boot on gru-kevin chromebook (rk3399) but didn't yet prepared all
<hanetzer> mps: should be fine, if it works. I have one but its inconveniently stored atm :)
<hanetzer> basically I want you to md a region of memory and see if the brom is dumpable :)
<mps> I've built u-boot but didn't yet created kpart image
<hanetzer> ah, you don't need a kernel for this, assuming you can access usb/sdcard to write stuff
<mps> I thought you want something from booted u-boot
<hanetzer> nah. md lets you see stuff at memory addresses (whether that's actual ram/sram or or mmio registers)
<mps> what you mean by 'md'
<hanetzer> its a command in u-boot's shell.
<mps> aha
<mps> so I have to boot with u-boot and break it
<hanetzer> yee
<mps> for this I must prepare kpart image with vboot-utils, I think
<mps> actually I had it with alpernebbis u-boot but erased this mmc
<hanetzer> oh, you're chainloading from coreboot/depthcharge? that should be fine, maybe.
<mps> yes, I don't want to write it to flash, at least for now
<hanetzer> fair nuff.
<mps> hanetzer: sorry but I got only blank screen when tried to boot
<hanetzer> its all good, thanks.
indy has quit [Quit: ZNC 1.8.2 - https://znc.in]
indy has joined #linux-rockchip
<vagrantc> hanetzer: i have several rk3399 and at least one rk3288 (although it failed to load mainline u-boot ~2022.04-rc~)
<vagrantc> well, several rk3288, but they're all the same
<vagrantc> firefly-rk3288
<lvrp16> hanetzer: I have one running if you need me to run something
uis has quit [Quit: ZNC 1.7.5 - https://znc.in]
uis has joined #linux-rockchip
<hanetzer> lvrp16: thanky. you in u-boot shell?
<lvrp16> yeah
<hanetzer> which soc?
<lvrp16> rk3399
<lvrp16> i have rk3328 as well if you need
<hanetzer> ok, lemme see what the address is :)
<hanetzer> md 0xfffd0000
<lvrp16> instant crash
<hanetzer> hah
<hanetzer> ok, try 0xffff0000 ifn' ya don't mind
<lvrp16> same
<hanetzer> worth a shot, thank.
<lvrp16> np
<hanetzer> I'd like to see this on the uh 3288 tho
<lvrp16> i have a tinkerboard but it's buried somwhere as well
<macc24> hanetzer: i have a rk3288 laptop
<hanetzer> macc24: got u-boot?
<hanetzer> if so, same two memory addresses
stikonas has joined #linux-rockchip
f476 has quit [Ping timeout: 268 seconds]
Danct12 has quit [Ping timeout: 252 seconds]