00:12
stikonas_ has quit [Remote host closed the connection]
00:42
vicencb has quit [Quit: Leaving.]
01:00
return0e has quit [Read error: Connection reset by peer]
01:00
return0e has joined #linux-rockchip
01:31
_whitelogger has joined #linux-rockchip
01:43
tuxd3v has quit [Quit: Leaving]
02:00
s_frit_ has joined #linux-rockchip
02:01
s_frit has quit [Ping timeout: 265 seconds]
03:47
vstehle has quit [Ping timeout: 265 seconds]
04:26
return0e has quit [Ping timeout: 265 seconds]
04:27
return0e has joined #linux-rockchip
05:27
s_frit has joined #linux-rockchip
05:31
s_frit_ has quit [Ping timeout: 265 seconds]
06:00
vstehle has joined #linux-rockchip
07:16
ldevulder_ has joined #linux-rockchip
07:20
ldevulder__ has quit [Ping timeout: 265 seconds]
07:54
ldevulder_ is now known as ldevulder
08:40
stikonas has joined #linux-rockchip
09:05
stikonas has quit [Remote host closed the connection]
09:48
matthias_bgg has joined #linux-rockchip
10:24
Kelsar has joined #linux-rockchip
12:03
mrueg has joined #linux-rockchip
12:16
matthias_bgg has quit [Ping timeout: 245 seconds]
12:31
alpernebbi has joined #linux-rockchip
12:42
robmur01 has joined #linux-rockchip
13:04
nsaenz has quit [Remote host closed the connection]
13:08
nsaenz has joined #linux-rockchip
13:50
matthias_bgg has joined #linux-rockchip
14:10
tuxd3v has joined #linux-rockchip
14:21
<
aalm >
if you read on from there, it will eventually get down to boot.scr too.
14:23
<
tuxd3v >
yeah, but I don't know what are the values for rk3399:
14:23
<
tuxd3v >
fdt_addr_r
14:23
<
tuxd3v >
kernel_addr_r
14:26
<
tuxd3v >
in atf v2.2 and uboot 2020.01 I think the parameters are.
14:27
<
tuxd3v >
kernel_add
14:27
<
tuxd3v >
but again I don't knoew the best values for rk3399 :(
14:32
JohnDoe_71Rus has joined #linux-rockchip
14:33
<
tuxd3v >
aalm, that wuld beam that I have toi twewak the uboot .config file right?
14:33
<
tuxd3v >
wuld beam -> would mean
14:38
<
tuxd3v >
hwe his always trying to boot from :
14:38
<
tuxd3v >
Trying to boot from MMC1
14:38
<
tuxd3v >
but sdcard, I think is mmc0
14:44
<
robmur01 >
tuxd3v: see include/configs/rk3399_common.h for the default environment vars. As far as I'm aware there shouldn't be any need to change them though; certainly distro boot with the standard GPT partition layout "just worked" on my board
14:50
<
tuxd3v >
this is my boot.cmd:
14:58
<
tuxd3v >
maybe doesn exist a MMCo
14:58
<
tuxd3v >
and its called MMC1
15:07
<
tuxd3v >
I am flashinf the 'idbloader.img' to bs=512 seek=64 conv=notrunc
15:08
<
tuxd3v >
and 'u-boot.itb' to bs=512 seek=16384 conv=notrunc
15:08
<
tuxd3v >
then I have a msdos partition table
15:08
<
tuxd3v >
with 2 partitions
15:08
<
tuxd3v >
1 starting at 32768 sector
15:09
<
tuxd3v >
and the other following
15:09
<
tuxd3v >
and I have kernel and such in partition 1
15:16
<
tuxd3v >
does I need to tell the address were my script address will be loaded?
15:16
<
tuxd3v >
scriptaddr=0x00500000
15:33
<
tuxd3v >
my dot config contain: CONFIG_SYS_BOARD="evb_rk3399"
15:33
<
tuxd3v >
is this correct?
15:39
matthias_bgg has quit [Ping timeout: 252 seconds]
15:47
<
tuxd3v >
but distrobut uses 5 partitions
15:47
<
tuxd3v >
distroboot
15:47
<
tuxd3v >
and I don't know were to find the corresponding binaries
15:49
<
tuxd3v >
I have 'CONFIG_DISTRO_DEFAULTS=y' set
15:50
<
tuxd3v >
but I would like to use 2 partitions
15:51
<
tuxd3v >
'idbloader.img' + 'u-boot.itb , then partition for /boot then partition for rootfs
15:59
<
fALSO >
tuxd3v, this weekend I tried the hantro patches on my rockpro64
15:59
<
fALSO >
with the experimental ffmpeg
15:59
<
fALSO >
it worked perfectly
16:00
<
fALSO >
now I wanted to build vlc with libva support
16:00
<
fALSO >
but it seems to require some functions that the "stable" libva doesnt have
16:00
<
fALSO >
it seems to need some "hacked" one, that i havent figure out yet
16:01
<
tuxd3v >
I am far behind, I am still stuck at bootloader on rk3399
16:01
<
fALSO >
im still using the same one that worked
16:01
<
tuxd3v >
can't get it to work..
16:01
<
fALSO >
every ttime i try to flash a new version, it never boots
16:01
<
tuxd3v >
its been a pita with that..
16:01
<
fALSO >
the uboot documentation isnt updated
16:02
<
fALSO >
they seem to commit code, but not update the documentation
16:02
<
fALSO >
no mention of rockpro64 on uboot
16:02
<
fALSO >
yhere some rk3399 stuff there, but seems old
16:02
<
tuxd3v >
but also the rockchip scheme is very strange compared with lets say sunxi
16:03
<
tuxd3v >
with sunxi you just flash a binary and that's it..
16:03
<
tuxd3v >
with rockchip I don't even know the amount of ninaries needed
16:03
<
fALSO >
from what is seems
16:04
<
tuxd3v >
'idbloader.img' + 'u-boot.itb
16:05
<
tuxd3v >
but I still facing problems booting, i couldn't verify were the source of them is.. :S
16:05
<
tuxd3v >
I still continue using my boot.scr
16:06
<
tuxd3v >
I don't know if rockchip uboot plays nice with it..
16:06
<
tuxd3v >
a lot of people simply uses extlinux config menu
16:06
<
tuxd3v >
and then uses syslonux to load the file..
16:07
<
tuxd3v >
syslonux -> syslinux
16:07
<
tuxd3v >
I feel that its ok, but I wanted to use boot.scr
16:08
<
fALSO >
yap, its very green the documentation
16:08
<
fALSO >
If i knew the correct way to do it
16:08
<
fALSO >
I would submit an update to the documenation
16:08
<
tuxd3v >
yeah me to :)
16:08
<
fALSO >
but only people who develop it probably knows
16:09
<
tuxd3v >
yeah that is a problem, but people that is doing integration..
16:09
<
tuxd3v >
or simply for end users
16:10
<
tuxd3v >
I see a lot of distro images still shiping android one
16:10
<
tuxd3v >
I own a rockpro64
16:10
<
tuxd3v >
and a rockpi4
16:10
<
tuxd3v >
I am attempting first in rockpi4
16:10
<
tuxd3v >
without any success in the last 4 months or so..
16:11
<
tuxd3v >
does you use boot.scr in your boot?
16:13
<
tuxd3v >
I am with ATFv2.2 and uboot v2020.01
16:13
<
tuxd3v >
at least attempting with them..
16:14
<
tuxd3v >
ethernet blinks a bit, bootloader says is trying to boot from mmc 1
16:14
<
tuxd3v >
and that's it..
16:35
<
fALSO >
tuxd3v, i dont think so
16:35
<
fALSO >
let me confirm
16:35
<
fALSO >
you want my boot.cmd ?
16:35
<
tuxd3v >
I would apreciate it, thanks, to compare
16:50
<
tuxd3v >
fALSO, thanks
16:51
<
tuxd3v >
I will post my revision based on your :)
16:55
<
tuxd3v >
I am loading dtb from rootfs
16:56
<
tuxd3v >
kernel is in boot partition :)
16:56
<
tuxd3v >
your boot.cmd is very clean :)
16:56
ldevulder_ has joined #linux-rockchip
16:56
<
fALSO >
it was made with help from someone here i think
16:56
<
fALSO >
especialy the uart part
16:56
<
fALSO >
because before It didnt print the kernel startup via serial
16:57
<
tuxd3v >
I saw that part and I was thinking what would it do..
16:57
<
fALSO >
it works, didnt touch it again :-)
16:58
<
tuxd3v >
yeah nice!
16:58
<
tuxd3v >
because I never saw the kernel bootmsg
16:59
<
fALSO >
with that bootcmd it works
16:59
<
fALSO >
at least for me
16:59
ldevulder has quit [Ping timeout: 265 seconds]
17:08
<
tuxd3v >
Channel 0: LPDDR4, 50MHz
17:08
<
tuxd3v >
Channel 1: LPDDR4, 50MHz
17:08
<
tuxd3v >
shouldn't the memory be @400Mhz ?
17:33
<
tuxd3v >
fALSO, you are setting the macaddress, it works?
17:33
<
tuxd3v >
I waslooking into_
17:34
<
tuxd3v >
'arch/arm64/boot/dts/rockchip/rk3399.dtsi'
17:34
<
fALSO >
the macaddrs problem was uboot related
17:34
<
tuxd3v >
gmac: ethernet@fe300000
17:35
<
tuxd3v >
but you have : fdt set /ethernet@ff540000
17:35
<
tuxd3v >
anyway if it works its because its ok
17:36
<
tuxd3v >
maybe its derefined in rockpro64 ;)
17:36
<
fALSO >
tuxd3v, well, i dont really know if thats doing anything
17:36
<
fALSO >
i added that once, because every time i booted it had a differnt mac address
17:36
<
fALSO >
some time ago that worked... dont know if its still doing anything ;-)
17:37
<
tuxd3v >
maybe itcould be ok
17:37
<
tuxd3v >
Iam with Mainline kernel 5.5.0
17:38
<
tuxd3v >
and maybe there are diferences..
17:38
<
fALSO >
im with mailine kernel
17:38
<
fALSO >
and a big pach
17:38
<
fALSO >
to enable hantro etc
17:38
<
tuxd3v >
I am clean in mainline
17:38
<
tuxd3v >
without patchs
17:39
<
tuxd3v >
well for some boards I have
17:39
<
tuxd3v >
maybe, maybe this is my problem hehehe
18:07
archetech has joined #linux-rockchip
18:16
<
tuxd3v >
dumping of driver model:
18:35
<
tuxd3v >
it is in loop reseting the cpu and making relocations I don't know why
18:37
vicencb has joined #linux-rockchip
18:50
stikonas has joined #linux-rockchip
19:27
chewitt has quit [Ping timeout: 265 seconds]
19:58
Depau has joined #linux-rockchip
20:02
paccer has quit [*.net *.split]
20:14
adjtm_ has joined #linux-rockchip
20:16
adjtm has quit [Ping timeout: 240 seconds]
21:03
jwerner has quit [Quit: leaving]
21:04
alpernebbi has quit [Quit: alpernebbi]
21:14
vagrantc has joined #linux-rockchip
21:17
jwerner has joined #linux-rockchip
21:19
archetech has quit [Quit: Konversation terminated!]
21:36
adamvy has joined #linux-rockchip
23:58
eballetbo has quit [Ping timeout: 258 seconds]
23:58
eballetbo has joined #linux-rockchip