ftg^ has quit [Read error: Connection reset by peer]
wasutton3 has joined #linux-sunxi
wasutton| has quit [Ping timeout: 480 seconds]
wasutton- has joined #linux-sunxi
wasutton3 has quit [Ping timeout: 480 seconds]
apritzel has quit [Ping timeout: 480 seconds]
montjoie_ has joined #linux-sunxi
montjoie has quit [Ping timeout: 480 seconds]
Asara has quit [Remote host closed the connection]
Asara has joined #linux-sunxi
f_ has quit [Read error: Connection reset by peer]
f_ has joined #linux-sunxi
Danct12 is now known as brrrrrrrrrrrrrrrrrrrrrrrrrrrrr
brrrrrrrrrrrrrrrrrrrrrrrrrrrrr has quit []
Danct12 has joined #linux-sunxi
tokyovigilante has joined #linux-sunxi
tokyovigilante has quit [Remote host closed the connection]
<KREYREN_oftc>
machinehum, in berlin specifically and OLIMEX didn't reply to me yet in which hackerspace it was sent to so decided to ask bcs i am impatient
hexdump01 has joined #linux-sunxi
hexdump0815 has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has joined #linux-sunxi
dsimic has quit [Ping timeout: 480 seconds]
dsimic has joined #linux-sunxi
macromorgan has quit [Ping timeout: 480 seconds]
mkazantsev has joined #linux-sunxi
mkazantsev is now known as Guest2595
mkazantsev has joined #linux-sunxi
Guest2595 has quit [Ping timeout: 480 seconds]
mkazantsev is now known as Guest2598
mkazantsev has joined #linux-sunxi
Guest2598 has quit [Ping timeout: 480 seconds]
mkazantsev is now known as Guest2599
mkazantsev has joined #linux-sunxi
mkazantsev has quit [Remote host closed the connection]
Guest2599 has quit [Ping timeout: 480 seconds]
<machinehum>
KREYREN_oftc: ahh, I see.
warpme has joined #linux-sunxi
dsimic is now known as Guest2605
dsimic has joined #linux-sunxi
Guest2605 has quit [Ping timeout: 480 seconds]
ndufresne has quit [Quit: Ping timeout (120 seconds)]
ndufresne has joined #linux-sunxi
apritzel has joined #linux-sunxi
chewitt has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
<machinehum>
I see the wiki has been updated with news of the T113-s4
<machinehum>
So called "ARTINCHIP AIC600E3"
<machinehum>
apritzel: Which was the board you showed me with the T113-s3 on it?
<apritzel>
those boards are pretty short-lived though, it's already no longer supported
<apritzel>
having a 256MB version would be nice, but if you really want to make a cool thing, make a A527 board with an M.2 slot
<gamiee>
apritzel: I mean, that Dongshang Pi is manufacturing some of Mango Pi boards, so it was possible to buy them from Dongshang Pi Aliexpress Store
<machinehum>
A527 would be quite a time investment
<machinehum>
ddr4 or 3?
<machinehum>
I like this T113-s4 because it's very simple
<machinehum>
Ah, ddr3 or ddr4
<gamiee>
is it possible to buy A527 at all?
dsimic is now known as Guest2618
dsimic has joined #linux-sunxi
Guest2618 has quit [Ping timeout: 480 seconds]
<machinehum>
I looked around and couldn't fine anything
warpme has quit []
<apritzel>
there are definitely boards out there already with the T527, which is the bigger brother of the A527
<macromorgan>
or TRP... is that a typo or are those different values?
<macromorgan>
this is an H700 with LPDDR4 it appears (let me double check to make sure though)
<apritzel>
macromorgan: ah, interesting, the tools omits values which are 0, so "0" is your answer
<macromorgan>
okay
<macromorgan>
I will try it with all those values and see if I can get past ram training
<apritzel>
well, 0 doesn't look right. It wouldn't matter if bit 17 of TPR10 was clear, but it's set. The boot0 log shows 0x05050606 for TPR12, so try that as well
<macromorgan>
also looks like that tool has a typo... TPR/TRP
<apritzel>
well, you know what to do, right? ;-)
<apritzel>
(meaning: I take patches)
<macromorgan>
I do... for now I'll see if I can rig mainline U-Boot on an H700
<apritzel>
maybe TPR12 being 0 has a special meaning, it looks like boot0 tries two values
<apritzel>
jernej_, junari: something for you, maybe? ^^^^
<macromorgan>
yeah, straight copy of the values from the boot0 file (including 0 where there is 0) results in no boot
<macromorgan>
RAM looks like a Samsung K4FBE3D 8Gb LPDDR4
<apritzel>
some boot0 files seem to ignore some or all parameters, depending on some other bits, I think, and either detect or try them
<macromorgan>
we don't by chance have a TRM/register docs for this chip do we? I'm hoping to mainline as much of it as I can, but that might take a while.
<macromorgan>
I assume it's very similar to an H616 (which is why I'm using that as a base)
warpme has quit []
<apritzel>
bummer, just wanted to ask *you* if you found a manual meanwhile ;-)
<apritzel>
my hunch it's the same die as the H616, potentially with different peripherals routed to pins, or maybe just slightly different spec, on video codecs, maybe?
<macromorgan>
I think it's main differentiator is the LCD controller
<macromorgan>
which I assume is just IP borrowed from other Allwinner boards
<gamiee>
from my info, H700 is almost same as H616, just that RGB controller.
<apritzel>
yes, that's what jumped at me as well, from looking at that "brief" document
<apritzel>
which would put it close to the T507, which might be the same, just aiming at a different market?
<apritzel>
macromorgan: so check if the T507 manual is any better. We have the pins already added to our pinctrl driver in mainline
<macromorgan>
okay... I don't have a mainline kernel yet and as you can see my mainline U-Boot is getting nowhere... but I'll look at the T507 manual.
<apritzel>
macromorgan: but you do have serial, right?
<macromorgan>
yes, where I got the dumps from
<apritzel>
(of course!)
<apritzel>
macromorgan: so I guess once you have DRAM, mainline should just work, minus the display, of course
<apritzel>
macromorgan: if you are stuck on this, let me know, there are tricks to let a boot0 do the DRAM init, and then load mainline U-Boot & kernel
<macromorgan>
the next worry after I solve this problem is what to do about the AXP2202 PMIC that has zero mainline support... in U-Boot or Linux
jernej_ is now known as jernej
<jernej>
hm... maybe best approach would be to parse live register values and work back configuration values?
<jernej>
sometimes BSP DRAM code overrides some configuration values
junari has joined #linux-sunxi
<apritzel>
another trick is to put just boot0 on an otherwise mostly empty SD card, so that boot0 doesn't find any payload. At least some boot0's then drop into FEL, after DRAM init, so you can upload U-Boot proper & Linux
<junari>
macromorgan: hmm arnbernic, interesting. T507 and H616 have different dram controller initialization arrays. Mainline for H616