i.MX ProcessorsのトピックRe: Android support

Android support

XXiao1z — Wed, 11 May 2011 04:00:35 GMT

The android code from freescale does not mention QS board support, is ubuntu the only option for now?

Re: Android support

MarianoGoluboff — Wed, 11 May 2011 04:16:50 GMT

You can get the Android BSP for the QSB from Adeneo. You can find the links to download both the source and the binary images here:

http://www.adeneo-embedded.com/en/Products/Board-Support-Packages/Freescale-i.MX53-QSB

Re: Android support

XXiao1z — Wed, 11 May 2011 04:23:22 GMT

Mariano Goluboff said:

You can get the Android BSP for the QSB from Adeneo. You can find the links to download both the source and the binary images here:
http://www.adeneo-embedded.com/en/Products/Board-Support-Packages/F...

Re: Android support

XXiao1z — Wed, 11 May 2011 04:24:22 GMT

just curious, why does not Freescale supply this as it normally does? thanks for the info!

Re: Android support

marshachang — Thu, 12 May 2011 02:53:51 GMT

Freescale supplies the Android BSP for the SABRE for Tablet www.freescale.com/imxsabre. But for the i.MX53 Quick Start board which is geared towards evaluation, Linux is supplied by Freescale and then Android and Windows Embedded are offered by third parties.

Re: Android support

XXiao1z — Fri, 27 May 2011 14:08:57 GMT

After android is up with my VGA LCD, the mouse scroll worked (not fully) _only_ for the first boot(to choose default or sdk activity), keyboard(DELL) _never_ worked, Android will enter to suspend mode and become unusable quickly, have you seen this?
Thanks,
Mariano Goluboff said:

You can get the Android BSP for the QSB from Adeneo. You can find the links to download both the source and the binary images here:
http://www.adeneo-embedded.com/en/Products/Board-Support-Packages/F...

Re: Android support

mark_smith — Tue, 07 Jun 2011 02:40:55 GMT

Xiao,

I've had the exact same experience with the keyboard/suspend issue. BUMP this question to the top of the list. What is needed to get keyboard and mouse support on the Adeneo Android LOCO package?

Thanks,

Re: Android support

XXiao1z — Tue, 07 Jun 2011 04:14:42 GMT

try this: remove usb mouse, just hook a usb keyboard.

while booting, keep hitting key F1, which should activate the bottom menu line, you can then set up the screen timeout to 30 minutes

Re: Android support

LarryLamb1z — Thu, 09 Jun 2011 11:36:48 GMT

I've found a similar circumstance with using the keyboard (after reviewing the i.MX Android R9.4 User Guide supplied by Adeneo in their i.MX53_Android Source BSP - available from their website: http://www.adeneo-embedded.com/en/Products/Board-Support-Packages/Freescale-i.MX53-QSB). Once the Android has booted, I hit F1 to perform the traditional unlock swipe. After that I use F1 to change settings (as mentioned by X Xiao), and I come back by using the Enter key on the keyboard. I've also used the Home key to get back to the Home screen. The arrow keys help navigate you through the applications and sub-menu selections. It's the next best thing to a touch screen.

Re: Android support

XXiao1z — Thu, 09 Jun 2011 13:18:06 GMT

This is correct. I'm hacking the code to change the timeout from 30 minutes to forever.

Re: Android support

JohnWeber — Wed, 15 Jun 2011 15:07:27 GMT

Can you pass along the steps to changing the display timeout to infinite? I'd like to do this as well. Thanks.

X Xiao said:

This is correct. I'm hacking the code to change the timeout from 30 minutes to forever.

Re: Android support

JohnWeber — Wed, 15 Jun 2011 19:06:32 GMT

Someone recently helped me out here. In the Android "Settings" menu, go to "Applications" then to "Development". Make sure that "Stay Awake" is selected. This will keep Android from putting the system to sleep.

Re: Android support

rlorriaux — Fri, 17 Jun 2011 18:35:57 GMT

The mouse cursor will be supported in our next Android Gingerbread release for the i.MX53 QSB. It should be available next week.

- RL (Adeneo Embedded)

Re: Android support

LeventeTamas — Mon, 20 Jun 2011 19:09:07 GMT

