<vagrantc>
i can short the eMMC, and then it gets into maskrom mode ...
<vagrantc>
and i can write things to the eMMC with rkdevelop, but so far, nothing that changes the boot behavior
<vagrantc>
rkdeveloptool
<vagrantc>
also struggling a bit to find instructions of exactly what to put on the microSD card ...
<vagrantc>
it seems to read that the microsd exists when it's plugged in
<vagrantc>
e.g. it reads the correct size information
<stdint>
vagrantc, yes for the firefly serial
<stdint>
since there is no hardware button to enter the maskrom mode
<stdint>
the default behaviour is to read bootloader at sdcard
<vagrantc>
sure, but what do i write on that sdcard?
<vagrantc>
there are lots of instructions on various sites, all of which are vaguely similar, rkdeveloptool, rkflashtool, rkflashkit, etc. all suggesting to write different bits to different places
<stdint>
vagrantc, use the dd
<stdint>
writing to the sdcard is the most simple thing without external tools requirement
pozzoni has joined #linux-rockchip
<wzyy2>
which bl31.bin do you use?
<wzyy2>
Do you build it from opensource atf?
<vagrantc>
bl31?
<vagrantc>
i've tried all sorts of atf images
<vagrantc>
what's not clear to me is it rkdeveloptool is actually writing anything
<vagrantc>
stdint: what do i write to the sd card?
<wzyy2>
but you should make sure you have erase emmc and it have boot into maskrom mode without sd-card inserted.
<vagrantc>
it doesn't boot into maskrom mode, it just hangs
<vagrantc>
rkdeveloptool ef ??
<vagrantc>
i get the impression it's actually loading *something* from eMMC and then hanging
lkcl has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
* vagrantc
sighs
wzyy2 has quit [Disconnected by services]
wzyy2 has joined #linux-rockchip
<vagrantc>
well, got a slightly changed behavior, two "hdr" lines: hdr 0x0:d0 d fe ed 0 0 3 65 0 0 0 38 0 0 2 e4
<vagrantc>
hdr 0x0:d0 d fe ed 0 0 3 65 0 0 0 38 0 0 2 e4
<vagrantc>
right after "No find bl32.bin" and before "theLoader 200000 147951"
<vagrantc>
still have to manually short eMMC to get it to go into maskrom mode
<wzyy2>
- -I think kever's branch is fro evb-rk3399, not firefly rk3399.
<vagrantc>
it's what kever suggested using
<wzyy2>
Maybe evb-rk3399 and firefly-rk3399 are different in sdram and u-boot spl don't support autodect it.
<vagrantc>
and the top commit is "WA: enable firefly-rk3399 board"
<wzyy2>
CROSS_COMPILE=aarch64-linux-gnu- CFLAGS='-gdwarf-3' make evb-rk3399_defconfig all -j8
<vagrantc>
i have another firefly-rk3399 that works with basically u-boot v2017.05-rc2 + most of the patches from kever's branch
<wzyy2>
chang it to firefly-rk3399_defconfig?
<vagrantc>
i'm pretty sure that doesn't matter, as there's no defconfig, and it works on the other board fine
<vagrantc>
i think i hosed something in a way that appears to be hard to recover
<vagrantc>
on the board where it works, i just updated u-boot and left everything else intact
techping has joined #linux-rockchip
<vagrantc>
ah well, i'll take another stab at it another day
vagrantc has quit [Quit: leaving]
zzarr has joined #linux-rockchip
kloczek has joined #linux-rockchip
kloczek has quit [Read error: Connection reset by peer]
wadim_ has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
ganbold has quit [Ping timeout: 240 seconds]
ganbold has joined #linux-rockchip
xming_ has joined #linux-rockchip
xming_ has quit [Changing host]
xming_ has joined #linux-rockchip
robogoat_ has joined #linux-rockchip
beeble has quit [Write error: Broken pipe]
rperier has quit [Write error: Broken pipe]
wzyy2 has quit [Remote host closed the connection]
xming has quit [Quit: No Ping reply in 180 seconds.]
robogoat has quit [Remote host closed the connection]
beeble has joined #linux-rockchip
rperier has joined #linux-rockchip
rperier has quit [Changing host]
rperier has joined #linux-rockchip
Aussie_matt has joined #linux-rockchip
athidhep has joined #linux-rockchip
kloczek has joined #linux-rockchip
kloczek has quit [Read error: Connection reset by peer]
lkcl has quit [Ping timeout: 268 seconds]
kloczek has joined #linux-rockchip
kloczek has quit [Remote host closed the connection]
kloczek has joined #linux-rockchip
lkcl has joined #linux-rockchip
libv_ has joined #linux-rockchip
libv has quit [Ping timeout: 252 seconds]
kloczek has quit [Ping timeout: 240 seconds]
kloczek has joined #linux-rockchip
paulk-collins has joined #linux-rockchip
kloczek has quit [Ping timeout: 260 seconds]
nighty-- has quit [Quit: Disappears in a puff of smoke]
nighty-- has joined #linux-rockchip
libv_ is now known as libv
kloczek has joined #linux-rockchip
techping has quit [Ping timeout: 260 seconds]
athidhep has quit [Quit: athidhep]
Aussie_matt has quit [Read error: Connection reset by peer]
Aussie_matt has joined #linux-rockchip
mrjay has joined #linux-rockchip
lkcl has quit [Ping timeout: 260 seconds]
lkcl has joined #linux-rockchip
afaerber has quit [Quit: Leaving]
afaerber has joined #linux-rockchip
menomc is now known as mnemoc
Aussie_matt has quit [Remote host closed the connection]
JohnDoe_71Rus has joined #linux-rockchip
cnxsoft has quit [Quit: cnxsoft]
cyteen has quit [Ping timeout: 258 seconds]
vagrantc has joined #linux-rockchip
wadim_ has quit [Remote host closed the connection]
mrjay has quit [Quit: Page closed]
dubis has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
vagrantc has joined #linux-rockchip
<vagrantc>
ok.
<vagrantc>
well, i dd'ed the first 512MB of the working firefly-rk3399's /dev/mmcblk0 to a microSD card and booted it with the one with the borked microsd
* vagrantc
sighs
<vagrantc>
but only if i short the eMMC
<vagrantc>
and only the first time i tried it...
<vagrantc>
gah.
<vagrantc>
ok, booted again successfully
matthias_bgg has quit [Quit: Leaving]
<vagrantc>
and them a little mmc erase from u-boot and it seems to be reliably booting from microSD
* vagrantc
sighs relief
kloczek has quit [Ping timeout: 255 seconds]
cyteen has joined #linux-rockchip
kloczek has joined #linux-rockchip
<paulk-collins>
vagrantc, are there still mmc issues with rk3288 at this point?
<paulk-collins>
I recall veyrons didn't do so well there
kloczek has quit [Ping timeout: 245 seconds]
<ayaka>
paulk-collins, I thought it has been solved
<paulk-collins>
ayaka, okay, I'll test again then
<ayaka>
anyway, if you still me a problem, send a mail to me
<paulk-collins>
thank-you
<vagrantc>
paulk-collins: i last tested with 4.10.x, and it was still not working well for me.
lkcl has quit [Ping timeout: 258 seconds]
<vagrantc>
if it's been updated since then, i'll be glad to test it again!
<vagrantc>
seemed to have the situation where what fixed it for me broke it for someone else, so i'm a little skeptical that it's "solved" until i see it myself
<ayaka>
I have nearly forget what is the emmc problem with rk3288
<ayaka>
in my memory, it is that, firefly reload can't stop report its change frequency of sdmmc
<ayaka>
but my firefly doesn't have this problem, so I think it is a hardware issue
lkcl has joined #linux-rockchip
<vagrantc>
i had an issue where on veyron-speedy, the eMMC was only detected maybe 1 out of 20 times
<vagrantc>
when compiled as a module
<vagrantc>
i should try it as a built-in again and see if it's more reliable
stdint has quit [Ping timeout: 240 seconds]
stdint has joined #linux-rockchip
kloczek has joined #linux-rockchip
kloczek has quit [Read error: Connection reset by peer]
kloczek has joined #linux-rockchip
kloczek has quit [Read error: Connection reset by peer]
kloczek has joined #linux-rockchip
kloczek has quit [Remote host closed the connection]
kloczek has joined #linux-rockchip
kloczek has quit [Read error: Connection reset by peer]
kloczek has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
kloczek has quit [Quit: kloczek]
kloczek has joined #linux-rockchip
zzarr has quit [Quit: This computer has gone to sleep]
zzarr has joined #linux-rockchip
zzarr has quit [Remote host closed the connection]