>-----Message d'origine-----
>De : Michal Suchanek [mailto:[email protected]]
>Envoyé : lundi 3 octobre 2016 14:29
>À : [email protected]
>Objet : Re: [opensuse-arm] openSUSE on Nexbox z68 (GeekBox like TV box)
>
>On Mon, 3 Oct 2016 10:54:41 +0000
>LOIC DEVULDER <[email protected]> wrote:
>
>> Hello all!
>>
>> I have a Nexbox z68 android TV box with a RK3368 processor that I
>> want to play with. This box is like the GeekBox but cheaper (I bought
>> mine for 30€). And, of course, also with less connectors, but it’s
>> really cheap for a 2GB RAM / 16GB eMMC box. The hardware of the two
>
>Hello,
>
>I have a Chinese RK based TV box lying on my table. Not sure about the
>exact details - been a while since I looked at it.
>
>The interesting bit is that it has three USB2 A connectors. Two of
>these are wired to the host controller and the third to the OTG
>controller. In the Android firmware the box came with there was a
>settings option to turn the OTG connector from host to device and use
>ADB and rkflashtool. https://github.com/crewrktablets/rkflashtools

I have the same connectors too, and I'm able to read/write eMMC with
rkflashtool or upgrade_tool.

>With these I pulled the firmware partitions from the device and modded
>a boot script to keep the OTG connector in device mode and that's as
>as far as I went.
>
>You can try to upload a kernel with rkflashtool without writing the
>in-device storage which might be helpful for unstable/development
>kernels.

What is the rhflashtool option to upload a kernel (or other image I think)
Without writing on the eMMC? I agree with you that's could be useful.

I undertand how the boot work (I think :-)). The resource.img contains the dtb,
the linuxroot is for the / image and the ramfs is for the kernel+initrd.

But my problem is that I've downloaded the latest JeOS for Tumbleweed, 
openSUSE-Tumbleweed-ARM-JeOS.aarch64-rootfs.aarch64-Current.tbz, but I cannot
find the initrd file in it...

>HTH
>
>Michal
>--
>To unsubscribe, e-mail: [email protected]
>To contact the owner, e-mail: [email protected]

Reply via email to