eballetbo has quit [Quit: Connection closed for inactivity]
ldevulder has quit [Remote host closed the connection]
ldevulder has joined #linux-rockchip
ldevulder has quit [Quit: Leaving]
<robmur01>
most likely the signal quality/power/etc. is marginal for SDR104 speeds, so a long series of transfers just increases the likelihood of seeing an error
<robmur01>
you could try checking/fiddling pinctrl properties - certainly I remember for HS200 eMMC most boards tended to need the driver strength cranking up from default
warpme has joined #linux-rockchip
<robmur01>
or perhaps just try dialling down the "sd-uhs-sdr104" cap in DT to "sd-uhs-sdr50" or lesser
<robmur01>
(especially given that our "SDR104" on Rockchip is still only really "SDR74" anyway...)
System_Error has quit [Ping timeout: 264 seconds]
System_Error has joined #linux-rockchip
vagrantc has joined #linux-rockchip
raster has quit [Quit: Gettin' stinky!]
warpme has quit [Ping timeout: 252 seconds]
Jookia has joined #linux-rockchip
<Jookia>
o/ is it possible to use u-boot with no/minimal blobs to boot an rk3328?
warpme has joined #linux-rockchip
<CounterPillow>
Jookia: yes
<CounterPillow>
both dram training and tf-a are open and mainline
<Jookia>
I have an RK3328 board that has decided it no longer wants to boot past ATF so I'm going to be doing a bit of bootloader debugging :(
<CounterPillow>
check whether the ATF you use is one with broken FDT size limits, there was a version like that once where the FDT u-boot spl passed to ATF iirc couldn't be >64k
<Jookia>
this happened between boots, so it's possibly a board issue
<Jookia>
so this is mostly for troubleshooting what's wrong
franoosh has quit [Remote host closed the connection]
<Jookia>
I did search online to try and find anyone else with similar symptoms (the board stops after INFO: SPSR = 0x3c9 in the boot log)
<Jookia>
Is miniloader and TF-A is loaded in to RAM, not SRAM?
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]