iWave is upgrading Android KitKat 4.4 BSP for its all variants of i.MX6 Qseven SOMs. The KitKat BSP supports following features and will be available in end of Q2 2015: i.MX6 ARM Cortex A9 Quad, Dual, Dual Lite & Solo CPU 1GB DDR3 RAM (Quad, Dual, Dual Lite CPU version)/ 512MB DDR3 (Solo CPU version) Freescale PMIC SPI NOR Flash eMMC Flash uSD slot Standard SD slot USB 2.0 Host USB 2.0 device 10/100/1000 Ethernet PCIex1 Port CAN Port LVDS display port Capacitive multi-touch PWM for backlight HDMI Port with Audio SATA (Support available only in i.MX6Q/D) Hardware Codecs (Encode/Decode) 2D/3D Graphics MIPI CSI camera port AC97 Audio In/Out Console UART Besides the Android support, Linux and WEC7 board support packages are also available for the i.MX6 Qseven SOMs from iWave systems. More details about the i.MX6 Qseven SOM & software features can be found in the i.MX6 Qseven product page. Device drivers will be supported for specific interface chipsets, which are used in iWave's Qseven Carrier board. More details about iWave i.MX6 Qseven development kit can be found in the following webpage: http://www.iwavesystems.com/product/development-platform/i-mx6-q7-development-kit-54.html

Added by Maciej Halasz on July 21, 2011 at 12:58pm Dual Display demo on i.MX53qsb. The demo has been built with LinuxLink including: - Qt Embedded based UI - hardware accelerated video playback with GStreamer - dual display with blending between framebuffers learn more at: http://www.timesys.com/embedded-linux/training/timesys-university/freescale_imx53

我们目前用的是Eink的9.7寸屏幕，打上freeescale 提供的uboot的patch之后发现默认是6寸屏，于是修改了timing，如下： short lcd_cmap[256]; vidinfo_t panel_info = {         .vl_refresh = 85,         .vl_col = 1200,         .vl_row = 825,         .vl_pixclock = 32000000,         .vl_left_margin = 12,         .vl_right_margin = 128,         .vl_upper_margin = 4,         .vl_lower_margin = 10,         .vl_hsync = 20,         .vl_vsync = 4,         .vl_sync = 0,         .vl_mode = 0,         .vl_flag = 0,         .vl_bpix = 3,         .cmap = (void *)lcd_cmap, }; struct epdc_timing_params panel_timings = {         .vscan_holdoff = 8,         .sdoed_width = 10,         .sdoed_delay = 20,         .sdoez_width = 10,         .sdoez_delay = 20,         .gdclk_hp_offs = 632,         .gdsp_offs = 20,         .gdoe_offs = 0,         .gdclk_offs = 1,         .num_ce = 3, }; 现在屏幕要进行四次全刷之后黑屏，全刷过程中可以看到logo，刷完就没有了，不知道还有些什么地方需要修改，求指导

