nighty- has quit [Quit: Disappears in a puff of smoke]
wzyy2 has quit [Ping timeout: 260 seconds]
indy has joined #linux-rockchip
nighty- has joined #linux-rockchip
ayaka has joined #linux-rockchip
cyteen has joined #linux-rockchip
wzyy2 has joined #linux-rockchip
<mxms>
ive got a rockchip unit from my car, and there's an MCU upgrader I found, but It seems I'm unable to flash any firmware to it. I get "File size error" when trying to flash.I have one image that passes these checks, but crashes the device as soon as it starts to update
<mxms>
are there any tools that can give me info on the update imgs?
matthias_bgg has quit [Remote host closed the connection]
matthias_bgg has joined #linux-rockchip
matthias_bgg has quit [Quit: Leaving]
cnxsoft1 has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 248 seconds]
cnxsoft1 is now known as cnxsoft
<rperier>
mhhhh, so I have found a fix for basic pinctrl for ethernet 1gbs (sent upstream), I am working on the same bug but with PINCTRL_FULL
<rperier>
apparently, GPIO4B1 (bank 4 , index 9) is muxed correctly to function 3 (so for mac_txclk) but the drive-strenght is not done
<rperier>
if I hack locally the function rk3288_pinctrl_set_pins() and I force drive-strenght to 12ma for bank=4, pin=9 after the pinmux to 3, everything is working fine
<rperier>
(I do it conditionnally only for this pin)
<rperier>
it looks like "&pcfg_pull_none_12ma" is not handled...
<rperier>
:/
vagrantc has joined #linux-rockchip
cnxsoft has quit [Quit: cnxsoft]
wzyy2 has quit [Ping timeout: 255 seconds]
wzyy2 has joined #linux-rockchip
* vagrantc
sighs
<vagrantc>
4.12.x didn't magically fix eMMC on my veyron-speedy
<vagrantc>
what's perplexing is with that simple .dts patch to 4.8.x it works reliably. but applying the same dts patch to later versions doesn't
<vagrantc>
it actually seems to get worse with each new version... 4.11.x and 4.12.x have mmcqd causing NMI stalls or something
<vagrantc>
so now USB rootfs basically doesn't work, as it's perpetually trying to access the eMMC and failing badly
<diego71>
vagrantc: on firefly-rk3288, kernel 4.12 seems to fix my problem with sd-card (emmc has always worked to me). But sometime, after the boot, the errors come back.
<vagrantc>
haven't had any issues with eMMC or microSD on firefly-rk3288
<vagrantc>
although i haven't used either extensively ... e.g. only use microSD for boot, and barely touch eMMC
<diego71>
I had with 4.9 and 4.11.
<vagrantc>
er, only use microSD for /boot
<vagrantc>
diego71: but glad to hear it's working for you now :)
<diego71>
and the boot from sd works, because file are readed by u-boot :)
<diego71>
(it just fail to mount /boot)
<diego71>
I could install u-boot on emmc, but after all it is safer loading u-boot from sd
matthias_bgg has joined #linux-rockchip
<vagrantc>
wow, finally managed to recognize the eMMC... but i bet this is the 1 out of 10-20 tries where it works
<vagrantc>
yeah, given how often i test u-boot, not too excited about having to short eMMC when it goes wrong :)
<vagrantc>
hmmmm...
<vagrantc>
this time i booted from USB rather than eMMC, and then inserted the microSD ... wonder if someone booting from microSD causes some misconfiguration that makes eMMC misbehave
* vagrantc
desperately grabs at straws
<vagrantc>
nope, just the freak "worked this time"
phinxy has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 240 seconds]
wadim_ has quit [Remote host closed the connection]
BenG83 has quit [Quit: Leaving]
afaerber has quit [Quit: Leaving]
wzyy2 has quit [Ping timeout: 260 seconds]
BenG83 has joined #linux-rockchip
nobe has quit [Quit: Page closed]
matthias_bgg has joined #linux-rockchip
matthias_bgg has quit [Quit: Leaving]
ayaka has quit [Ping timeout: 240 seconds]
ayaka has joined #linux-rockchip
Myy has joined #linux-rockchip
<Myy>
にゃ！
<Myy>
There seems to be a typo in spdif address defined in mainlined RK3288.dtsi
<Myy>
spdif: sound@ff88b0000
<Myy>
There's one digit too much
<Myy>
The thing is I don't know if the right address is ff88b000 or ff8b0000
<BenG83>
I had a similar experience with the rk3328.dtsi yesterday
<BenG83>
I was adding HS-200 to the emmc node
<BenG83>
and it turns out the clock names in the driver are ciu-sample, not ciu_sample as in the dtsi
<BenG83>
not sure what the right convention is here
<Myy>
Yeah, there's a few typos here and there that need to be solved. I don't know if I should reunite them in a big patch and send it to arm-soc for review, of it that can be done directly by the maintainers ?
<Myy>
I'll prepare the patch I guess
inode has quit [Quit: ]
wzyy2 has joined #linux-rockchip
<Myy>
Well, there's clearly some contradiction in the dw_mmc-rockchip.c code.