Archive

Posts Tagged ‘samsung’

Samsung Exynos 7 ARM Cortex A57 Processor Linux Code Submitted

August 28th, 2014 2 comments

Samsung has not announced any 64-bit processor yet, but according to a recent patchset Exynos 7 may be their first 64-bit ARM SoC, and it will be based on the faster Cortex A57 cores. A quick way to learn a little more is to check the device tree file (exynos7.dtsi).

Samsung_Exynos_7Here’s an interesting snippet:

+	cpus {
+		#address-cells = ;
+		#size-cells = ;
+
+		cpu@0 {
+			device_type = "cpu";
+			compatible = "arm,cortex-a57", "arm,armv8";
+			reg = ;
+		};
+	};

As it stands, Exynos7 would be a single core Cortex A57 processor. This sounds unlikely that a company would launch a single core processor at this stage, so it’s probably early code that may not support all cores just yet.  We also now Samsung uses ESPRESSO board for development with Samsung Exynos 7 processor and 3 GB RAM.

Thanks to David for the tips.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Embedded Linux Conference Europe 2014 Schedule – IoT, ARM vs x86, Optimization, Power Management, Debugging…

August 21st, 2014 2 comments

The Embedded Linux Conference Europe (ELC 2014), CloudOpen, and LinuxCon Europe will jointly take place at the Congress Centre Düsseldorf, in Germany on October 13 – 15, 2014. The 3-day events will consists of keynotes, presentations, and tutorials. Each day will open with two or three keynotes by speakers including  Jim Zemlin (Executive Director, Linux Foundation), and Jono Bacon (XPRIZE), followed by presentation and tutorials. There will be 45 presentations for ELCE, 58 for LinuxCon, and 47 for CloudOpen, I’ll make a virtual schedule with a few sessions part of the Embedded Linux Conference Europe “track”.

ELCE_2014

Monday, October 13

When faced with a performance problem, the initial steps towards a solution include identifying the sections of code responsible and the precise reasons they are time-consuming. To this end, the ‘perf’ profiling tools provide valuable insight into the characteristics of a program. The presentation will show, using real-world examples, how the ‘perf’ tools can be used to pinpoint the parts of a program in need of optimization.

It’s not uncommon to produce embedded Linux based devices that end up with long and inconvenient boot times – yet eliminating boot time delays can be difficult and time consuming. Furthermore once a minimal boot time has been achieved it’s often just as difficult to maintain it through subsequent software development.

In this presentation, Andrew unfolds 12 keys lessons learned in his experience of boot time reduction. These lessons provide an insight into the common causes of boot time delays, why they are present and how they can be overcome. In describing these lessons Andrew will also take you on a journey that indicates why file system benchmarks should probably be ignored (with respect to boot time reduction) and a journey that illustrates that the Linux kernel is rarely the worst offender for boot delays.

With the introduction of Bluetooth Smart (aka Low Energy), the ubiquity of Bluetooth is more and more present. Millions of devices support Bluetooth Low Energy and with Bluetooth 4.1 specification, they are ready for the Internet of Things. This presentation will give an overview of Bluetooth Low Energy, and its usage for the Internet of Things. It will also introduce 6loWPAN over Bluetooth and show the possibilities this opens for Linux.

With experience developing community based open hardware for both the ARM based PandaBoard project and the x86 based MinnowBoard project, this presentation will provide a detailed comparison of the pros and cons of each platform with highlights of what each platform can learn from the other. Not only limited to the hardware aspect of the platforms, but also discuss community, software, corporate and general embedded aspects.

For almost as long as there have been deployments of Linux, there has been someone wondering “how can I get the device started quicker?” and “how do I configure some redundancy, easily, in case something goes wrong?”. And for the longest time, the answer has been “hack this and this and that” or “hire these consultants, they have done it before”. In this presentation, Tom will show what you need to turn on and the prep work required for, getting a lot of those items out of the box in U-Boot, what the hardware (and/or ROM) needs to do, and the what works is left going forward.

Got a question, comment, gripe, praise, or other communication for the Yocto Project and/or OpenEmbedded? Or maybe you’d just like to learn more about these projects and their influence on the world of embedded Linux? Feel free to join us for an informal BoF.

Tuesday, October 14

