Build Android for i.MX Issue 2

We'd need more information to even try to answer.  what exactly are you trying to build?  where did you get the source code?  are you in the correct directory?  Is your command correct (no silly typos or anything similar)?

If I type your first make command in a completely empty directory I get exactly the same message, so it really doesn't tell us anything.

Hi,

I am trying to build a u-boot image per the "Freescale Sabre Lite User Manual V1.3":

$ cd ~/ android-imx6-r13.3/bootable/bootloader/uboot-imx

$ export ARCH=arm

$ export CROSS_COMPILE=~/android-imx6-r13.3/prebuilt/linux-x86/toolchain/arm-eabi-

4.4.3/bin/arm-eabi-

Command to build for i.MX6Q Sabrelite board is:

$ make distclean

$ make mx6q-sabrelite_android_config

$ make

So here is what I did:

now@Here:~$ cd mydroid/sabre/android-imx6-r13.3/bootable/bootloader/uboot-imx

now@Here:~/mydroid/sabre/android-imx6-r13.3/bootable/bootloader/uboot-imx$ export ARCH=arm

now@Here:~/mydroid/sabre/android-imx6-r13.3/bootable/bootloader/uboot-imx$ export CROSS_COMPILE=~/android-imx6-r13.3/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-

now@Here:~/mydroid/sabre/android-imx6-r13.3/bootable/bootloader/uboot-imx$ make distclean

now@Here:~/mydroid/sabre/android-imx6-r13.3/bootable/bootloader/uboot-imx$ make mx6q-sabrelite_android_config

make: *** No rule to make target `mx6q-sabrelite_android_config'.  Stop.

now@Here:~/mydroid/sabre/android-imx6-r13.3/bootable/bootloader/uboot-imx$

And, of course if I try to continue and type:

now@Here:~/mydroid/sabre/android-imx6-r13.3/bootable/bootloader/uboot-imx$ make

System not configured - see README

make: *** [all] Error 1

now@Here:~/mydroid/sabre/android-imx6-r13.3/bootable/bootloader/uboot-im

It is because  of "make: *** No rule to make target `mx6q-sabrelite_android_config'.  Stop." The source code is from this site at Freescale i.MX6 Development Platforms Software Download Center (SABRE Lite).

I am not sure how to fix this.

Ok, in the u-boot directory you'll probably find a file called boards.cfg. Look in that for a line that has mx6q-sabrelite_android

In recent versions of u-boot the line looks something like this:

Active arm armv7 mx6 boundary nitrogen6x mx6qsabrelite nitrogen6x:IMX_CONFIG=bo

but you'll need one where the bold part is mx6q-sabrelite_android

Exactly how it's defined will depend on how old the version of u-boot you're trying to build is and what vendor patches have been done to it.

I'd probably also suggest having a look at the Boundarydevices.com blog. There's a lot more information on sabre-lite there and I believe they also have pre-built android images if that's of use to you.

Hey alright. I'll look into it.

Thanks,

So assuming you're not bothered about building the source yourself, perhaps a combination of these two might get you a running system

http://boundarydevices.com/u-boot-2014-04-release-mx6/

http://boundarydevices.com/bluetooth-on-jellybean/

I've not tried either of these as I don't use Android, but the boundarydevices people are very good with this stuff, so I'd be surprised if there are problems.

Awesome...I bookmarked them. This helps a lot.

I built two roms for my tablet; both from the source, one rooted JB4.3. The second is Paranoid Android. I have not been able to get the tablet to even come on. These are both using the sabresd. The sabresd and the sabrelite are almost identical, right? I would think the roms would work. I guess I have to try debugging (usb to TTL).

Any thoughts?

While there are probably similarities between sabre-lite and sabresd I think there may also be enough differences that it won't work.

The reason I think that is that there are different configs in u-boot for these two boards.

Getting access to the serial console on both boards is really a requirement if you want to try debugging anything like this as it tends to be where all of the u-boot messages are sent and often where any early boot messages from linux or android go to as well

I don't have a sabresd myself, so I'm not really in a position to give you much help with it, however getting boot logs from the serial console might let us at least point you in some general directions on where to start looking.

Well by your response, it looks like I was thinking in the right direction. I will most likely set up the device tree for the sabrelite and build from the source. I will go from there and debug.

Thank you for all your help.