stikonas_ has quit [Remote host closed the connection]
kevery has joined #linux-rockchip
<tuxd3v>
hello all,
<tuxd3v>
does anybody knows if mainline uboot/Linux kernel are working nice in rockpro64?
<anarsoul>
yes
<tuxd3v>
anarsoul, thanks when I got some time will try it ;)
cyteen has quit [Ping timeout: 240 seconds]
cyteen has joined #linux-rockchip
chiastre has quit [Remote host closed the connection]
chiastre has joined #linux-rockchip
s_frit has quit [Remote host closed the connection]
s_frit has joined #linux-rockchip
vstehle has quit [Ping timeout: 240 seconds]
<wens>
tuxd3v: seems you are working on a lot of boards at the same time?
ldevulder__ has quit [Ping timeout: 240 seconds]
<tuxd3v>
wens, just evaluating options, til the moment rockpro64 seems to be the only board capable to sustain heat under extreme pressure for long periods of time due to the cooling system..
<tuxd3v>
other boards reach easilly 80C, under rockpro64 with the fan tunned I only got 56-57C
<tuxd3v>
its big but has its advantages :)
<wens>
with an external fan?
<tuxd3v>
yes
<tuxd3v>
maybe hardkernel with xu4, but I don't have it to test
<tuxd3v>
rockpro64 winter or summer maximum go close to 60C, if you tune the fan right :)
<tuxd3v>
so for intensive work, til now, its the only option I see,
<tuxd3v>
had you experinced with some board that has a nice cooling system?
<tuxd3v>
capable to work 24x7?
_whitelogger has joined #linux-rockchip
vstehle has joined #linux-rockchip
camus1 has joined #linux-rockchip
kaspter has quit [Ping timeout: 264 seconds]
camus1 is now known as kaspter
s_frit has quit [Ping timeout: 246 seconds]
ldevulder has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
mias_ has joined #linux-rockchip
mias_ has quit [Ping timeout: 256 seconds]
lkcl has joined #linux-rockchip
paulk-leonov has joined #linux-rockchip
lkcl has quit [Ping timeout: 260 seconds]
lkcl has joined #linux-rockchip
ldevulder has quit [Quit: Leaving]
ldevulder has joined #linux-rockchip
mias_ has joined #linux-rockchip
stikonas has joined #linux-rockchip
robmur01_ has joined #linux-rockchip
robmur01_ has quit [Ping timeout: 265 seconds]
robmur01_ has joined #linux-rockchip
kevery has quit [Ping timeout: 264 seconds]
robmur01_ has quit [Ping timeout: 264 seconds]
lkcl has quit [Read error: Connection reset by peer]
robmur01_ has joined #linux-rockchip
robmur01_ has quit [Ping timeout: 265 seconds]
chiastre has quit [Remote host closed the connection]
chiastre has joined #linux-rockchip
robmur01_ has joined #linux-rockchip
dlrobertson has quit [Ping timeout: 246 seconds]
lkcl has joined #linux-rockchip
field^Zzz1 has joined #linux-rockchip
lkcl has quit [Ping timeout: 240 seconds]
robmur01_ has quit [Ping timeout: 264 seconds]
robmur01_ has joined #linux-rockchip
robmur01_ has quit [Ping timeout: 240 seconds]
robmur01_ has joined #linux-rockchip
lkcl has joined #linux-rockchip
lkcl has quit [Read error: Connection reset by peer]
JohnDoe_71Rus has joined #linux-rockchip
mps has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
stikonas_ has joined #linux-rockchip
lkcl has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas_ has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
sigmaris_ has joined #linux-rockchip
sigmaris has quit [Ping timeout: 272 seconds]
sigmaris_ is now known as sigmaris
stikonas_ has joined #linux-rockchip
robmur01_1 has joined #linux-rockchip
robmur01_ has quit [Ping timeout: 246 seconds]
robmur01_1 is now known as robmur01_
robmur01_1 has joined #linux-rockchip
<mps>
where I can send bug report related to rockchip drm and analogix bridge
robmur01_ has quit [Ping timeout: 250 seconds]
robmur01_1 is now known as robmur01_
matthias_bgg has quit [Ping timeout: 265 seconds]
matthias_bgg has joined #linux-rockchip
adjtm has quit [Remote host closed the connection]
adjtm has joined #linux-rockchip
lkcl has quit [Read error: Connection reset by peer]
lkcl has joined #linux-rockchip
mfny has joined #linux-rockchip
robmur01_ has quit [Ping timeout: 264 seconds]
<mfny>
Hi all
<mfny>
looking for some input on which of the various Rockchip SBC makers has the best support/community ecosystem right now ?
robmur01_ has joined #linux-rockchip
robmur01_ has quit [Client Quit]
<JPEW>
mfny: Not sure what kind of support your looking for, but the RockPi4 and the Asus Tinkerboard have good upstream support. I've been helping to maintain them in Yocto project: http://git.yoctoproject.org/cgit/cgit.cgi/meta-rockchip
<mfny>
JPEW: I mean good documentation, plenty of examples and such of use, frequent software updates and an active community
<mfny>
that sort of thing
<Jin^eLD>
mfny: if you just want to use it and not cross compile anything, I'd check the armbian website and see what devices they support
<Jin^eLD>
and pick one you like
chiastre has quit [Quit: chiastre]
vagrantc has joined #linux-rockchip
<tuxd3v>
Hello guys, I am still stuck at bootloader..
<tuxd3v>
can't find a way to build one that works..
<tuxd3v>
for rockpi4A
<tuxd3v>
here is my log of the boot attempt, its a ~10MB file
<vagrantc>
at any rate, it seems you're having troubles booting, not compiling
<tuxd3v>
aarch64-elf-
<tuxd3v>
then for Uboot
<vagrantc>
any way you could just use a text pastebin?
<tuxd3v>
export bl31=bl31.elf
<vagrantc>
is this still describing the compilation process?
<tuxd3v>
and compile in with aarch64-elf-
<tuxd3v>
for platform rk3399
<tuxd3v>
the compilation process I can extract a lot of all compilation process if you want
<vagrantc>
that's more of a meta-description of what you did with some specific details ... what exact commands did you run?
<tuxd3v>
I will build it and extract a lot
<tuxd3v>
:)
<vagrantc>
but i don't think the compilation process is where you're having issues
<tuxd3v>
lot -> log
<vagrantc>
presuming you can actually boot partially
<vagrantc>
based on what you said
<vagrantc>
if you can paste the boot log or something
<tuxd3v>
yeah I will do that, thanks for the sugestion :)
<inode>
tuxd3v: it would also be good to see what u-boot says about the mmc before attempting to boot the kernel - ie. is it actually listed in the output of mmc list (from u-boot command line) and if it is then what is reported when you request detected information about the chip
lkcl has quit [Read error: Connection reset by peer]
<tuxd3v>
inode: that would be great but I can't stop bootloader, since poweron it starting printing garbage and looping and telling 'command unknown', and such
<tuxd3v>
at line 229, I have a warning:
<tuxd3v>
tools/image-host.c:310:42: warning: format ‘%ld’ expects argument of type ‘long int’, but argument 3 has type ‘ssize_t {aka int}’ [-Wformat=]
<tuxd3v>
I am only using: idbloader.img, and u-boot.itb
<inode>
that behaviour sounds very strange ... and i wouldn't worry too much about that warning, you could change the format string introducer if it really bothers you
<tuxd3v>
in the proceedings of install the bootloader I am dd if=/zero /dev/sdb{1,2,3}
<inode>
do you have a log of the u-boot output that isn't 10MB? :)
<tuxd3v>
should I used "tr '\0' '\377' < /dev/zero >/dev/sdb{1,23}"
<tuxd3v>
you need to open it with less otherwise it would be complex to read it
<tuxd3v>
it fils 10MB super fast because some guys put seria at 1500000
<tuxd3v>
so it prints too fast :(
<inode>
i was asking because i don't want to download 10MB of logs :)
<tuxd3v>
its only a log file :)
<tuxd3v>
I redirected stdout to a log file to get serial information
<tuxd3v>
and stoped it moments later
<inode>
i live in a place where internet connectivity is poor :)
<tuxd3v>
but serial is 1500000, so it writes really fast :(
<tuxd3v>
thats why the log is 10MB
<tuxd3v>
:(
<vagrantc>
it is possible to truncate the log, if most of the messages are the same...
<inode>
if you have so much garbage appearing over UART, how is your board grounding?
<inode>
and how are you connecting your host to the board?
matthias_bgg has quit [Ping timeout: 256 seconds]
<tuxd3v>
vagrantc, you mean try to find repetitive garbage?
<tuxd3v>
and delete it?
<vagrantc>
tuxd3v: or at least just copy a few of the last lines?
<vagrantc>
like a screenfull or three
<vagrantc>
and the first few lines ...
<vagrantc>
you might want to keep the full log, but only paste the top and bottom pages to the log ... most likely the most useful parts
<vagrantc>
paste them to the pastbin, i mean
chiastre has joined #linux-rockchip
lkcl has quit [Read error: Connection reset by peer]
<Jin^eLD>
tlwoerner: seems you are now Tever and I am probably Joshua ;)))
<Jin^eLD>
wrong window, sorry :>
warpme_ has quit [Quit: Connection closed for inactivity]
<Jin^eLD>
althoiugh.. tlwoerner is here anyway, so that wasn't so wrong after all :)
<Jin^eLD>
*allthough
<tlwoerner>
Jin^eLD: lol, which is even more confusing because there is a "Kever Yang" at rock-chips
<Jin^eLD>
tlwoerner: I am not sure I got that? How does he come into this? :) I was referring to Karthiks mail
<tlwoerner>
Jin^eLD: yes, i saw the email. i was just pointing out that "Tever" could either be me, Trevor, or possibly Kever Yang at rockchips
<tlwoerner>
the mis-spelling Tever could go either way :-)
<Jin^eLD>
oooh! well he was reponding to your UART suggestion so I think Tever is you ;)
<Jin^eLD>
but yeah, quite some options here
<tlwoerner>
well, if "Joshua" is really you, then...
<Jin^eLD>
hehe, that'd be quite a conversion :>
<Jin^eLD>
tlwoerner: btw did you check the date issue yet?
<Jin^eLD>
on your board I mean
<Jin^eLD>
I worked around the problem by building the armbian kernel and all their patches, but I was not really able to figure out which one made the difference
afaerber has joined #linux-rockchip
lopsided98 has quit [Remote host closed the connection]