[llvmlinux] ODROIDUX

Tinti viniciustinti at gmail.com
Sun Nov 24 01:19:28 UTC 2013


Hi Renato,

Can you send the ODroid official page with Android images? I did not find
it so easily.
Then we can be sure that we are on the same point.

On Sat, Nov 23, 2013 at 4:51 PM, Renato Golin <renato.golin at linaro.org>wrote:

> Hi Vinicius,
>
> So, I'm a bit green on Android, but here's what I've done:
>
> 1. Got the Android image from ODroid webpage
> 2. Flashed an SDcard with it, which created 4 partitions:
>
> /dev/mmcblk0p1  4.0G  329M  3.7G   9% /media/rengolin/7FB2-80EE
> /dev/mmcblk0p3  2.0G   77M  1.8G   5%
> /media/rengolin/1d41d736-bc13-417e-82c1-d6931befb0e8
> /dev/mmcblk0p4  248M  132K  248M   1%
> /media/rengolin/57f8f4bc-abf4-655f-bf67-946fc0f9f25b1
> /dev/mmcblk0p2  992M  261M  732M  27%
> /media/rengolin/57f8f4bc-abf4-655f-bf67-946fc0f9f25b
>
>         Device Boot      Start         End      Blocks   Id  System
> /dev/mmcblk0p1         6982800    15377339     4197270    c  W95 FAT32
> (LBA)
> /dev/mmcblk0p2          136620     2246639     1055010   83  Linux
> /dev/mmcblk0p3         2246640     6451499     2102430   83  Linux
> /dev/mmcblk0p4         6451500     6982799      265650   83  Linux
>
> p1 is my "/sdcard" partition, mounts ok.
> p2 has "app", "backup", "data", "drm", "dontpanic", etc. Not sure what it
> is...
> p3 seems to be empty?
> p4 seems to be /root, with init.*, /dev, /etc, etc.
>
> I have no zImage on any of the partitions, and I can't find the /boot
> partition or directory.
>

That is expected. Android (usually) has a special binary format that is
composed by the:
- kernel parameters
- kernel itself
- minimal rootfs

Then you do not have access to the zImage directly. You need to use three
tools that are
available on this link http://ge.tt/5CFeOx11/v/0

They are 'abootimg' that checks and shows this boot image binary.
'mkbootimg' which
generates it and 'mkunpackbootimg' which extracts it. Normally what I do is
to
extract the boot.img which will give me a kernel. Then replace it and run
'mkbootimg'
with all other files and parameters given by 'mkunpackbootimg'.

But as I said usually some vendors implement other types of "packing"
schemes.
There are ones that will even put the kernel inside a partition as Linux
does.
Others will use uImage for compatibility with uBoot.

Karim's book talk about it as far as I remember.

Embedded Android - Porting, Extending, and Customizing
By Karim Yaghmour.

The  we need to know first which scheme is ODroid using. I will try to
check it and
send you the procedures.


> Questions:
>
> 1. How do I replace my current kernel with your LLVM-compiled one?
>

We need to check the scheme used by ODroid.


> 2. Do I un-tar your /lib/modules/ tar ball onto /root's /lib/modules?
>

Yes. Exactly that. I really need to do a better documentation of it.


>
> 3. My SDcard is only 4GB, so I think there might have been some issues
> with the size... I'm flashing on a 16GB SD, lets see if the same issue
> persists.
>
>
It should not be a problem. Android itself is really small. 300 MiB for
Android system itself should be more than enough.
We can try anyway.

Thanks Renato, I will try to generate a image here too.

Regards,
Tinti


> Thanks,
> --renato
>
> _______________________________________________
> LLVMLinux mailing list
> LLVMLinux at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/llvmlinux
>



-- 
Simplicity is the ultimate sophistication
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/llvmlinux/attachments/20131123/48c94aa2/attachment-0001.html>


More information about the LLVMLinux mailing list