Hi freescale, For using platform I.MX6QP and Android 6.0.1, test camera format is failed in CTSV R13. CTSV need to test format N21, YV12, YUY2,(160x120, 176x144, 320x180, 320x240, ...,640x480). Question list : (1.) It test YUY2 format is failed for handing preview screen was show green screen. For logcat issue log: 01-18 03:10:50.856 221 1252 E imx6.gralloc: int GPUBufferManager::lockYUVHandle(private_handle_t*, android_ycbcr*) not support format:0x14 01-18 03:10:50.856 221 1252 W GraphicBufferMapper: lock(...) failed -22 (Invalid argument) 01-18 03:10:50.892 221 311 E FslCameraHAL: processBufferWithIPU:320, IPU_CHECK_TASK ret=12 01-18 03:10:50.892 221 1252 E imx6.gralloc: int GPUBufferManager::lockYUVHandle(private_handle_t*, android_ycbcr*) not support format:0x14 01-18 03:10:50.892 221 1252 W GraphicBufferMapper: lock(...) failed -22 (Invalid argument) 01-18 03:10:50.924 221 311 E FslCameraHAL: processBufferWithIPU:320, IPU_CHECK_TASK ret=12 01-18 03:10:50.924 221 1252 E imx6.gralloc: int GPUBufferManager::lockYUVHandle(private_handle_t*, android_ycbcr*) For failed status: Test_fail_picture (2.) For test YV12 , 424X240, the result is failed. Logcat failed log: 01-18 03:29:51.547 1213 1229 D OpenGLRenderer: endAllStagingAnimators on 0x917f0700 (ListPopupWindow$DropDownListView) with handle 0x92564f30 01-18 03:29:51.637 221 1259 I FslCameraHAL: Stream::Stream(int, camera3_stream_t*, Camera*) create preview stream 01-18 03:29:51.637 221 1259 I FslCameraHAL: stream: w:424, h:240, format:0x103, usage:0x8000302, buffers:3 01-18 03:29:51.637 221 1259 I FslCameraHAL: create callback stream 01-18 03:29:51.637 221 1259 I FslCameraHAL: stream: w:424, h:240, format:0x101, usage:0x8000303, buffers:3 01-18 03:29:51.650 221 1325 I FslCameraHAL: int32_t VideoStream::configure(android::sp<Stream>): w:160, h:120, sensor format:0x14, stream format:0x103, fps:15, num:3 01-18 03:29:51.651 221 311 I FslCameraHAL: virtual int32_t UvcDevice::UvcStream::onDeviceStopLocked() 01-18 03:29:51.664 221 311 I FslCameraHAL: virtual int32_t DMAStream::freeBuffersLocked() 01-18 03:29:51.664 221 311 I FslCameraHAL: freeBufferToIon buffer num:3 01-18 03:29:51.664 221 311 I FslCameraHAL: virtual int32_t UvcDevice::UvcStream::onDeviceConfigureLocked() 01-18 03:29:51.664 221 311 I FslCameraHAL: virtual int32_t DMAStream::onDeviceConfigureLocked() 01-18 03:29:51.664 221 311 I FslCameraHAL: virtual int32_t USPStream::onDeviceConfigureLocked() 01-18 03:29:51.664 221 311 I FslCameraHAL: virtual int32_t MMAPStream::onDeviceConfigureLocked() 01-18 03:29:51.664 221 311 I FslCameraHAL: Width * Height 424 x 240 format YUYV, fps: 15 01-18 03:29:51.664 221 311 E FslCameraHAL: width:424 height:240 is not supported. 01-18 03:29:51.694 221 311 I FslCameraHAL: virtual int32_t DMAStream::allocateBuffersLocked() 01-18 03:29:51.694 221 311 I FslCameraHAL: allocateBufferFromIon buffer num:3 01-18 03:29:51.696 221 311 I FslCameraHAL: phyalloc ptr:0xa9b8d000, phy:0x26180000, ionSize:208896 01-18 03:29:51.698 221 311 I FslCameraHAL: phyalloc ptr:0xa9b21000, phy:0x261c0000, ionSize:208896 01-18 03:29:51.701 221 311 I FslCameraHAL: phyalloc ptr:0xa9aee000, phy:0x26200000, ionSize:208896 01-18 03:29:51.701 221 311 I FslCameraHAL: virtual int32_t UvcDevice::UvcStream::onDeviceStartLocked() 01-18 03:29:51.701 221 311 I FslCameraHAL: buf[0] length:203520 01-18 03:29:51.701 221 311 I FslCameraHAL: buf[1] length:203520 01-18 03:29:51.701 221 311 I FslCameraHAL: buf[2] length:203520 Fail Piture: YV12_test_fail For freescale camera HAL description ./hardware/imx/mx6/libcamera3/CameraHAL.cpp /* Hardware limitation on I.MX6DQ platform * VPU only support NV12&I420 format. * IPU doesn't support NV21 format. * But android framework requires NV21&YV12 format support. * YV12&I420 Y/UV stride doesn't match between android framework and IPU/GPU. ** Android YV12&I420 define: * - a horizontal stride multiple of 16 pixels * - a vertical stride equal to the height * - y_size = stride * height * - c_stride = ALIGN(stride/2, 16) * ** GPU YV12&I420 limitation: * - GPU limit Y stride to be 32 alignment, and UV stride 16 alignment. * ** IPU hardware YV12&I420 limitation: * - IPU limit the Y stride to be 2x of the UV stride alignment. ** IPU driver YV12&I420 define: * - y_stride = width * - uv_stride = y_stride / 2; * So there is work around to treat the format on I.MX6DQ platform: * Change format NV21&YV12 to NV12&I420 in Camera framework. * The NV21 format required by CTS is treated as NV12. * YUV alignment required by CTS doesn't match on I.MX6DQ platform. */ How to fix the issue in IMX6qp for CTSV?

Hi NXP expert : Deaufult iMX8M apply 3GB DRAM density with the system, How to modify DRAM configration that could cutdowm density to 1GB DRAM ? 

HI Li, The particular video attached in ticket is playing properly in below 2 cases. But not playing properly with HW decoder. That is the issue here.   4. On my x86_64 & window 7 PC, use VLC to play test_aspect_h263p_43.avi, no issue observed. VLC is configured to not use GPU codec, so VLC use SW decoder to decode the video stream. 5. On my x86_64 & ubuntu virtual box, use ffmpeg to play test_aspect_h263p_43.avi, no issue observed. ffmpeg use SW decoder to decode the video stream.

​ Horw, Switzerland: Toradex announced it has joined Microsoft Azure Certified for Internet of Things (IoT), ensuring customers develop and deploy IoT solutions quickly with hardware and software that has been pre-tested and verified to work with Microsoft Azure IoT services. Microsoft Azure Certified for IoT allows businesses to reach customers where they are, working with an ecosystem of devices and platforms, enabling faster time to production. Toradex offers robust and compact embedded computing solutions encompassing System on Modules (SOMs) and Customized Single Board Computers (SBC), which are used in variety of industries such as Industrial Automation, Medical, Automotive, Robotics and many more. Toradex modules are ideal for quickly creating proof-of-concepts as well as scaling seamlessly from prototypes to tens of thousands of devices without the need to redesign the embedded computer. This reduces risk and time to market. A list of certified Toradex Apalis and Colibri SOMs can be found here. Toradex will be offering a webinar on “Getting Started with Azure IoT on Devices”. Free registration can be done here. “Microsoft Azure Certified for IoT validates our ability to jumpstart customers’ IoT projects with pre-tested hardware and operating system combinations,” said Stephan Dubach, CEO, Toradex. “Decreasing the usual customization and work required for compatibility ensures Toradex helps customers get started quickly on their IoT solution.” “Microsoft Azure Certified for IoT extends our promise to bring IoT to business scale, starting with interoperable solutions from leading technology companies around the world,” said Barb Edson, general manager for Data Platform and Internet of Things, Microsoft. “With trusted offerings and verified partners, Microsoft Azure Certified for IoT accelerates the deployment of IoT even further.” IoT projects are complex and take a long time to implement. Customers find that choosing and connecting the right set of devices, assets or sensors to the cloud can be time-consuming. To jumpstart their IoT projects with confidence, customers are looking for certified devices and platforms that are tested for readiness, compatibility and usability with the Microsoft Azure IoT Suite. By choosing a partner from the Microsoft Azure Certified for IoT program, customers can save time and effort on project specs and RFP processes by knowing in advance what devices and offerings will work with the Azure IoT Suite. To learn more about Azure IoT Suite, click here. About Toradex Toradex is a Swiss based company with offices around the world, offering ARM based System on Modules (SOMs) and Customized SBCs. Powered by NXP®/Freescale i.MX 6, i.MX 7 & Vybrid, and NVIDIA ® Tegra processors, the pin compatible SOMs offer scalability in terms of price, performance, power consumption, and I/Os. Complemented with direct online sales and long-term product availability, Toradex offers direct premium support and ex-stock availability with local warehouses.

Added by Sonia Leal on August 12, 2011 at 5:33pm See Nucleus RTOS with fully integrated toolchain and UI running on the i.MX28 EVK.

Currently in industries from medical diagnostics and transportation to precision agriculture and entertainment, engineers are increasingly challenged to find new ways to design in greater intelligence, connectivity, and performance—while cutting costs, power consumption and size. Single Board Computers (SBC) are an ideal platform for quick and focused product design. They continue to evolve in sophistication, and the range of possibilities continues to expand as well. And as those capabilities grow, so do the choices for design engineers. But what are the factors that matter most in SBC evaluation and selection? http://www.digi.com/pdf/Design_vs_Build_web.pdf