<apritzel>
MasterR3C0RD: that actually seems to work! Without an M.2 card in, PH19 (configured as GPIO-IN) reports High, with my NVMe in the pin reads Low
<apritzel>
directly from FEL, not further power rails or GPIOs involved
Schimsalabim has quit [Read error: Connection reset by peer]
Schimsalabim has joined #linux-sunxi
<MasterR3C0RD>
apritzel: Is that with PERST# at logic low?
<MasterR3C0RD>
Or were you just reading PH19 without setting up any muxing?
jernej has quit [Quit: Konversation terminated!]
<MasterR3C0RD>
Well I guess at reset it would already be at logic low so that's a silly question
<apritzel>
MasterR3C0RD: just from FEL, so most pins still in their HighZ reset config. I just configured PH19 as GPIO-IN, then read the level
<MasterR3C0RD>
Interesting; I wouldn't think PH19 would be held high by anything, I wonder if there's a pull-up I missed in the schematic, or if there's an internal pull-up set for it
Schimsalabim has quit [Read error: Connection reset by peer]
BroderTuck has quit [Quit: Stayed up far too late]
<apritzel>
yeah, I was wondering as well. The GPIO controller can enable pull-ups or pull-downs, but it's not programmed. Maybe it's some random floating level read as high?
<apritzel>
I think we can detect a floating state explicitly, by enabling the pull-up bit, then checking for high, then switching to the pull-down bit, and checking for low
Schimsalabim has joined #linux-sunxi
<apritzel>
so I have a proper DT for the Radxa now, with all the voltages rails, USB (2.0) and SD card. However the SPL is behaving strangely: often the board turns off, or reading from SD card fails. Will debug tomorrow ...
apritzel has quit [Ping timeout: 480 seconds]
ftg has quit [Read error: Connection reset by peer]
JohnDoe_71Rus has joined #linux-sunxi
hexdump01 has quit [Ping timeout: 480 seconds]
jernej has joined #linux-sunxi
jernej_ has joined #linux-sunxi
jernej_ has quit []
Schimsalabim has quit [Read error: Connection reset by peer]
Schimsalabim has joined #linux-sunxi
Ixnus has quit [Remote host closed the connection]
Schimsalabim has quit [Read error: Connection reset by peer]
tiop has joined #linux-sunxi
Schimsalabim has joined #linux-sunxi
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
apritzel has joined #linux-sunxi
JohnDoe_71Rus has quit [Quit: KVIrc KVIrc Quasar 5.2.6, revision: 5.2.6+git-7609-afed1336e, build type: debug, sources date: 20160102, built on: 2024-12-18 20:43:05 UTC 5.2.6+git-7609-]
colinsane has joined #linux-sunxi
colinsane has quit [Ping timeout: 480 seconds]
dsimic is now known as Guest6352
dsimic has joined #linux-sunxi
colinsane has joined #linux-sunxi
Guest6352 has quit [Ping timeout: 480 seconds]
colinsane has quit [Ping timeout: 480 seconds]
colinsane has joined #linux-sunxi
<jernej>
apritzel: is it possible that your board is unstable due to DRAM?
colinsane has quit [Ping timeout: 480 seconds]
apritzel has quit [Ping timeout: 480 seconds]
apritzel has joined #linux-sunxi
<apritzel>
jernej: blaming DRAM is always a welcome straw I like to grasp to ;-) , but I don't think that's it, really. It would explain the SD card issues, but not the FEL failures
<apritzel>
which btw shows the same issue as the Avaota: return-to-FEL from 64-bit doesn't work. So I added another hack to let the 32-bit FEL build work with 4GB, but it oddly enough turns off
<apritzel>
I checked all the regulators, but they seem fine, actually even the PMIC reset would already work (DCDC3 is at 1.1V already)
<jernej>
apritzel: ok, that's good enough reason to make JTAG adapter :)
<apritzel>
interestingly that TV box is unimpressed by all those issues, and works nicely
<apritzel>
jernej: also: I tried some DRAM parameters I dumped from the image, and also those found in this BSP overlay tgz, but they make things worse
<apritzel>
so the values I use for the Avaota seem to work best
gsz has joined #linux-sunxi
<jernej>
do you have tpr13 value from your dump?
<jernej>
if bit 11 is set, DRAM driver does its own calibration and important timings from tpr11, tpr12 and tpr14 are overriden
kepstin has quit [Remote host closed the connection]
kepstin has joined #linux-sunxi
tiop has quit []
<apritzel>
the image says it's 0xc60, so that would be the case
<apritzel>
but I also tried the values as dumped by boot0, not sure if those are dumped before or after the init, though
<jernej>
oh, sorry, I didn't express myself properly. Calibrated values are then per single line, not per bundle of 8 as in tpr values case. That's why they are stored right after DRAM parameters (I think).
<apritzel>
would it be worth to hack boot0 to go to FEL afterwards and dump the DRAM registers? Or does that not help, since those TPR values are not fine grained enough anyway?
<jernej>
well, I think taking some average of those would help
<jernej>
btw, I think there is easier solution. create fresh boot0 sd card and run it. It should do calibration again and calibration process should print out some values.
<jernej>
If I'm not mistaken, it should print new tpr11, 12 and 14 values.
<jernej>
on uart
apritzel has quit [Ping timeout: 480 seconds]
junari_ has joined #linux-sunxi
<Jookia>
jernej: btw thanks for the clocking notes i implemented variable clocking in my kernel and its been working for a year or so now :D
<Jookia>
i think it was your notes that helped
<jernej>
Jookia: not sure what exactly you're referring?
<Jookia>
i can't find it, nevermind
<Jookia>
someone posted notes on how to do variable frequency clocking on allwinner boards
<BroderTuck>
or is that expected, like if (with nand) the android stuff and the allwinner stuff is incompatible?
<BroderTuck>
I mean android/allwinner and mainline, ofc
apritzel has quit [Remote host closed the connection]
apritzel has joined #linux-sunxi
<apritzel>
BroderTuck: well, that doesn't look that much different, does it? So I am afraid the cache was a red herring, and there is something else missing?
<BroderTuck>
Now it at least manages to identify the chip.
<BroderTuck>
But the cache issue seems to be symptom, not cause.
<BroderTuck>
Maybe a red herring as well, but the android bootlog says "mmc 2 bias 17fb", not sure what that means
<jernej>
apritzel: can you dump boot0 afterwards and give me bin file?
dliviu has quit [Ping timeout: 480 seconds]
apritzel has quit [Ping timeout: 480 seconds]
tiop has quit []
junari_ has quit [Ping timeout: 480 seconds]
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
ftg has joined #linux-sunxi
<jernej>
anyone here with 1.5 or 3 GB RAM board?
<jernej>
3 GB obviously on H616
apritzel has joined #linux-sunxi
dliviu has joined #linux-sunxi
cp- has quit [Ping timeout: 480 seconds]
psydroid has quit []
psydroid has joined #linux-sunxi
ftg has quit [Ping timeout: 480 seconds]
hallyn has joined #linux-sunxi
cp- has joined #linux-sunxi
hexdump0815 has joined #linux-sunxi
Schimsalabim has quit [Read error: Connection reset by peer]
apritzel has quit [Quit: Leaving]
Schimsalabim has joined #linux-sunxi
apritzel has joined #linux-sunxi
<apritzel>
jernej: I think junari knew someone? ^^^^ And I dimly remember someone sending a hackish patch once, but can't find it quickly