<hurricos>
vagrantc: Hey! I found you. Can I ask some questions about veyron boards?
<vagrantc>
hurricos: i don't know much, but i have one
<hurricos>
Ah, that's enough :) SEO pushes irc logs very high so you know more than enough ... I have what claims to be a veyron jerry, out of a CTL J2; it gives access to the 4MB flash SOIC
<hurricos>
Can you confirm that as a chromeos device the soic contains coreboot, and the eMMC has depthcharge?
<vagrantc>
likely conmtains coreboot and depthcharge
<vagrantc>
contains...
<vagrantc>
it's not impossible to put something else there, i think there may be a u-boot port for it
<vagrantc>
but out of the box i'd guess coreboot/depthcharge
<hurricos>
My goal: I have some scrapped veyron jerry's that I'd like to flash the SOICs on so they can easily boot e.g. from a USB.
<hurricos>
I'm surprised to hear depthcharge on the SOIC as if I'm not mistaken coreboot is not the one initializing graphics
<hurricos>
which usually means blobs which are big
<hurricos>
The libreboot guide for the C201 (veyron_speedy) mentions requiring root in ChromeOS which I do not have. Since I don't have a servo header to solder onto the board to get serial I've been assuming I would need something which I can build to boot over USB by default, which could then load up a linux kernel, modeset, boom, I can fix things in eMMC.
<hurricos>
so I'm curious to know how you have your veyron configured.
<vagrantc>
i had to flash the SOIC
<vagrantc>
well, i think the first time i did it from chromos somehow ... but then botched u-boot testing at some point
<hurricos>
Yeah, that's what confuses me a bit -- I am unsure where CrOS state is stored and would want a reliable way to not rely on it.
stikonas has quit [Remote host closed the connection]
mrjay has quit [Remote host closed the connection]
lkcl has joined #linux-rockchip
robmur01_ is now known as robmur01
damex has quit [Read error: Connection reset by peer]
damex has joined #linux-rockchip
stikonas has joined #linux-rockchip
stefan_ has joined #linux-rockchip
lkcl has quit [Ping timeout: 264 seconds]
kevery has quit [Ping timeout: 256 seconds]
lkcl has joined #linux-rockchip
<stefan_>
HI, trying to boot RK3399 from SPI but having troubles. I am now using mainline U-Boot 2020.10 and the latest ATF and am trying to build the tpl + spl + u-boot.itb
kevery has quit [Remote host closed the connection]
kevery has joined #linux-rockchip
<stefan_>
dvergatal: it is one custom board, but has SOM-RK3399 v2
<stefan_>
I made some progress
<stefan_>
But now I am getting error
<stefan_>
unrecognized JEDEC id bytes: 00, 81, 10
<dvergatal>
stefan_: i dunno how about you but i had a problem with firefly-rk3399 for over a month because of bad dts files for this board in u-boot mainline
<dvergatal>
first try to but using sd card
<dvergatal>
if it wil work for you than try to work with spi
<dvergatal>
more over stikonas has some experienc in booting from spi
<dvergatal>
stefan_: he has also a blog on which he has described it all