How to make r10.3 BSP support QSB?

Showing results for 
Search instead for 
Did you mean: 

How to make r10.3 BSP support QSB?

Contributor III

i want to make android 2.3.4 run on the QSB? however, Adeneo just release the r10.2 QSB BSP, no any more update.

i found that r10.3 only support mx51_bbg and mx53_smd, 

who can give me some advice to porting the BSP r10.3 to QSB? thanks a lot!


Actually, i want to know the difference between the fsl BSP and the Adeneo BSP! 

what modification base on the QSB by Adeneo?

Tags (1)
0 Kudos
4 Replies

Contributor III

I use the 8192cu, I have porting the driver to the kernel.

However, when I enable WIFI in Settings app, the result is error.

I try insmod the module manually, and then enable WIFI in Settings app, it works normally.

How to set the default wifi module in Android system?

0 Kudos

Contributor I
For USB WiFi, I think you have to enable USB WiFi driver firstly. What USB WiFi module are you using?
0 Kudos

Contributor III

Lily, Thanks for your reply!

my solution is very seem to yours

my solution is base on the i.MX53-QSB-Android-Gingerbread-Release4.0 configure

1. replace the mx53_loco.c file in the R10.3, use the  imx5_android_defconfig

2. copy the /device/fsl/imx53_loco directory from the Release4.0 to the R10.3, and make PRODUCT-imx53_loco-eng directly

3. modify the vold.fstab

4. modify the  mx53_loco.c to enable the hdmi output

 static struct mxc_lcd_platform_data sii902x_hdmi_data = {   

.analog_reg = "DA9052_LDO2",   

.fb_id = "DISP3 BG",   

.boot_enable = 1,   

.reset = sii902x_hdmi_reset,};

Now,  I try to let the usb wifi work on the R10.3, Do you have any idea?


thanks advance!

0 Kudos

Contributor I

Actually you can use FSL BSP to run android on QSB directly.

For example, if you are using Android R103, you can try the following:

1. Build one bootloader for MX53 QS.

$ cd ~/myandroid/bootable/bootloader/uboot-imx

$ make distclean

$ make mx53_loco_config

$ make


2. Build the Kernel

$ cd ~/myandroid/kernel_imx

$ make imx5_android_defconfig

$ make uImage


3. Reuse SMD android rootfs and make some minor changes for LOCO;

$ cd ~/myandroid

$ source build/

$ lunch imx53_smd-user

$ make


4. Modify the init.freescale.rc in the ramdisk to fix the screen rotation issue:

$ cd ~/myandroid/out/target/product/imx53_smd

$ cp -r root root_loco

$ cd root_loco

$ vim init.freescale.rc   (modify the init.freescale.rc by comment out this statement: setprop ro.sf.hwrotation 270)

$ find . | cpio --create --format='newc' | gzip > ../ramdisk-loco.img

$ cd ..

$ mkimage -A arm -O linux -T ramdisk -C none -a 0x70308000 -n "Android Root Filesystem" -d ./ramdisk-loco.img ./uramdisk-loco.img


5. Program the uboot.bin, uImage, system.img, recovery.img and uramdisk-loco.img to a TF card and boot from QSB board.  The uboot cmd are as follows:

setenv ethaddr 00:04:9f:01:57:8B

setenv fec_addr 00:04:9f:01:57:8B

setenv loadaddr 0x70800000

setenv rd_loadaddr 0x70D00000

setenv bootcmd 'run bootcmd_SD; bootm ${loadaddr} ${rd_loadaddr}'

setenv bootcmd_SD 'mmc read 0 ${loadaddr} 0x800 0x2000; mmc read 0 ${rd_loadaddr} 0x3000 0x300;'

setenv bootargs 'console=ttymxc0 init=/init androidboot.console=ttymxc0 ldb=off gpu_nommu, gpu_memory=64M video=mxcdi1fb:GBR24,VGA-XGA di1_primary vga'



6. To make sdcard and extsd mounted correctly, it needs to modify the vold.fstab.  In order not to change the default vold.fstab in the build env.  Thus, suggest to do it in this way. Boot up the QSB and then do the following changes in the console:

# mount -o remount,rw /dev/block/mmcblk0p2 /system   ß to make the system partition writable

# bash

bash-3.2# busybox vi /system/etc/vold.fstab  ß busybox is installed in R10.3 now, so we have vi to edit the file directly

0 Kudos