While user experiences are increasingly moving to 3D, rendering of 2D content remains at the core of how we interact with computer applications today. Skia is an open-source project maintained by Google whose goal is to bring the best 2D graphics library to a variety of targets, from mobile to desktop and embedded. Skia is used in highly popular projects like Mozilla Firefox, the Chromium browser and Android.

This talk will introduce Skia to developers and users, giving an overview of its design, architecture and features. It will also discuss briefly how hardware acceleration improves performance of Skia in the context of new devices, form-factors and the industry shift to mobile; with focus set on Linux and Android platforms.

The 4.4 KitKat release includes the results of “Project Svelte”: a set of tweaks to the operating system to make it run more easily on devices with around 512 MB RAM. This is especially important for people working with Android Wearables and “Embedded Android”, that is, implementing Android on devices at the lower end of the Android ecosystem. A large part of the problem is knowing how much RAM is really being used. Android offers a variety of tools for the purpose: procrank, procmem, meminfo and procstats, which Chris covers in the first part of the talk. In the second part, he takes a real-world example and show the practical steps you can take to optimize memory use including tuning the size of the Dalvik heap, enabling KSM (Kernel samepage merging) and swap to zRAM.

Android has relied from its early days on the Linux kernel for sandboxing the processes it runs. Yet, the permission model presented to app developers is significantly different from the Unix permission model. What’s the relationship between those two models? How is Android’s app security framework tied to the Linux kernel’s security model? More recently, Android has started using SELinux and has been extended by SEAndroid to support similar functionality. How is SELinux used by Android and what is SEAndroid about? Furthermore, how does Android provide support for multiple users?

This talk will explore Android’s security model in great detail and explain how the functionality found in the kernel is used to isolate user processes and the SE enhancements are leveraged by Android. As we’ll see, there are quite a few moving parts in Android’s security model.

Since last year, Free Electrons has been working on supporting the SoCs from Allwinner, a Chinese SoC vendor, in the mainline kernel. These SoCs are cheap, wide-spread, backed by a strong community and, until last year, only supported by an out-of-tree kernel. Through this talk, Maxime will share the status of this effort: the status a year ago, what solutions were in place, where we are currently, and what to expect from the future. He will also focus on the community around these SoCs, the work that is done there, etc.

Enlightenment Foundation Library is a set of libraries designed to use the full potential of any hardware to do great UI. It has been designed with the embedded devices in mind, but it is a desktop class toolkit. Being done in C, it is providing a stable API/ABI, high efficiency, low memory and low battery usage for all kind of Linux devices. Enabling development of modern UI adapted to any hardware that run Linux. These are the reason why Samsung uses it in its Tizen devices. This talk, after a short overview of what this libraries cover, will focus on this year improvement, and where it is heading. It will also be an opportunity to learn about project around EFL that will help people develop product with it. And it would also be a good opportunity to see where EFL are used with some real use case.

Wednesday, October 15

A major issue the community faces is the lack of power measurement (PM) instrumentation, coupled with poor integration: development boards not designed for it, expensive high-precision lab equipment not accessible to hobbyists (plus limited Linux support), limited low-cost solutions (precision, sampling rate) to monitor high-performance SoC (System On Chips) platforms (e.g. smartphones, tablets, IoT, …). After a brief introduction to the problematic (PM techniques, sense resistor / ADC selection, …) and a comparative study of existing solutions, this presentation will focus on a new upcoming initiative to close these gaps and bring a full-blown multi-channel but low-cost power (and temperature) measurement equipment to the community, including the definition of an open standard PM connector. After having covered motivations, challenges, key decisions, a live demo will close the talk.

In 2013, at the Embedded Linux Conference in Europe in Edinburgh, there was a race between a dog and a blimp. It was said that despite the dogs win, that the blimp had participated in the miracle of flight. In 2014, John wants to show that the brains of that dog can be transplanted and that it too, can participate in the miracle of flight. The talk is mainly targeting taking an off the shelf embedded platform, Minnowboard Max, and it’s use in UAVs, specifically quad-copters. With the ability to do real time computer vision, as well as various GPIO capabilities he will explore the directions that significantly more autonomous UAVs can take with Linux and embedded platforms using, mostly, off the shelf components.

