Adam Outler · Apr 26, 2012 at 11:00 pm

The Galaxy S III S5E4412 Processor—A Hacker’s Overview

The Exynos 4412 processor, aka S5E4412, has been confirmed as the application processor for the Samsung Galaxy S III. After scouring the web for publicly available data sheets, best information listing I could come up with came from 8gpad. I’d like to take a minute and talk about the S5E4412 procssor.

Lets start by breaking down the model number.  S5= Samsung 5th generation processor.  E is an unknown, however this has traditionally stood for the packging type (PoP or BGA). 44 = Exynos 4th generation and 4 cores.  The 12 is unknown to me at this time, however I do believe it deals with the video capabilities and/or revision.  Please correct me in the comments below.

This Quad-Core CORTEX A9 processor supports NEON extensions as expected.  Unexpectedly though, while it is a 32 bit processor, this bad mama-jamma supports up to 128bits internally, which is double that of  the previous Exynos models.

For those of you “connected” individuals, you should be happy to know that the processor natively supports USB-OTG, USB-Host, and USB-Device modes.  Lets all just hope that Samsung does not let us down and forget to connect a 5V line to the USB driver chip.  The processor also supports up to 4 SD Cards. For those interested in communicating directly with the processor, this processor supports Samsung’s CORESIGHT debugger at 200 MHz and 1v.  4 UART ports, 8 i2c ports and 3 SPI ports.  It also has 64KB of IROM memory that is used to initialize the processor itself.

Personally, I think it’s time that Samsung took a hard look at their configuration issues.  Given the hardware above, the features of the device could greatly be expanded with only a small change to their standard operating procedures  seen previously. I’d like to see some changes to the boot sequence.  More specifically, in that 64KB of IROM memory, there is a set of instructions which lets the device boot directly from USB.  This needs to be accessible somehow for those emergencies we at XDA-Developers have every day.  Why this is kept locked down, I will never understand.  The device should be easily revived in case of emergency, and its well within the capabilities of the device. xOM5 modification please.

Here’s hoping Samsung uses their own hardware the way it’s designed to be used!


_________
Want something on the XDA Portal? Send us a tip!
Mario Tomás Serrafero · Feb 28, 2015 at 03:45 pm · no comments

MWC 2015: What Are Your Predictions?

This wonderful Geek-Christmas time of the year is back once more, promising a lot of exciting reveals from big manufacturers such as HTC and Samsung, but also some pretty gems teased by other smaller OEMs. What kind of exciting products will we see? While we've got a lot of leaked information from the highly expected S6 and M9, there is still a lot to learn about both - and about everything else that will be shown. What kind of trends will...

XDA NEWS
Chris Gilliam · Feb 28, 2015 at 03:13 pm · 1 comment

Best Apps To View RAW Images On Android

Last week, I wrote about the best apps to unleash the raw photographic power of your Lollipop smartphone. All four of those cameras generate lossless DNG images with pounds of potential for apps like Photoshop to unlock, but what if you’re looking to edit or view those pics on the go? QuickPic, Google Photos, and the other mainstays treat raw images like they don't exist. This rundown seeks to fill the void and give you full control over your precious pictures....

XDA NEWS
Emil Kako · Feb 28, 2015 at 10:15 am · 1 comment

Which App Is Most Desperately in Need of an Update?

While the majority of the top apps have already incorporated Google's newest design language, there are still very many apps that are in need of some Material Design love. Which apps do you think are most desperately in need of an update?

DISCUSS
Share This