<asciilifeform>
i do not have a servo, nor any means to solder the 0.5mm connector
<amstan>
which you could use now if you had the hardware, but that's not much different from just soldering 8 wires around the spi chip
<asciilifeform>
right, next stop is the 8 wires.
Kamikaze84 has joined #linux-rockchip
<asciilifeform>
( this works on some machines, but not others, sometimes the other devices on the board interfere, and then you gotta lift the chip and replace with socketed )
<asciilifeform>
was hoping to avoid this.
nighty- has quit [Quit: Disappears in a puff of smoke]
<amstan>
other devices? like what? I can check schematics
<asciilifeform>
i was not aware that the schem is published
<asciilifeform>
where can i find it ?
<amstan>
it's not, but i can still check it :)
<amstan>
i wish this was opensource, it would prevent such awkwardness
<Kamikaze84>
Hi all. Is anyone willing to try a DTS patch for mainline for a rk3399-firefly ? This patch fixes the fan53555 & pwm-regulator issues I have with my board. I understand that this seems to only affect some firefly boards, so am wondering if anyone would be willing to try the patch on their board. If it works OK I will try and submit it as a patch to the linux-rockchip mailing list.
<asciilifeform>
amstan: consider to pgp it to me, i will host it .
<amstan>
asciilifeform: nope, i won't be able to do that
<asciilifeform>
sucks
<vagrantc>
Kamikaze84: happy to try it
<amstan>
asciilifeform: but i should be able to answer specific questions about it, so if you get stuck on something let me know
<vagrantc>
xypron in #u-boot was mentioning this issue earlier today
<asciilifeform>
amstan: where's the uart ?
<asciilifeform>
if i can find the uart, i can prolly bring it up via maskrom mode's uart boot
<asciilifeform>
and which usbc ( there are 2, one nearer to lcd, and one nearer to front )
<Kamikaze84>
if you want the already merged patch to the DTS it's in that same directory too: https://github.com/VenKamikaze/firefly-rk3399-build/tree/master/kernel/configs/working-4.16-rockchip not sure if there's any small differences in dts between that version of the kernel and the latest for-next or master (although i tried applying it to master the other day and it was ok), so i just linked the patch tho.
<amstan>
strap it as a debug accessory(forgot the strapping, check the spec), and you'll if you connect the sbu lines to another host you'll get access to a bunch of uart devices
<amstan>
port0 maybe?
<asciilifeform>
these are normal ttl-voltaged serial ?
<amstan>
asciilifeform: if you wait a couple of days I might be able to finish the documentation and release it, then you'll be set
<asciilifeform>
rx/tx pair ?
<asciilifeform>
amstan: that would be very neat
<amstan>
asciilifeform: and a little bit later you'll even be able to buy this cable, so you don't have to hack with breakout boards
<asciilifeform>
i've already ordered the breakout
<asciilifeform>
should be here in day or 2.
<amstan>
i'll have instructions on how to make your own too
<asciilifeform>
i expect it will take about 5min to make the cable.
<asciilifeform>
amstan: these lines, do they go straight from the rk3399 , or are they molested by the ec controller like the sdio lines ?
<amstan>
heh, probably molested
<asciilifeform>
so no use then
<amstan>
though... not sure what you mean by ec
<asciilifeform>
the boobytrap controller that prevents the thing from booting from sd, as you described earlier
<asciilifeform>
(and controls e.g. the keyboard, but this is incidental)
<amstan>
ec is not involved at all on the sdmmc slot
<amstan>
it's just that we assume ap(rk3399) always boots from spi flash, so we don't let it boot from anything else, to get the sdmmc working the rk3399 already has to output high on the en pins for the sdmmc voltage
<asciilifeform>
hm earlier i understood it to mean that the thing cannot suck boot rom off microsd because there is a trap preventing sd power and io from reaching the slot until disarmed by google's bootloader
<amstan>
it's not really a software trap, it's just that the rk3399 has to enable the pins before it's booting, and it can't, unless someone told it to do that beforehand
<asciilifeform>
amstan: sounds like you were among the builders ? what would it take to enable loading rom from sd ?
<amstan>
hardware changes
<asciilifeform>
well yes
<amstan>
if you get those 2 power en pins, that's probably enough (i think, i never tried it)
<amstan>
there might be some rk3399 strapping you have to do too, but i'm not too familiar
<asciilifeform>
do you know where they are ?
<amstan>
I can find out, but it'll have to be tomorrow
<asciilifeform>
ok thanks amstan
<amstan>
for the uart thing...
<amstan>
can you tell me about the protocol there? is 115200 8n0?
<amstan>
what you can get to via the typec breakout is like an onboard usb to serial stuck on a certain baud rate
<asciilifeform>
the boot-via-uart thing, i recall very vaguely from the datasheet, cannot immediately remember the baud