There have been many presentations on what a device tree looks like and how to create a device tree. This talk instead examines how the Linux kernel uses a device tree. Topics include the kernel device tree framework, device creation, resource allocation, driver binding, and connecting objects. Troubleshooting will consider initialization, allocation, and binding ordering; kernel configuration; and driver problems.

Providing real-time capabilities to a general purpose operating system is an outstanding technical problem, and Linux Preempt-RT has been developed for 10 years for this goal. In this presentation, Jim proposes a lightweight open source para-virtualization layer, called “rtmux”, using resource-multiplexing techniques to provide a highly deterministic RT environment for Linux/ARM. Typically, less than 500 lines modification against Linux kernel are required to enable rtmux accompanied by POSIX/PSE51 compatible runtime.

During the last 2.5 years, a team of engineers at Free Electrons has been involved in mainlining the support for several ARM processors from Marvell, converting the not-so-great vendor-specific BSP into mainline quality code progressively merged upstream. This effort of several hundreds working days, has led to the integration of hundreds of patches in the kernel. Through this talk, Thomas will share some lessons learned regarding this mainlining effort, which could be useful to other engineers involved in ARM SoC support, as well as detail the steps Free Electrons engineers have gone through, the mistakes made and how they’ve been solved, as well as their overall experience on this project.

To make your own schedule matching your interests, you can check out the events’ program.

To attend the conference, you can register online.

The fees are listed as follows:

  • All-access Registration Fee – $600 until August 22 (tomorrow), $750 until October 2, and $850 afterwards
  • Attendee Networking Pass Registration – No access to conference sessions. $250 until August 22, $300 afterwards.
  • Student Registration Fee – $200 (valid student id required).
  • Registration Discount Scholar – $300. For active open source community members who can’t be sponsored by their company. .

Fees are significantly higher than last year, because there are only all-in-one (ELCE, CloudOpen and LinuxCon )options, and you can’t simply register to one single event.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Samsung Announces Exynos 5430 SoC, Manufactured with 20nm Process

August 14th, 2014 4 comments

Samsung already have a few octa-core big.LITTLE SoCs part of Exynos 5 Octa family with Exynos 5410, Exynos 5420, and Exynos 5422/5800, all based on 28nm process. The company has just announced a new Exynos 5 Octa processors with Exynos 5430, but this time manufactured using 20nm High-K Metal Gate (HKMG) process technology providing 25% less power consumption compared to 28nm Exynos SoCs.

Samsung_Exynos_5430

Exynos 5430 SoC will feature four ARM Cortex A15 cores at 1.8 GHz, four Cortex A7 cores at 1.3 GHz, supports WQHD (2560×1440) and WQXGA (2560 x 1600) displays using hibernation display and Mobile Image compression (MIC) in order to lower power consumption. It also said to support HDMI, come with a Multi Format Codec (MFC) supporting HEVC/H.265 decoding, as well as an enhanced dual ISP, and up to 17GB/s of memory bandwidth. That’s about all the information I could get at this point. The CPU core frequencies are lower than Exynos 5422, but the maximum memory bandwidth appears to be higher (17GB/s vs 14.9GB/s), and of course the power consumption is significantly lower. It will also be found in the recently announced Galaxy Alpha smartphone.

More details should eventually surface on Samsung Exynos 5430 page.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Linaro 14.07 Release with Linux Kernel 3.16 and Android 4.4

August 1st, 2014 No comments

Linaro 14.07 has just been released with Linux Kernel 3.16-rc6 (baseline), Linux Kernel 3.10.50 (LSK), and Android 4.4.4.

This month, Linaro has continued development on Juno 64-bit ARM development board, as well as other member boards from Broadcom (Capri), Qualcomm (IFC6410), Hisilicon D01, Samsung (Arndale / Arndale Octa), etc.. Android have been upgraded to version 4.4.4 with images released for Pandaboard, Arndale, Nexus 10, and Nexus 7, built with Linaro GCC 4.9.

