HDMI Dongle SW:
The attachment is an HDMI dongle patch based on R13.4 GA. The patches include r13.4-ga-add-on-patches. You can patch it after applying R13.4 GA patch such as add-on patches. You can run script to revb_dongle_patch_install.sh to apply these patches.
How to apply the hdmidongle_REVB_R13.4_patch-20121115.tgz:
1. Suppose your android source top is ~/myandroid
2. tar zfvx hdmidongle_REVB_R13.4_patch-20121115.tgz -C ~/
3. copy revb_dongle_patch_install.sh to ~/
4. cd hdmidongle_REVB_R13.4_patch
5. ~/revb_dongle_patch_install.sh
6. The revb_dongle_patch_install.sh will take ~/myandroid as default directory to do patch
7. If your android source tree top is not ~/myandroid. For example, ~/myandroid_ICS, please run ~/revb_dongle_patch_install.sh ~/myandroid_ICS
The following is the release notes for hdmidongle_REVB_R13.4_patch-20130118.tgz
1. New features:
a. uboot fastboot
b. ldo bypass
c. ntfs support
d. bluetooth A2DP
2. Bug fix
a. WifiDirect connect issue
b. realtek throughput issue with TPLink AP
3. File list:
README.TXT --- this file
0001-uboot_fastboot.patch --- uboot fastboot patch
0002-LDOBYPASS.patch --- enable ldo bypass patch
0003-WifiDirect.patch --- wifi direct connect patch
0004-ntfs_support.patch --- ntfs support patch
0005-BT_enable.patch --- enable bluetooth A2DP
0006-1G_boot_stable.patch --- make 1G bootup stable
ntfs-3g.tar.gz --- open source ntfs-3g for ntfs support
rtl8192ce_v4.0.0_6239.20121226_TPIOT1.tgz --- realtek new driver for TPLink AP throughput issue
MD5SUM.TXT --- md5 check sum
4. Patch guide
Please run md5sum -c MD5SUM.TXT first to confirm all the files received are ok.
All these patches are based on the patch release hdmidongle_REVB_R13.4_patch-20121115.tgz
You need to do as following: R13.4 GA--->patch hdmidongle_REVB_R13.4_patch-20121115.tgz --> patch hdmidongle_REVB_R13.4_patch-20130118.tgz
Supposed the ~/myandroid is your top directory of the android source tree.
Please run the following command to apply the patches .
$tar zfvx hdmidongle_REVB_R13.4_patch-20130118.tgz -C ~/
$cd ~/myandroid
$git apply ~/hdmidongle_REVB_R13.4_patch-20130118/0001-uboot_fastboot.patch --verbose
$git apply ~/hdmidongle_REVB_R13.4_patch-20130118/0002-LDOBYPASS.patch --verbose
$git apply ~/hdmidongle_REVB_R13.4_patch-20130118/0003-WifiDirect.patch --verbose
$git apply ~/hdmidongle_REVB_R13.4_patch-20130118/0004-ntfs_support.patch --verbose
$git apply ~/hdmidongle_REVB_R13.4_patch-20130118/0005-BT_enable.patch --verbose
$git apply ~/hdmidongle_REVB_R13.4_patch-20130118/0006-1G_boot_stable.patch --verbose
$rm -rf kernel_imx/drivers/net/wireless/rtl8192ce
$tar zfvx ~/hdmidongle_REVB_R13.4_patch-20130118/rtl8192ce_v4.0.0_6239.20121226_TPIOT1.tgz
$tar zfvx ~/hdmidongle_REVB_R13.4_patch-20130118/ntfs-3g.tar.gz -C external
5. Build and run
new patch 0007-battery_always_full.patch:
Some games check the battery capacity to determine, it could run or not. But on the hdmi dongle we have no real battery, it makes some games can not run on the hdmi dongle. We enable the fake battery let the andorid feel it has battery and it is 100% full.
1. Please use this patch after patch hdmidongle_REVB_R13.4_patch-20130118.tgz
2. suppose your android top directory is ~/myandroid and you put he 0007-battery_always_full.patch in your home directory ~
3. cd ~/myandroid
4. git apply --verbose ~/0007-battery_always_full.patch
5. please rebuild bootimage and run
patch 0008-boot_unlock_screen.patch:
When bootup, it goes into desktop rather than screen locker.
1. suppose your android top directory is ~/myandroid and you put the 0008-boot_unlock_screen.patch in your home directory ~
2. cd ~/myandroid
3. git apply --verbose ~/0008-boot_unlock_screen.patch
4. please rebuild systemtimage and run
2. cd ~/myandroid
3. git apply --verbose ~/0008-boot_unlock_screen.patch
patch 0009-uboot-enable-mmu-fix.patch:
This patch is for some issue in mmu enable.
It will improve all the modules in uboot.
1. suppose your android top directory is ~/myandroid and you put the 0009-uboot-enable-mmu-fix.patch in your home directory ~
2. cd ~/myandroid
3. git apply --verbose ~/0009-uboot-enable-mmu-fix.patch
4. please rebuild uboot and rub
patch tarball hdmidongle_REVB_R13.4_patch-20130123.tgz:
hdmidongle_REVB_R13.4_patch-20130123.tgz contains 0007-battery_always_full.patch 0008-boot_unlock_screen.patch 0009-uboot-enable-mmu-fix.patch
remove attached files here: 0007-battery_always_full.patch 0008-boot_unlock_screen.patch 0009-uboot-enable-mmu-fix.patch
Remove hdmidongle_REVB_R13.4_patch-20130123.tgz, hdmidongle_REVB_R13.4_patch-20130118.tgz and upload hdmidongle_REVB_R13.4_patch-20130124.tgz
hdmidongle_REVB_R13.4_patch-20130124.tgz contains all patches in hdmidongle_REVB_R13.4_patch-20130123.tgz, hdmidongle_REVB_R13.4_patch-20130118.tgz.
Please use the hdmidongle_REVB_R13.4_patch-20130124.tgz.
hdmidongle_REVB_R13.4_patch-20130131.tgz:
Besides all the patches released before.
Three more patches are added in this patch tar ball.
0010-boot_disable_screenlocker.patch --- For fix 0008-boot_unlock_screen.patch
0011-wm8326-DC_CONTROL_RATE.patch --- Change the wm8326 pmic rate to immediate voltage change
0012-Added-default-video-mode-check-make-sur.patch --- Video mode check
hdmidongle_REVB_R13.4_patch-20130201.tgz:
Just change the readme to place emphasis on the 0006-1G_boot_stable.patch reverse
Reverse patch 0008-boot_unlock_screen.patch and 0006-1G_boot_stable.patch
0008-boot_unlock_screen.patch: it has some problem but doesn't do any harm to the hdmi dongle.
Please use 0010-boot_disable_screenlocker.patch, instead.
0006-1G_boot_stable.patch: The patch take more cpu delay to adapt the pmic, we change the pmic setting
in 0010-boot_disable_screenlocker.patch. This patch is no needed. And it will lower
the performance. Please reverse it.
cd ~/myandroid
git apply --verbose ~/0006-1G_boot_stable.patch
hdmidongle_REVB_R13.4_patch-20130221.tgz:
There are three important fixes include in this release. They make the dongle stable.
1. lowmem killer issue fix
2. Update realtek wifi driver to fix the soft ap issue
3. Wifi p2p framework fix to resovle wifi direct only one side work issue
Please read the README.TXT for detail and the other changes.
hdmidongle_REVB_R13.4_patch-20130308.tgz:
This patch tar ball include all the patches in hdmidongle_REVB_R13.4_patch-20130221.tgz.
Besides, it has a new patches 0020-DL_WifiDirect_Concunrrent_crash_fix.patch to fix the crash issue on DL board.
HDMI Dongle schematic, pcb, gerber and BOM have been attached, the detailed hardware feature has been list below:
Android 4.x HDMI Dongle SPECIFICATION | |
Core Configure | |
Operating System | Android 4.x Operating System Based on Micro-PC Platform |
CPU Processor | Freescale i.MX6x DualLite/Quad Core |
DRAM Storage | DDR3 1GigaByte Size, Data rate 1066MT/s |
Flash Storage | 4GigaByte NAND flash ROM |
Power System | |
Power Supply | DC JACK / Micro USB : 5V/2A |
LED Status | Green: Power ON; Red: System Run |
Socket/Connector | |
MicroSD Socket | SDXC Support, Up to 32GB size |
USB HOST 2.0 | USB 2.0 HOST Support |
USB OTG 2.0 | USB 2.0 OTG Support |
Display/Audio | |
HDMI Output | HDMI TypeA Plug connector, 1080p@60Hz output |
Video Decoder | Support Variety of Video Format: MPEG4/H.263/H.264/MJPEG/Xvid/VC-1/WMV/MPEG2/VP8... |
Audio Decoder | Support Variety of Audio Format: MP3/AAC/LPCM/FLAC/AMR/AC3/WMA/Vorbis |
GPU Support | GC2000 GPU core,2D/3D engine support,OpenGL support |
Wireless Network | |
WiFi Network | IEEE 802.11b/g/n,Up to 300Mbps,AP/P2P/Sta Mode Support |
Others | |
Key | Recovery key support |
RevB2 |
OTT TV BOX LINK: https://community.freescale.com/docs/DOC-94561
JB4.2 patches link : Patches for HDMI Dongle JB4.2.2_1.0.0-GA Release
We are designing this products, how to get your support?
Thank you very much, how can I get you and Mr.Jiang Wei's contact details?
Can you provide the contacts?
You can visit http://www.freescale.com/webapp/sps/site/homepage.jsp?nodeId=05 to get the support.
I'd be interested in add support for it in Yocto; that's why I asked.
Someone I can contact to discuss it?
Thanks for that. I've provided more instructions to build it in Ubuntu 12.04 64-bit in case some are interested.
Great work! The schematics include additional circuity for LVDS, SATA etc, it doesn't look like the pcb layout include the io lines for theses? Furthermore what type of cooling heatsink would be the preferred option considering the small dimensions of the device.
Hi Jas, the NVCC_LVDS2P5 must be powered for this power is not only for LVDS display interface, but also for DDR I/O. This pin cannot be disconnected, even if the LVDS interface is not used. The SATA circuits are reserved for POWER ESATA interface which has not been used on revB2. As to the thermal design, aluminium is preferred for the heatsink.
Hello,
Is this board available now ?
I'd like to buy this mini PC for evaluation.
Thanks
M.Phuong
The board is available, you can ask fae to get it.
Dear Sir,
Sorry, what fae means ?
Could you please show me the contact ?
Regards
Hi Sir,
Sorry, you can not get the board for we do not sale the board, you can make the PCB by yourself.
please refer to link https://community.freescale.com/docs/DOC-94817 to get patches for JB4.2 hdmi dongle
Dear all,this is henry ,According to the freescales data ,we bulit the PCBA samples ,if any body need this type samples ,pls contact with me .or you can leave some information .
How much cost each sample?
Cost 1~10 pcs 300USD/Unit
11~50pcs 200USD/Unit
51~100pcs 150USD/Uint
>100pcs Negotiate the Price .
For the first bacth had been sold out ,we begin the second bacth booking . And get the 50 pcs order total ,we will run the batch .
Why I cannot run the kernel from fresscale.com to gk802?
who can help me?
whether is the gk802 the same as hdmidongle?
Hello Mr. Jiangwei,
Could you please provide the WM8326 config EEPROM data ?
Best Regards,
Thank you very much.
Hi ,
I am having imx6q sabrelite board.
Is HDMI dongle android is same as normal android runs on imx6?
If want to make same thing on sabrelite board,What will be changes i need to do?
Thanks,
Pratik
Hi Pratik,
Is there a reason you're not using our (Boundary Devices') Android?
We fully support Android on the SABRE Lite platform:
The latest published binary release is '4.3-beta', but our source trees have been updated to include 4.3-ga.
http://boundarydevices.com/second-release-jellybean-4-3-beta-mx6/
If you follow our blog, you'll see that we're documenting most of the steps we take:
Hi Eric,
Thanks for fast reply, I am using imx6-jb-sdcard-20130628.img.gz on Board.
when I go through HDMI Dongle Design I Think to try same think out of sabrelite.
But you are saying Boundary Device's android is doing same thing as this dongle is doing , if I am right.
Will you please clarify that.
Thanks ,
Pratik.
Hi Pratik,
The image you listed is one of ours (a Boundary Devices' version), though a bit out-dated. Our latest Jellybean version is the second release pointed to above.
I haven't gone through the details, but I suspect the HDMI dongle release has the same origin, but has been tailored for different hardware.
Dear Wei:
Dose you have config file of wm8326? Is it same with OTT TV box?
Hi All:
hdmi dongle board can't bring up. When I use DDR_Stress_Tester_V1.0.2 to test the ddr, the board can't pass the DQS gating, read/write delay calibration. Pls see the log below:
Type 0 for 650MHz, 1 for 800MHz, 2 for 1GHz, 3 for 1.2GHz
ARM set to 650MHz
Please select the DDR density per chip select (in bytes) on the board
Type 0 for 2GB; 1 for 1GB; 2 for 512MB; 3 for 256MB; 4 for 128MB; 5 for 64MB; 6
for 32MB
For maximum supported density (4GB), we can only access up to 3.75GB. Type 9 to
select this
DDR density selected (MB): 1024
Calibration will run at DDR frequency 528MHz. Type 'y' to continue.
If you want to run at other DDR frequency. Type 'n'
Enter the DDR frequency for calibration [350MHz to 528MHz]:
350
The freq you entered was: 350
DDR Freq: 352 MHz
Would you like to run the write leveling calibration? (y/n)
Please enter the MR1 value on the initilization script
This will be re-programmed into MR1 after write leveling calibration
Enter as a 4-digit HEX value, example 0004, then hit enter
0004 You have entered: 0x0004
Start write leveling calibration
Write leveling calibration completed
MMDC_MPWLDECTRL0 ch0 after write level cal: 0x00010001
MMDC_MPWLDECTRL1 ch0 after write level cal: 0x00180018
MMDC_MPWLDECTRL0 ch1 after write level cal: 0x000A0013
MMDC_MPWLDECTRL1 ch1 after write level cal: 0x000A0015
Would you like to run the DQS gating, read/write delay calibration? (y/n)
Starting DQS gating calibration...
. . . . . . . . . . . . . . ERROR FOUND, we can't get suitable value !!!!
dram test fails for all values.
The DDR stress test can run with an incrementing frequency or at a static freq
To run at a static freq, simply set the start freq and end freq to the same valu
e
Would you like to run the DDR Stress Test (y/n)?
End of Test !
^C
D:\DDR_Stress_Tester_V1.0.2\DDR_Stress_Tester_V1.0.2\Binary>
When I use MFG tools of OTT TV box, It stopped at Loading uboot
So, What's wrong? DDR is not ok?