ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | IRC log http://irclog.whitequark.org/linux-rockchip | Community GH https://github.com/linux-rockchip | Rockchip GH https://github.com/rockchip-linux | ML https://groups.google.com/group/linux-rockchip
vstehle has quit [Ping timeout: 245 seconds]
wwilly has quit [Ping timeout: 245 seconds]
wwilly has joined #linux-rockchip
vstehle has joined #linux-rockchip
omegamoon[m] has joined #linux-rockchip
ldevulder has joined #linux-rockchip
sphalerite_ has joined #linux-rockchip
inode has joined #linux-rockchip
ldevulder has quit [Quit: Leaving]
ldevulder has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
sphalerite has quit [Quit: WeeChat 2.4]
sphalerite_ is now known as sphalerite
kilobyte_ch has quit [Ping timeout: 248 seconds]
kilobyte_ch has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
field^Mop has joined #linux-rockchip
ckeepax has quit [Quit: WeeChat 2.2]
ckeepax has joined #linux-rockchip
s_frit has quit [Remote host closed the connection]
s_frit has joined #linux-rockchip
vicencb has joined #linux-rockchip
jelly has quit [Read error: Connection reset by peer]
jelly-home has joined #linux-rockchip
<fALSO> yo ppl
<fALSO> just received a rockpro 64
<fALSO> gonna play with it today, see if I can get it booting
<fALSO> I already created a page with instructions on my personal wiki
<fALSO> Untested, but ill test later today
<fALSO> If anyone has any changes please tell me
<fALSO> Im trying to do it using only free/open source stuff
<fALSO> i have doubts specially on the boot process
<fALSO> i couldnt find any "real" up to date instructions
adjtm_ has quit [Ping timeout: 248 seconds]
<fALSO> Havent seen anyone talking here
<fALSO> Is there any other rockchip related channel?
jelly-home is now known as jelly
mrjay has joined #linux-rockchip
<mrjay> paccer: did you made any progress?
<paccer> hmmm, not really, you saw my last message?
<paccer> this: cer> mrjay, didn't give up, haven't had too much time... made some more tries, but with same result (black screen during boot, no serial output).. even tried with another kernel which i believe should be working, but with same results.. so i guess it could be my packaging method thats failing... perhaps :/
<mrjay> yep ... lets start with basics ... how do you compile your kernel?
<paccer> ill have another go at it if you're planning to stick around for a bit
<mrjay> what toolchain do you use?
<mrjay> yep ... i have time
<paccer> as mentioned, i tried with a precompiled kernel but with exactly same result
<paccer> hang on, will get everything ready
<mrjay> hmmmmm ... did you use kernel for rk3066 armhf arch?
<paccer> yeah, tried with the kernel from picuntu or whatever its called
<paccer> basicly extracted it and re-packaged it
<mrjay> so you didn't try with mainline (linux stable or next)?
<paccer> i doubt i can find a mainline precomiled rk3066 kernel
<paccer> (i did compile my own first, same result)
<paccer> what im trying to say, is that i am suspicious that something is wrong with my "partition", not my kernel
<mrjay> if its tablet than you most probably won't get any output on tablet screen only on hdmi and/or serial console
<mrjay> with mainline kernel
<paccer> im relying on serial terminal, i dont trust drivers etc to work
<mrjay> ok ... you need to compile mainline kernel ... do you know how?
<paccer> i already did? we talked about it last time...
<paccer> you even went over my kernel config
<mrjay> ah ok ... i remember now
<paccer> booting another kernel was just another approach to confirm that at least that worked (which it did not)
<paccer> to exclude options
<paccer> bah, cant boot tablet right now, drained battery since last time
<paccer> will need to charge it first for a few mins
<paccer> serial output stops when it tries to boot
<paccer> uhm
<paccer> i can't figure out if its because the kernel stops it, or because it stops because it fails to boot partition
<paccer> my conclusion after trying another precompiled kernel was pretty much, that something is wrong with my partition
<mrjay> ok ... maybe you could try with my kernel for other device but i'm at work now and will be home later
<paccer> sure :) i think that would at least help narrow down the problem
<paccer> until then, ill still have another go at it and see what i can figure out
<mrjay> ok ... see you later
<paccer> wait, what?
<paccer> im not leaving, and you said you were around for a bit :P
<mrjay> ok i'm not going anywhere
<paccer> so, this is what my boot log looks like in both cases:
<paccer> when i flashed the pre-made rk3066 picuntu recovery image (containing kernel), my boot log got further and it seemed it booted fine until kernel re-routed serial output
<paccer> so again, my suspicion is that im doing something wrong creating the image
<paccer> been doing this as you recommended https://pastebin.com/d2iNLZjC
<paccer> except for corrected address of course
<paccer> im not sure if there are other steps needed for recovery partition, but its my understanding that its basicly just another boot partition and should work
<paccer> i feel like its very difficult to research on, because theres a lot of information out there, some from before openssourced kernel ,some before mainline etc., some instructions say you can't do something, some says you can etc.
<paccer> oh, also, you recommended me some kernel parameters, i tried them out
<paccer> didnt have to recompile kernel since i can add them with a parameter to mkbootimg
<paccer> perhaps its my dtb file
<paccer> did you try mainline kernel, mrjay ?
<mrjay> yep ... mainline linux-next is the kernel i'm using
<paccer> making a shell script now for packaging the kernel/image, to make it easier to try some differenet parameters etc
_kj_ has joined #linux-rockchip
<_kj_> Hi all. I have following question regarding RockChip 3399: is there any official documentation regarding secure efuse layout? Especially: what is offset for public key hash, which banks are free for user to put custom data?
<paccer> mrjay, ok, something weird is going on... the rx LED on my uart reciever is flashing after serial output stops... could be either wrong baud rate (it should be correct), or i guess it could be the uart being used as some other gpio function i guess
<paccer> i have a logic analyzer, so i can take a look at whats going on, on the rx line
<mrjay> paccer: baud rate should be 115200 ... but you see the output from rockchip loader so you should be ok
<paccer> i've hardcoded baudrate to 115200, so yeah
<paccer> (console=ttyS2,115200 or similar)
<mrjay> yep
<mrjay> thats it
<paccer> rx led should only blink on activity, so im curious whats going on
<paccer> since its blinks after output stops
<mrjay> weird :/
<paccer> logic analyzer time ;)
<paccer> interesting, its definitely a lower speed than initial speed
<paccer> but looks like data
<paccer> aha! seems to be 9600
<mrjay> so you have output at 9600 bauds ?
<paccer> bingo!
<paccer> yep
<paccer> kernel outputs in 9600
<mrjay> which kernel ? mainline or picuntu
<paccer> mainline
<paccer> weird since im using --cmdline with mkbootimg, which should override boot parameters
<mrjay> it ignores console= line ... some bug maybe
<mrjay> are you able to login?
<paccer> nah, it doesnt get that farh
<paccer> *far
<paccer> let me dump the output, hang on
<paccer> but yeah, i haven't even really focused on a system image yet since i just wanted to get the kernel booting first of all, so it might not be "ready" to get that far
<paccer> i do have picuntu system image on sd card, but that might not work
<paccer> at least now i know my partition is working
<mrjay> paccer: use marsboard dtb or rayergear dtb not mk808 one
<paccer> np :) i have a shell script for that now :P
<paccer> one moment
<fALSO> im gonna try to boot archlunix on my rockpro64 today
<paccer> mrjay, ok, rayergear seems to have made it worse (no serial output when booting kernel), wil try marsboard
<paccer> things are slow because tablet is being weird sometimes and doesnt boot properly into some of the modes half of the time
JohnDoe_71Rus has joined #linux-rockchip
field^Mop has quit [Ping timeout: 252 seconds]
<paccer> and ince i dont have hardware access to booloader mode or whatever its called, i access it by booting android first and then booting into bootloader mode
<paccer> so process can be a bit slow
<paccer> oh, im an idiot
<paccer> i used dts instad of dtb
<paccer> trying again
<mrjay> :)
<paccer> i really need to add a hardware button for bootloader access
<paccer> but trying to avoid messing with it too much, screen cable had a bad connection and wants to break
<paccer> mrjay, with rayergear: https://pastebin.com/AZygHn38
<paccer> and this is with marsboard: https://pastebin.com/Ck6Vq24L
<paccer> bootloader mode = mask ROM mode, but you probably figured out whta i meant :)
<mrjay> ok ... i need to go now but will be back in 2h
mrjay has quit [Remote host closed the connection]
elektirnis has joined #linux-rockchip
adjtm has joined #linux-rockchip
elektirnis has quit [Ping timeout: 245 seconds]
elektirnis has joined #linux-rockchip
elektirnis has quit [Ping timeout: 245 seconds]
aalm has joined #linux-rockchip
vicencb has quit [Ping timeout: 244 seconds]
wwilly has quit [Ping timeout: 272 seconds]
vicencb has joined #linux-rockchip
JohnDoe_71Rus has quit [Ping timeout: 246 seconds]
wwilly has joined #linux-rockchip
adicarlo has joined #linux-rockchip
<adicarlo> I'm working on a librecomputer "renegade" board but I assume this question is more general...
<adicarlo> are there any pointers to how to override the HDMI resolutions? I can set videomode in u-boot but it doesn't seem to have any effect
<adicarlo> I wonder if I need a devicetree overlay perhaps?
vagrantc has joined #linux-rockchip
mrjay has joined #linux-rockchip
<mrjay> paccer: i'm back
<paccer> hey :)
<mrjay> paccer: hi
<mrjay> now the hard work begins
<mrjay> you must find gpios ... and write your own devicetree file
<mrjay> could you paste links to bootlogs ... irclog has bad gateway again
<paccer> sure :)
<paccer> rayergear: https://pastebin.com/AZygHn38
<paccer> marsboard: https://pastebin.com/Ck6Vq24L
matthias_bgg has quit [Ping timeout: 258 seconds]
<paccer> initially, when i installled the picuntu kernel/recovery partiton, i did get some output on screen (garbled, wrong resoution/refresh rate)
<paccer> so i was hoping to find some info about the dtb from there and base mine on that
<mrjay> picuntu uses kernel from before dtb era
<mrjay> all was hardcoded then
<paccer> ohh... :/
<paccer> maybe i can get some info from the running android or something
<paccer> dumped all the info i could find from it
<mrjay> maybe you could but i don't know how android handles stuff
<paccer> me neither :P but i guess its pretty close to linux in general
<paccer> i dont see any specific errors that stops kernel boot in the logs...
<paccer> was expecting some kind of error
<mrjay> pwm-regulator vdd-log: Failed to get PWM: -517
<paccer> any idea what the regulator supplies?
<paccer> if something is not being powered, i would still expect some kind of error when trying to initialize it or something
<mrjay> this one is dangerous as it can hang the board ... vdd-log is the important one ... it can hang the board ... that is all i know
<paccer> ah ok :) at least you know its critical
<paccer> oh shit yeah, vdd_log might be a whole power rail of some sort if anywhere close to this schematic: http://www.haoyuelectronics.com/service/RK3066/Schematic/CM-RK3066/CM-RK3066_SCH.pdf
<mrjay> yeah ... vdd_log is important
<paccer> i guess it should be possible to find a regulator (perhaps SY8009B) and figure out where its connected to
<mrjay> did you found old kernel source for your tablet?
<paccer> oh no
<paccer> its a very generic rebranded tablet
<paccer> pretty sure i wont find any
<mrjay> what model is that
<paccer> heh
<paccer> Ennovia TAB E309
<paccer> good luck :P
<paccer> android says TAB-E309(V3)
<mrjay> yep ... i've got nothing :)
<paccer> at least its not just me then :P
<paccer> the PCB is relatively simple, i should be able to figure this out
<mrjay> cool
<paccer> im looking for a GPIO connected to a regulator i assume
<mrjay> vdd_log is a PWM driven regulator
<paccer> yup
<paccer> but i assume its the RK3066 providing the pwm signal for it
<mrjay> yep
<paccer> i believe its probably a tps65910 (according to the previous paste from android log)
<paccer> hmm... seems a bit odd to me that its pwm controlled
<paccer> meh, or maybe not...
<paccer> but tps65910 seems to be i2c if im not mistaken
<mrjay> yeah it uses i2c bus to configure
<mrjay> voltage
<paccer> so not pwm *controlled* then?
<mrjay> tps65910? no
<paccer> how do we even know that vdd-log is supposed to be a pwm controlled regulator?
ldevulder_ has joined #linux-rockchip
<paccer> some other solution could have been used in this case
<paccer> hence the configuration mismatch
ldevulder has quit [Ping timeout: 245 seconds]
<paccer> oh, theres already an #include "tps65910.dtsi"
<paccer> in rk3066a-marsboard.dts
<paccer> might not be the chip i'm looking for then i guess
<paccer> or i guess maybe it could be.... but with wrong gpip's being used...
<paccer> sorry for thinking out loud :P i seem to be confusing myself here a bit
<mrjay> np :)
<paccer> do you know of a place with documentation for the dts files?
<paccer> for an examle an explanation of the meaning of "pwms = <&pwm3 0 1000>;
<paccer> " etc
<paccer> not really sure exactly where the gpio numbers are specified
<mrjay> Documentation/devicetree/bindings/pwm/pwm-rockchip.txt
<mrjay> in linux source tree
<paccer> ah, thanks
<mrjay> pwm3 - pwm used, 0 - i think its polarity, and 1000 is a pwm frequency
<paccer> ah, right
<paccer> theres actualy a pin named pwm3
<paccer> found it in rk3066 datasheet
<paccer> was expecting a number
stikonas has joined #linux-rockchip
<paccer> my best bet at finding kernel sources is probably searching for pcb "model", which is "ZM973L-MB-V1.3"
stikonas has quit [Read error: Connection reset by peer]
stikonas_ has joined #linux-rockchip
mrjay has quit [Remote host closed the connection]
stikonas_ has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
lkcl has quit [Ping timeout: 258 seconds]
Putti has quit [Ping timeout: 268 seconds]
field^Mop has joined #linux-rockchip
lkcl has joined #linux-rockchip
inode has quit [Quit: ]
field^Mop has quit [Ping timeout: 252 seconds]
stikonas has quit [Ping timeout: 252 seconds]
<adicarlo> does anyone have guidance on how to force an HDMI videomode on a renegade soc (RK3328)? I think its a u-boot thing... possibly rockchip specific u-boot...
vicencb has quit [Quit: Leaving.]
vagrantc has quit [Quit: leaving]