Remi: is it gonna be published like the previous releases like the 3.3 version, with the complete build scripts and source code? What is the ETA on the package? The reason I am asking, because I was trying to get the gingerbread version to work on QSB but it fails with various reasons. Sometimes the dalvikvm reports GC low memory and won't boot, sometimes the kernel panics, sometimes after uart init I get garbled serial output. I tried from the freescale r10.2 release doc to build it, but I got stuck a little bit with these various errors, and your previous build systems work so nicely I can only hope the next will work just as smooth:)

Thx

Levi

Remi Lorriaux said:

The mouse cursor will be supported in our next Android Gingerbread release for the i.MX53 QSB. It should be available next week.

- RL (Adeneo Embedded)

Re: Android support

XXiao1z — Mon, 20 Jun 2011 19:20:09 GMT

have you tested your board with ubuntu? the 3.3 android should run fine on it, though mouse is dead.

Re: Android support

LeventeTamas — Mon, 20 Jun 2011 19:24:47 GMT

Yes, it works with ubuntu even with a fresh ltib build, and from freescale the r10.1 android release as well, and adeneos package 3.3->android 2.2 as well. it is only freescales r10.2 that I have problems with. The uboot works compiled with: imx53_loco (ard won't even show up), kernel for some level works with imx53_ard, and with android I tried product-imx53_ard-eng/user, none seemed to show up.

Any good suggestions where to look for the problem?

Re: Android support

rlorriaux — Mon, 20 Jun 2011 20:36:19 GMT

Levi,

Yes, it will come with the same bundle, most likely this week.

Re: Android support

ThomasBandelier — Thu, 23 Jun 2011 14:28:06 GMT

Hi Remi,

Still can not find QSB's Gingerbread release on Adeneo's web site

Do you confirm availability before end of the week?

Many thanks for your support!

Remi Lorriaux said:

Levi,
Yes, it will come with the same bundle, most likely this week.

Re: Android support

RichardFelician — Fri, 01 Jul 2011 23:47:46 GMT

Hi looking for some help with the new Adeneo version 4.0. I used the script flash_prebuilt_android.sh to create a Android SD card. the script ran fine but when I try to run it I get a kernel image error. I had been using the 3.3 version and was able to use the scripts and run the micro card just fine. Moved to Version 4.0 for mouse support. Anyway at the bottom I get a CRC error. I am going to try building the images from scratch still I am curious why these images are not working

CPU:   Freescale i.MX53 family 2.1V at 800 MHz
mx53 pll1: 800MHz
mx53 pll2: 400MHz
mx53 pll3: 216MHz
mx53 pll4: 455MHz
ipg clock     : 66666666Hz
ipg per clock : 33333333Hz
uart clock    : 66666666Hz
cspi clock    : 54000000Hz
ahb clock     : 133333333Hz
axi_a clock   : 400000000Hz
axi_b clock   : 200000000Hz
emi_slow clock: 133333333Hz
ddr clock     : 400000000Hz
esdhc1 clock : 80000000Hz
esdhc2 clock : 80000000Hz
esdhc3 clock : 80000000Hz
esdhc4 clock : 80000000Hz
nfc clock     : 26666666Hz
Board: MX53-LOCO 1.0
Boot Reason: [WDOG]
Boot Device: SD
I2C:   ready
DRAM:   1 GB
MMC:   FSL_ESDHC: 0, FSL_ESDHC: 1
In:    serial
Out:   serial
Err:   serial
Serial reinitilized!
Checking for recovery command file...
Net:   got MAC address from IIM: 00:04:9f:01:b4:56
FEC0 [PRIME]
Hit any key to stop autoboot: 0

MMC read: dev # 0, block # 2048, count 6144 partition # 0 ...
6144 blocks read: OK

MMC read: dev # 0, block # 12288, count 768 partition # 0 ...
768 blocks read: OK
## Booting kernel from Legacy Image at 70800000 ...
   Image Name:   Linux-2.6.35.3-01073-g7d68974-di
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3260128 Bytes = 3.1 MB
   Load Address: 70008000
   Entry Point: 70008000
   Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
MX53-LOCO U-Boot >

Re: Android support

LeventeTamas — Sat, 02 Jul 2011 05:54:40 GMT

Probably you had a different image on the card before, the only thing missing from the adeneo scripts is the possibility to zero out the first 8-10 MBs of the SD card. try dd if=/dev/zero of=[your sd card] bs=1M count=10 and then transfer the image again it will fix it. BTW the problem I think lies in the the value, where it says 0x800 0x1800, you need to change that to 0x800 0x2000 and it will boot. it is realated to the size of the kernel being too big.

Levi