For the release by the end of this quarter, I would like to know whether UVC camera will be supported in Android.
(i.e. The standard camera app in android can support the UVC camera)
In current release R4.0, I found that there is a file named "V4l2UVCCamera.h" but without .cpp implementation. Will this be implemented in the next release?
Remi Lorriaux said:
@Levente: we should have an updated release by the end of this quarter. It will be aligned with the latest release from Freescale.
Remi: I saw freescale release a 10.2.1 version with some performance enhancements, are you planning to rebase your build?
Also anyone saw the weird effect of saving 2-3 files at the same time from the browser at the same time and the SDcard crawls... I mean CPU iowait is 98% and the dl speed is 4-8kbyte/s on each files.
There is no sound when playing music or video under Android vesion 4.0, and could not connect to internet network.
Thanks you were right I am able to run the prebuilt image. Again thanks for the assistance
Levente Tamas said: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
There is no sound when playing music or video under Android vesion 4.0, and could not connect to internet network.
You want to look at Levente Tamas' post above.
https://community.nxp.com/topic/listForContributor?user=18czvddrlmjgm" rel="nofollow
Help in building android OS (i.MX53-QSB-Android-Gingerbread-Release4.0)
////////////////////////////////////////////////////////////////////////
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:a9:81
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 >
/////////////////////////////////////////////////////////////////////////////////////////////
How to solve this problem?
Thanks a lot
would FREESCALE provide a software like Advanced ToolKit for QUICK START BOARD?
This will be easy for your customers to make OS
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
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
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 >
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!
Levi,
Yes, it will come with the same bundle, most likely this week.
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?