elektrinis has joined #linux-rockchip
elektirnis has quit [Ping timeout: 265 seconds]
stikonas has quit [Remote host closed the connection]
Depau_ has quit [Ping timeout: 260 seconds]
vstehle has quit [Ping timeout: 268 seconds]
Depau has joined #linux-rockchip
Depau has quit [Ping timeout: 265 seconds]
vagrantc has quit [Quit: leaving]
tlwoerner has quit [Quit: Leaving]
archetech has quit [Quit: Konversation terminated!]
marcodiego has quit [Read error: Connection reset by peer]
vstehle has joined #linux-rockchip
kevery has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
kevery has quit [Remote host closed the connection]
kevery has joined #linux-rockchip
kevery has quit [Ping timeout: 265 seconds]
stikonas has joined #linux-rockchip
<
paulk-leonov>
is it possible at all to run mainline u-boot on rk3288 without tpl these days?
<
paulk-leonov>
I'm using the miqi config, which does not enable TPL, but fatally produces a SPL larger than SRAM size
chewitt has quit [Quit: Adios!]
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
alpernebbi has joined #linux-rockchip
stikonas_ has joined #linux-rockchip
stikonas has quit [Ping timeout: 272 seconds]
stikonas has joined #linux-rockchip
stikonas_ has quit [Read error: Connection reset by peer]
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
JohnDoe_71Rus has joined #linux-rockchip
<
paulk-leonov>
ah ok, disabling CONFIG_SPL_ROCKCHIP_BACK_TO_BROM drags MMC support which makes the image too large
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
stikonas has quit [Read error: Connection reset by peer]
stikonas has joined #linux-rockchip
MoeIcenowy has joined #linux-rockchip
JohnDoe_71Rus has quit [Ping timeout: 265 seconds]
stikonas has quit [Remote host closed the connection]
return0e_ has quit [Ping timeout: 268 seconds]
return0e has joined #linux-rockchip
chewitt has joined #linux-rockchip
return0e has quit [Remote host closed the connection]
return0e has joined #linux-rockchip
stikonas has joined #linux-rockchip
vicencb has joined #linux-rockchip
ldevulder__ has joined #linux-rockchip
ldevulder_ has quit [Ping timeout: 268 seconds]
vagrantc has joined #linux-rockchip
tuxd3v has joined #linux-rockchip
<
tuxd3v>
hello guys
<
tuxd3v>
does any one knows a good conbination of ATF+ uboot for rk3399?
<
vagrantc>
build the arm-trusted-firmware package from sid, adding the appropriate line an build-depends for rk3399 ... and build on stretch
<
vagrantc>
i should be able to post a diff somewhere
<
vagrantc>
i should just add them as comments to the package
<
vagrantc>
and then you need u-boot 2019.10 or newer
archetech has joined #linux-rockchip
<
tuxd3v>
ATF v2.2 from github would work?
<
tuxd3v>
or do you think its something that its not there or there wrongly?
<
tuxd3v>
I was thinking in crosscompiling it..
<
tuxd3v>
but I never succeded in booting a bootloader compiled by me in rk3399 :(
<
vagrantc>
oops, i had assumed i was in #debian-arm ...
<
vagrantc>
also guix has working arm-trusted-firmware for rk3399
<
tuxd3v>
no problem
<
tuxd3v>
I just wanted to know a version that works of ATF + Uboot
<
vagrantc>
yeah, atf 2.2 requires u-boot ... 2020.01 maybe
<
vagrantc>
there was a change of address between 2019.10 ... or atf 2.1 works with 2019.10
<
vagrantc>
but only on debian
<
tuxd3v>
I will try with atf v2.2 and uboot v2020.01
<
tuxd3v>
and let you know if I succeded :)
<
tuxd3v>
I believe for that I need 3 crosscompilers.. amazing..
<
tuxd3v>
1 baremetal aarch64,
<
vagrantc>
yeah, you need the baremetal arm compilers
<
tuxd3v>
one for aarch64-linux-gnu
<
vagrantc>
i think the baremetal is arm 32-bit, not aarch64
<
tuxd3v>
and one for armeabi-none-linux
* vagrantc
adds some patience :)
<
tuxd3v>
yeah this last one is for the ARM Cortex M0
<
vagrantc>
i didn't know you needed a baremetal compiler for aarch64
<
tuxd3v>
I want to use a baremetal for uboot
<
tuxd3v>
but ATF needs a baremetal for cortex m0
<
tuxd3v>
so you endup with 3 hehehe
<
tuxd3v>
I will start in a minute :)
<
vagrantc>
i've always just used aarch64-linux-gnu an armeabi-none
<
vagrantc>
i suspect upstream u-boot uses aarch64-linux-gnu as well
<
tuxd3v>
I believe you have several options
<
tuxd3v>
its compiling..
<
tuxd3v>
ho its done..
<
tuxd3v>
now I have: idbloader.img, u-boot.itb, /u-boot-tpl.bin, u-boot-spl.bin
<
tuxd3v>
the problem will start now :D
<
tuxd3v>
now for what it seems write idbloader.img to bs=512 seek=64
<
tuxd3v>
and u-boot.itb to bs=512 seek=16384
<
tuxd3v>
and the bootloader should be in place ??
<
vagrantc>
looks about right
* vagrantc
usually just uses dd defaults so doesn't pass bs=
<
vagrantc>
which appears to be 512
<
tuxd3v>
what should be the baudrate?
<
tuxd3v>
I am using 1500000
<
tuxd3v>
but I don't even know if pins are correct
<
tuxd3v>
I own a rockpi4
<
tuxd3v>
it should be 6=GND, 8=TXD, 10=RXD
<
tuxd3v>
but I see nothing in the console :(
<
vagrantc>
either 1500000 or 115200
<
tuxd3v>
cant see s*t :D
<
archetech>
what board ya working on there guys
<
tuxd3v>
seems like a dead horse
<
tuxd3v>
ats v2.2 + uboot v2020.01
<
archetech>
im on rock64
<
archetech>
not too happy atm with it
<
tuxd3v>
does you managed to build the bootloader?
<
archetech>
I use arch arm to boot linux from scratch on it
<
tuxd3v>
how does it knows were is the boot.scr
<
tuxd3v>
I mean the bootloader?
<
archetech>
its in /boot
<
tuxd3v>
I marked 1st partition with boot flag
<
tuxd3v>
no I mean the bootloader
<
archetech>
loader.img?
<
tuxd3v>
how does he knows were is the boot.scr
<
tuxd3v>
i idbloader.img to bs=512 seek=64
<
tuxd3v>
and u-boot.itb to bs=512 seek=16384
<
archetech>
they get flashed to spots on geginning of drive
<
tuxd3v>
but when they start
<
archetech>
per their install doc
<
tuxd3v>
they don't know were is the boot.scr cript
<
tuxd3v>
what partition it is on
<
archetech>
no partition its in 0-32768
<
tuxd3v>
maybe it defaults to the 1st one :)
<
archetech>
sda1 starts at 32769
<
archetech>
which holds /boot
<
tuxd3v>
do you sure sda1 starts at 32769 and not at 32768?
<
archetech>
right 768 it is
<
tuxd3v>
right... bootloader searches for the partition that starts at 32768 :)
<
tuxd3v>
it should be :)
<
tuxd3v>
can you get a serial conection printing the boot info ?
<
archetech>
no serial adapter here on armbian 5.4.x just hangs
<
archetech>
4.4 works
<
archetech>
been trying to get armbian rc1 to boot
<
tuxd3v>
sda1 should be fat16 or ext2
<
tuxd3v>
or doesn't matter
<
tuxd3v>
I am using ext2
<
archetech>
ext4 here
<
archetech>
since its /
<
tuxd3v>
I mean in /boot
<
archetech>
/boot is in my /
<
archetech>
what are trying to do ?
tlwoerner has joined #linux-rockchip
<
tuxd3v>
my Idea was to have 2 filesystems
<
tuxd3v>
sda1 for /boot
<
tuxd3v>
and sda2 for /
<
archetech>
thats not how arm does it
<
tuxd3v>
I do that for other ARM boards
<
archetech>
fine for x86
<
archetech>
well yeah it can be done depends what distro you want to boot
<
archetech>
arch dont need it debian might
<
tuxd3v>
the thing here is how bootloader knows were to pick boot.scr
<
archetech>
my armbian ubu which is deb like ofc uses 7 partitions per ayufans way of booting
<
tuxd3v>
I don't know why 7 partitions
<
archetech>
have to ask ayufan
<
archetech>
some kind of voodoo I dont understand
stikonas_ has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
stikonas has quit [Ping timeout: 272 seconds]
<
aalm>
tuxd3v, does it have the distro defaults in env ?
vagrantc has joined #linux-rockchip
midnightmagic is now known as midnight
alpernebbi has quit [Quit: alpernebbi]
vagrantc has quit [Quit: leaving]
field^Mop has joined #linux-rockchip
<
tuxd3v>
aalm, sorry don't undertood what you mean
archetech has quit [Read error: No route to host]
<
tuxd3v>
does any one has a rockpi4 here?
<
tuxd3v>
I am stuck with bootloader..
field^Mop has quit [Ping timeout: 240 seconds]