matthias_bgg has quit [Read error: Connection reset by peer]
matthias_bgg has joined #linux-rockchip
vicencb has quit [Quit: Leaving.]
kaspter has quit [Remote host closed the connection]
perr_ has joined #linux-rockchip
kaspter has joined #linux-rockchip
perr has joined #linux-rockchip
perr_ has quit [Ping timeout: 265 seconds]
ifbizo has quit [Remote host closed the connection]
ifbizo has joined #linux-rockchip
vicencb has joined #linux-rockchip
perr has quit [Remote host closed the connection]
perr has joined #linux-rockchip
JohnDoe_71Rus has joined #linux-rockchip
<Depau>
Hi, I'm having boot related issues with the pinebook pro, I thought I'd ask here too. In short it's very unstable, out of roughly 500 times I rebooted it it managed to get to xorg on their stock image ~5 times, I got a shell ~20 times, otherwise it just failed to boot, the kernel crashed, it froze without any messages, wouldn't detect/power on eMMC, wouldn't manage to bring up eDP link, all sorts of things
<Depau>
Things I tried: test emmc with an external adapter (it works), boot from SD (same issues), flash an uboot build from github to SPI (kinda more reliable but same issues)
<Depau>
Now I'm out of ideas. Currently if I try to power it on, most of the times it hangs like this: https://pastebin.com/PQW193b9
<Depau>
What I'm planning to do is try to get it into maskrom and reflash it from there, however I'll have to learn how to do that and anyway it seems the "recovery" button they placed on the board doesn't actually do anything
<Depau>
Other than that I'm pretty much out of ideas. A friend suggested it might be a memory-related issue, but I don't know how to troubleshoot that/get more info
perr has quit [Ping timeout: 264 seconds]
ifbizo has quit [Remote host closed the connection]
ifbizo has joined #linux-rockchip
ifbizo has quit [Remote host closed the connection]
ifbizo has joined #linux-rockchip
tuxd3v has joined #linux-rockchip
ldevulder_ has joined #linux-rockchip
field^Mop has joined #linux-rockchip
ldevulder has quit [Ping timeout: 268 seconds]
ifbizo has quit [Remote host closed the connection]
ifbizo has joined #linux-rockchip
<anarsoul>
Depau: likely a faulty unit, contact pine64 support
<anarsoul>
micken: what's with grf settings?
<Depau>
anarsoul: thank you. I contacted them, they dismissed my ticket without even reading it and told me to ask help on IRC
<micken>
anarsoul: probably nothing , you talked about gpio not working
<anarsoul>
Depau: so ask on their irc? :)
<Depau>
I did ofc :D
<Depau>
I just found other people complaining
<anarsoul>
I don't see anything from you on their irc on #pinebook channel
<Depau>
Or other people complaining about pulseaudio lol
<Depau>
It's not on freenode
<anarsoul>
I know
<anarsoul>
was it today?
<Depau>
12.30PM UTC
<Depau>
Today
<micken>
Depau: tried to boot something else from sdcard?
<Depau>
micken: same random issues
<micken>
ok
<Depau>
Sometimes it boots, sometimes it does not, rarely the display turns on
<Depau>
Most times it's just like the last logs I sent
<micken>
:(
<anarsoul>
I assume you already tried reseating emmc?
<anarsoul>
Depau: ^^
<Depau>
anarsoul: yep
<Depau>
I also tested it with the USB adapter I also bought, it works fine over usb
<anarsoul>
micken: so how gpios are related to grfs?
<micken>
but not together with pinebook I assume?
<anarsoul>
pinebook uses the same emmc as in their other products
<micken>
anarsoul: a lot of settings for for gpio is in the GRF
<anarsoul>
I see
<anarsoul>
I wonder what's missing
<anarsoul>
:(
<micken>
but without gpio , I think you shouldnt even have sdcard
<micken>
or
<micken>
it might just redirect things from not using gpios
<micken>
dont remember
<anarsoul>
it doesn't require any gpios
<anarsoul>
I mean sd card
<micken>
right
<anarsoul>
well, one for detection but I doubt u-boot uses it
<micken>
probably not
<micken>
but what exactly doesn't work ? DO you know where in source?
<micken>
caps not intended
<anarsoul>
sd card works fine
<anarsoul>
as well as emmc and ethernet
<anarsoul>
usb doesn't get any power
<micken>
ok
<anarsoul>
I checked and gpios don't work
<micken>
so usb start reports error?
<anarsoul>
no
<anarsoul>
it detects no devices
<micken>
I see
<anarsoul>
since there's literally no 5v on USB ports
<anarsoul>
"gpio set 154" says "Warning: value of pin is still 0"
<anarsoul>
this gpio enables 5v for usb
<micken>
maybe it is the gpio command that isnt working?
<micken>
dunno
<micken>
I am not using mainline
<anarsoul>
try it? :)
<micken>
hmm
<robmur01>
anarsoul: is the I/O supply to the GPIO bank enabled?
<anarsoul>
robmur01: hmm, I don't see any supplies for gpio in rk3399.dtsi
<anarsoul>
am I missing something?
vicencb has quit [Quit: Leaving.]
<robmur01>
anarsoul: I mean the supply to APIO4_VDD, i.e. LDO6 of the RK808 (assuming we're talking about RockPro64)
vicencb has joined #linux-rockchip
<anarsoul>
ah, it's enabled
<anarsoul>
yes, it's rockpro64
<anarsoul>
there was a guy yestarday who said that usb works in mainline u-boot on rockpro64 for him
<anarsoul>
I really wonder *how* :)
<anarsoul>
maybe usb hdd with its own power supply?
<micken>
good idea try powered usb hub
<micken>
I need to try mainline
<micken>
but I dont have any sd spare cards
<anarsoul>
I don't have one
<micken>
ok
<robmur01>
the GPIO failing to go high certainly smells like the I/O voltage is missing (or insufficient) - I'd be inclined to stick a meter on the PMIC output to check there's really 3V there
<robmur01>
that or a short to ground, but then it wouldn't work outside u-boot either ;)
<micken>
isn't pmic code more or less the same u-boot <-> linux?
<micken>
ayofan's version works fine , expect for display
<robmur01>
dunno how exactly u-boot handles regulators, but it looks very different to Linux's massive framework
<micken>
true
<micken>
I can have a look
<micken>
if I can find a sd card :/
<micken>
does mainline have pmic or regulator commands ?
<micken>
the pmic status regs has to say something?
<robmur01>
if you can do raw i2c you could poke it directly
<micken>
yea
<micken>
if not do a simple test bin that does
<robmur01>
in fact it looks like most of the driver isn't even compiled outside the SPL :/
<micken>
bad
tuxd3v has quit [Quit: Leaving]
ldevulder_ is now known as ldevulder
<micken>
anarsoul: I can write a test program for you but I am afraid that it willb be aarch32 code ,, it might be easier to do it inside uboot using alrady existing i2c code
matthias_bgg has quit [Ping timeout: 240 seconds]
<robmur01>
hmm, puma-rk3399_defconfig selects CONFIG_CMD_I2C=y, so hopefully it ought to work on RK3399 in general
vagrantc has joined #linux-rockchip
<anarsoul>
robmur01: it works fine in linux
<anarsoul>
I'll check pmic output later tonight
<anarsoul>
thanks for the tips
<anarsoul>
micken: it has regulator commands
<anarsoul>
and rk808 driver is here
stikonas has joined #linux-rockchip
chewitt has quit [Quit: Zzz..]
chewitt has joined #linux-rockchip
<anarsoul>
robmur01: LDO6 on rockpro64 is vcc_1v5 according to dts
<anarsoul>
it's always-on, boot-on and not referenced anywhere
<hanetzer>
use that on Image. assuming this is coming from buildroot?
<sphalerite>
no, it's coming from me building the kernel from kernel sources myself
<hanetzer>
payloads/external/LinuxBoot/arm64/kernel_fdt_lzma.its << use this to join kernel and initramfs
<hanetzer>
and you can compress the initramfs with payloads/external/LinuxBoot/Makefile:42
<sphalerite>
right
<sphalerite>
or maybe it would be easier to let coreboot's build system build linux for me x)
<hanetzer>
perhaps. I just used buildroot and did the compression and fit image myself, stuck the uImage into the coreboot tree and pointed it at that.
<sphalerite>
right
<sphalerite>
I'll see how letting coreboot take care of it goes, if that fails I'll try what you said
<sphalerite>
because I'm not all that familiar with this stuff and think I have better chances of using a thing that does it for me than doing it myself :D
<sphalerite>
anyway, thank you very much for your help! I really appreciate it
<hanetzer>
np. also, make sure you feed it an uncompressed Image iehter way :)