Here are the highlights of this release:

  • Linux Linaro 3.16-rc6-2014.07 released
    • GATOR version 5.18 (same version as in 2014.04)
    • updated basic Capri board support from Broadcom LT. Good progress in upstreaming the code: now the topic has 21 patch on top of v3.16-rc4 vs 53 patches on top of v3.15 in 2014.06 cycle
    • removed cortex-strings-arm64 topic as the code is accepted into the mainline
    • new topic from Qualcomm LT to add IFC6410 board support
    • updated Versatile Express ARM64 support (FVP Base and Foundation models, Juno) from ARM LT. cpufreq support for Juno has been added.
    • updated Versatile Express patches from ARM LT
    • more HiP0x Cortex A15 family updates from HiSilicon LT
    • switched to mainline support for Arndale and Arndale-octa boards
    • updated llvm topic (follows the community llvmlinux-latest branch)
    • Big endian support (the 2014.05 topic version rebased to 3.16 kernel)
    • removed ftrace_audit topic as the code is accepted into the mainline
    • config fragments changes – added ifc6410.conf
  • Linaro Toolchain Binaries 2014.07 released – Based on GCC 4.9 and updated to latest Linaro TCWG releases:  Linaro GCC 4.9-2014.07 & Linaro binutils 2.24.0-2014.07
  • Linaro Android 14.07 released
    • built with Linaro GCC 4.9-2014.07
    • Pandaboard, Arndale, Nexus 10, Nexus 7 upgraded to Android 4.4.4.
    • LSK Engineering build moved back to 4.4.2.
    • Android LSK v3.14 CI loop added
  • Linaro OpenEmbedded 2014.07
    • Integrated Linaro GCC 4.9-2014.07
    • Integrated Linaro EGLIBC 2.19-2014.07
    • Integrated Linaro binutils 2.24.0-2014.07
    • Upstreaming:
      • fixes recipes related to oe-core autotools update
      • cleaned up overlayed recipes
      • updated PM QA to 0.4.12
  • Linaro Ubuntu 14.07 released
    • added gstreamer 1.0
    • updated packages: ARM trusted firmware (support latest FVP models), PM QA (0.4.12), LSK 3.10.49/3.14.13 and linux-linaro 3.16-rc6 kernels.
  • Integrate ARMv8 Big endian systems into LAVA and CI
  • Migrate Linaro Android builds to 4.9 Linaro toolchain
  • LSK: add ARMv8 kernel + arm32 rootfs CI loop
  • Package rt-app
  • LSK: enable member kernel configs for build testing

You can visit https://wiki.linaro.org/Cycles/1407/Release for a list of known issues, and further release details about the LEB, LMB (Linaro Member Builds), and community builds, as well as Android, Kernel, Graphics, Multimedia, Landing Team, Platform, Power management and Toolchain components.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Thread is a New IP-based Wireless Protocol Leveraging 6LoWPAN and 802.15.4 Standards

July 21st, 2014 2 comments

Wi-Fi is a neat way to connect devices to Internet, but it has two main inconveniences: relatively high cost and power consumption. Luckily there are standards that addresses the cost and power consumption issues. Radio chips based on IEEE 802.15.4, a standard which specifies the physical layer and media access control for low-rate wireless personal area networks, are common place and found in many existing devices relying on higher level wireless protocols such as ZigBee, ISA100.11a, WirelessHART, and MiWi. AFAIK, Zigbee is the most popular of the aforementioned protocols, but is hindered by the requirements of the license for commercial products (annual fee), Zigbee membership requirements conflict with many open source license such as GPL, and the standard suffers from lack of interoperability and IPv6 support, and power requirements that are too high for some applications. So a consortium of seven companies namely ARM, Big Ass Fans, Freescale, Nest, Samsung, Silicon Labs, and Yale Security, have come together to start working on “Thread”, a new wireless protocol leveraging 802.15.4 standard and existing transceiver chips,  that is legacy-free, and is based on 6LoWPAN (Low Power IPv6 connectivity), and UDP protocols.

 

Thread_Wireless_Protocol

Thread specifications are currently work in progress, but it will be a low power IP based open protocol supporting mesh networking (Up to 250 devices), that is both secure and user-friendly, and provides fast-time to market thanks to existing radio silicon. It will be used in various products such as electric appliances, access control, climate control, energy management, lighting, as well as safety and security devices. Two products companies are part of the group Nest and Big Ass Fans, so thermostats and fans based on Thread are likely to be available soon. Nest V2 actually comes with a 802.15.4 capable SoC (Ember EM357) that used to be disabled, but “is already being used successfully in Nest products today” thanks to a simple firmware upgrade, although I’m not sure if this is the case internally, or on customer’s premises.

