<karlp>
needed root to get something that could turn on adb tcp on boot for me.
<karlp>
got it now.
<karlp>
just trying to ponder next steps.
<karlp>
Should I be able to rkunpack a dd image of the boot partition?
<karlp>
or should I use upgrade_tool/rkflashtool to dump the partition instead?
<naobsd>
there is no difference
<naobsd>
probably boot should be ANDROID! image, you need to use proper tool for "unpack". there is no difference for "dump"
<karlp>
yeah, just found it's got a proper ANDROID! header,
<karlp>
so I should be able to use the adnroid sdk tools for that then.
<karlp>
ah, abootimg was what I'd forgotten
<naobsd>
android sdk tools?
<naobsd>
if you are talking about tools for ANDROID! image, you need to use mkbootimg in Rockchip SDK for packing. you may use any unpacking tool for ANDORID! image
<naobsd>
mkbootimg for _Rockchip_ in Rockchip SDK or somewhere else
<naobsd>
as same as past Rockchip SoCs.
<naobsd>
nothing is changed
<karlp>
yes, I think it's just that in the past I'd used rkflashtool/Upgrade_Tool to dump partitions, but this time I'd used dd from within android, so I was only seeing the direct ANDROID! image format this time.
<naobsd>
any dumping tool doesn't convert image format
<naobsd>
do't you have USB A-A cable?
<karlp>
oh yeah, and that's how I got it up, but I want to put it back in another room,
<karlp>
I know I'll hav eto use usb for any real reflashing.
<karlp>
did you ever try mmind's tree or any mainline kernel on the mxq4k you got?
<naobsd>
I tried rk3228-evb configuration in linux-next, and it worked
<naobsd>
if your board is T066, there are UART2 holes for console
<karlp>
oh, neat I don't think you'd gotten that far last time.
<karlp>
that was with the kernel+dtb flashed to boot partition?
<karlp>
ethernet/usb working?
<naobsd>
boot.img with kernel+ramdisk+dtb will work, but I think I used kernel/boot(ramdisk)/resource(dtb) separately
<naobsd>
I cannot remember detail. rk3228/3229 support was very few when I tried (February? March?) and I don't try anything lately
<naobsd>
please check rk3228 dts. you can see what's supported
<naobsd>
sorry, I have to leave now
<naobsd>
if you want to use UART2, default bootloader binaries set console speed something not 115200
<karlp>
ok, thanks for the notes
<naobsd>
RK u-boot can be recompiled with 115200. you can use 115200 on kernel. other binary blobs (e.g. DDR init, trust) cannot be changed so you will see some garbage very beginning
<karlp>
hrm, rk3228 in linux-next only has emmc and tsadc.