jakllsch has quit [Remote host closed the connection]
<apritzel>
loki666: I wouldn't wait that long, maybe mid next week. Hopefully macromorgan and acmeplus still reply and can confirm the patch
Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #linux-sunxi
ftg has quit [Read error: Connection reset by peer]
vagrantc has quit [Quit: leaving]
Daanct12 has quit [Ping timeout: 480 seconds]
Daanct12 has joined #linux-sunxi
Daanct12 has quit [Ping timeout: 480 seconds]
junari has quit [Ping timeout: 480 seconds]
hexdump01 has joined #linux-sunxi
hexdump0815 has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has joined #linux-sunxi
junari has joined #linux-sunxi
Daanct12 has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
<loki666>
Ok
LordKalma has quit [Quit: Server has probably crashed]
LordKalma has joined #linux-sunxi
<loki666>
Is it possible to boot mainline kernel+dtb from BSP u-boot ?
gsz has joined #linux-sunxi
ity has quit [Quit: WeeChat 4.4.3]
Daanct12 has quit [Quit: WeeChat 4.4.3]
apritzel has joined #linux-sunxi
<apritzel>
loki666: on H616/H700? Tricky, I'd say, and in general we don't support or recommend that.
<apritzel>
Back in the (A64) days U-Boot was still 32-bit, and only supported Android boot images, for instance, so booting mainline required quite some tricks
<apritzel>
loki666: is that U-Boot in question a 64-bit build, and does it have the "booti" command? Then you might be able to pull that off
<loki666>
Not sure about the BSP u-boot script, neither if it's a 64bit.
<loki666>
I'm asking because the dram detection issue can very annoying
<loki666>
I can also try to extract the blobs (env.txt, boot.scr and whatnot for a BSP image)
<loki666>
It does boot a 64 bit kernel
dsimic is now known as Guest1626
dsimic has joined #linux-sunxi
Schimsalabim has quit [Ping timeout: 480 seconds]
Guest1626 has quit [Ping timeout: 480 seconds]
<apritzel>
yeah, but U-Boot is running in 32-bit ("NOTICE: BL3-1: Next image spsr = 0x1d3" gives that away), and this "Android's image name: sun50i_arm64" means it's using an Android boot image
Schimsalabim has joined #linux-sunxi
apritzel has quit [Remote host closed the connection]
apritzel has joined #linux-sunxi
<apritzel>
loki666: are you using the latest mainline U-Boot? We tried to fix something there, though I hear it's not perfect still?
<apritzel>
in general MasterR3C0RD is looking into merging/porting some of the A133 DRAM code into the H616 DRAM driver, this might improve the stability
<apritzel>
loki666: is this for your personal use of your devices? Then you might want to hack it meanwhile, to reboot, for instance, if 2GB are detected?
<apritzel>
Because I don't think using BSP U-Boot is a good solution (to say it politely). You would also need BSP TF-A, which I think is even worse.
<loki666>
apritzel: well it's to use in a CFW (ROCKNIX), rebooting the device usually works, but sometime you have do reboot 3,4,5 times before it works
<loki666>
currently I'm using v2025.01-rc1
<apritzel>
ah yeah, bummer, this should contain those changes we merged - though nothing from MasterR3C0RD's work yet
<apritzel>
if you clearly mark it as a hack, you could still check for the known good DRAM size in those builds or some tree you publish
<loki666>
I tried the MAX_DRAM option of u-boot but i didn't make any difference, 2GB is only the symptom of a badly initalised dram
<loki666>
I could try a loop of init dram until it detect 1GB, but no idea where to hack this
<apritzel>
yeah, this was my hack-idea as well, to get you going for now
<apritzel>
you could try to loop around the function calls, starting with mctl_auto_detect_rank_width, in sunxi_dram_init(), and compare the size after it's calculated
<apritzel>
don't know if that helps, but trying this might give us also some data points to pinpoint the actual issues
<loki666>
I'll give it a shot
Javad_ has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
kasesag has joined #linux-sunxi
javad2 has joined #linux-sunxi
davidpete9 has joined #linux-sunxi
Javad_ has quit []
davidpete9 has quit []
javad2 has quit [Ping timeout: 480 seconds]
<kasesag>
Is the Allwinner H713 supported? I looked at the wiki but there was no information on that.
hazardchem has quit [Read error: Connection reset by peer]
hazardchem has joined #linux-sunxi
apritzel has joined #linux-sunxi
<apritzel>
kasesag: the one in those projector devices? No, and I wouldn't know of anyone working on it
Schimsalabim has quit [Read error: Connection reset by peer]
smaeul_ has quit [Read error: Connection reset by peer]
Schimsalabim has joined #linux-sunxi
smaeul has joined #linux-sunxi
<apritzel>
and as there does not seem to be any manual, it's quite hard to get this supported. There are some code hits for sun50iw12 on github, though, so the info *could* be pieced together
<loki666>
apritzel: which sunxi_dram_init()? arch/arm/mach-sunxi/dram_sun50i_h616.c ?
<loki666>
there are already logs inside the functions, so I guess I should start with enabling DEBUG and writdown the values reports for success and failure detections
digetx is now known as Guest1644
digetx has joined #linux-sunxi
Guest1644 has quit [Ping timeout: 480 seconds]
<apritzel>
loki666: yes, in this file
<apritzel>
please note that we already looked at that problem, so I don't suspect many low hanging fruits there
<loki666>
ok I guess I need to enable CONFIG_SPL_LOG and CONFIG_SPL_LOG_MAX_LEVEL=9 ?
<loki666>
dram init is in spl right
<apritzel>
you would need to "#define DEBUG" at the very beginning of this file (before any #include's)
<loki666>
ah ok
<apritzel>
I doubt that this will find anything useful, but by all means give it a go
<loki666>
I'm not trying to fix anything, i just want it to loop until it detect 1GB
<apritzel>
but then you wouldn't need debug, just add a "do {" after the clrbits_le32() call, and "} while (size != 1024 * 1024 * 1024);" after the mctl_calc_size() call
<loki666>
ok thanks
Nemo_bis has quit [Remote host closed the connection]
apritzel has quit [Ping timeout: 480 seconds]
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
ftg has joined #linux-sunxi
apritzel has joined #linux-sunxi
warpme has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has quit [Quit: KVIrc KVIrc Quasar 5.2.6, revision: 5.2.6+git-7606-51f3abb83, build type: debug, sources date: 20160102, built on: 2024-11-13 20:14:24 UTC 5.2.6+git-7606-]
Nemo_bis has joined #linux-sunxi
<loki666>
damn! is possible that enabling DEBUG "fixed" the dram detection? I just reboot my device like 50 times, and not once did it failed
warpme has quit []
warpme has joined #linux-sunxi
<gamiee>
loki666 this sounds like some additional debug prints helped with dram detection, so maybe some parts of detection code is time sensitive?
<loki666>
I'll test more, I have a device where the fail rate is higher
<loki666>
But I need to open it to access uart
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
vagrantc has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
vagrantc has quit [Quit: leaving]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
Eyad_Ahmed has joined #linux-sunxi
warpme has joined #linux-sunxi
tokyovigilante has quit [Ping timeout: 480 seconds]