The Thread Group is now looking for new members, and companies that are interested in Thread can join the consortium as a Sponsor (with more voting rights), or Contributor member. There’s no individual membership at this stage.

Via Semiwiki

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Google Releases Android Wear SDK, LG G Watch and Samsung Gear Live Smartwatches Are Now Available

June 26th, 2014 1 comment

I’ve just covered what’s new in Android L?, and I’m going to focus on Google I/O 2014′s announcements related by Android wear starting with hardware with LG G Watch ,and Samsung Gear smartwatches, followed by some details about the first official release of Android Wear SDK.

LG G Watch

LG_G_WatchSpecifications:

  • SoC – Qualcomm Snapdragon 400 @ 1.2 GHz
  • System Memory – 512MB RAM
  • Storage – 4GB eMMC
  • Display – 1.65” IPS display (280 x 280)
  • Connectivity – Bluetooth 4.0 LE
  • Sensors – 9-Axis (Gyro / Accelerometer / Compass)
  • IP Rating – IP67 dust and water resistant
  • Battery – Li-ion 400mAh
  • Dimensions – 37.9 x 46.5 x 9.95 mm
  • Weight – 62.5 grams

LG G watch will run Android Wear (as it’s the subject of this post), and it currently available on Google Play for $229 (US only?) with shipping scheduled for early July.

Samsung Gear Live

Samsung_Gear_LIveSpecifications:

  • Processor – Unnamed 1.2 GHz processor (Samsung Exynos?)
  • System Memory – 512MB RAM
  • Storage – 4GB Internal Memory
  • Display – 1.63” Super AMOLED (320 x 320)
  • Connectivity – Bluetooth 4.0 LE
  • Sensors – Accelerometer, Gyroscope, Compass, Heart rate monitor
  • IP Rating – IP67 dust and water resistant
  • Battery – Li-ion 300mAh
  • Dimensions – 37.9 x 56.4 x 8.9 mm
  • Weight – 59g

It looks similar to Samsung Gear 2 with Tizen, but this one runs Android Wear with Google Services, Google Now,  Google Voice, Google Maps & Navigation, Gmail, Hangouts, and you can recieve notification for SMS, E-mail, etc. It’s available for $199 on Google Play.

LG G Watch has a larger battery (33% more), a barely larger screen (1.65″ vs 1.63″0 but at lower resolution (280×280 vs 320×320), but the Samsung Gear Live features an Heart rate monitor which at first glance makes it a better deal.

If you’re wondering about Motorola’s Moto 360 rounded smartwatch, it will be available later. In the meantime, Android Community wrote an hands-on post.

Android Wear SDK and Apps.

Back in March, Google released Android Wear Developer Preview, and the company will release the first official release of the Android Wear SDK later today possibly via the Android L developer preview page, so developers can actually develop for Android (Wear) based wearables with a stable API to build user interfaces, control sensors, handle voice actions, and exchange data between phones and wearables.

Google also showcased a few apps optimized for Android Wear such as Eat24 that let’s you order food with your watch using a few swipes, and Lyft an leverages Google Now so that you can use a voice command to call a (ride-sharing) car, and rate the driver.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Meet Samsung Smart Bike fitted with an Arduino, a Rear Camera, Lasers and More

June 12th, 2014 1 comment

Samsung Maestros Academy has introduced a Smart Bike prototype integrating various “smart” components within its aluminum frame, such as an Arduino board connected to a Wi-Fi + Bluetooth module, a battery, four laser projectors, and a digital camera controlled by a Samsung smartphone.
Samsung_Smart_Bike

The camera is fitted at the back just under the seat, and allows the riders to have a real-time rear view image on the phone. The four lasers are used to create a virtual bike lane in case a real one is missing, and remind other drivers to keep a safe distance to your bicycle. The bike can also detect ambient conditions using the smartphone sensors, and modify its behavior. For example, it can switch on or off the laser beams depending on the brightness sensor data from the smartphone. Each bike also tracks daily routes of the riders using GPS, and can let local authorities know where bicycle traffic is most intense, and where they should build bike lanes.

For information is available on www.maestrosacademy.it/progetto-sbike.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter